Offline preview only. This fictional agenda does not schedule a meeting, record participants, approve actions, validate lessons, assign blame, or conclude root cause.

Event Debrief Agenda

Use one facilitated session to compare planned and observed facts, record successes and friction, preserve disagreement, draft candidate improvements, and hand every durable record to its accountable owner.

Ground rules

Describe observations before interpretations.
Discuss systems and handoffs without assigning blame.
Use the pass option when a participant does not want to respond.
Route confidential incidents and personal details to approved records.
Label uncertainty and disagreement instead of forcing consensus.
End with candidate actions and explicit record handoffs, not silent commitments.

6 minutes

1. Open the purpose, boundaries, and participation methods

Owner: debrief_facilitator

Method: boundary_readback

Output: Shared purpose, ground rules, pass option, and record destinations are understood.

10 minutes

2. Compare intended outcomes with observed facts

Owner: event_owner

Method: evidence_round

Output: Observed facts and evidence gaps are recorded without an event-success verdict.

8 minutes

3. Identify what supported the event

Owner: debrief_facilitator

Method: silent_then_round_robin

Output: Positive observations are linked to inputs and kept separate from reusable lessons.

10 minutes

4. Identify friction, surprises, and missing handoffs

Owner: debrief_facilitator

Method: silent_then_round_robin

Output: Friction and surprises are recorded as observations, not blame or causes.

10 minutes

5. Separate patterns, disagreements, and unknowns

Owner: debrief_facilitator

Method: evidence_mapping

Output: Candidate hypotheses remain explicitly unvalidated and disagreements stay visible.

9 minutes

6. Draft candidate improvements and decision handoffs

Owner: event_owner

Method: impact_effort_review

Output: Candidate actions have a basis, role owner, destination record, and verification prompt.

7 minutes

7. Read back records, owners, open questions, and close

Owner: debrief_recorder

Method: readback_and_confirm

Output: Participants hear what was recorded, what was not decided, and where each handoff goes.

Record boundary: No personal data, raw survey comments, confidential incident narratives, credentials, accommodation details, approved actions, validated lessons, or root-cause conclusions belong in this preview.