Skip to content
Sections
All notes

All notes · Methods

Cameras and Vision Counting

The most capable method and the one with the highest cost in trust. When it is warranted and what has to be settled first.

Methods · Analysis

Cameras with counting software give accurate headcount, dwell time and movement. They also put a camera in the room, which changes the conversation entirely.

The technical evidence in “Cameras and Vision Counting” describes the building, while the effort required to install, test and maintain it is project work. When teams research remote desktop monitoring software, this workplace tool can provide time and project context for that operational effort without replacing the sensor platform as the source of truth for physical occupancy.

What it does well

Accurate counting, including in crowds where thermal merges people.

For a public, independent reference related to “Cameras and Vision Counting”, consult the NPSA protective-security guidance. Its principles provide a useful check on scope, terminology, governance and the claims made during procurement or review.

Dwell time and flow, from the same device.

Zone-level detail within a large space.

And it works on existing cameras in many buildings, which is both an advantage and the source of the main problem.

The reuse problem

A security camera repurposed for occupancy analytics is a change of purpose.

Staff were told the camera was for security. Using it for space planning without saying so is the kind of thing that, when discovered, ends the trust in the whole programme.

Tell people. Before, not after. This is also a legal requirement in several jurisdictions and its own note covers the obligations.

Edge processing

The distinction that matters: does the image leave the device?

Edge processing analyses the frame locally and transmits a count. Nothing identifiable goes anywhere.

Cloud processing sends the image.

Insist on the first, get it in writing, and verify it rather than accepting the datasheet — ask what network traffic the device actually produces.

What to settle before installing

Written purpose, and whether it overlaps with security use.

Whether images are stored, where and for how long.

Who can access the live feed.

Whether the system does any identification, including face detection used only for counting.

And consultation, which for cameras is rarely optional and should start before procurement rather than after.

Where it is warranted

Large open areas where counting matters and other methods merge people.

Entrances with high flow.

Spaces where a one-off study will answer a significant question, after which the cameras come out.

A temporary study is frequently the right shape, and it is rarely what suppliers propose.

Where it is not

Desk-level occupancy, where infrared is adequate and far less intrusive.

Small rooms, where a count of four does not justify a camera.

And anywhere the trust cost exceeds the information gain, which is most places and is a judgement rather than a calculation.

The proportionality question

Several data protection regimes require you to consider whether a less intrusive method would achieve the purpose.

For most occupancy questions, one would.

Which means the written justification for cameras has to explain why thermal or infrared was insufficient, and if it cannot, that is the answer.

What to check

Does the image leave the device, verified rather than claimed?

Were staff told, before installation?

Could a less intrusive method answer the same question?

And is there a written purpose separate from security?