Event debrief template: agenda, questions and a worked example

A useful event debrief template gives your team a way to compare the plan with what happened, explain the differences, and agree what you'll change before the next event. Collect staff observations first, bring the results into a focused meeting, and finish with decisions that have someone responsible for delivering them.

So you've packed down, the team is tired, and everyone has a different version of the night. The door was a mess. The door was fine. Marketing worked. Marketing brought the wrong crowd. You can spend an hour trading those opinions, or you can get specific enough to improve the next event.

This guide gives you a copyable meeting template, preparation instructions, a timed agenda, questions for each team, and a worked example. It's written for operators running paid events, where an avoidable delay, an unhappy ticket buyer, or another unplanned staffing bill has a real cost.

Copy this event debrief template

Put the following into your meeting document. Send it before the debrief so people can add observations while the details are still clear. You don't need everyone to write a report. You need enough information to choose what deserves discussion.

Meeting details

• Event name and date:

• Debrief date and meeting length:

• Person leading the discussion:

• Person recording decisions:

• People attending and roles represented:

• People contributing written input:

• Link to the event plan and results:

• Decisions this meeting needs to make:

Individual input before the meeting

• What were you responsible for, and what was supposed to happen?

• What happened? Include a time, location, or example where you can.

• What worked well enough that we should deliberately repeat it?

• Where did you have to improvise, repeat work, or wait for someone?

• What did that change for attendees, staff, costs, or revenue?

• What supports your account, and what are you unsure about?

• What change would you propose, and what would it need?

Discussion notes

• Agreed facts:

• Different accounts we still need to check:

• Practices to keep:

• Problems selected for discussion:

• Likely causes and the evidence behind them:

• Decisions made and options rejected:

• Questions someone will investigate after the meeting:

• Changes approved, person responsible, and next check-in:

Closing questions

• Can each person responsible explain what they're doing next?

• Does anyone need budget, access, or another person's approval?

• Which decisions affect a supplier, a ticket buyer, or the next event plan?

• Where will the decisions live, and when will we check progress?

Keep the template alongside your post-event report. The report supplies the results; the debrief is where your team explains them and makes decisions. If you already have an action record in that report, update it rather than starting another list that nobody owns.

Decide when to meet and who needs to be there

Capture immediate observations while your team can still remember the details. Hold the fuller meeting when people have rested and you have enough information to make useful decisions. Booking it before the event makes this much easier than chasing everyone's availability after they've moved onto another job.

For a small recurring paid event, you might collect notes the next working day and meet later that week. That's a practical starting point, not an industry deadline. A festival with multiple contractors may need separate operational conversations before a wider review. A weekly event may need an early decision before the next ticket release or staff booking.

Don't wait for every invoice to arrive. Mark the financial figures as provisional and give unresolved costs to someone to confirm. You can still decide to improve the staff briefing while you're waiting for the final venue bill.

Invite the people who can explain the work and authorize changes. That usually means the event lead and representatives for ticketing, marketing, operations, production, and attendee support. At a small event, one person may cover several roles. Include the person who worked the door, even if someone more senior is already representing operations.

Ask key suppliers for their account where their work affected the outcome. A venue manager may know why access started late. A production contractor may explain a change your internal team never saw. Give them the questions in advance and agree which part of the meeting needs them.

The UK's Health and Safety Executive recommends debriefing after an event, including other agencies where relevant, and considering both problems and successes. Its guidance is about event safety; the same habit of hearing from the people involved is useful in your wider operational review.

Keep urgent incidents on the appropriate incident process. A routine commercial debrief isn't a reason to delay a safety response or to investigate sensitive individual matters in front of the whole team. You can discuss a process change without circulating personal details in the general meeting notes.

Choose someone to lead the discussion who can challenge an account without turning it into a fight. If you made the decision under review, let another person lead that section. You still explain your reasoning, but you shouldn't also decide which questions get asked about it.

Prepare the team before the debrief

Start with a short note explaining what the meeting is for. Name the decisions you want to reach, such as whether to change admission staffing or keep a new ticket offer. A vague invitation to discuss how it went encourages equally vague answers.

For example, your invitation could say that you'll review the delayed opening, decide whether the admission plan needs to change, and confirm what to keep from the workshop format. Ask contributors to complete their input before the meeting, and include the link to the report they'll use. People should know what they need to prepare without sending you another message.

Ask people to submit their own observations before reading everyone else's. That gives you a better chance of hearing what the floor assistant noticed, rather than five versions of the event lead's opening opinion. Offer a private route for anything someone doesn't feel comfortable putting in a shared document.

