Event spend reporting

A report is not a record. A record exists so information is retained; a report exists so someone makes a decision. Most meetings reporting is built as a record and circulated as a report, which is why so much of it goes unread.

This page is about the reports rather than the data behind them — the fields and capture points are on meetings data and reporting, and the underlying case for seeing the category at all on meetings spend visibility.

The most common mistake is building one report and sending it to everyone. Efficient to produce, ineffective to read, because the three audiences want materially different things.

These should share a data layer and should not share a document. Three short targeted reports get read; one long combined report gets filed. The procurement view feeds meetings procurement and supplier management decisions; the departmental view is what changes behaviour, because it is the only one the person commissioning meetings will open.

Eight looks like a lot. In practice most are one page, several come from the same extract, and only the annual review needs real preparation. A programme producing three well is ahead of one producing eight badly.

Most confusion in this category comes from collapsing three different numbers into one figure called “spend”.

Committed is contracted value — what the organisation is obliged to pay, including deposits and cancellation exposure. Known at contract, often months before money moves.

Actual is what has been invoiced and paid. The number finance recognises, and the only one that reconciles to the ledger.

Forecast is committed plus expected activity not yet contracted, adjusted for the historical gap between contracted and final values.

Report all three, labelled, on the same page. The gap between committed and actual is where the programme learns: if final invoices consistently exceed contracted values, either the contracting is incomplete or on-site additions are not being controlled. Neither is visible once the numbers are merged.

Variance reporting is only useful if it explains itself. A £40,000 overrun with no attribution produces an argument about whether the number is right rather than what caused it.

Categorise variance when it occurs, from a short fixed list: attendee numbers changed, scope added, dates moved, on-site additions, supplier price change, cancellation charge, currency. Seven categories is usually enough, and it turns a defensive conversation into a decidable one.

Run that for two or three cycles and the pattern is normally unmistakable — a far more tractable problem than “event costs are unpredictable”.

Meetings reporting attracts challenge more than most categories, partly because the figures are unfamiliar and partly because they often reflect badly on someone in the room.

A great deal of meetings reporting is produced diligently, circulated monthly and read by nobody. The causes are consistent and avoidable at the design stage.

It contains no decision, so there is no cost to not reading it. It goes to people without authority to act. It covers a period too short to show anything — monthly supplier concentration across forty events a year is noise presented as signal. It answers a question nobody asked, because it was designed around available data rather than decisions. Or it never changes, with no follow-up on last period’s actions.

The test is worth applying annually: for each report, name a decision made differently because of it. Anything that fails should be stopped rather than improved, and stopping a report is a legitimate outcome of a meetings governance review.