The spreadsheet that was right in June
Every event starts with a budget spreadsheet built for the proposal: venue, catering, AV, staging, transport, speakers, print, staff, contingency, your fee. It was accurate on the day it was approved. Since then the client added a breakout, the caterer's quote went up after a menu change, and the production manager ordered extra lighting on the company card because the room was darker than expected.
Each of those changes lives somewhere: an email, a revised quote, a card statement. The spreadsheet still shows the June numbers. The account director believes the event is on budget. Six weeks after it happens, the last supplier invoices arrive, and the margin is a fraction of what was expected.
Why the budget tells you nothing mid-event
A budget spreadsheet is a plan. It does not know about commitments or invoices unless someone types them in, and nobody has time to during the build-up.
- Confirmed quotes are not linked to budget lines, so committed cost is not visible.
- Purchase orders, where you use them, sit in the accounts package, not in the budget.
- Card spend and small on-site purchases are coded late or to the wrong event.
- Client-approved changes add cost to the event but not always income to the budget.
- Supplier invoices arrive weeks later, after everyone has moved on to the next job.
Finding the overspend after the party
When the overspend is found at reconciliation, the options are gone. You cannot renegotiate with a supplier whose service has been delivered, and going back to the client after the event is awkward. The same pattern repeats because the team never sees where the budget slipped while it was happening. Across a year, a handful of events like this decide whether the business made money.
Event budgets that track three numbers
- The budget holds lines under your standard headings, each with a planned cost and, where relevant, the client price.
- When a supplier quote is confirmed, it becomes committed cost against the matching line, with a link to the quote.
- Purchase orders and card spend are coded to an event and line at the point they are raised, with a phone upload for receipts on site.
- Supplier invoices are read from your accounts package, such as Xero or QuickBooks, through its API, and matched to the commitment so the actual cost appears on the right line.
- Client-approved changes are recorded with both their cost and the extra client price, so the margin effect is visible.
- The event view shows planned, committed and actual per line, and flags any line where committed has passed planned.
- A portfolio view shows every live event's expected margin, so the director sees which events need attention this week.
| Line | Planned | Committed | Actual | Flag |
|---|---|---|---|---|
| Catering | Budget figure | Confirmed quote | Invoice received | Committed over plan |
| AV and lighting | Budget figure | Quote plus card spend | Part invoiced | Watch |
| Transport | Budget figure | Confirmed quote | Not yet invoiced | On plan |
| Speakers | Budget figure | Fees and travel booked | Claims pending | On plan |
The numbers stay in your accounts package, which is the book of record. The event budget reads from it rather than replacing it.
Budget meetings with current numbers
The weekly event status meeting opens on the portfolio view. Two events show a committed cost over plan. On one, the extra catering was a client change that was never priced to them; the account manager sends the change note that afternoon. On the other, the production manager agrees to drop an optional extra. After the event, reconciliation is mostly checking that the actuals match the commitments, not discovering what happened.
Is your event budget a plan or a picture?
- Your event budget spreadsheet is not updated after the proposal.
- Overspends are found at reconciliation, after the event.
- Card spend on site is coded to events late or not at all.
- Client-approved changes add cost but not always a matching charge.
- Directors cannot see the expected margin across live events.