A room occupancy counter is a tool that tracks how many people are currently inside a room by recording entries and exits separately, then showing the net current headcount as a live number. Unlike a one-way tally that only counts events, an occupancy counter subtracts exits from entries so the visible number always represents the people inside right now. The People Counter tool in your browser does exactly this: you press "Record entry" when someone walks in and "Record exit" when someone leaves, and the page displays "Current people" as the running net total. The counter is disabled from dropping below zero, which means an accidental extra exit cannot produce a misleading negative figure. Entered and exited totals are saved separately for each local calendar day, so you can review how arrivals and departures shaped the room's occupancy over time. Because every interaction is a deliberate manual click, the number reflects the operational record you actually kept, not an automated guess about who is standing where.
What "Room Occupancy" Tracking Actually Means
An occupancy count is not the same thing as a tally. A tally simply adds up events: every press is plus one, and the visible number grows forever. That works when you want to know how many tickets were sold, how many cars pulled in, or how many reps were completed. It does not answer the question "how many people are inside this room right now," because exits are not subtracted.
A room occupancy counter, by contrast, is built around two-way movement. Every time the door opens inward, the counter records a new entry. Every time the door opens outward, it records an exit. The headline number on the page — "Current people" — is the net of those two streams. That makes it useful for any room where arrivals and departures both happen: a small meeting room, a quiet study room, a fitness studio, a clinic waiting room, a workshop space, or a community room with a stated capacity.
The key practical detail is what happens when arrivals and departures are out of balance. If a class lets out and people file out faster than new ones enter, the current count falls. If a session is filling up, the current count climbs. Watching the live number gives the front-of-house team a continuous read on whether a room is filling toward its limit or emptying out, which is the question an occupancy counter exists to answer in the first place.
Why Manual Counting Still Works for Rooms
Door sensors, cameras, badge readers, and time-of-flight sensors are all real ways to count people in a room. They are also expensive, require installation, and produce data on a server. For a single small room — a yoga studio running three classes a day, a community centre managing open hours, a church hall with a childcare room, or a co-working space with a quiet study — the operational question is usually simpler than that.
For those settings, a manual occupancy counter that lives in a browser tab on the front desk is often enough. Someone presses entry when a guest arrives and exit when they leave, and the running net count tells the team at the door exactly what they need to know: how many people are inside. Because the record is kept in the browser, no account, server, badge, or special hardware is required to start.
The trade-off is clear and worth naming: a manual counter only knows what you choose to record. If staff forget to press the button, the count drifts. That is not a defect — it is the deliberate scope of a private, local tool. When you need an automated reading of who walked through which door at what time, you are looking for a different kind of system entirely.
How to Use People Counter for Room Occupancy
- Open People Counter on the device you plan to keep at the door — front desk, side counter, or a laptop by the entrance.
- If you have a target occupancy in mind, type a whole number into the capacity alert field before the room opens. This sets an operational reminder that triggers when the current net count reaches or exceeds your chosen number. You can leave it blank if you do not want a threshold.
- Each time a guest arrives, press "Record entry." The page adds one to the entered total and increases "Current people" by one.
- Each time a guest leaves, press "Record exit." The page adds one to the exited total and decreases "Current people" by one. The exit control is disabled when the current count is already at zero, so a stray press cannot push the number negative.
- Glance at the "Current people" value whenever a question comes up at the door — it is the live occupancy reading.
- At the end of the day, open the daily history section to confirm the entered, exited, and net totals recorded for the date.
- If you need a file outside the browser for reporting, export the day's record as PNG or CSV using the export controls on the page.
A simple worked example: if you record 12 entries and 5 exits by 2pm, the current people in the room is 12 minus 5 = 7. If the capacity alert is set to 10, the page would not yet be showing the alert, because the current net count of 7 has not reached 10. The threshold fires at or above your chosen number, not below it.
Reading the Entered, Exited, and Net Numbers
Each local calendar day in People Counter keeps three separate values. The first is Entered, the total number of entry clicks for that day. The second is Exited, the total number of exit clicks for that day. The third is Net, which is Entered minus Exited and represents the occupancy carried out of the day.
Splitting these into three columns matters for a reason that becomes obvious during review. A single unexplained total — say, "34" — tells you nothing about whether the room had 34 entries and 0 exits, or 100 entries and 66 exits, or some other combination. Splitting the count into entries and exits shows you the flow that produced the number, so a sudden spike in net can be traced to either a burst of arrivals or a slow trickle of departures.
| Field shown on the page | What it represents | Why it is shown separately |
|---|---|---|
| Entered | Total entry clicks recorded for the local date | Reveals the arrival side of the day's traffic |
| Exited | Total exit clicks recorded for the local date | Reveals the departure side of the day's traffic |
| Net | Entered minus Exited for the local date | Matches the "Current people" value carried out of the day |
When a new local day begins, the visible current count resets to zero and earlier nonzero days remain in the history. That means a count made near midnight stays on the day it happened rather than shifting because of a UTC boundary — a small detail that matters when an evening session crosses midnight and the team needs to reconcile the two days cleanly.
Setting a Capacity Threshold Without Overclaiming
The capacity alert field is an optional feature. When you fill it in with a whole number, the page starts showing a clear alert as soon as the current net count reaches or exceeds that value. If you leave it empty, no alert is shown and the counter behaves purely as a record.
It is important to keep two limits in mind. First, the threshold is only as accurate as the manual record behind it — if staff forget to press entry or exit, the alert fires off the actual recorded occupancy, not the real one. Second, the alert is an operational reminder, not a safety certification, fire-code determination, legal occupancy calculation, or access-control system. Treat it the way you would treat a sticky note on the door: useful for keeping an eye on the room, but not a substitute for trained staff, posted limits, or local regulations.
In practical terms, set the threshold slightly below the room's real limit so the alert gives your team a chance to pause before the room is genuinely full. For a room with a posted limit of 25, a threshold of 22 or 23 is usually a sensible operational cushion.
Exporting the Daily Record
People Counter offers two export formats, both generated in the browser with native canvas and Blob APIs. Nothing is uploaded, so the file you save is the only copy that exists.
- PNG — a 1080 by 1350 summary image that includes the Lizely mark, the total figure, and recent date rows. It is a quick way to drop a screenshot into a chat or a printed schedule without exposing a URL.
- CSV — a plain text file with the columns Date, Entered, Exited, and Net people, with one data row for every saved local date. It opens directly in any spreadsheet for sorting, filtering, or further analysis.
Use PNG when the goal is a visual summary that anyone can read at a glance. Use CSV when the goal is to combine the day's numbers with other operational data — for example, a class roster, a shift schedule, or a monthly capacity review. Both files stay on your device unless you choose to share them.
When a Manual Counter Is Enough — and When It Is Not
People Counter fits naturally into the daily rhythm of a small staffed room: a door that one person watches, a steady flow that does not outrun the click rate, and a team that wants a private local record rather than a connected platform. For those settings it does the job well, and the daily history is enough to answer "how busy were we today."
If you need a reading from a sensor, a camera, or an automatic door tally, a manual browser counter is the wrong tool. For a fuller comparison of manual entry versus sensor-based systems, see Manual vs Sensor People Counter: A Practical Choice.
| If the operational question is | A closer-fitting tool | Why |
|---|---|---|
| How many times did an event happen today? | Online Tally Counter | A simple one-direction counter is enough when exits do not matter |
| How do several groups compare side by side? | Multi Counter | Multiple labelled counters live in one daily record |
| Have I kept up a personal streak? | Daily Habit Counter | Built for daily streaks and habit labels, not room flow |
| How many people are inside right now? | People Counter | Two-way movement plus an optional capacity threshold |
Pick People Counter when the distinct need is two-way movement plus a manual capacity threshold. Pick something else when the question is just "how many taps" or "which habit did I keep today" — those tasks are better served by tools built for them.