Ultimate Business CCTV Guide

Set clear security objectives

Be specific about what success looks like. Typical objectives:

• Deterrence: visible cameras and signage, audio challenge where appropriate.

• Evidence: clear, time‑stamped footage that supports HR, insurance or police action.

• Operational oversight: remote viewing for duty managers and FM teams.

• Compliance: proportionate use, fair processing, appropriate retention and access controls.

Capture this in a short requirements brief so every design decision ties back to outcomes.

Run a structured survey (with a sketch plan)

Walk the site and note risks, lighting, traffic flow, and site constraints. Mark entrances, exits, reception, tills, corridors, bays, gates and perimeters. Record:

• Areas that require recognition or identification (see DORI below)

• Lighting conditions (day/night, backlight, street/yard lighting)

• Mounting options and heights, cable routes, network points/PoE availability

• Hours of risk (business hours vs out‑of‑hours) and response expectations

• Any existing systems to retain, replace or integrate

This becomes the backbone of your coverage plan.

Camera fundamentals you actually need

• Form factors:
  Domes/turrets for general indoor coverage; bullets outdoors; PTZ for wide areas/incident tracking; panoramic/multi‑sensor for large spaces; thermal for dark perimeters.

• Resolution & lenses: 4–8MP (up to 4K) is common for business scenes. Choose fixed or varifocal lenses to frame each scene to its DORI target.

• Dynamic range & low‑light: Look for WDR, good SNR and IR performance; plan for stray reflections and wind‑moved foliage.

• Analytics: Use sensibly (line crossing/object detection) to reduce nuisance alerts; tune per scene.

Coverage design using DORI

DORI (Detection, Observation, Recognition, Identification) gives objective image detail targets in pixels per metre (px/m) to design scenes that match your goals:

• Detection ~25 px/m – something is present

• Observation ~62.5 px/m – characteristic details (e.g., behaviour)

• Recognition ~125 px/m – person known to you could be recognised

• Identification ~250 px/m – an unknown person could be identified

Practical examples

• Building entrance: aim for Recognition (≈125 px/m) so you can match faces to access‑control logs.

• Reception desk / tills: often Identification (≈250 px/m) at the transaction point.

• Car park perimeter: Detection/Observation (25–62.5 px/m) to trigger response, with PTZ presets for closer views.

Design tip: pixel density depends on both camera resolution and field of view. Narrowing the field of view (zooming in or choosing a different lens) raises px/m without changing the camera. Validate with vendor calculators and on‑site test captures.

Night‑time performance & lighting

Great cameras still struggle if the scene is pitch black or full of glare. Plan for:

• Supplementary lighting (white or IR), avoiding back‑lighting and reflective hot‑spots

• IR positioning to prevent halos, spider webs and vegetation within the IR beam

• Exposure tuning to curb motion blur (especially at gates, doors and yards)

• Weather & environmental factors: rain, wind‑moved trees, insects, condensation

Recording, retention & storage sizing

Decide retention (e.g., 30–90 days) by purpose and policy, then size storage accordingly. Always test in your scenes—bitrate varies with motion and lighting.

Quick sizing method (rule‑of‑thumb):

Storage (TB) ≈ (Bitrate Mb/s ÷ 8) × 3600 × hours/day × days × number of cameras ÷ 1,024 ÷ 1,024

Example: 8 cameras at 4 Mb/s, recording 12 h/day for 30 days
= (4/8) × 3600 × 12 × 30 × 8 ÷ 1,024 ÷ 1,024 ≈ ~4.9 TB total.
H.265 and “smart codecs” can reduce this, but validate with pilots before you commit to disks.

Good practice

• Use NVRs or server‑based VMS with RAID where appropriate

• Monitor disk health, recording gaps and actual retention

• Consider cloud backup or dual‑recording for critical views

Networking & cyber hygiene (keep video secure)

Treat cameras as IP endpoints on your network:

• Sized PoE switching with headroom; sensible VLAN segmentation

• Vendor‑supported firmware management, change control and backups

• Role‑based access, strong credentials and MFA for remote access

• Time synchronisation (NTP), watermarking and audit logging

Remote access & 24/7 monitoring options

• Secure remote viewing for managers: encrypted clients, roles, MFA, audit.

• Detector‑activated monitoring via an ARC (Alarm Receiving Centre) for out‑of‑hours escalation: operators verify alarms, issue audio challenge, contact keyholders and, where the design and force policy allow, request police using a URN (Unique Reference Number).

• For police‑response eligibility, detector‑activated CCTV should be designed to the relevant British Standard and onboarded with an accredited ARC (force policies apply).

Installation day: what “good” looks like

• Method statements and permits in place; work areas cordoned and clean

• Neat bracketry and cabling; weatherproofing/glands correct; safe fixings

• Cameras aligned and lensed to DORI targets; privacy zones set where required

• NVR/VMS configured to policy (users/roles, retention, time‑sync, alerts)

• Remote access tested on approved devices

Commissioning, acceptance & handover

Don’t skip the paperwork. Your acceptance pack should include:

• Test images and pixel‑density screenshots for key scenes

• Recording/retention proof, export tests and chain‑of‑custody notes

• User/role list, password policy, MFA setup and administrator run‑book

• Drawings, camera schedule, IP addressing, PoE plan and as‑builts

• Firmware/software versions and a simple change‑control log

Maintenance that prevents silent failures

Plan PPM (planned preventative maintenance): clean lenses/domes, re‑aim and refocus, check seals and fixings, verify IR/WDR tuning, confirm recording/retention, update firmware with rollback plans, refresh user roles and test exports. Consider remote health monitoring to flag offline cameras, disk issues and retention shortfalls between visits.

Budgeting: indicative ranges & what drives cost

Every site is unique, but budgets typically scale with camera count, imaging performance, retention targets, network works and working hours.

• Small office (6–12 cameras): design, install, retention to 30–60 days, secure remote access.

• Retail/venue (8–20 cameras): better low‑light performance, some analytics, till‑point ID.

• Warehouse/perimeter (24–40+ cameras): PTZs, lighting/IR, longer retention, monitoring setup.

We’ll give clear, itemised options after a free survey—often including a phased path for upgrades and integrations.

Copy‑paste checklists

A) Survey checklist

• Objectives agreed (deterrence/evidence/oversight/compliance)

• Risks & incident history captured; hours of risk noted

• Coverage plan sketched; DORI targets per scene

• Lighting/IR needs; mounting heights/positions; cable/network routes

• Integration points (access control/alarms)

• Retention target; governance needs (signage, roles, export)

B) Acceptance checklist

• Test images meet DORI targets; day and night samples saved

• Recording & retention verified; time‑sync correct; watermark visible

• Export tested with audit notes; run‑book completed

• Users/roles set; MFA for remote access; admin credentials sealed

• Drawings/as‑builts, schedules and firmware versions handed over

C) Maintenance checklist

• Optics clean; housings sealed; fixings tight; cable glands intact

• Focus/aim re‑validated; privacy masks current; PTZ presets tested

• IR/WDR/exposure tuned; motion blur checked in night captures

• NVR/VMS health, RAID/SMART status and actual retention verified

• Firmware updates with rollback; user/role review; change log updated

Next steps & how we can help

We’re a friendly, business‑only CCTV team serving Greater London & Surrey. If you’d like pragmatic, standards‑aware advice (and a tidy install with real aftercare), our engineers will survey your site and give you clear options—no jargon, no fuss.