Route event accessibility requests to the right organiser

Ask about the arrangement required

Ask what arrangement the person wishes to discuss, their preferred contact method and when they need an answer. Focus on participation needs rather than broadly collecting diagnoses or detailed personal histories. Provide a route to discuss the request with an organiser instead of requiring every detail in an open text box. Make clear that a submission begins a conversation and is not an automatic promise that every request can be fulfilled. The actual arrangement depends on the venue and event; a form cannot establish that a room or service is accessible in practice.

Separate the private case from the roster

Link a private case register to the general booking using a registration ID. Useful fields include arrangement category, owner, preferred contact, response deadline, agreed action and confirmed-at time. Reception does not need a verbatim copy of the conversation. Give venue staff preparation instructions and reception staff the relevant arrival guidance. Check Airtable’s actual access model when using it: hiding a column in a convenient view is not the same thing as enforcing access restrictions. Choose a location for the private case that matches the people who should be able to read it.

Verify what can be delivered at the venue

Check current venue conditions with the responsible venue contact for requests involving steps, entrances, aisles, listening support or seating. A feature may exist but be unavailable on the day, or another activity may alter the route. Record who confirmed the arrangement and when, then align the attendee response with that evidence. Describe what is agreed and what still needs discussion instead of an ambiguous we can accommodate. Do not mark the case resolved simply because a checkbox was selected; completion requires an arrangement that the organiser and relevant staff can actually deliver.

Keep notification messages minimal

A notification can contain only the registration reference, review deadline and an appropriate internal link. If conditional routing chooses a recipient, test unset and unexpected categories so a private request is not sent to a broad distribution list. Tally supports dynamic recipients and message content, but that does not require including every form answer. Reducing copied detail also makes later access cleanup easier when staff change. Record assignment separately from sending a notification: a message arriving at an address does not establish that someone accepted responsibility for reviewing and answering the case.

Reconcile attendee agreement and day-of instructions

Turn the agreed arrangement into a concrete assignment: who prepares what, by when, and who covers an absence. Meeting at an entrance, a seating layout or lending equipment should become concise operational instructions that a replacement organiser can understand. Tell the attendee the agreed plan and day-of contact, including how changes will be communicated. Keep personal discussion out of general handouts. Before the event, review unresolved cases for mismatches such as prepared but not answered, or answered but not handed to venue staff. Those are different recovery tasks and should remain visible.

Use a proportionate private workflow

A small number of requests can be managed through an existing private contact channel and a restricted register. Before adding another integration, establish access, review deadlines and cover for an absent organiser. Evaluate collaboration access, notification features and retention work as well as subscription price. Do not let an automated category decide the arrangement on its own; unclear answers need a human conversation. A template can prevent missing an ownership or handoff field, but it does not replace checking the venue or reaching agreement with the attendee. Buy additional tooling only for a defined operational need.

Test access and absence cases

Use fictional requests to test an unset category, absent owner, pending venue check, a changed arrangement, cancellation and roster export. Verify that private discussion does not appear in broad notifications or exported attendance sheets and that access restrictions work for the actual lower-permission user. Completion means the agreed arrangement matches the day-of assignment, with an owner for any uncertainty. The related registration, conditional-form and attendance guides support adjacent tasks. Keep the private review separate even when all of those records share the same registration reference.

• Collect workshop applications with Tally
• Set up Tally conditional logic: visibility, required answers and changing choices
• Track event attendance in Airtable