Security camera assessment as a paid service

A security camera assessment is a fixed-scope, paid review of a customer’s camera system that ends in a written, prioritized list of what is wrong and what it will take to fix. For an integrator, it is a front door: the customer pays for the first engagement, and the findings become the next quote.

Many integrators give this work away as a free CCTV site survey. The free version has two problems. The customer has no reason to value it, and the findings often end up attached to a competitor’s bid. A paid assessment with a defined deliverable signals that the integrator’s judgment is worth something, filters out buyers who are only collecting quotes, and produces a document the customer has already paid for and is inclined to act on. Many integrators credit the fee against the remediation work if the customer goes ahead.

What to check

An assessment covers two halves. A walk-through alone catches the physical half and misses the device half, which is where most silent failures live.

The physical half, done on site:

• Coverage: entrances, exits, cash handling, loading docks, and anything a regulation or insurer names. Gaps are covered in how to find security camera blind spots.
• Aim and image: cameras pointed at walls, ceilings, or glare, and images too dark or too far to identify anyone.
• Condition: dirty domes, cracked housings, loose mounts, damaged cabling, failed IR.
• Environment: cameras exposed to weather, heat, or vandalism without the right housing.

The device half, checked on each camera:

• Reachability: which cameras are offline or dropping in and out.
• Firmware: current version, and whether the model is still supported by its manufacturer.
• Credentials: factory defaults, shared passwords, and accounts nobody can explain.
• Certificates: expired, expiring, or self-signed where the customer’s policy requires otherwise.
• Storage: SD cards missing, failed, or worn, on cameras that are supposed to record locally.
• Time: clocks drifting from each other, which breaks timestamps in an investigation.
• Hardening: services enabled that the customer does not use. The checklist is in camera hardening at fleet scale.
• Hardware origin: equipment from manufacturers covered by Section 889 of the NDAA.

Watch the system for a few weeks

A one-day walk sees the system on one day. Many camera failures are intermittent: a camera that drops every few nights, an SD card that fails under load, a clock that drifts a little more each week. An assessment that includes a monitoring period of two to four weeks catches what a single visit cannot, and it gives the customer uptime figures for their own cameras rather than an estimate.

The monitoring period also shows the customer what ongoing service would look like. When the assessment ends, the question of whether to keep watching is already in front of them.

What to deliver

The deliverable is what the customer paid for. Make it something they can hand to a manager, an auditor, or an insurer.

1. A one-page summary. How many cameras, how many have findings, the three most serious problems, and uptime for the monitoring period.
2. A findings table, one row per finding, with the camera named and located, what is wrong, and a severity.
3. A phased plan. What to fix now, what to plan for the next budget cycle, and what ongoing service would keep the system from drifting back.
4. A quote for each phase, separate from the report, so the customer can approve one phase without the others.

Use the same four severity names the integrator uses for alerts in a service agreement, so the language is familiar when the customer signs up for monitoring. In a report, location can raise a finding: an offline entrance camera ranks above an offline storage-room camera.

Severity	Meaning in the report	Example findings
Critical	Coverage or recording is lost where it matters most	Entrance camera offline, site recorder not recording
High	Failure that will cost footage soon, or an exposed device	Failed SD cards, default passwords, models past support with published vulnerabilities
Medium	Degraded coverage or a single camera problem	Camera aimed at a wall, frozen image, dirty dome
Low	Will become a problem if ignored	Certificates expiring in months, clock drift, unused services enabled

How to scope it

Fix the scope before the price. State the sites, the approximate camera count, whether recorders and network gear are included, the length of the monitoring period, and the format of the deliverable. An assessment that grows without a change order is free work again.

Keep remediation out of the assessment. Fixing a few easy problems while on site feels like good service, but it blurs what the customer paid for and gives away the work the assessment was meant to scope. Note the fix, put it in the findings, and quote it.

Doing this across 500 cameras

A small assessment can be done with a clipboard, a laptop, and a few days of follow-up. On a large or multi-site system, the device half alone is days of work by hand, and the monitoring period is not practical without tooling.

MentatNOC is a white-label managed services toolkit for security integrators. It puts every Axis, Bosch, and Hanwha camera under management on continuous watch for the assessment period: reachability, image, storage, firmware and its support status, credentials, certificates, and time. Findings arrive classified by severity, with each camera named and located, and uptime is measured for every camera from the first day. It monitors device health, not video.

If the customer goes ahead, the same monitoring carries straight into the service contract, bundled with the monitoring the integrator already sells. From then on each alert opens a ticket in the integrator’s own ticketing system under their own SLA, dispatch knows which camera at which site failed before the truck leaves, and the integrator is the one who calls the customer first. The layers are on the platform overview, and the live demo shows a 500-camera fleet with its findings.