Don't promise anonymity you can't provide. In a small team, a description of a specific shift may identify its writer. Be clear about who will read the input and what will appear in the shared record.

Gather enough evidence to discuss the differences

Attach the current report, the running order, and the relevant operational notes. Highlight what changed against the plan. The team shouldn't spend the meeting hunting for the right version of a staffing schedule.

Use the records your tools already provide. With Loopyah's ticketing, sales by source show which posts and emails sold tickets. Bring that information into the marketing discussion alongside campaign costs. Your team still needs to explain what it tried and why; the sales record gives that conversation something firmer than likes or enthusiasm.

Choose evidence that answers the question on the agenda. If attendees complained about finding the entrance, bring the arrival instructions they received, the signage plan, and specific complaints. A total ticket-sales figure won't explain why a buyer walked around the block twice.

For feedback, keep the question wording and the number of responses visible. Say that respondents reported a problem, rather than implying every attendee had it. AAPOR's survey best practices explain why sampling, question wording, and who responds affect what you can conclude. A few detailed complaints can justify investigating a failure without establishing how common it was.

Choose the meeting's focus

Read the inputs and group observations that describe the same issue. Keep the original examples attached so a useful detail doesn't disappear into a label like communication.

Then select the issues that need a shared decision. Prioritize immediate obligations and serious attendee problems, followed by recurring costs, missed revenue, and failures likely to happen again. Handle a simple typo outside the meeting. Give a complicated supplier disagreement its own conversation if it would consume the whole hour.

Don't circulate your preferred explanation as an agreed finding. You can say that admission started late and ask the team to explain the sequence. Saying the door team caused the delay before they arrive defeats the point of inviting them.

Run a focused 60-minute debrief

Here's a suggested agenda for a small or medium event with a manageable list of issues. The timings are a working template. Increase the time or split the review when the event needs it, but protect the part where you make decisions.

Minutes 0 to 5: set the purpose

Name the decisions the meeting needs to make. Confirm who will record them and who can approve spending or changes to the next event.

Explain how you'll handle disagreement. Ask people to separate what they saw from what they think caused it. Everyone can challenge an explanation, including yours, but they need to describe the event rather than label a colleague careless or difficult.

A useful opening is simple.

Minutes 5 to 12: agree what happened

Review the event's original goals and the main results. Confirm any changes to the running order and flag figures that aren't final. Don't read the whole report aloud; everyone received it in advance.

If two records disagree, identify the difference now. Ticket sales and checked-in attendance describe different things. A scheduled opening time and the first successful scan aren't necessarily the same moment either. Write down what each record actually measures before building an explanation around it.

The World Health Organization's after-action review approach examines what happened, what worked, what didn't, and why. It was developed for public-health work. We're adapting that sequence here to keep an event review grounded in what the team can establish.

Minutes 12 to 22: identify what to repeat

Ask for specific practices that helped the event work. A smooth soundcheck might have depended on getting technical details from speakers early. A strong ticket release might have followed a clear offer to an existing audience.

Find out what made the practice possible. Who did the work? What did it cost? Did it depend on someone staying late or taking on an unplanned job? You don't want to repeat an apparent success by assuming the same person will keep absorbing the extra work.

Give credit here. Then capture the part you can repeat in the next event plan. Great teamwork is pleasant feedback; having the stage manager confirm every handover before doors open tells the next team what to do.

Minutes 22 to 40: examine the priority problems

Work through the selected issues one at a time. Start with the person closest to the work, then hear the other accounts. Keep a visible sequence of the relevant decisions and events.

Ask what the team expected, what changed, when they noticed, and what information they had at that moment. The final outcome can make a decision look obvious in hindsight. You need to understand why it made sense, or seemed necessary, at the time.

If the discussion stalls at we need better communication, ask what message was missing, who needed it, and when. If nobody knows, assign someone to check. Don't fill a gap in the evidence with the explanation that sounds most convincing.

Minutes 40 to 52: decide what changes

Compare the proposed fixes with the problem you've actually identified. More staff won't solve instructions sent to the wrong people. Another email won't help if nobody has authority to approve a change.

Ask what each fix costs, who will implement it, and how you'll tell whether it worked. Choose what the team can deliver before the relevant deadline. If a larger change needs approval, record the decision needed and who will obtain it.

Be explicit when you're testing an idea. We think clearer arrival instructions will reduce questions at the door is a reasonable hypothesis. We've solved the queue problem is a claim you can't make yet.

Minutes 52 to 60: read back the decisions

