Start with the event you need to notice

A CCTV audit is not a camera-counting exercise. It begins with an operational question.

Examples include:

  • Is a vehicle entering a restricted gate after hours?
  • Does a warehouse aisle need an alert when someone enters?
  • Is a production zone visible enough to review a safety-related event?
  • Can a shop team find a specific incident without searching hours of footage?

Choose one or two priority events first. This makes the audit practical and prevents a vague project such as “put AI on every camera.”

1. Check the camera view

Stand where the event happens and view the feed. Ask:

  • Can the relevant person, vehicle or zone be seen clearly?
  • Is the camera too high, too far away or pointing through glare?
  • Is a gate, entrance or aisle partly blocked by stock, signage or a parked vehicle?
  • Does the field of view change when a shutter, door or vehicle moves?

Analytics cannot repair a view that does not contain the event clearly. Repositioning or adding a camera may be more useful than changing software.

2. Check day, night and difficult light

A camera that works at noon can struggle at dusk, under a bright gate light or when headlights point towards it.

Review representative conditions:

  • Daylight
  • Low light
  • Backlight at entrances
  • Rain or dust where relevant
  • Busy periods with people and vehicles moving through the scene

Do not make a decision from one ideal screenshot. Test the view when the real event is likely to happen.

3. Confirm the video and recording path

For each priority camera, check:

  • It is recording and can be played back
  • Storage retention is sufficient for investigation
  • The approved stream can be accessed reliably
  • Network equipment and recorder health are known
  • Backup power protects the parts of the chain that must keep recording

For a related outage check, see PGAK's CCTV power-backup checklist.

4. Define the response before the alert

An alert without an owner becomes noise. Write down:

  • The exact event
  • The person or team receiving it
  • The time they should review it
  • The action they may take
  • What happens after hours
  • How false alerts will be reviewed and tuned

A small pilot with a clear response route is more valuable than broad notifications to everyone.

5. Check privacy and access controls

Confirm that only appropriate people can view live feeds, playback and exports. Camera placements should match a genuine purpose, and the site should have clear guidance for access and retention.

See who should view CCTV footage at work for a practical access-policy checklist.

6. Run a limited pilot

A good pilot uses a few high-value views: for example, a vehicle gate, dispatch point or restricted aisle. Test normal, busy and low-light conditions. Review useful alerts, missed events and false alerts with the people who use the system.

Expand only when the site understands what the workflow delivers and where it has limits.

A simple scoring sheet

For each priority camera, mark:

  • View: clear / needs adjustment
  • Lighting: suitable / needs testing
  • Recording: confirmed / needs repair
  • Power backup: confirmed / needs review
  • Event definition: clear / unclear
  • Alert owner: assigned / unassigned
  • Access controls: reviewed / needs action

This does not replace a technical survey, but it creates a clear starting point.

Review your site with PGAK

PGAK helps businesses assess suitable existing CCTV camera views and design practical video-analytics workflows around real operational events. Suitability depends on the camera, scene, lighting, connectivity and response process; it should be assessed before rollout.

Explore AI CCTV for warehouses or request a feasibility check.