VIEW-ONLY VENUE POPULATION β€” shared by the organiser
TEST ENVIRONMENT β€” explore freely, nothing you do here is saved.
Venue Population Β· For event organisers

How many people are on site at three o'clock on Saturday? Know the number.

Venue Population estimates who is at your venue during every sub-event, by customer group β€” spectators, teams, media, broadcasting, staff β€” and does the capacity math for you. Peaks flagged, totals computed, front of house and back of house split. Built by an event director, not a software company.

  • Your customer groups and sub-groups become the columns β€” automatically
  • Every row totals itself; no formula to break, ever
  • % of capacity live β€” gold at 90%, red over the line
  • Peak Board: capacity bars per sub-event for the safety meeting
  • Data owners and confidence per group, so estimates have names

Log in.

or
The free test runs on an example event. Nothing is saved.
Bought the app? Your login was emailed after purchase.
Β© Bonacube Oy Β· Saanakatu 20, 15840 Lahti, Finland Β· jesse@bonacube.com

My events

All projects saved in this browser. Accounts & cloud sync come with the Pro version.

Share view-only link

The whole population model travels inside the link β€” no account needed. Recipients see a read-only copy (a snapshot of this moment; re-share after changes).

How to use Venue Population.

One row per sub-event. One column per customer group. The totals compute themselves.

1 Β· What a venue population model is

An estimate of how many people are at your venue, at what time, and who they are. You need it for capacity and crowd safety, and every function reads it for its own dimensioning: catering counts mouths, security counts gates, transport counts arrivals, cleaning counts toilets. One model, many readers.

2 Β· Customer groups β€” the columns

The πŸ—‚ Customer groups tab is the master list: main groups (Spectators, Teams, Media, Broadcasting, Event staff…) with their sub-groups. Every sub-group automatically becomes a column on every venue sheet. Add a group there β€” or straight from a sheet's οΌ‹ column header β€” and it appears everywhere. Each main group is front of house (public) or back of house (accredited); the split is computed for you.

3 Β· Venues β€” the tabs

One tab per venue, each with its own maximum capacity. Stadium, team compound, media centre, fan zone β€” if it has a fence and a capacity, give it a tab. The capacity drives the % column and the warnings.

4 Β· Days and sub-events β€” the rows

Days are the navy rows. Under each day, list the sub-events from your programme: delivery window, training, gates open, competition, ceremony, egress. Times are approximate on purpose β€” this is a population model, not the rundown. Then estimate each group's headcount per row. Empty means not estimated yet; zero means zero β€” the difference matters, and the readiness bar tracks it.

5 Β· The math you never write again

Row totals, group subtotals, % of capacity β€” computed, always, for every row. At 90% of capacity the number turns gold; over 100% it turns red. The biggest row of each day carries the PEAK tag. There is no formula to overtype, stretch one column too far, or quietly sum the wrong range.

6 Β· Data owners and confidence

Every group has an owner, a data source and a confidence level β€” from guess to confirmed. That's the honest part of population modelling: the number is only as good as its source, so the source has a name and the name has a deadline. The readiness bar counts estimated cells; the confidence column tells you which ones to trust.

7 Β· Peak Board β€” the capacity view

β–Ά Peak Board is the full-screen view for the safety and security meeting: every sub-event as a bar against venue capacity, the 90% line in gold, the capacity line in red, the peak flagged, front of house / back of house split on top. Pick a venue and a day, or show the whole event. It prints as an A4 capacity report for the authorities. πŸ”— Share sends a view-only link, including a direct Peak Board link.

8 Β· Saving

Everything saves automatically in this browser. πŸ—‚ My events holds all your event projects. – Save file / β€’ Open file in the top bar move an event between computers or into your archive as a file.

Want the worked example as a reference? πŸ—‚ My events β†’ οΌ‹ Example event. Your own events start clean.

Paste sub-events

Paste customer groups

From the group library

Group structures from real events, genericised. A structure adds several main groups at once; a single group adds one. Nothing is overwritten β€” the library only adds what you don't have.