Security camera maintenance agreement: what to include

A security camera maintenance agreement is the contract that commits an integrator to keep a customer’s cameras working for a recurring fee, and spells out exactly what that fee covers. A good one names every camera in scope, sets a response target for each kind of failure, separates included work from billable work, and lists what is excluded before anyone has to argue about it.

Without one, an installed camera or CCTV system earns revenue only when it breaks badly enough for the customer to call. The warranty runs out, the integrator hears nothing for a year, and the next call is either a complaint or a competitor’s quote. The agreement is how an integrator turns the cameras it already installed into steady monthly work.

The ten sections that matter

Most disputes over camera service come from one of these sections being missing or vague. Write all ten, even when some are one sentence.

1. Covered equipment. A list of every camera by site, model, and serial or MAC address, plus recorders and network gear if they are in scope. Say how cameras added later join the agreement and how removed cameras leave it.
2. Monitoring. What is watched (reachability, image, storage, firmware, certificates, tamper), how continuously, and during which hours alerts are acted on.
3. Response by severity. Define the severities by what the customer loses, and give each a response and restore target. The integrator sets the numbers. The structure is in how integrators set a surveillance system SLA.
4. Remote work included. Firmware updates, password and credential rotation, certificate renewal, and hardening changes. Say whether they are included, capped, or billed, and that they run in maintenance windows the customer agrees to.
5. Site visits. How many preventive visits per year and what each one checks (cleaning, aim, mounts, housings, cabling). Then how break-fix visits are handled: included, included up to a number, or billed per visit.
6. Parts. Who pays for SD cards, power supplies, housings, and other consumables. Camera replacements are almost always quoted separately.
7. Reporting. What the customer receives and how often: uptime by site and camera, open conditions, work completed. The contents are in camera uptime reporting.
8. Exclusions. Vandalism, damage by others, failures of the customer’s network or power, changes made by the customer or another vendor, and models past the manufacturer’s end of support.
9. Customer obligations. Site access on reasonable notice, advance notice of network changes, a named contact, and agreement that camera admin credentials are not changed without telling the integrator.
10. Term and changes. Length, renewal, notice period, how the fee changes when cameras are added, and who owns the credentials and configuration if the agreement ends.

The last point in section 10 is the one integrators skip and customers remember. State that the customer owns the admin credentials and configuration, and that they are handed over at the end of the term. It costs nothing to write, and it removes the fear that keeps some customers from signing at all.

Included versus billed

The fee should cover the work that keeps the system healthy. Work caused by events outside the integrator’s control should be billed. Drawing that line clearly is what keeps the agreement profitable without making the customer feel nickel-and-dimed.

How the fee is structured is the integrator’s decision. Common patterns:

• Per camera per month, with recorders and network gear priced as their own lines. Easy to adjust when cameras are added.
• Tiered, where a base tier covers monitoring, response, and reporting, and a higher tier adds remote work and more visits.
• Flat per site, for small sites where per-camera pricing feels fussy.

Whichever structure, put the per-camera or per-site basis in writing so the fee moves cleanly when the system grows.

Clauses that cause disputes

These are the lines that come back at renewal time. Get them right the first time.

Clause	What goes wrong	Write it this way
Response time	Customer reads “four hours” as fixed in four hours	Separate response (someone is working it) from restore (it is working again)
Coverage hours	Customer expects weekend response on a business-hours agreement	State the hours per severity, and what happens to an alert outside them
Covered equipment	A camera added last spring is not on the list	Include an add process and a monthly reconciliation against the live inventory
End of support	Customer expects the integrator to keep an unsupported model secure	Exclude models past manufacturer support from security commitments, and offer a refresh quote
Third-party changes	Another vendor changes a switch and cameras drop	Exclude changes by others, and require notice of network changes
Proof of work	Customer cannot see what the fee bought	Name the report, its contents, and how often it arrives

Make it measurable

An agreement only holds up at renewal if both sides can check whether it was met. Anything the integrator cannot measure should be measured or taken out. That means three records the integrator keeps as a matter of course:

• Ticket timestamps for every alert, from the ticketing system, measured against the response target for its severity.
• Uptime history by camera and site, so a claim that cameras “were down all month” can be checked.
• A work log of every remote change and site visit, with date, camera, and outcome.

Camera health monitoring is what produces most of those records, so it belongs in the agreement itself as a named line item. Bundle it with the monitoring services the integrator already sells, and present it as alarm monitoring for the cameras already on site. The customer gets one contract and one invoice, and the integrator gets alerts in the same ticket queue, under the same SLA, as everything else they monitor.

Doing this across 500 cameras

A maintenance agreement for one building can be run from a spreadsheet and a calendar. Across many customers and hundreds of cameras, the agreement holds up only when monitoring, response, remote work, and reporting run the same way for every account.

MentatNOC is a white-label managed services toolkit for security integrators, built to be written into the agreement and bundled with the monitoring they already sell. Each alert opens a classified ticket in the integrator’s own ticketing system, where the integrator’s own SLA applies, naming the condition, the camera, and the site. Dispatch knows what failed before the truck leaves the shop, the tech brings the right part when the alert calls for one, and break-fix visits are billed as fixes rather than lost to unbilled diagnostic trips. Firmware, credentials, and certificates are changed remotely in staged waves with automatic rollback, and every change is recorded.

Each customer sees uptime by site and camera in a view-only view under the integrator’s brand, from the same record the integrator works from. The integrator catches outages before the customer does and calls first, which is what a customer remembers at renewal. It monitors device health, not video. The layers are on the platform overview, and the live demo shows the views a customer would see.