Skip to main content

Guide

The event debrief that writes your next estimate

A useful event debrief records why each budget line came in over or under, what the scope change was and what the next producer should know, and keeps an as-built record of what the show actually used. The next estimate then starts from that record at today's rates.

By Pedro van Tol, founder of ShowOps.AI and an executive producer for 15 years

A useful event debrief records three things: why each budget line came in over or under, what changed in scope and why, and what the next producer should know. Alongside it, keep an as-built record of what the show actually used, so the next estimate starts from real quantities and roles and is priced again at today's rates instead of copied from last year's numbers.

Most debriefs fail the same way. They happen late, they turn into a list of complaints, and nothing in them reaches the next estimate. The fix is to make the debrief answer the questions the next estimate will ask.

The close-out checklist

  1. Actuals in. Every budget line has an actual, from the roster, the vendor contracts, shipments or a manual entry.
  2. Change orders recorded. Each one tied to the budget, with what caused it.
  3. Variance reasons written. For every line over or under your threshold, one reason.
  4. Debrief held. Within a week of strike, with the producer, the technical lead and whoever owned the budget.
  5. As-built saved. What the show actually used, by line.
  6. Project closed. So it stops showing up as active and its record is final.

What the debrief asks

QuestionWhy the next estimate needs it
Why did this line come in over or under?

Pick a reason: scope added or reduced, estimate too low, rate change, overtime, crew size change, equipment substitution, freight, a venue requirement, weather, a vendor miss, an internal miss, currency, or other with a note.

What changed in scope, and what caused it?

A client request and an estimating miss look the same on a budget and mean opposite things for the next quote.

Which roles would you book again?Tells the next producer which parts of the crew plan held up. Record it by role, not by person.
How did each key vendor do?A short rating, so the next show knows who to call first.
What should the next producer know?The one paragraph you wish you had read before this show.

From as-built to the next estimate

The as-built record is the bridge. It keeps two things apart on purpose:

  • The shape of the show: what kind of item, quantity, unit, number of days, the role or the catalog item. This travels to the next estimate.
  • The price it was bought at: the actual cost, the rate card in force and the date. This stays as evidence of what one show cost in one market on one date.

When the next show comes in, start its estimate from the as-built: the quantities and roles carry over, and every line is priced again. That gives you an estimate built on what a real show needed, at what things cost now.

A worked example (illustrative)

The figures below are made up for the example and do not come from any customer.

Last year's conference used 3 days of an LED wall, 2 camera operators for 2 days each and 1 A1 for 3 days. The debrief recorded that the A1 line ran over because a rehearsal was added (reason: scope added, client request).

This year's estimate starts from that as-built: LED wall × 3 days, camera operator × 2 for 2 days, A1 × 1 for 3 days. None of last year's prices come with it; each line is priced fresh for this year. The producer reads the note about the added rehearsal and adds a fourth A1 day before the client asks.

How ShowOps.AI handles it

  • The close panel, the debrief and the as-built record sit on the project page. The debrief asks for a reason code on each flagged variance, scope-change notes with their cause, vendor ratings and lessons for the next producer. When a show's end date passes and the project is still open, ShowOps.AI sends a reminder to close it.
  • The as-built record keeps the shape of the show apart from the prices paid.
  • Start the next estimate from this record creates a new estimate from the as-built. Quantities and roles carry over; old prices and vendors do not. You price the new show fresh.

What it does not do: union rules are not part of carry-forward pricing, and it will not invent a price for a line that has no matching rate.

For estimates and deals, see Sales. If your close-out lives in a spreadsheet today, read When does an event production spreadsheet stop working?.

Frequently asked questions

What should an event debrief include?
A reason for every budget line that came in well over or under, the scope changes and what caused them, which roles you would book again, how each key vendor performed, and a short note for the next producer. Keep it to what changes the next estimate.
When should you hold the debrief?
Within a week of strike, while the details are fresh and before the team moves to the next show. Record actuals as the show runs so the debrief is about reasons, not about finding numbers.
What is an as-built record?
It is a record of what the show actually used, line by line: equipment, crew roles and days, vendor services, logistics and venue. It holds quantities and days, so the next estimate can start from what really happened instead of from what was planned.
Why not just copy last year's budget?
Because last year's prices are last year's market. Copy the shape of the show, the quantities, roles and days, and price it again at today's rates. Otherwise an old number carries the authority of a real project and is still wrong.
Does ShowOps.AI carry prices into the next estimate?
No. Starting a new estimate from an as-built record carries quantities and roles, not the old prices. You price the new show fresh.

See it in your production

Talk to the team

We are happy to walk through how ShowOps.AI fits your productions, your tools, and your data requirements.