What makes this checklist different
Accessibility is not a single pre-event checkbox. A request may depend on clarification, a human organizer decision, a provider, a room setup, accessible materials, an onsite owner, and confirmation from the attendee. The checklist keeps those facts separate.
- A named accessibility contact and response expectation
- Request cutoff, provider lead time, and cancellation dates
- Minimum-necessary handoffs for providers and onsite staff
- A requester confirmation step after the plan is assembled
- Delivery evidence, incident follow-up, and retention-aware closeout
Use it before registration opens
Start while event dates, venues, and registration copy are still editable. That is when teams can set realistic response targets, verify communication-access lead times, identify room and technology dependencies, and give attendees a clear request path.
Use it again at each operational handoff
Review the same checklist when registration opens, at the request cutoff, before provider cancellation windows, during the final readiness review, and after the event. Each review should produce an owner and a dated next action—not a vague status.
Build the timeline backwards from event day
Start with doors open, then work backwards through room access, technical tests, provider arrival, material delivery, attendee instructions, requester confirmation, purchasing approval, provider availability, request clarification, and the public response date. Record both the internal target and any external cancellation or change deadline. Every checkpoint needs a named owner, a required artifact, and an escalation path.
- Event day, doors-open time, and session-level service windows
- Final requester-plan review before provider cancellation dates
- Provider acknowledgement, purchase approval, and technical-test dates
- Accessible-material deadlines tied to speaker and production schedules
- Registration launch, response target, and planning-date language
Review readiness service by service
Do not mark the event accessible because a single top-level checklist is green. Review each accepted request and each planned service separately. For every service, confirm the event context, owner, provider or internal team, room or platform, equipment, materials, attendee instructions, fallback, and evidence expected at closeout. Shared services can support several attendees, but the private request records and confirmations must remain distinct.
Finish with evidence, not memory
After the event, record what the provider reports, what the organizer observed, what the requester reports, and any incident or discrepancy as separate facts. Resolve open work, append corrections with an actor and reason, remove unnecessary sensitive exports, and retain only the approved record. Strip attendee-specific information from reusable venue or provider notes.
Keep decisions human and evidence explicit
Evencue records decisions made by authorized organizers and coordinates their event-specific consequences. It does not determine legal reasonableness, medical validity, entitlement, or venue certification. Provider and onsite views receive only the information required for their task.
What teams usually ask
When should event accessibility planning begin?
Begin before registration opens. Provider availability, accessible materials, room setup, and attendee communication all become harder to change close to the event.
Does this checklist decide which requests are reasonable?
No. It organizes operational work after authorized people review a request. It does not make legal, medical, or entitlement decisions.
Can I use the checklist without an Evencue account?
Yes. The checklist works in the browser without registration and can be printed or saved as a PDF.
What informed this page
Reviewed July 31, 2026. These sources establish organizer responsibilities and operational context; Evencue’s workflow recommendations remain product guidance, not legal or medical advice.
- USC — Event planner responsibility Organizer responsibility, request channels, coordination, and advance planning.
- UC Berkeley — Planning disability access and accommodations Coordinator ownership, event context, timely response, and institutional knowledge.