Book a Demo Try Speak AI Free Login

Debrief Meeting Notes Template With Questions and Examples

Use this template to take notes in a debrief meeting held right after a project, launch, event or incident. It captures what happened, what worked, what did not, and what changes next time.

Book a DemoTry Speak AI Free

Used by 300,000+ individuals and teams. Free trial, no credit card required.

Debrief meeting notes: the template

Eight sections follow the order of a good debrief, from the facts to the changes you will make. Each shows an example entry, written for a product launch debrief.

Debrief meeting notes

Fill in during or right after the meeting

  • Event or project: [What is being debriefed]
  • Date of the event: [Date]
  • Debrief date and time: [Date, start and end time]
  • Facilitator: [Name]
  • Notes taken by: [Name]
  • Present: [Names and roles]
  • Time since event: [e.g. 2 days]

What was supposed to happen

The goal and plan, in two or three sentences. Use the numbers and dates agreed beforehand.

ExampleLaunch the new reporting feature on 12 May to all paid accounts. Target: 15% of accounts open a report in week 1.

What actually happened

The facts in order, without opinion. Give times, results and who was involved.

ExampleReleased at 10:05. Rollback of the export button at 11:40 after errors. Final adoption in week 1: 9%.

What went well

Specific things to repeat, each tied to a person or practice.

ExampleThe staged rollout caught the export bug on 5% of users. Support had macros ready by 9:00.

What did not go well

Specific problems, described as events and not as blame.

ExampleNo load test on the export path. Marketing announced before engineering confirmed the release time.

Why it happened: root causes

For the top two problems, the cause behind the cause. Ask why until you reach something you can change.

ExampleNo load test because the test environment lacked production-sized data. No release time sent because nobody owned it.

What we will change

Concrete changes to the process, each with an owner. Do not list more than five.

ExampleAdd a production-sized dataset to staging. Name a release coordinator for every launch.

Open questions and parked items

Anything unresolved and who will find the answer.

ExampleWas the 9% adoption caused by the bug, or by the report being hard to find? Product to check usage logs.

Follow-up and distribution

When the changes are reviewed, and who receives the notes.

ExampleReview the changes in 4 weeks. Notes to launch team and the support lead.

Action items

Task Owner Due
Load staging with a production-sized dataset Engineering lead End of next sprint
Add a release coordinator role to the launch checklist Product manager Next Friday
Pull week 1 usage logs for the report page Data analyst 3 working days
Send the debrief notes to the launch team Note taker Next working day
Copy as textDownload .txtPrint or save as PDF

Copy-ready notes text

Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].

Copy the text
DEBRIEF MEETING NOTES

Event or project: [What is being debriefed]
Date of the event: [Date]
Debrief date and time: [Date, start and end time]
Facilitator: [Name]
Notes taken by: [Name]
Present: [Names and roles]
Time since event: [e.g. 2 days]

WHAT WAS SUPPOSED TO HAPPEN
[The goal and plan, in two or three sentences. Use the numbers and dates agreed beforehand.]

WHAT ACTUALLY HAPPENED
[The facts in order, without opinion. Give times, results and who was involved.]

WHAT WENT WELL
[Specific things to repeat, each tied to a person or practice.]

WHAT DID NOT GO WELL
[Specific problems, described as events and not as blame.]

WHY IT HAPPENED: ROOT CAUSES
[For the top two problems, the cause behind the cause. Ask why until you reach something you can change.]

WHAT WE WILL CHANGE
[Concrete changes to the process, each with an owner. Do not list more than five.]

OPEN QUESTIONS AND PARKED ITEMS
[Anything unresolved and who will find the answer.]

FOLLOW-UP AND DISTRIBUTION
[When the changes are reviewed, and who receives the notes.]

ACTION ITEMS
Task | Owner | Due
[Task] | [Name] | [Date]

Next meeting: [Date, time]
Notes prepared by: [Name]

How to run this meeting

  1. Hold it within a few days, not a few weeks

    Memory fades fast. Aim for two to five days after the event, long enough for emotions to settle and short enough that details are fresh.

  2. Ask the same four questions in order

    What did we plan? What happened? Why was there a gap? What will we change? The order keeps people from jumping to solutions before agreeing on the facts.

  3. Focus on the process, not the person

    Frame problems as 'what in our process allowed this?' Blame stops people from telling you what really happened, and it ends the learning.

  4. Limit changes to the few that will actually happen

    Pick at most five changes, each with an owner and a date, and review them at the next team meeting. A long list of ideas is a list nobody does.

Capture the real reasons things went wrong

The most useful part of a debrief is what people say about why, and that is the part that gets lost when notes are typed live. Speak AI records the meeting and writes the summary and action list for you.

  • Record the debrief on Zoom, Google Meet or Microsoft Teams, or upload the recording afterwards.
  • Get a transcript with speakers labelled, so you can find exactly what each person said about the cause.
  • Get an automatic summary split into what went well, what did not and what will change.
  • Get action items with owners and dates pulled out, so the changes get tracked, not forgotten.

See how the AI meeting assistant and the AI notetaker work, or start with a free account.

Book a DemoTry Speak AI Free

Frequently asked questions

What is a debrief meeting?

A debrief meeting is a structured review held soon after a project, launch, event or incident. The team compares what was planned with what happened, finds the causes of any gap, and agrees a few changes to make next time.

What four questions should be asked during a debrief?

What did we expect to happen? What actually happened? Why was there a difference? What will we do differently next time? Asking them in that order keeps the group on the facts before it moves to fixes.

What are some good debrief questions?

What went better than expected? Where did the plan break down? What surprised you? What did we lack at the time? What is one thing you would change next time, and who needs to know about it?

What are the 5 key points of debriefing?

Set the purpose and ground rules, review the facts, look at what worked and what did not, find the root causes, and agree changes with owners and dates. Close by saying when the notes arrive.

What is a good template for an agenda for a debrief meeting?

Open with purpose and ground rules (5 minutes), then plan versus actual (10), what went well (10), what did not (10), root causes (15), changes and owners (15), and close (5). That is 70 minutes, or cut to 45 for small events.

Related templates and tools

Debrief Meeting Minutes TemplatePost Meeting Agenda TemplateClosing Meeting Agenda TemplateAll meeting templatesAI Meeting AssistantAI Notetaker

Get debrief notes without typing them

Book a demo to see how Speak AI turns a debrief recording into a summary, root causes and action items, or try it free on your next meeting.

Book a DemoTry Speak AI Free