How to Audit a Festival Attendance Claim Before You Report It to a Sponsor

Before an attendance figure leaves your building and lands in a sponsor's inbox, it should survive an audit — yours. Learning to audit a festival attendance claim is a fifteen-minute skill that saves you from the worst moment in this business: a number you reported getting picked apart in a renewal meeting. Whether the claim is your own, a co-organizer's, or a venue's, the same five questions decide whether it is evidence or a hostage to fortune. This is the checklist, plus the red flags that should stop a claim before it ships.

Key takeaways

• Audit any attendance claim against five questions: method, error range, source, coverage, and honesty about the hard parts.
• A defensible report states its method, discloses error bars, shows in/out and occupancy, and can be verified independently.
• Red flags: a single confident number with no range, a headline accuracy percentage with no evidence, and ticket counts sold as total attendance.
• Self-audit first, but the strongest position is an independently produced count with a verification page a sponsor can open.

Why audit before you report, not after

The cost of a weak attendance number is not paid when you write it down. It is paid months later, when a sponsor's finance team or a grant auditor questions it and you have nothing behind it. By then the figure is public and walking it back is worse than the original doubt. Auditing before you report flips the timeline: you catch the weakness while you can still fix it — by getting a better count. It is the same discipline as never trusting an unverified number, applied one step earlier.

How to audit a festival attendance claim: five questions

Run every claim through these. If it fails one, it is not ready.

1. What method produced this number?

Ask for one sentence: how was it counted? "Line-crossings from gate video across all four entrances" passes. "Security's estimate," "we rounded up from ticket sales," or a shrug fails. No method means nothing to audit — the number is an assertion. The pillar guide, how to count event attendance, covers what good methods look like.

2. What is its error range?

A claim with no error range is hiding its uncertainty, not lacking it. A defensible figure is a band — "34,000–36,500" — not a suspiciously exact single number. Be more trusting of a claim that admits a range, and suspicious of one that does not. And treat any bare "99% accurate" headline as a red flag in itself: real accuracy depends on footage, angle, and density, so a single blanket percentage is marketing, not measurement.

3. Can the source be checked independently?

This is the one that separates evidence from storytelling. Can a sponsor confirm the number without taking your word for it? A verification page, a raw count file, an annotated clip that shows the count happening — any of these lets an outsider check. If the only source is "trust us," the claim cannot survive a determined counterparty.

4. How much of the event did it actually cover?

A figure projected from fifteen minutes of the quietest gate is not the same as a full-event count, even if it prints the same way. Ask what fraction of the event was observed and at what confidence. A responsible claim states its coverage and marks a thin sample as indicative rather than dressing it up as a settled total — the logic of sampling done honestly.

5. Are the hard parts treated honestly?

Dense crowds, dark footage, congested gates — these are where counts get least certain. A trustworthy report flags those intervals with wider error bars and says so. A claim that presents its crush hour with the same false precision as its quiet open is either naive or hiding something.

What a defensible Attendance Report must contain

If you are producing the claim yourself, this is the bar to clear. A defensible Attendance Report contains:

• a stated method in plain language;
• in/out totals with a disclosed error range, not a single confident figure;
• an occupancy curve and an hourly profile so the number has shape, not just size;
• a coverage and confidence statement saying how much was observed and how strongly it projects;
• a quality note listing any footage issues (low light, shake, small subjects);
• an independent verification route — a QR page or link a sponsor opens themselves;
• and a frank limitations section.

That last one matters more than it looks. A report that names its own weak spots is more credible than one that pretends it has none. We walk through each of these in how to read your Attendance Report.

The red-flag shortlist

Stop a claim if you see any of these: a single confident number with no range; a total that exactly matches last year's press figure; a headline accuracy percentage with no evidence; ticket scans presented as total attendance at a free-entry event; or any figure with no method attached. Each is a sign the number was asserted, not measured.

The strongest position: an independent count

You can pass your own audit and still be vulnerable, because you produced the number and you benefit from it being large — the conflict-of-interest objection every sponsor knows to raise. The cleanest answer is a count produced independently, with a verification page the sponsor checks themselves. That is exactly the artifact GateProof is built to hand you, with its error bars and QR verification baked in. If you want the maths behind the error and confidence language, see what "accurate" really means.

Before your next report goes out, run the claim through the five questions — and if it wobbles, get a real count. Count your gates with a $199 Event Report at your next event to see a claim that passes its own audit, then check the pricing to certify the whole thing.