Applied AI

The Post-Event Debrief Prompt That Actually Gets Used

By Ed Richards,

Debriefs get skipped because they are a meeting nobody has time for. Here is a prompt that turns the voice notes, run sheet and invoices you already have into a one-page debrief in minutes.

The meeting that never happens

Every events business says it does post-event debriefs. Almost none of them actually do, not properly, not every time.

I worked with a twenty-five-person agency in Leeds last year where the debrief existed on paper as a calendar invite sent two days after every job. It got moved so often it became a joke. Nobody wanted to be the one who scheduled a meeting people would rather skip.

The problem was never that people did not care. It was that a debrief takes an hour, the team is already three jobs down the road by the time it happens, and half of what needs saying has already been forgotten.

You already have the inputs, you just never gather them

Here is what most teams have sitting around after a job, unused:

  • Voice notes from the site team, recorded on the drive home, transcribed by whatever app is already on the phone
  • The run sheet, with the scrawled amendments from the day
  • The client's thank-you email, or the slightly awkward one that lists three things that went wrong
  • The supplier invoices that came in higher than quoted, or for the wrong thing entirely

None of that is a debrief. All of it is the raw material for one. The reason it never becomes a debrief is that turning scattered notes and PDFs into a coherent page is exactly the kind of dull assembly work everyone puts off.

The prompt

This is what I hand teams instead of the meeting. Paste your inputs underneath it: the transcribed voice notes, the run sheet text, the client email, a plain description of any invoice discrepancies. Your AI assistant will not chase down anything itself, so give it everything you have and nothing you are guessing at.

You are helping an events team write a one-page post-event debrief. I will give you several
unedited inputs below: transcribed voice notes from the crew, the run sheet with amendments,
a client email, and notes on any supplier invoice discrepancies. Not all inputs will be present
every time, use whatever I give you.

Produce a one-page debrief with exactly these four sections:

1. What worked - the parts of the day that ran to plan or better, specific enough that someone
   could repeat them on purpose next time.
2. What cost margin - anything that took longer, cost more, or needed more people than quoted,
   with a plain reason where one is stated in the inputs. Do not estimate a cost if none is given.
3. What to change in the template - concrete edits to the run sheet, brief, or quote template
   that would have prevented the problems above. Write these as instructions, not observations.
4. Three questions for the client call - questions that would clear up something ambiguous or
   unresolved in the inputs, phrased the way you would actually ask them out loud.

Rules:
- Only use what is in the inputs I give you. If something is unclear or missing, say so in the
  relevant section rather than filling the gap with a guess.
- Do not invent numbers, timings, names, or outcomes that are not in the text.
- Keep the whole thing to one page. Use short sentences.
- If the inputs contradict each other, note the contradiction rather than picking a side.

Here are my inputs:
[paste voice note transcripts, run sheet, client email, invoice notes]

The instruction to refuse invention matters more than any other line in that prompt. An assistant that is short on inputs will happily smooth over the gaps with something plausible. A debrief built on something plausible is worse than no debrief, because it looks finished.

What good looks like

The output should read like something a slightly blunt colleague wrote in fifteen minutes, not a report. If it is generating tidy paragraphs about "stakeholder alignment" or crediting the whole team with a flawless delivery, you have not fed it enough real detail, or you have let it fill in for you. Send it back with more of the actual inputs and less summarising.

A conference venue in the north west I spoke to runs this after every event with three inputs only: the duty manager's voice note, the client's follow-up email, and whatever the catering supplier's invoice said versus what was quoted. Three inputs, one page, five minutes to assemble. That is the whole bar you are clearing. It does not need to be more sophisticated than that to be useful.

Where the value actually lands

The debrief itself is not the point. The point is the second section, the run sheet edits and the template changes, because those are the only parts of the document anyone reads twice. A debrief that never changes a template is just a diary entry.

Keep a running file of the "what to change" lines across a few months and a pattern usually appears fast: the same supplier always invoices wrong, the same stage of the brief is always missing a number, the same client always emails the same question. Once you can see the pattern, it stops being an event problem and becomes a five-minute fix to a document.

Do this on your next job

You do not need to roll this out across the business to try it. Pick your next event, gather whatever inputs you naturally end up with, and run the prompt once. See whether the output is something you would actually send to the team, or something you would bin.

If it is useful and you want help working out where else in the business the same approach would save real hours, a Discovery Lab looks at exactly this kind of gap between the work people do and the systems that are meant to support it. Details are here, and there are more prompts like this one, free, on Zoby OS.

More insights