Most security-system service agreements are two pages long and describe an annual inspection. That is not an agreement. It is a recurring invoice with a site visit attached.
The purpose of an agreement is to make behaviour predictable when something fails at an inconvenient time. Whether it does that depends on a small number of clauses, most of which are absent from the standard template. What follows is the set worth insisting on.
None of this requires an adversarial posture. A service provider who does the work properly benefits from the same clarity, because scope defined in writing is scope that can be resourced.
Start with the inventory, because everything else depends on it
An agreement priced without an accurate device schedule is a guess. The provider guesses low to win it and then treats anything unexpected as out of scope, which is exactly the argument you signed an agreement to avoid.
The schedule needs to list every controller by model and address, every reader by door, every input and output in use, every server and workstation with its role, every camera with its model, and the software versions running on each. It needs a revision date. It needs to be attached to the agreement, not referenced as a document somebody has.
Expect the first accurate inventory to differ from the drawings. Doors get added, panels get repurposed, cameras get moved, and the as-built set stops being accurate about eighteen months after handover. Discovering that during the inventory is cheap. Discovering it during an outage is not.
- Device schedule with revision date. Attached as a schedule, updated at every preventive visit, issued back to you afterwards.
- Software and firmware version register. Head end, database engine, operating system, controller firmware, camera firmware.
- Panel address map. Which controller sits on which communication loop or subnet, and which doors it serves.
- Known deviations. Anything found non-standard and left in place, recorded deliberately rather than forgotten.
The clauses that matter when something breaks
What “covered” means, itemized
- Labour, travel, parts and after-hours premium are four separate questions. Answer each.
- Define whether remote diagnosis is billed, included or a prerequisite to an onsite attendance.
- Name the exclusions plainly: new cabling, construction work, damage, and anything the provider does not do at all.
- State who pays when the fault turns out to be on the network side rather than the security side.
Response, defined as a process
- Define what starts the clock: a phone call, a ticket, an acknowledged ticket.
- Separate remote triage from onsite attendance. They are different commitments.
- Define severity levels against operational impact, not against device counts. A single failed door on a secure perimeter outranks four failed cameras in a parking area.
- Name the escalation path and the second name on it.
Preventive visit content
- A checklist, attached, not the phrase “annual inspection”.
- Battery age recorded and replacement criteria stated, since float voltage alone proves nothing.
- Supervised input loop values verified against expected resistance.
- Database size, growth rate and free space recorded each visit so the trend exists.
- A written report issued afterwards with findings, actions taken and actions recommended.
Configuration custody
- Backups are taken on a defined schedule and a copy is held by you, not only by the provider.
- You can restore without the provider. That means holding the licence files and knowing the version.
- Administrative accounts remain owned by you. Provider accounts are named individuals, not a shared login.
- A restore is rehearsed at least annually, to a test instance, and the result is recorded.
Change and firmware policy
- Nobody applies firmware or a software update without an approved change window.
- Every change has a stated rollback and a backup taken immediately before.
- Version compatibility is checked across head end, controller firmware and client before scheduling, not during.
- Emergency changes are permitted and documented afterwards. Undocumented changes are the ones that cost you later.
Exit terms
- On termination you receive the current configuration backup, the device schedule and all documentation.
- Administrative credentials transfer to you or to your nominee.
- No proprietary lock on your own data, cardholder records or camera configuration.
- A defined notice period on both sides, and no automatic multi-year renewal without a review.
The clause people regret leaving out
Documentation deliverables. An agreement that produces no artefacts leaves you with exactly as much knowledge of your system after three years as you had at the start, and all of the accumulated knowledge sits with the provider.
Insist that each preventive visit issues an as-maintained device schedule, a version register and a findings report, and that these are yours. This is not about mistrust. Staff change on both sides. The person who knows why that one panel is addressed out of sequence will eventually not be reachable, and the only durable place for that fact is a document you hold.
Sizing the agreement to the environment
A commercial office and a correctional facility do not need the same agreement, and the difference is not only frequency. In a high-security environment, testing itself requires coordination, escorts and controlled windows, and a test that cannot be performed safely will simply not be performed. That has to be planned into the visit rather than discovered on the day. The specifics are covered in preventive maintenance for high-security facilities.
Where servers and recording infrastructure are in scope, the agreement should say who watches array health, database growth and backup success between visits, because those three fail quietly and a quarterly visit is not a monitoring strategy. See why security servers and storage should be monitored.
Skyfal Security publishes its own coverage and escalation details rather than embedding them in prose: see 8:00 AM – 5PM for standard coverage and 24/7/365 for after-hours arrangements, and Service Agreements for how scope is structured.
Review an agreement before it renews
Bring the current agreement and the device schedule, if one exists. The gaps are usually visible in an hour.