An Airtable cohort project portal can connect teams, project milestones and successive submissions so adult participants know what to deliver and mentors know what to review. miniExtensions supplies the participant-facing records; the program team maintains membership, deadlines and the review process.
The fictional Harbor Design Fellowship asks adult learners to develop a community wayfinding concept in small teams. The goal is coordinated group work, not individual grading or a full learning-management system. Use fictional materials when prototyping and keep confidential client work out of the example.
For individual assignments rather than shared team work, start with the adult learner submission guide. Here, staff must additionally maintain shared participant scope and choose which team version is authoritative. Created time records record creation; if draft saving is added, use a separately verified submission-time mechanism rather than treating draft creation as deadline evidence.
Organize work around the team’s milestone
A team project differs from an individual assignment because several people share one outcome. If every participant creates a separate copy of the deliverable, mentors may review the wrong file and teammates may receive different feedback. Give each milestone one authoritative record and preserve versions beneath it.
Team Harbor’s first milestone is a concept board; the second is a revised route map. The concept board can be submitted, reviewed and returned for revision without marking the whole project complete. Keep membership administration separate from the work itself.
Designate one submission lead as an operational convention initially. This convention does not automatically restrict editing to that person: the shared participant link controls record scope, not a lead-only editing role. In the simplest shared-team setup, agree who submits and have staff reconcile competing versions. If lead-only submission is essential, configure and verify a separate restricted route before launch. This design does not promise simultaneous document collaboration or conflict-free editing.
Create linked teams, milestones and submissions
- Participants: Name as primary text, Email as email and Cohort label as text.
- Teams: Team name as primary text, Members as multiple links to Participants, Project brief as long text and Mentor name as text.
- Milestones: Milestone reference as primary text; Team and Visible participants as links; Deliverable instructions as long text; Due date as date; Milestone state as single select; Current submission as a link to Submissions.
- Submissions: Submission reference as primary text; Milestone and Team as links; Submitted by and Visible participants as links to Participants; Version label as text; Work files as attachment; Author note as long text; Submitted at as created time; Review state as single select; Participant-facing feedback as long text.
Visible participants is a direct multi-record link to the Participants table, maintained by staff for each displayed record. The proposed design does not assume that linking a milestone to a team automatically synchronizes access for all members. Staff updates these explicit links when membership changes, or separately designs and tests a synchronization process.
Use stable milestone references such as HARBOR-M1. A filename alone is a poor identifier: “final.pdf” may describe several submissions. Put Version label and Submitted at beside each file so the mentor can distinguish the material under review.
Configure team scope deliberately
Build the direct participant links first and follow the Users Table setup. Use Personal records only for participant-facing views, based on those links. Choose suitable authentication using the login guide.
Keep mentor-only deliberations outside participant-facing fields. The shared feedback field should contain only what the whole team is meant to read. An individual coaching comment belongs elsewhere, with separately verified access, not on a shared submission.
Test nested selectors and existing linked values too. A participant who sees only Team Harbor’s milestones must not be able to select another team’s submission, inspect its attachment or relink a record to gain access. Keep membership and access fields out of participant editing.
Run a submission through review and revision
The program coordinator creates the milestones and assigns the visible participants. The submission lead uploads the concept board, adds a short author note and identifies which milestone it addresses. Staff verifies the saved relationships before moving the milestone into review.
The mentor opens that specific version and writes actionable feedback: “Show how visitors reach the entrance from the east path.” They mark it Revision requested rather than Accepted. Participants can now tell what needs work without interpreting a comment as approval.
The lead submits version two as a new record. Staff changes Current submission only after verifying the file and milestone. Version one remains visible as history where appropriate. Mentors should review the designated current version, not simply the last file that happens to be attached.
Protect history and handle team changes
Use the per-view editing controls for completed submissions, and review every alternative editing and unlinking path. This preserves practical history only when the configuration supports it; it is not an immutable submission ledger.
When a participant changes teams, staff reviews current and historical access deliberately. Decide whether the person should retain access to their former team’s past work, then update the direct participant links accordingly. Changing a Team field by itself is not proof that every related record’s access changed.
If two members submit conflicting versions, do not delete one as a duplicate based on its filename. Ask the team which version represents the agreed submission, record that choice and keep the other as superseded if retention is appropriate. The portal organizes the decision; it does not resolve authorship disputes.
Check the complete team experience
Use two fictional teams with at least two participants each. Try reading shared work, submitting a new version, opening old feedback and switching a member between teams. Check the current submission pointer and direct links in Airtable after reload.
Include a participant who belongs to two teams and one who has no team. The expected result should be explicit in each case. Test that mentors’ private notes and unrelated teams’ files remain outside every participant route, including previews and expanded records.
These are recommended acceptance checks, not a tested implementation. The workflow is useful when a cohort needs a shared deliverable trail with human review. Scheduling, live collaboration, grading, plagiarism checks and credential issuance require separate processes. The intended benefit is simple: everyone can identify the next milestone, the submitted version and the feedback that applies to it.


