Close event registration and preserve the final roster

Define the cut-off and roster-freeze times

For example, close registration at 18:00 on Friday and freeze the printable roster at 19:00. The intervening hour is an organiser’s reconciliation window, not a technical requirement. Use the same time zone on the announcement, form and internal checklist. A submission’s arrival in a connected table may differ from its original acceptance time. Decide which timestamp establishes eligibility before you close registration, and do not delete a delayed integration record merely because its destination timestamp falls after the public deadline.

Use form closing controls for intake

Tally documents manual closing, scheduled closing, submission limits and a custom closed-form message. Configure the organiser’s deadline and make the closed message explain where late enquiries or the next session belong. A limit on submissions is not automatically a limit on people if one response contains a party of several attendees. Keep capacity management separate from a time-based cut-off. Test a form that was opened before the deadline but submitted afterwards, and inspect the actual respondent experience rather than assuming an open browser page grants a place.

Create an identifiable roster version

Record an event ID, session, frozen-at time, owner, registration count and attendee count for each roster version. Preserve source submission IDs and the reasons for excluding cancellations or duplicates. Export only columns needed for the day; private free-text answers and contact details often do not belong on a reception printout. Label printed copies with a version too. A filtered Airtable view remains a view of changing records, so decide whether staff need a fixed snapshot, a current operational list or both. Do not confuse a saved filter with an immutable roster.

Keep post-freeze changes as a delta

After the freeze, record approved additions and cancellations in a change register rather than silently replacing the roster. Include change ID, original submission, add or cancel, approver and the time reception was informed. If distributing a new version, retire old copies or specify how they must be used with the delta sheet. A receptionist holding paper and another using a live list need a shared rule about the authoritative state. A late enquiry is not an approved addition until capacity and the organiser’s acceptance conditions have been checked.

Reconcile delayed or failed integrations

When a last-minute submission is absent from the roster table, compare source IDs, destination IDs and failed-run history. Matching totals are insufficient: one duplicated record can conceal one missing record. Resume a failed transfer by checking existing identifiers before inserting anything. Reconcile time zones as well as display formats. Airtable’s automation documentation explains that date handling can differ from a field’s displayed time zone; use controlled records immediately before and after the cut-off to test the exact eligibility rule your workflow applies.

Set an owner before buying more automation

A small one-off workshop may need only native form closing, manual reconciliation and a labelled CSV. Consider integrations when daily rosters or several venues make that work burdensome. Assess run frequency, collaborators and retained history, not submission volume alone. Automatic file generation does not solve a receptionist continuing to use yesterday’s copy. Name the roster owner and the person who confirms receipt of the final version first. This clarifies whether the remaining problem is data transfer, communication or an actual requirement for a more capable event platform.

Test the boundary and the final handoff

Test submissions before and after the cut-off, an interrupted integration, a late cancellation and an approved addition. Reconcile counts, people and original IDs, then verify that a person holding an older version receives the relevant changes. Check the closed form for confusing routes that encourage duplicate registrations. Use the related waitlist guide for promotions and the attendance guide for arrival records. This workflow is complete when reception has the agreed roster and applicable changes, not merely when an organiser sees that the form has stopped accepting responses.

• Collect workshop applications with Tally
• Track event attendance in Airtable
• Manage event registration and a waitlist with Make