To track event budget vs actuals, keep one budget per show with a budgeted and an actual amount on every line, record actuals as they become known rather than after the show, and note where each actual came from. The variance on each line, and its cause, is what tells you where the plan was wrong and what to change in the next estimate.
A budget that only gets compared with reality at wrap is a report on the past. One that fills in during the build is a tool you can still act on.
The columns that matter
| Column | What goes in it |
|---|---|
| Category | Labor, equipment, venue, travel, production and so on. Keep the same categories from estimate to wrap. |
| Line description | Specific enough to match an invoice: "LED wall, 3 days," not "video." |
| Budgeted | The approved number. It does not change when spending does. |
| Actual | What the line cost or will cost, updated as soon as it is known. |
| Variance | Actual minus budgeted. Positive is over budget. |
| Source | Where the actual came from: a crew booking, a vendor contract, a shipment, a manual entry. |
| Reason | For any line over a threshold you set, one line on why. |
Five habits that keep actuals current
- Lock the budget you approved. Save it as a version and compare against it. A budget you keep editing cannot tell you what changed.
- Record change orders separately. A client-requested addition is not an overrun. Keep it as its own record so the variance shows the difference.
- Take crew actuals from the roster. Confirmed bookings already know days, rates and per diem. Retyping them invites a second number.
- Note the source on every actual. "From the vendor contract" and "estimated by Jo" are different levels of certainty.
- Write the reason while it is fresh. At wrap nobody remembers why lighting ran over on day two.
A worked example (illustrative)
The figures below are made up for the example and do not come from any customer.
| Line | Budgeted | Actual | Variance | Source and reason |
|---|---|---|---|---|
| Crew labor | $18,400 | $20,200 | +$1,800 | Roster. Rehearsal added a day for two crew. |
| LED wall | $12,000 | $12,000 | $0 | Vendor contract. |
| Freight | $3,500 | $4,150 | +$650 | Shipment. Late-change truck. |
| Catering | $2,800 | $2,450 | -$350 | Manual entry. Smaller crew meal count. |
Two of the four variances trace back to one schedule change. That is the pattern to look for: a date change that nobody priced before it was confirmed.
How ShowOps.AI handles it
- Each budget line carries a budgeted and an actual amount, and the actuals view shows the variance per line, filterable by category and by source.
- Sync actuals pulls the latest figures from the modules that hold them: work orders, shipments and any crew cost lines already posted to the roster. Anything else is entered by hand, and every actual shows its source.
- Budgets are versioned, change orders are their own records, and the actuals view exports to CSV.
- When a producer confirms a timeline change, ShowOps.AI reports the staffing cost change and the budget lines linked to the crew bookings that move, before anyone approves it. An approved change updates those lines, and it can be undone. This step is switched on for each organization during setup.
- At close-out, the debrief asks for a reason on each flagged variance, so the next estimate starts from what actually happened.
What it does not do: it does not import invoices or purchase orders, and it does not invoice the client.
For budgets, versions and change orders, see Budget. If the budget lives in a spreadsheet today, read When does an event production spreadsheet stop working?.