Planning Camera Coverage Without a Camera Count

Camera projects are often specified backwards: a count is chosen, devices are distributed, and the first real incident reveals what the system cannot actually show. A better starting point is the list of events the building needs to observe—then coverage, positioning, and budget follow from that list.

Start with observed events, not devices

Write down what the recording must be able to answer. Who entered through this door? What happened at the loading dock? Was the visitor area occupied? Each question implies a location, a field of view, and a level of detail—identifying a person is a different requirement from confirming that an area is occupied, and the difference changes lens, placement, and cost.

Sightlines, mounting, and lighting decide image quality

A capable camera in a poor position produces poor evidence. Review the actual sightlines: obstructions, mounting height, backlighting from glass entrances, night-time lighting levels, and seasonal changes like landscaping. These conditions—not the specification sheet—determine what the recording is worth. This is why a site walk belongs in the proposal stage, not after installation.

Retention and review are scope items

How long footage is kept, at what quality, and who reviews it are decisions with real storage and cost consequences. Longer retention or higher resolution multiplies storage; motion-based recording reduces it but changes what is available after the fact. Decide retention from operational and any regulatory needs first, then size storage—not the reverse.

The network is part of the system

IP video is network infrastructure: switch capacity, power-over-Ethernet budgets, pathway to camera locations, and head-end space all belong in the scope. Confirm who provides the network components and who configures them, or the gap will surface during commissioning.

Privacy expectations are a design input

Commercial video systems observe employees, tenants, and the public. Coverage areas, signage, retention, and access to footage should reflect the property's privacy obligations and policies from the start—retrofitting restraint is harder than designing with it.

Questions to settle before comparing proposals

• Which events must the system be able to reconstruct, and at what level of detail?
• Has each proposed location been evaluated on site for sightlines and lighting?
• What retention period is required, and what storage does it imply?
• Who owns network provisioning, configuration, and cybersecurity basics?
• Who may access footage, and how is that access controlled and recorded?

Every building answers these differently, which is the point: coverage planned from the building's own requirements beats a camera count copied from the last project.