Reading the live view during an event

Who should be looking at it

Decide this before doors. The live view does not notify anyone: there are no push notifications to an organizer's phone, so its entire value depends on a person having it open. Give it to whoever is not holding a radio.

The numbers

Attendance against capacity

Attendance counts guests who checked in, excluding anyone marked as crew. Capacity is the number you set during setup. When attendance passes it, Blend'n says so — and does not refuse anybody, because the geofence covers the queue and rejecting someone there would delete them from the record entirely.

Occupancy — read this before you rely on it

Occupancy counts everyone inside the boundary, including crew, because a headcount taken for safety counts bodies rather than job titles.

It does not fall as people leave. Automatic check-out exists and is tested on the server, but the app does not yet send the presence pings that drive it. Until that ships, occupancy is cumulative: it climbs all night. Read it as "how many people have been inside" rather than "how many are inside now". It is on the roadmap as the highest-value item there.

The arrival curve and entry rate

The curve shows when people actually turned up, which is usually not when you expected. The entry rate is measured against that venue's own median for that time of night, so it tells you the doors are slow for this building — not slow compared to some industry figure. A venue's first Blend'n event has no median yet; the comparison appears once there is history to compare to.

What the chatroom is telling you

Every attendee joins the event chatroom on check-in. Messages are classified on a one-minute loop into operational categories, so what you see is a count per category rather than a wall of messages to read.

The categories:

• entry_queue — the doors
• crowding — density inside
• wayfinding — people cannot find something
• facilities — toilets, cloakroom, water
• food_drink — bars and vendors
• sound_av — sound, lighting, screens
• technical — anything else that broke
• staff_service — your team
• safety_conduct — see below

Two things escalate on their own

• Safety. Anything classified safety_conduct escalates on a single message, regardless of tone. A calmly worded report of being followed is a safety incident, not a mildly negative data point, and waiting for a pattern is the wrong behaviour.
• A sliding room. Once at least ten messages have been classified and 40% or more are negative, that is flagged as a trend rather than as individual complaints.

What it cannot see

It reads the chatroom, not the room. People who are not typing are not represented, so it is a strong sample rather than a census — and quiet does not reliably mean fine. Treat a cluster as a reason to go and look.

The short version

• Someone has to be watching — nothing is pushed to a phone.
• Occupancy is cumulative today; it does not drop as people leave.
• Over-capacity is reported, never enforced.
• Safety reports escalate on one message.
• Silence in the chatroom is not evidence of a happy room.