Stadium analytics
Stadium analytics: the city sees its asset every morning
Most cities get a report from the stadium operator once a quarter. With Bigger Picture, the city opens a dashboard every morning with yesterday’s attendance, revenue by source, spend per attendee and use of the venue.
Municipal Stadium · YesterdaySample data
Yesterday’s attendance28,640Match · round 14
Spend per attendee$ 24.80Food, drinks and merchandise
Revenue by source
Tickets61%
Food23%
Merchandise9%
Boxes7%
Days of activity · October
MatchEvent
Entries by gate
G1G2G3G4G5G6
The quarterly report arrives too late
In many cities the municipal stadium is run by an operator, used by a club and, in the end, paid for by the treasury. The city learns how its asset performed when the operator hands over the quarterly report: a PDF of totals, with no detail per event and no way to check the numbers against what actually happened at the venue.
By then it is too late to change a price, move an event or renegotiate a term. Bigger Picture stadium analytics changes the rhythm. Every ticket sale, every purchase at a food stand and every entry through a gate is recorded on the same platform, and the city dashboard is built from that record. The city no longer waits for a report. It looks whenever it needs to.
- One dashboard across matches, concerts, tours and municipal events.
- Attendance, revenue by source and spend per attendee for every date.
- Days of activity at the venue, entries by gate and capacity by section.
- Ready-made reports for the treasury and the city council.
Every morning, yesterday at the stadium
Business intelligence is not much use if someone has to go looking for it. So the summary comes to you: first thing in the morning, the person who runs the stadium gets yesterday on their phone.
- Event attendance and occupancy against the licensed capacity.
- Total revenue and how it splits between tickets, food, merchandise and boxes.
- Average spend per attendee, compared with the last event of the same type.
- The busiest gate and the entries rejected at validation.
The notification opens the full dashboard, with detail by section, by stand and by hour. Each role gets only the summary that belongs to it.
7:005G
At the stadium · 7:00Yesterday
Concert: 31,200Stadium · now
Revenue$1.12M
Per attendee$26.10
Occupancy96%
Busiest gateG3
Rejected entries12
Sample dataMonth closedTo treasury
What each role sees
All the data lives on one platform, but each organisation sees its own. Permissions are set by role, and data separation between organisations is built in.
The whole asset, not just the match
The city sees the stadium as an asset: how many days it was used, how many people came, what each revenue source produced and how one month compares with the next. It does not need fans’ personal data to make those decisions.
- Days of activity and use of the venue by event type.
- Revenue by source and spend per attendee, by date and by period.
- Reports for the treasury and the council, in the same format every time.
The day’s operation, in detail
The operator sees what it needs to run the venue: sales by channel, stock at every stand, cash-up per shift and live entries by gate.
- Tickets, food and merchandise in a single record.
- Cash control per shift and live stock.
- One calendar for matches, concerts, tours and events.
Its fans, its season tickets, its campaigns
The club sees its fans: season ticket holders, renewals, how often they come and what they spend. That data belongs to the club. A concert promoter or another organisation using the same stadium does not see it.
- Season tickets and renewal status.
- Attendance and spend by fan segment.
- Sales by match, section and channel.
Capacity and entries, in real time
Security sees entries by gate and by section, the capacity of each zone and the entries rejected at validation. It does not see revenue or commercial data.
- Entries by gate and by hour, against the capacity of each section.
- Rejected entries and the validation reason.
- An audit log of every entry.
Ask the data
The AI data assistant is part of the analytics module. It answers natural-language questions about sales, attendance and capacity, using the same data as the dashboard and respecting the permissions of whoever is asking.
- Ask the way you talk: “how many days was the stadium used this quarter?”
- Compare events, months and seasons without building a spreadsheet.
- Answers come with charts you can drop into a report.
- Every answer uses only the data your role is allowed to see.
✦Data assistantBigger Picture AI
How many days was the stadium active in Q3, and what did each type of event bring in?
AnswerThe venue was active on 41 days: 19 matches, 6 concerts, 9 tour days and 7 municipal events.
Matches$ 3.2 M
Concerts$ 2.0 M
Tours, events$ 0.4 M
Which match had the highest spend per attendee?
AnswerRound 9, at $ 27.90 per attendee. 64% of food spend came during half-time.
Add to the council report
Add to the council report
Ask about sales, attendance or capacity…↑
Conversation with sample data
Reports for the treasury and the council
The dashboard is for day-to-day work. Accountability needs formal reports, in the same format every time, without anyone copying figures from one system into another. The platform produces them from the same record of sales, entries and cash-ups.
| Report and audience | What it covers |
|---|---|
| Daily summary Stadium management | Attendance, revenue by source, spend per attendee and entries for the previous day. |
| Monthly close Treasury | Revenue by event and by source, reconciled with the cash-ups. |
| Venue use report City council | Days of activity, event types, attendance and discounts given to residents, students and seniors. |
| Season report City and club | Attendance per match, season tickets, occupancy by section and a comparison with last season. |
From quarterly report to daily data
You do not have to change everything at once. Most stadiums take this path in stages.
1
Quarterly report
The operator sends a PDF of totals, months after each event.
2
Monthly close
Spreadsheets put together by hand from box office, tills and gates.
3
Daily dashboard
Every sale and entry in one record, with yesterday’s summary each morning.
4
Decisions on data
Natural-language questions, automatic reports and open data through the API.
Separate data, role permissions
A municipal stadium brings several organisations into one place: the city, the operator, the home club, concert promoters. Sharing the platform does not mean sharing all the data.
- Data separation by organisation: each one sees only its own.
- Role permissions inside each organisation, from the treasury to the gate supervisor.
- The city sees the asset in aggregate figures; the club sees its fans.
- An audit log of every query, change and export.
What each organisation can see is set in the agreement between the city, the operator and the club. The platform applies those rules in the dashboard, in reports, in the AI assistant and in the API.
Exports and an open API
Stadium data does not have to stay in the dashboard. Any report exports to a spreadsheet, and the open REST API lets you send sales, attendance and entries to the city’s finance system, its own data warehouse or the business intelligence tool it already uses.
With webhooks, partners receive events as they happen: a sale, a cash-up, an entry. The platform is cloud-native, so there are no servers to look after at the venue.
A platform already running at scale
~70venues in operation
500screens and spaces
8countries
20 M+tickets sold
Today the platform runs cinemas, attractions, live venues and basketball and handball clubs, with offices in Israel, Bulgaria, Mexico and Argentina. The dashboards and reports those venues use every day are the foundation of our stadium analytics, whether the game is football (soccer, for US readers) or baseball.
Related use cases
Frequently asked questions
What is stadium analytics?
It is the set of dashboards, reports and queries that show how a stadium performs: attendance, revenue by source, spend per attendee, days of activity and capacity. In Bigger Picture it comes from the same record where tickets, food and entries are sold and validated.
Can the city see the data if a third party operates the stadium?
Yes, if the agreement between the parties provides for it. The city gets its own access with role permissions and sees the asset in aggregate figures, without waiting for the operator’s quarterly report.
Does the club share its fan data with the city?
Not by default. Data is separated by organisation: the club sees its fans and the city sees the use and revenue of the venue. What is shared is defined in each project.
What can the AI data assistant answer?
Natural-language questions about sales, attendance and capacity, such as how many days the stadium was used or which event had the highest spend per attendee. It is part of the analytics module and respects each role’s permissions.
Can we take the data into our own systems?
Yes. Reports export to a spreadsheet, and the open REST API, with webhooks, lets you send sales, attendance and entries to the city’s systems or to its partners.
See your stadium on one dashboard
We review what data the city receives today and how often, and show you what the morning summary would look like for your own venue.
Keep reading: stadium management software theatre and event ticketing family entertainment center software