Most festival governance structures are designed in a calm month and tested in the loudest week of the year. The ones that hold up share a few decisions made early.
Decide who can say no
A festival has dozens of vendors and one opening date. The PMO must hold explicit authority to stop a change that puts the date at risk, and that authority has to be written into vendor contracts, not assumed.
One change log, not one per vendor
Every scope change, whatever its size, goes through a single register with a cost, a schedule impact, and a named approver. The register is the only document leadership reads in the final month.
Report by exception
A weekly deck with forty green boxes hides the one red one. From six weeks out, the PMO reports only what has moved, what is at risk, and what needs a decision this week.
Plan the closeout before the opening
Benefits realisation, vendor performance reviews and the impact assessment are scheduled before the event, with owners. Otherwise the team disperses on the last night and the learning leaves with it.
Example article. Author and role are placeholders.