Debrief while the detail is still recoverable
Hold the internal debrief within a few days, before the run sheets, radio logs, incident notes and vendor invoices become archaeology. A later, tidier meeting will produce a cleaner narrative and fewer usable facts. If the full group cannot meet quickly, collect written accounts quickly and meet later.
Keep three accounts separate
For each service and each incident, record what the organizer observed, what the provider or vendor reported, and what the attendee or delegate reported, as three distinct entries. Resist reconciling them in the room. A captioner who reports a clean feed, a floor lead who reports no problems, and an attendee who reports twenty minutes of unreadable text are all describing something real, and the gap between them is usually the actual finding.
- Organizer observation, with the role and time it was made
- Provider or vendor attestation, in the provider's own terms
- Attendee or delegate report, including anything raised onsite
- Incident log entries with the action taken and by whom
- Discrepancies left open rather than resolved by consensus
Review the numbers you set before the event, not the ones that look good
Compare against the targets that existed beforehand: registered versus attended, no-show rate, session attendance against room capacity, guarantee versus actual covers, budget versus final invoices including the service charge and tax lines, response time on requests against the published target, and the count of services delivered against services planned. Picking metrics after the fact produces a report that always passes.
Ask the accessibility questions specifically
Accessibility outcomes rarely surface in a general debrief because the people affected are not usually in the room. Ask them as their own block: did every accepted request receive a plan, was each plan confirmed by the requester before the event, did any service start late or fail, were accessible materials available when the session started, did room or schedule changes invalidate a plan, and did anyone have to ask twice. Record answers per service, not per event.
- Requests received, accepted, planned and confirmed, as four counts
- Services delivered on time, delivered late, degraded, or missed
- Requester-reported outcomes, kept distinct from provider reports
- Plans invalidated by an agenda, room or platform change
- Anything an attendee had to escalate to get delivered
Every finding becomes a change to a document
A finding with no artifact attached will not survive the year. Push each one into the thing that will be read next time: a line on the run of show, a field on the registration form, a clause in the venue contract or RFP, a lead time in the provider brief, a step in the day-of checklist, a date in the planning timeline. Name the owner and the date the change is due, and check it at the start of the next event's planning rather than at the next debrief.
Write the post-event report from the debrief, not instead of it
The report a client, board or sponsor reads is a summary of the record, not a replacement for it. Keep it short and let it carry the delivered scope, the attendance and financial actuals against plan, the incidents and how they were closed, the outstanding items with owners and dates, and the recommendations. Strip attendee-identifying detail before it circulates: accommodation outcomes belong in the report as counts and service facts, not as named cases.
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
How soon after the event should the debrief happen?
Within a few days, while run sheets, radio logs and incident notes are still fresh and the vendor invoices have not yet replaced people's memory of what actually happened. Speed matters more than attendance.
What is the difference between a debrief and a post-event report?
The debrief is the internal working session that produces the record: separate accounts, open discrepancies and assigned fixes. The post-event report is the summary written from that record for a client, board or sponsor. Writing the report without holding the debrief produces a narrative with nothing behind it.
Who should be in the room?
The people who were on the floor. Production, registration, venue liaison, the accessibility or accommodation owner, and whoever handled escalations. A debrief attended only by managers will produce findings only about the things managers saw.
What should be excluded from a circulated report?
Attendee names, diagnoses, and request narratives. Accessibility outcomes belong in a shared report as counts, service facts and dated actions. Keep the identified detail in the private case record and apply your retention rules to it.
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.
- Cornell University - Accessible meeting and event checklist Public checklist covering the participation and communication items worth reviewing after an event.
- ADA.gov - ADA requirements: effective communication Federal guidance on effective communication obligations, useful when reviewing whether a delivered service met its purpose.