The installers have packed up. The cameras are on the walls, the recorder is humming in the server room and the monitors in the security office show a neat grid of images. It looks finished.

But many problems with industrial camera systems are found months later, at the worst possible time. A camera that looked fine at noon turns out to be useless at night. Recording stopped on three cameras weeks ago and nobody noticed. The plates at the gate are unreadable. The analytics alert on every passing bird.

Proper CCTV acceptance testing catches these issues before you sign off and before you need the footage.

Why Does Acceptance Testing Matter?

A large camera system is a significant investment. For a plant, yard or distribution centre with 64 or more cameras, it is also part of your safety, security and insurance commitments.

Acceptance testing confirms the system does what the design promised. It protects your budget, since issues found before final payment are fixed at the installer’s cost. It also gives you a baseline of how every camera should look, so future problems are easier to spot.

What Should You Check for Coverage and Image Quality?

Start with the purpose of each camera. Every camera should have a stated job: detect, recognize or identify.

• Field of view. Does each camera cover the area shown in the design drawings?

• Identification points. At gates, doors and docks, can you clearly identify a face or read a licence plate?

• Day and night. Test every camera after dark, with site lighting as it normally is. Check infrared range and glare.

• Weather and glare. Look for sun glare at sunrise and sunset, and reflections from wet pavement.

• Obstructions. Check that racking, trailers, stored materials or trees do not block views.

• PTZ presets. Confirm PTZ cameras move to each preset and return to their home position.

Walk a person and drive a vehicle through key areas while someone watches live and recorded video.

How Do You Verify Recording and Storage?

Recording failures are the most expensive problems to discover late.

• Every camera recording. Confirm each camera records at the specified resolution and frame rate.

• Retention. Check that storage will actually hold the promised number of days at full settings. Ask the installer to show the calculation, then verify it after a week or two.

• Redundancy. If the design includes RAID or failover recording, test it by simulating a failure.

• Time sync. Confirm all cameras and recorders show the same, correct time.

• Playback and export. Retrieve footage from several cameras for a specific time and export it. Time how long it takes.

What About Analytics, Alarms and Integrations?

Analytics need tuning to the real site.

• Zones and rules. Confirm intrusion zones, line crossings and loitering rules match the design.

• Detection testing. Walk test every zone, day and night, including at the far edge of each camera’s range.

• False alarm rate. Run analytics for at least a week and review alerts. Agree on an acceptable rate with your installer.

• Alarm delivery. Confirm alerts reach the right people and monitoring centre, with video attached.

• Integrations. Test links to access control, gate systems, intercoms and alarm panels.

The handover package. Do not sign off without:

• As-built drawings showing every camera, cable route and network device.

• A camera list with location, purpose, IP address and settings.

• Reference images from each camera, day and night.

• Admin credentials, held securely by your team, with default passwords changed.

• Firmware versions and an update plan.

• Warranty, service contacts and response times.

• Training for security, operations and IT staff.

Also confirm the system meets your IT security requirements, such as network segmentation and secure remote access. Bring your IT team into the final walkthrough, since they will often be the ones maintaining the network, updating firmware and managing user accounts long after the installer has gone.

How Do You Keep the System at That Standard?

Acceptance is a starting point. Treat CCTV acceptance testing as the baseline for every future check, not a one-time event. Schedule a 30-day review to fix early issues, then regular health checks. Use the system’s health monitoring to alert on cameras that go offline or stop recording. Compare current images against the reference set every few months to spot drift, dirt or new obstructions.

ForceVision designs, installs and commissions camera systems for large plants, yards and logistics hubs across Burlington, Oakville, Hamilton and Southern Ontario, with acceptance testing built into every project. If you are planning a new system or inheriting one, we can help you test it properly.

The Takeaway

Before you sign off on your next camera project, block out one day and one night to walk the site with this checklist. Thorough CCTV acceptance testing is the cheapest insurance you can buy for the system you have just paid for.

FAQ

Q: How long should CCTV acceptance testing take?
A: For a large site, plan at least one day and one night of testing, plus a one to two week period to verify retention and analytics.

Q: Should analytics be tested at night?
A: Yes. Detection and false alarm performance often differ significantly after dark.

Q: What if storage doesn’t meet the promised retention?
A: Raise it before final payment. The installer should adjust settings or add storage to meet the specification.

Q: What documentation should we receive?
A: As-built drawings, a camera list, reference images, credentials, firmware versions, warranty details and training.