Legacy Balance Sheet
After the festival: what visitors loved, what services owed, what residents paid.
The job
Separates what visitors loved at each festival or major event from the city services that failed them and the cost residents carried. Books each problem to the agency that owns it, carries unsettled ones into the next edition, and judges the legacy after 90 days.
The moment
At the season review, the events CEO expects to be blamed. Set out like a company's annual accounts, the statement shows the festival was the asset: 71% of visitor comments were delight in the shows.
The biggest liability, 38% of complaints, is the park-and-ride shuttle run by the transport department. It started on day three, was never fixed, and has now carried over into a third edition of the festival.
Two districts carried three weeks of parking complaints. By contrast, last edition's ticketing queue is stamped "debt cleared" by the ticketing operator.
Ninety days later, the lasting impression differs by visitor market: a short-lived buzz for one, and a lasting boost of 12% for another.
The minister says: "For the first time we could see the festival is our asset and our services are the debt."
What it does
- Book yesterday into the running statement
- Close the edition and build the statement
- Book a liability to its owning agency
- Record the owner's remediation plan
- Send the one-page legacy statement
- Open any figure's note to the accounts
What you see
An audited annual statement per edition with notes to the accounts and an auditor's opinion stamp, a daily running statement during the event, and a multi-year debt maturity schedule.
What it moves
The share of carried-over problems settled at each edition, cleared rather than rolled over, and the verdict 90 days later on whether each visitor market's boost lasted.
Built for
- Operations
- Executives & leadership
- CX leaders & VoC
