Debrief Meeting Minutes Template (Event, Project or Call)
Use this template to write up a debrief held right after an event, launch, sales call or incident. It records what was planned, what happened, what to repeat and what to change, with an owner on every change.
Used by 300,000+ individuals and teams. Free trial, no credit card required.
Debrief meeting minutes: the template
Eight sections move from facts to learning to action. Each shows an example entry from a conference debrief, so you can see how specific to be.
Debrief meeting minutes
- Subject of the debrief: [Event, project or call]
- Date and time of debrief: [Date, start and end time]
- Date of the event or work: [Date or period]
- Facilitator: [Name]
- Minutes taken by: [Name]
- Present: [Names and roles]
- Not present: [Names and roles]
Goal and plan
What the work set out to do and the measures agreed beforehand.
What actually happened
The facts in order, without opinions. Dates, numbers and who did what.
Results against the goal
Numbers beside the targets. Say plainly if the goal was missed.
What worked
Specific things to keep doing. Write who or what, not 'good teamwork'.
What did not work
Specific problems and, where known, the cause. Describe the process, not the person.
Root causes and lessons
The reason behind the main problems, as lessons the next team can use.
Decisions and changes
Each change agreed, with who decided and what it replaces.
Actions and owners
Every action with a named owner and date. Link to the tracker if there is one.
Action items
| Task | Owner | Due |
|---|---|---|
| Write the booth setup checklist including the onsite load test | Marcus, events lead | 28 June |
| Share the qualifying question script with the sales team | Priya, sales lead | Next Friday |
| Follow up the 12 paper-form contacts | Sales operations | Within 2 working days |
| File the debrief minutes in the event folder | Minute taker | Next working day |
Copy-ready minutes text
Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].
DEBRIEF MEETING MINUTES Subject of the debrief: [Event, project or call] Date and time of debrief: [Date, start and end time] Date of the event or work: [Date or period] Facilitator: [Name] Minutes taken by: [Name] Present: [Names and roles] Not present: [Names and roles] GOAL AND PLAN [What the work set out to do and the measures agreed beforehand.] WHAT ACTUALLY HAPPENED [The facts in order, without opinions. Dates, numbers and who did what.] RESULTS AGAINST THE GOAL [Numbers beside the targets. Say plainly if the goal was missed.] WHAT WORKED [Specific things to keep doing. Write who or what, not 'good teamwork'.] WHAT DID NOT WORK [Specific problems and, where known, the cause. Describe the process, not the person.] ROOT CAUSES AND LESSONS [The reason behind the main problems, as lessons the next team can use.] DECISIONS AND CHANGES [Each change agreed, with who decided and what it replaces.] ACTIONS AND OWNERS [Every action with a named owner and date. Link to the tracker if there is one.] ACTION ITEMS Task | Owner | Due [Task] | [Name] | [Date] Next meeting: [Date, time] Minutes prepared by: [Name]
How to run this meeting
-
Hold it within 48 hours
Memory fades fast. A debrief held two days after the event gets details a debrief held two weeks later never will.
-
Facts first, then opinions
Spend the first third of the meeting agreeing what happened, using numbers. Only then ask what worked and what did not, or the debate will be about the facts.
-
Blame the process, not the person
Ask 'what let this happen' rather than 'who did this'. People share problems they expect to be fixed, not punished.
-
Finish with changes, not themes
A debrief that ends with 'we should communicate more' has failed. Each lesson becomes one change with an owner, a date and a place where the next team will see it.
Capture the lessons while people are still sharing them
Debrief value comes from candid detail that is easy to lose in handwritten notes. Speak AI records the discussion and organizes what was said.
- Record the debrief on Zoom, Google Meet or Microsoft Teams, or upload the recording.
- Get a transcript with speakers labelled, so each point and its source is easy to find.
- Get an automatic summary of what worked, what did not and the lessons.
- Get action items with owners and dates, ready to move into your tracker.
See how the AI meeting assistant and the AI notetaker work, or start with a free account.
Frequently asked questions
What is a debrief meeting?
A debrief meeting is a short review held soon after an event, project, call or incident to learn from it. The group agrees what happened, what worked, what did not, and which specific changes to make next time.
How do you write a debriefing?
Record the goal, the facts of what happened, the results against targets, what worked, what did not, the causes, and the changes agreed with owners and dates. Keep it factual and specific, and aim for one or two pages.
What is the proper term for an after-event meeting?
It is usually called a debrief, a post-mortem or an after-action review. Teams in project work also use retrospective or lessons learned session. The structure is the same: facts, learning, then changes.
How long should a debrief meeting be?
Fifteen to 30 minutes suits a single call or small event. A large event, launch or incident review takes 60 to 90 minutes. Hold it within 48 hours while details are fresh.
What is the difference between debrief minutes and an event report?
Debrief minutes record what the team learned and what will change, with owners. An event report records what happened for people who were not involved. Many teams write both from the same recording.
Debrief the work, let Speak AI write down the lessons
Book a demo to see Speak AI turn a debrief call into a summary, lessons and action items, or try it free on your next meeting.