Have the person responsible for each change confirm it in their own words. That often exposes a missing dependency before everyone leaves.

Confirm who needs the outcome, including people who weren't invited. Book the next check against a real event milestone, such as the supplier booking, ticket launch, or staff briefing. A deadline after that decision has already happened is useless.

Ask questions that fit each team's work

Use these prompts selectively. Sending every question to every person will give you a lot of homework and a meeting that tries to cover everything. Pick the questions that help explain the event you're reviewing.

Ticketing and marketing

• Which ticket offers sold, and which needed more explanation than we expected?

• Where did actual sales differ from the forecast, and what changed before that happened?

• Which messages produced repeated buyer questions or complaints?

• Did discounts bring useful extra demand, or mostly reduce what existing buyers paid?

• What do we know about sales sources, and which conclusions are still uncertain?

Keep the discussion tied to purchases and buyer behavior. Strong reach can be useful, but it doesn't explain a weak ticket-sales result on its own. If the issue is people failing to understand the offer, revisit your event description before deciding you simply need a larger advertising budget.

Door team and attendee support

• What did arriving attendees struggle to find or understand?

• Which requests stopped the normal admission flow?

• Could staff resolve ticket problems, or did they repeatedly need someone else's access?

• Were ticket buyers promised something that wasn't available when they arrived?

• Which complaints are still waiting for a response?

Ask for the exact point where a problem started. Someone unable to find their ticket needs a different fix from someone arriving at the wrong entrance. Grouping both under slow check-in can send you towards an expensive staffing change that misses the cause.

Production, venue, and suppliers

• Which part of the running order changed, and who knew about the change?

• Were access times, setup requirements, and handovers clear before the day?

• What work took longer than planned, and what caused the delay?

• Where did a supplier deliver something different from the agreed scope?

• Which successful arrangement should go into the next booking or brief?

The TeamSTEPPS debrief checklist from the US Agency for Healthcare Research and Quality asks about communication, role clarity, workload, and resources. Those are useful prompts for an event team too, although the checklist's original setting is healthcare. Use them to find the missing instruction or resource behind a broad complaint.

Event lead and commercial owner

• Which decision created extra work or cost elsewhere in the event?

• What did we spend money on that attendees actually used or valued?

• Which unresolved problem could damage a repeat booking or sponsor relationship?

• What needs to change before we commit to the next venue, supplier, or ticket offer?

• What will we deliberately keep, and what are we willing to stop paying for?

You should answer questions too. If a last-minute change came from you, explain the information you had and hear what it required from everyone else. Otherwise the team learns that the debrief applies only to decisions made below you.

When you have a small team or several sites

If you run the event with one assistant and a venue partner, keep the same questions and shorten the meeting. Write your own observations before asking for theirs. Otherwise you can accidentally brief them on the answer you're hoping to hear. Ask a supplier about the part they actually delivered, and bring only the unresolved decisions into the conversation.

For a larger event, let each site or department collect its own account first. The shared debrief should concentrate on decisions that affect several teams, such as a schedule change that delayed production and extended venue staffing. Ask someone from each affected team to explain its consequences. Reviewing the same issue separately can leave you with fixes that clash when everyone comes together again.

Use one agreed record for the final decision and link the department notes behind it. People can retain the detail they need without carrying different versions of what was approved. Before closing the wider meeting, check that the change is workable for the team that has to deliver it.

Handle disagreement without inventing certainty

Suppose marketing says the arrival email was clear, while the door team says attendees didn't know where to go. Both accounts can be true. An email can look clear on a laptop and still leave someone confused outside the venue.

Ask each person for their observation. Then check the actual message, the route to the entrance, and what attendees asked. You might discover that the email named the venue correctly but omitted the side entrance used that evening. You might also discover that you don't have enough evidence to explain it yet.

Keep separate notes for an observation, an explanation, and a decision. Observation means what someone saw or what a record shows. Explanation means why the team thinks it happened. Decision means what you've agreed to do. Keeping those separate makes it harder for an early guess to become an accepted fact.

If one person dominates, stop the exchange and invite the people who did the work to speak first. Ask the senior person to respond after you've heard those accounts. For a remote meeting, give everyone a short writing pause before opening the discussion again. It gives quieter contributors a way back in.

You can redirect a heated exchange without making a speech about meeting behavior. Ask the door lead to finish describing the handover, then invite production to explain what it received. If someone makes a personal accusation, bring them back to the specific action and its effect. That gives you something the team can investigate and change.

When an attendee's account conflicts with a staff account, record both accurately. You don't need to choose a winner to identify something worth improving. A clearer instruction may help even while the exact sequence remains unresolved.

