How to Specify CCTV System for Business Sites

Most CCTV problems do not start on installation day. They start much earlier, when the brief says “cover the site” and nobody pins down what that actually means. If you are working out how to specify CCTV system requirements for a business customer, the job is less about picking cameras and more about defining outcomes, constraints and evidence quality before anything is ordered.

A good specification protects everyone involved. The end user gets a system that does what they expect. The installer avoids return visits, underpowered PoE budgets and awkward conversations about blind spots. Procurement gets a clear schedule of equipment rather than a vague shopping list. On commercial jobs, that clarity matters just as much as the cameras themselves.

How to specify CCTV system requirements properly

The starting point is always the site objective. A warehouse wanting to deter opportunist theft needs something different from a school that must monitor access control points, or a retail unit investigating till disputes. “General coverage” is not a useful design standard on its own. You need to know whether the customer wants deterrence, detection, recognition or identification, because each one drives different camera positioning, lens choice and image quality.

This is where many specifications go wrong. A client may ask for high definition cameras everywhere, but if the real requirement is facial identification at entrances and number plate capture at the gate, blanket 4MP domes will not solve the problem. The right approach is to break the site into scenes and assign a purpose to each one.

External perimeter coverage, car parks, loading bays, reception desks, cash handling points, corridors and plant rooms all have different risks. Once the purpose of each scene is clear, the rest of the specification becomes much easier to justify.

Start with risk, not products

A proper survey should look at access routes, lighting conditions, asset value, incident history and operational hours. A small office with a single front entrance might only need a focused system with a few well-placed cameras. A transport yard with mixed pedestrian and vehicle movement, poor lighting and long perimeters needs a more layered design.

It also helps to ask what happens after an incident. If the customer needs usable footage for police, HR or insurers, then image quality and retention become business-critical. If they only want broad visibility to check activity after hours, the system can often be specified more efficiently.

Coverage, camera type and positioning

Once you know what each area must achieve, you can decide on camera type. Turrets are often preferred for general commercial use because they are straightforward to install and less prone to the IR reflection issues that can affect some domes. Domes still have a place indoors where tamper resistance or aesthetics matter. Bullet cameras suit longer views and obvious visual deterrence. PTZs can add value on larger sites, but they should not be treated as a replacement for fixed coverage.

Positioning matters more than headline resolution. A badly aimed 8MP camera will still miss the shot that matters. Mounting height, angle of approach, expected subject distance and the direction of available light all affect whether footage is genuinely useful. At entrances, aim for frontal views rather than steep top-down angles. In corridors and choke points, use the layout to your advantage and force subjects through known fields of view.

There is always a trade-off between wide coverage and detail. A single camera covering a whole yard may look economical on paper, but if nobody can identify a face or read a plate, it is false economy. In most business environments, several purpose-positioned cameras outperform one “do everything” unit.

Resolution is only one part of the picture

Installers are often asked for the highest resolution available, but that is not always the best answer. Higher resolution increases storage demand, bandwidth load and sometimes processing requirements at the recorder. If the scene is poorly lit or the lens is wrong for the target area, extra pixels will not rescue it.

Frame rate needs the same common-sense approach. Critical scenes such as cash handling, gates or vehicle movement may justify higher frame rates. General perimeter or low-activity internal areas often do not. Good CCTV specification is about balancing evidence quality against recording costs and infrastructure limits.

Lighting, low-light performance and scene conditions

Lighting is one of the most overlooked parts of CCTV design. Daytime performance may be excellent, only for the same camera to deliver noisy, blurred footage after dark. Before specifying cameras, assess whether the area relies on street lighting, PIR floods, permanent white light or infrared.

Colour at night can be valuable in commercial investigations, but it usually depends on enough usable light. Infrared works well in many cases, although reflective surfaces, fencing and nearby walls can create problems if the scene has not been assessed properly. Warehouses with roller shutters, yards with vehicle headlights and glazed entrance areas all present different challenges.

If the customer needs reliable out-of-hours evidence, lighting should be part of the discussion, not an afterthought. Sometimes the right answer is not a more expensive camera but better scene illumination.

Recording, retention and storage calculations

No CCTV specification is complete without clear recording assumptions. The first question is how long footage must be kept. Some sites are comfortable with 14 to 30 days. Others need longer retention due to policy, insurance requirements or the time it takes to notice an incident.

Storage sizing should be based on camera count, resolution, codec, frame rate, recording mode and expected scene activity. Motion recording can reduce storage use, but it is less predictable on busy sites or in outdoor scenes with constant movement. Continuous recording gives certainty but demands more capacity.

This is where trade customers often benefit from support at design stage. A 16-channel NVR with a pair of drives might look sufficient until the customer requests 30 days of retention across high-resolution cameras in a busy car park. By then, changing recorder or storage architecture becomes more expensive than getting it right at specification stage.

Network impact and PoE budget

IP CCTV is not just a camera decision. It is also a network decision. Managed switches, uplink capacity, VLAN planning and PoE power budgets all need checking before the system is signed off. This is especially important on sites where CCTV shares infrastructure with data, WiFi, VoIP or access control.

The common mistake is counting ports but ignoring power. If the switch budget is tight and the cameras include heaters, IR or motorised varifocal lenses, you can run out of PoE headroom quickly. Equally, if multiple high-bitrate cameras backhaul over a limited uplink, live view and playback performance can suffer.

For remote buildings, outbuildings or gates, wireless bridges or fibre may be the right answer, but only if they are specified around real throughput and environmental conditions. Reliable surveillance depends on the path back to recording just as much as the camera on the wall.

Compliance, privacy and commercial expectations

Business customers do not just need image quality. They need a system that is appropriate, proportionate and lawful. In the UK, that means considering signage, privacy, data handling and access to recorded footage. If cameras overlook public areas or neighbouring property, the customer should understand their responsibilities from the start.

There is also an operational side to compliance. Who can export footage? Who has admin access? Is remote viewing required for managers or keyholders? Does the customer want cyber security features such as password policy control, segmented networks or restricted remote access? These questions belong in the specification, not in the handover notes.

A commercial CCTV system should also reflect how the site is actually run. If staff need simple playback on reception, overcomplicated software will cause frustration. If a multi-site business wants central visibility, recorder and platform choices should support that from day one.

Writing a specification that can be priced and installed

The final specification should be precise enough for procurement and practical enough for the engineer on site. That means listing each camera location, intended scene purpose, mounting type, lens approach, resolution, recording assumptions, retention period, storage requirement, network provision and power method. If there are environmental concerns such as vandal resistance, weather rating or hazardous areas, include them clearly.

It is also worth noting what is excluded. If no civil works, lighting upgrades or containment changes are included, say so. Ambiguity is where project margins disappear.

For trade buyers and installers, the best specifications are the ones that reduce surprises. That may mean challenging a customer’s first idea, especially when budget and outcome do not line up. A smaller system specified properly will usually outperform a larger one built around assumptions.

Where projects involve switching, wireless links, storage planning and recorder setup, having a supplier that can support design as well as supply can save a lot of time. VibeTek works with installers and integrators on exactly that basis - helping turn a site brief into a workable system rather than just shipping boxes.

The strongest CCTV specification is the one that still makes sense when you stand on site, look at the light, the distances and the customer’s real risk, and can explain why every camera is there.