What Blend'n does for organizers

The shape of it

Blend'n covers the hours an event is actually happening. Everything before the doors open — selling, registering, marketing — belongs to other tools, and everything after belongs to a survey. Blend'n sits in the middle, which is the part nobody watches.

Four things happen, in order:

1. You define the venue boundary. A circle, or a polygon traced around the building.
2. Attendees check in on their own phone. The check-in is validated against that boundary, with the device's reported accuracy folded into the decision.
3. They join the event chatroom automatically. It is pseudonymous and moderated.
4. You watch the live view, which shows the numbers and what the chatroom is reporting, updated as the event runs.

The three numbers, and why they are not one

Most tools report a single attendance figure that only ever goes up. Blend'n keeps three, because organizers ask three different questions and collapsing them is how a room reads "full" on one screen and "over by eight" on another.

What the live view looks like

Attendance against capacity, the arrival curve, and the entry rate measured against the venue's own median for that night — so "fast" means fast for this venue rather than fast in the abstract.

Over capacity is shown, not enforced

When a room passes the capacity you set, Blend'n tells you. It does not refuse anyone's check-in.

That is deliberate, and it is the one design decision here most worth understanding. Your geofence covers the queue on the pavement. Blocking check-in at the limit would remove the hundred-and-first person from the chatroom and erase them from your attendance record — you would finish the night believing a hundred came when a hundred and twenty did. Turning people away is the door's job. Knowing that you need to is ours.

What the chatroom is for

Every attendee who checks in joins a pseudonymous chatroom for the event. Messages are classified into operational categories on a one-minute loop while the room is open, so a cluster becomes visible as it forms:

• entry_queue, crowding, wayfinding
• facilities, food_drink, sound_av, technical
• staff_service, safety_conduct

Anything matching safety_conduct escalates regardless of tone, because a calmly worded report of being followed is a safety incident, not a mildly negative data point.

What it does not do — read this part

Stated plainly so nothing here is a surprise on the night.

• Occupancy does not fall as people leave. Automatic check-out is written and tested on the server, but the app does not yet send the pings that drive it. Today the number climbs all night and never drops. This is the single most important limitation on this page.
• Nothing is pushed to your phone. Everything surfaces on the live event screen, which somebody has to be looking at.
• It reads the chatroom, not the room. People who are not typing are not represented.
• No ticketing, payments, registration forms, badge printing, sponsor management or session agendas. Run Blend'n alongside a ticketing platform, not instead of one.
• No heatmaps, dwell time, custom branding or mood scoring. These are on the roadmap and are not built.