Construction Site Technology
Why Digital Occupancy Counts Can Differ From the Actual Number of People
Published 24 August 2026
A digital occupancy count is a count of confirmed movements the system received. The actual number of people is a physical fact. They can differ, and the difference is usually an operational gap rather than a mysterious software error.
Two counts that look similar
A dashboard occupancy figure is usually the number of people whose last confirmed scan points at that area. A supervisor counting heads is counting bodies. On a quiet morning those numbers can match. They stop matching as soon as someone moves without leaving a record, or leaves a record without matching the move they actually made.
This article is about the operational reasons that gap appears. A related article, Occupancy Count vs. Actual Headcount, explains the same difference from the system’s point of view. Neither article is a site-specific procedure.
Missed scans
The most common cause is a person who uses a stair, opening, or hitch with a colleague and does not scan. The previous recorded area stays in place. The destination area is then short, and the previous area may look more occupied than it is.
Missed scans increase when the code is hard to see, when the landing is congested, or when the movement feels too short to “count.” Placement and a single clear meaning for each code reduce this. They do not eliminate it.
Duplicate scans and the wrong code
Scanning twice at the same point may not change occupancy if the person is already recorded in that destination. Scanning the wrong code — two prints close together, an old print left after a diversion, or a code meant for the opposite direction — can move the record to the wrong area while the person walks somewhere else.
From the dashboard this looks like a confident number. On the floor it is a confident wrong story. Retiring old prints when routes change is as important as putting up new ones.
Devices, networks, and shared phones
A phone that cannot open the page, a basement with no signal, or a confirmation that never finishes sending leaves the last successful record in place. Shared phones record one profile, not two people. Private browsing or cleared site data can force a recovery step, during which occupancy may lag behind the physical move.
These are not reasons to ignore occupancy. They are reasons to read it as a log of received events.
Temporary access changes
When a stair is closed and people are sent around another way, occupancy will follow the codes that are still being scanned, not the cones on the floor. If the diversion has no QR point, people will arrive in an area without a matching record.
Treat access changes as occupancy changes: move or cover codes, and do not leave a live print on a closed route.
An operational aid, not the emergency method
Digital occupancy can help a site office see unusual build-up, notice that an area still has people recorded at the end of a shift, or support a discussion about who was last confirmed in a zone. It must not be treated as the sole emergency headcount method.
People missing from occupancy may already be outside. People still listed in an area may have left without scanning. Emergency instructions, assembly arrangements, and the project safety team’s process remain in charge. The screen does not replace them.
Reducing the gap in day-to-day use
The practical work is ordinary: put codes where people can pause, give each code one movement meaning, retire prints when routes change, and remind people that occupancy only updates after a completed scan. Compare the dashboard with what supervisors see on the floor, and treat a persistent mismatch as a placement or process problem rather than a reason to trust the larger number.
QR and RFID have different failure modes. Neither produces a guaranteed physical count. The useful standard is better operational awareness than a paper list that nobody updated, with the limitations left visible.