Event Accessibility Requests: A Triage and Fulfilment Workflow

An event accessibility request workflow is the controlled path from a fan asking for an adjustment or service to the right team accepting, delivering and verifying it. It should minimise repeated disclosure, protect personal information and keep the fan informed without treating every request as identical.

The inbox is not the workflow. A request can be acknowledged quickly and still fail at the ticketing, venue, supplier or front-line handoff. The operational test is whether the promised support appears at the right time and place.

This is a planning framework, not legal advice. Duties vary by jurisdiction, organisation and event. Consult disabled people, qualified access professionals and applicable advisers when setting policy.

What should an event accessibility request process include?

Provide one discoverable contact route; ask only for information needed to understand the barrier and requested outcome; classify urgency and dependencies; assign one accountable owner; agree the action with the fan; share only the minimum operational instruction; confirm changes; and verify delivery at the event.

The fan should not become the integration layer between ticketing, venue operations and suppliers.

Build one Request-to-Receipt chain

The Request-to-Receipt chain is a WENOTIFT operating model. It makes ownership visible; it does not decide whether a particular adjustment is legally required.

Make the request route easy to find and use

Publish the contact method beside ticket and venue-access information, not only in a policy footer. Offer a practical alternative when one channel creates a barrier. State what information helps, expected response times, how urgent requests are handled and what happens after submission.

The US Department of Justice's effective-communication guidance explains that the appropriate aid or service depends on the nature, length, complexity and context of the communication and the person's usual method. It also says reasonable advance notice may be requested where acquisition takes time, but excessive notice should not become a barrier; walk-in requests should be met where possible.

Do not frame an internal cut-off as proof that a later request is invalid. Instead explain which services need lead time, what can still be attempted and who can make an event-day decision.

Triage the outcome, not a diagnosis

Start with the participation barrier and requested result: step-free arrival, an accessible seat, captioning, an interpreter, a quiet-space route, medication storage, assistance at entry or another event-specific need. Ask follow-up questions only when they change delivery.

Separate four decisions:

1. Information: can existing accurate information resolve the question?
2. Allocation: does the request need an inventory, seat or time-slot decision?
3. Service: must a trained person, supplier or piece of equipment be arranged?
4. Exception: does the request expose a conflict, safety dependency or unplanned barrier needing senior authority?

Do not ask a fan to send broad medical records to prove an operational requirement unless applicable law and qualified advice establish a necessary, proportionate basis. Limit access to request information and define retention before collection.

Assign two kinds of ownership

The case owner communicates with the fan and maintains the complete picture. The delivery owner controls the actual action: ticketing changes the seat, production books captioning, transport confirms drop-off or venue operations briefs the entrance team.

One person may hold both roles on a small event. The distinction still matters because “we replied” and “we delivered” are different states. Record owner, action, due time, evidence and escalation route for each commitment.

Connect public expectations to WENOTIFT's venue accessibility information guide. If requests repeatedly contradict the published page, update the page or the operation; do not normalise case-by-case repair.

Use a triage matrix without flattening people

Priority should reflect delivery lead time, event proximity and consequence of failure—not assumptions about whose disability is more important.

Agree substitutions with the fan

An internal team may see two arrangements as equivalent when they are not usable in the same way. The DOJ guidance says US public entities must give primary consideration to the person's requested aid or service, subject to defined limitations, and encourages covered businesses to consult the person about what is effective. That legal detail is jurisdiction-specific, but the operational lesson travels: do not quietly replace the requested outcome.

Describe the proposed arrangement precisely, including location, timing, collection point, companion implications and any action the fan must take. Ask whether it addresses the barrier. If it does not, return to the decision owner rather than closing the case because a resource was booked.

For assigned seating in the United States, the DOJ's accessible-ticketing guidance requires accessible tickets to be sold through the same methods and stages as other tickets and described with enough detail for purchasers to assess fit. Treat a separate request channel as coordination support, not a slower substitute for an equal sales route.

Hand off instructions, not the whole case history

Front-line staff need the action, location, time, contact and exception route. They rarely need the fan's full correspondence. Convert the agreed plan into a concise service instruction and restrict the underlying record to authorised people.

Use role-based views: ticketing sees the allocation; access staff see the meeting point and service; security sees the approved entry instruction; a supplier sees the booked specification. Keep one case reference across those views without putting sensitive detail on a public radio channel or printed list.

Verify before the fan arrives

Run a readiness check far enough before doors to recover missing resources. Confirm the booking, route, staff brief, equipment, seat or service point against current event conditions. If the plan changes, the case owner contacts the fan through the agreed channel and updates every affected handoff.

At delivery, use a discreet receipt signal: collected, met, seated, service started or exception escalated. Do not require the fan to provide a satisfaction statement while they are trying to enter. Afterwards, invite feedback through an accessible channel and distinguish service receipt from service quality.

Link physical route changes to the accessible-route recovery framework and hospitality allocations to the companion-ticket planning guide.

Measure the workflow without scoring disabled people

Track acknowledgement time, time to named ownership, overdue actions, repeated disclosures, late substitutions, event-day exceptions and failures found by readiness checks. Review recurring barriers by channel, venue, supplier and process stage.

Avoid publishing a single “requests fulfilled” percentage without context. A fast closure may hide an unusable substitute, and complex requests may reasonably take longer. Pair timeliness with evidence of agreed action and actual receipt.

A practical readiness review

Before opening sales or announcing the request route, ask:

• Can a fan find and use the route without searching a policy archive?
• Is every open request attached to a named case owner and delivery owner?
• Are only necessary details collected and shared?
• Does the fan know what has been agreed, when and where?
• Can event-day staff retrieve the instruction without exposing private history?
• Who can approve a change, alternative or exception before doors?

If one answer is unclear, the request is acknowledged but not yet controlled.

Sources

• US Department of Justice: ADA Requirements—Effective Communication
• US Department of Justice: ADA Requirements—Ticket Sales
• UK Government: Disability quick start guide for service providers