Use Airtable and a miniExtensions Portal to give adult workshop attendees a clear prework checklist, collect their files or notes, and let a trainer review what still needs attention. Track each attendee’s assigned preparation items separately so a shared instruction does not become a shared completion record.

This is a preparation workflow, not a certification system. Opening an instruction, uploading a file, or checking a box does not prove that an attendee understands the material. The trainer still decides whether the submission is sufficient for the workshop’s practical activities.

Start with a specific readiness outcome

For a fictional data-visualization workshop, attendees need to install a permitted practice tool, review a sample dataset, and bring a short question they want to explore. Priya has completed the dataset exercise but has a question about the installation instructions. Leo has not yet uploaded an exercise file. The trainer needs to distinguish those situations before the session rather than discovering them at the door.

A useful readiness view shows the attendee, the exact item, the submitted evidence, the trainer’s feedback, and the next action. Do not collapse all three preparation requirements into one “Ready” checkbox unless someone has actually reviewed what it means.

Model the assignment separately from the instruction

  • Attendees: Name as primary single line text and Email as email.
  • Workshops: Workshop name as primary single line text, Session date as date, and Trainer as collaborator.
  • Preparation Items: Item name as primary single line text, Workshop as linked record to Workshops, Instructions as long text, Resource URL as URL, and Reference file as attachment.
  • Attendee Prework: Assignment as primary single line text, Attendee as linked record to Attendees, Workshop as linked record to Workshops, Preparation item as linked record to Preparation Items, Due date as date, Submission as attachment, Attendee notes as long text, Review status as single select, and Trainer feedback as long text.

Use statuses such as Assigned, Submitted, Needs an update, and Reviewed. A coordinator creates one Attendee Prework record per person per required item, linking the appropriate instructions. Creating three shared Preparation Items is not the same as creating the six attendee assignments needed for two people. In this baseline, assignment creation and status changes are manual.

Give attendees a focused prework portal

Select Attendee Prework as the Portal Data Table and Attendee as the User Field. Its direct link to the login table matters; linking only to a workshop would not identify the attendee. Follow the users-table setup and configure email verification for the attendee email field.

In each assignment view, use the Personal records only setting so attendees see their own work. Show the assignment, due date, instructions, trainer feedback, and submission fields. Keep review decisions and assignment ownership staff-controlled; let the attendee edit only Submission and Attendee notes in this example.

A linked instruction can be opened without letting the attendee change the shared source. Configure the child form as read-only and prevent changes to which preparation record is linked, following the linked-record permission guide. The parent relationship and the child form’s fields are separate controls; verify both.

Use the opening requirement for the right purpose

If attendees should open each linked instruction before submitting, open that linked field under Form Fields, enable expansion in Creating and Editing Records, then enable Require users to open linked records. The documentation describes a red indicator removed when a record is opened. The rule covers records currently displayed in the field.

Treat this as a navigation requirement, not a reading receipt or skills assessment. Put any genuine readiness check into the workflow explicitly: for example, ask for a small practice output, then have the trainer review it. Do not label a person qualified merely because the red indicators disappeared.

Make review and revision visible

Priya uploads her sample chart and notes that the dataset loaded successfully. The trainer checks the file, sets the assignment to Reviewed, and writes feedback. Leo uploads the wrong exercise file; the trainer selects Needs an update and explains which exercise is missing. Keeping feedback on the assignment helps each person correct the specific item instead of resubmitting an entire registration.

Use staff Airtable views filtered to Submitted and Needs an update to organize review. A workshop-level summary may help planning, but keep it separate from individual evidence. A person can be ready for the dataset exercise while still needing help with installation.

Run a small readiness check before launch

  • Create two test attendees with different assignment records and email addresses you control. Verify their record sets stay separate.
  • Open the linked preparation instructions and confirm that neither the relationship nor the shared instruction text can be changed by an attendee.
  • Try submitting with an unopened linked item, then open it and repeat. Verify actual behavior in the published test form rather than assuming the toggle is sufficient.
  • Upload a harmless sample file, save, reload, and verify the trainer sees the same attachment and attendee note.
  • Return one item for revision and confirm that the attendee sees the feedback but cannot mark their own review as complete.

Keep preparation distinct from attendance and accreditation

The result is a practical list of who needs which preparation step, not proof of attendance or a formal learning-management record. Use your attendance process during the session and your assessment process afterward. The attendance correction workflow addresses a different problem: correcting a session record after the fact. Keeping these records separate makes both easier to interpret.