Construction Site Technology
Occupancy Count vs. Actual Headcount
Published 19 August 2026
System occupancy is a count of last confirmed areas. A physical headcount is a count of people. They can disagree, and the disagreement is expected when scans are missed.
Two different numbers
An occupancy count in a QR system is usually: how many active registered users currently have this named area as their last confirmed destination. An actual headcount is: how many people a responsible person can account for in a place, or after an assembly, using the site’s own method.
Those definitions look similar on a quiet morning when everyone scans. They diverge as soon as someone moves without scanning, scans late, scans the wrong code, or never reaches the server. Treating the dashboard as if it were a camera count hides that difference.
Missed scans
The most common gap is a movement that happened in the building but never became a confirmed record. A person takes the stairs, follows a colleague, or uses a route that has no code. The recorded area stays where it was. Occupancy on the destination floor is then too low, and occupancy on the previous floor may be too high.
Busy landings, damaged prints, and simple forgetfulness produce the same effect. The software can only count events it received. It cannot invent the scans that were never made.
Shared devices and operation errors
If two people use the same phone, the identification stored in that browser belongs to one profile. Confirming a move records that profile, not both people. If someone selects the wrong recovery candidate, later occupancy follows the wrong person. Those are operational errors. They change the numbers without a matching change in who is actually standing in the area.
Private browsing and cleared site data can also force a recovery step. Until that step is finished, a returning person may not be recognized. Occupancy then lags behind the physical movement even if the person is already on the destination floor.
Network and device issues
Basement levels and temporary work areas often have weak mobile coverage. A scan page that never finishes sending the confirmation does not update occupancy. Low battery, an interrupted browser, or a phone that cannot open the page have the same outcome: the last successful record remains in place.
From the dashboard, this looks like a stable occupancy figure. On the floor, people may already have moved. The figure is still a correct count of received confirmations. It is not a guarantee of current physical presence.
Using occupancy during an emergency
In an incident, administrators may look at last recorded areas as one clue: who was last confirmed in B2? That can support a search or a roll-call. It cannot replace the site’s emergency instructions, assembly arrangements, or a physical accounting of people.
People missing from occupancy may already be outside. People still listed in an area may have left without scanning. Both mistakes are dangerous if the number is treated as complete. The safe reading is: this is the last confirmed record, and it may be incomplete or stale.
Do not use the system number as the only check
Occupancy is an operational aid. It is useful for ordinary shift visibility and for noticing unusual patterns. It is not the sole emergency headcount method, and it should not be described that way in site procedures.
If a number on a screen and a number from a physical count disagree, the physical process required by the project takes priority. Investigate missed scans later. Do not delay an evacuation or an assembly because a dashboard has not caught up.