A post-event debrief should explain how the operation worked from setup to departure and identify practical changes for the next event. Use the run sheet, operational records and staff observations rather than relying only on the closing impression that the day went well.
Keep formal incident, safety, complaint or other required processes separate and active. A later debrief is not a reason to postpone them or decide their findings informally.
Reconstruct the operational sequence
Review setup, briefing, arrivals, program delivery, transitions, guest departure and pack-down as applicable. Compare planned and actual timings while checking the dependencies behind a delay or change.
Redland City Council’s event-planning tools include debrief resources and run-sheet guidance. Use the actual event records and responsible people when preparing the review.
Include different operational perspectives. Arrival staff may have information about a queue that the facilitator never saw, while the venue contact may identify a handover issue after guests left.
Use a practical event-review agenda
Ask:
- Setup: were the approved areas and resources ready before their dependent activities?
- Briefing: did staff have current role information and contacts?
- Arrival: could guests find the correct route and obtain needed assistance?
- Program: which transitions or dependencies required changes?
- Departure: were guest information and operational handovers clear?
- Pack-down: were responsibilities and completion checks understood?
- Follow-up: which matters need another process or an owned improvement?
Record observed facts and uncertainty. A long queue does not by itself establish whether the cause was registration, timing, signage or another factor.
A fictional arrival problem
In this original invented workshop, guests begin arriving before the welcome desk has the current attendee information. Staff can identify the approved arrival time, the time information became available and the effect on enquiries.
The debrief confirms that the information handover was scheduled too close to guest arrival. The agreed action is for the coordinator to check the current approved material with the desk lead before the next arrival period begins.
The team does not describe the problem simply as staff being slow. It identifies a dependency that can be changed and checked.
Record decisions and owners
For each improvement, state the action, responsible person, required approval and review point. Distinguish an idea from an approved change to the next event’s process.
Keep sensitive guest or staff information in the proper restricted record. A general debrief can reference a separate case without repeating personal details or attempting to settle an allegation.
Preserve useful practices too. If a particular handover or communication worked, record the conditions that made it effective so the next team can apply it appropriately.
Check the improvement before reusing the plan
Update the run sheet, briefing pack or other controlled document through its owner. Test the changed dependency at the next suitable opportunity and compare the relevant outcome.
Retain the event context, because a method suited to a small indoor workshop may need different arrangements elsewhere. A useful debrief leaves the next operation with clearer responsibilities and a traceable improvement, rather than a list of comments that never reaches the planning documents.
Our guide to event work and responsibilities can help place the operational feedback in context without treating one event’s arrangements as universal.
