The debrief is what closes the loop on the event. Without it, the event happened; with it, the team learned something the next event can use.
Why debriefs matter
Most safeguarding incidents come from drift — small things that worked at one event, didn’t work this time, weren’t noticed, became normal. The debrief is the team’s practical defense against drift: a structured opportunity to surface what was different from plan, what almost went wrong, and what the implications are for the next event.
Timing
Debriefs typically happen within a week or two of the event. Earlier than that, the team is still recovering and not in reflective mode. Later than that, the details have softened and the urgency has gone. Some teams hold a quick debrief immediately after for operational items and a full debrief a week later for learning.
Who participates
The full event team, ideally. Coordinators across functions. Sometimes, external participants (the venue, contractors, host families). Sometimes, attendees themselves, where the event involved a group with an ongoing relationship to the organization.
Two questions running in parallel
The debrief asks two questions:
- Was the planning fit for purpose?
- Was the event itself fit for purpose?
The first measures against the strategic, operational, and universal criteria the team set during planning — did the plan hold up? Where did it fall short? The second measures against objectives — did the event achieve what it was for? Where did it succeed, where did it struggle? These are different questions because a good plan can fail in execution and a bad plan can luck out. Surfacing them separately keeps the team honest about each.
Allegations and concerns
The debrief explicitly asks whether any allegations of misconduct or policy violations surfaced during the event. This isn’t the place to investigate them — the Incident Response system handles that. The debrief captures whether anything happened so the planning record is complete.
Root causes
When something went well or poorly, what produced that result? Root cause language is borrowed from safety science: the proximate cause is rarely where the lesson is. Asking “why did that happen?” until the answer becomes structural — supervision plan, staffing model, venue choice, communication structure — is what makes the debrief useful for next time.
Documents and learning
What gets captured in the debrief should also feed forward. New considerations belong in the team’s working knowledge — not just in the debrief notes for an event no one will reread.