Some disagreements need evidence you can't produce in the room. Name who will check it, where they will look, and when they'll report back. Decide what must happen in the meantime. If a decision can safely wait, say so. If the next event depends on it, agree a provisional approach and the conditions for changing it.

Don't turn the meeting into a vote on what happened. Agreement is useful for choosing a plan. It can't make an unsupported account true.

Worked example: a paid evening workshop

Here's a fictional example to show how the meeting works. The event, figures, timings, and decisions are illustrative, not Loopyah customer results or industry benchmarks.

The workshop had room for 200 people. The operator aimed to sell 175 tickets, sold 180, and recorded 164 of those ticket holders checking in. Doors were planned for 6:00 pm and the first session for 6:30 pm. Doors actually opened at 6:12 pm, and the session began at 6:45 pm.

The organizer's first reaction is that the door team needed more staff. Before approving that cost, they ask for written input from the door lead, venue contact, production lead, and customer-support person.

What the team brings

The door lead says the admission team was ready before 6:00 pm but hadn't received confirmation that the room was ready. The production lead says they told the venue contact when the room was ready at 5:55 pm. The venue contact understood that the event lead would authorize opening. The event lead was dealing with a speaker and thought production owned that decision.

The team checks the running order. It includes the planned opening time but doesn't name who confirms readiness to the door lead. Nobody can point to a shared instruction that assigns that handover.

Support also received complaints about waiting outside. The team treats those complaints as evidence that some attendees had a poor arrival experience. It doesn't claim all 164 attendees complained, or assume the opening delay explains the 16 tickets that weren't checked in.

What they keep

The workshop sold above its target, and the team wants to retain the offer for the next edition while reviewing the full commercial results separately. Production also reports that collecting speaker requirements in advance made setup straightforward.

The debrief records the advance technical brief as a practice to repeat. It names who will request those details next time so the successful preparation survives a staff change.

What they change

The meeting identifies an unassigned readiness handover as a supported explanation for the late opening. The event lead will add a named person responsible for confirming readiness with production and passing the opening decision to the door lead. The revised brief will also identify who covers that responsibility when the named person is occupied.

They agree to review that instruction with the venue and door leads before the next event. At the staff briefing, each lead will explain their part back to the group. On the day, the team will record when readiness was confirmed and when doors opened.

For this fictional meeting, the next workshop is in four weeks. The event lead agrees to circulate the revised instruction within three working days. The venue and door leads will confirm it by the end of that week, leaving time to resolve a disagreement before staff receive their brief. The production lead records that schedule in the existing action record.

The customer-support lead separately agrees to reply to the outstanding arrival complaints the next working day. Improving the next workshop doesn't answer the people still waiting for a response about this one. That work has its own owner and deadline, so it won't disappear behind the larger operational change.

That gives them a way to check whether the change happened and whether admission began as planned. They haven't proved that staffing is sufficient under every condition. They've avoided hiring another person before addressing a responsibility nobody had been given.

What stays open

The first session began 15 minutes late, while doors opened 12 minutes late. The team doesn't assume one fully explains the other. Production will compare the final running order with its notes to establish what else affected the start.

The 16 unchecked tickets also remain a separate question. The team will check the attendance records before calling them no-shows and decide whether follow-up could clarify the reasons. Nothing in this debrief proves that those buyers stayed away because of arrival instructions or the delay outside.

Make the decisions part of the next event

Send the agreed notes while the discussion is still fresh. Keep disputed points labeled and give people a way to correct factual errors. A useful record explains the decision and why the team chose it; it doesn't need to reproduce every sentence spoken in the room.

Put each approved change into the place where the next team will use it. Admission instructions belong in the door brief. A changed setup responsibility belongs in the running order and supplier briefing. A revised offer belongs in the next event's sales plan.

FEMA's after-action review training distinguishes a report from an improvement plan that turns recommendations into concrete corrective actions. Its setting is emergency management, but the practical lesson carries over: a review document needs to lead to changes in the work.

Use your existing action record to check those changes before the next relevant deadline. If someone is blocked, decide whether to approve the resources, narrow the change, or choose another approach. Don't let a repeatedly missed deadline stand in for a decision to drop the work.

At the next event, check the specific thing you changed. Did the named person confirm readiness? Did the door lead receive the instruction? Did doors open as planned? If the result still missed the mark, you now have a more precise starting point for the next review.

Book the debrief, send the template, and ask for individual observations before the meeting. Your team already knows a lot about what happened. The job is to hear it clearly enough to decide what you'll do differently next time.