CCTV Maintenance Checklist
A CCTV maintenance checklist template built on a distinction most service visits never make: a camera that records is not the same as a camera that is useful. Every camera is graded against what it is actually there to do, last week's footage is played back from each one to prove the recording is real, and the data protection obligations sit on the same sheet as the lens cleaning rather than in a policy nobody opens.
- Every camera graded against the job it was installed for
- Last week's footage played back, camera by camera
- Retention checked against the oldest footage actually held
- Night image checked after dark, not in daylight
CCTV Maintenance Checklist
Graded against purpose
| # | LIVE AND RECORDED VERIFICATION | DONE | RESULT | REQUIRED |
|---|---|---|---|---|
| 1 | Every camera confirmed live on the monitor | |||
| 2 | Every camera confirmed recording, not just displaying | |||
| 3 | Recorded footage played back from each camera |
The document you will get. Download for the full, editable file.
Who this CCTV maintenance checklist is for
One system, four people, and the one who will eventually need the footage is not on this list.
The service engineer
Lenses, housings, focus, illumination and the recorder. The night image check is the one that has to be done at the wrong time of day to be worth anything.
Whoever will ask for footage
Image quality against purpose. The grading is the difference between footage that identifies somebody and footage that proves a person-shaped object was present.
The data controller
Signage, retention, the access log and privacy masking. These sit on the maintenance sheet because that is the only visit where anybody checks them.
The facilities or security manager
Availability and meeting-purpose as two separate figures, because a system can be ninety percent available and a good deal less than ninety percent useful.
Where CCTV has to actually work
The structure suits any recorded system. What changes is what the footage will be asked to prove. If you run one of these, the sector page goes further than the template does.
- Retail and malls
Stores and centers where the footage is asked to identify a person rather than record that an incident happened.
Retail maintenance software - Commercial real estate
Multi-tenant buildings where the system covers common parts and the data controller is the landlord rather than the occupier.
Portfolio maintenance software - Corporate facilities
Workplaces where employees are covered, which brings consultation and policy obligations onto the same sheet as the lens cleaning.
Corporate facilities software - Education
Campuses with wide coverage, long retention expectations and a constant stream of requests for footage.
Campus maintenance software - Healthcare
Clinical sites where privacy masking and the areas cameras must not cover matter as much as the areas they do.
Healthcare maintenance software - FM service providers
Contracted sites where the system is serviced by one party and the data protection duty sits with another.
FM service provider software
What a CCTV service should cover
A CCTV maintenance checklist is the service record for a recorded surveillance system. It grades each camera's image quality against the purpose it was installed for, verifies that footage is genuinely recorded and retrievable rather than merely displayed, checks cameras, housings, recorders, storage and network, and confirms the data protection obligations including signage and retention.
A. Purpose, proof, equipment, obligation
| Field | What goes in it | Why it earns its place |
|---|---|---|
| System details and purpose | What the system is for, stated specifically, with the retention period and the data controller | Every judgment further down depends on it. A system installed for one purpose and used for another is where the legal problems start. |
| Image quality against purpose | Per camera: the quality achieved against the quality required | Graded Monitor, Detect, Observe, Recognise or Identify, spelled exactly that way. A camera covering a till that can only Observe will never give you a face. |
| Live and recorded verification | Eleven checks, including footage played back from every camera | Confirmed recording rather than confirmed displaying. These are different claims and only one of them is usually tested. |
| Oldest available footage | The date, recorded | The only honest test of the retention period. It catches a system holding less than it promises and, more often, one holding a great deal more. |
| Export tested | Footage exported and confirmed viewable | The export is the thing that will actually be handed over, and it fails on its own schedule: wrong codec, missing player, corrupt file, nobody finds out until it matters. |
| Cameras and housings | Twelve checks from lens cleaning to cabling and glands | Includes vegetation, signage or stock growing into the view, which is the commonest way a correctly installed camera stops covering what it was aimed at. |
| Night image in actual darkness | Checked after dark, not simulated | A camera producing a good picture at two in the afternoon and a white bloom at two in the morning is useless for exactly the hours it was installed to cover. |
| Recording, storage and network | Twelve checks across recorder health, disks, capacity, firmware and access | Disk health rather than free space. A recorder reporting plenty of capacity on a failing disk keeps recording right up to the point where none of it is recoverable. |
| Default passwords and accounts | Changed, and reviewed | On a maintenance sheet because that is the only visit where anybody looks. A recorder reachable from the internet on its factory password is a breach waiting to be discovered. |
| Data protection and signage | Twelve checks from signage naming the operator to staff consultation | Signage, privacy impact assessment, access logging, subject access procedure, disclosure logging and privacy masking, all on the same page as the cleaning. |
| Retention actually applied | Compared against the stated policy | A system that says thirty days and holds ninety is not being generous, it is holding personal data beyond its stated purpose, and the failure is invisible without this check. |
| Camera register and status | Operational, Degraded or Failed, spelled exactly that way | Status and meeting-purpose are separate questions, which is why both are counted and reported rather than blended into one availability figure. |
The grading scale is the reason this document is worth more than a visit that cleans lenses and ticks a box, because it asks the only question that matters about a camera, which is whether it can do the specific job it was installed to do. The scale runs Monitor, Detect, Observe, Recognise, Identify, and each step demands substantially more of the image than the one below it. A camera that lets an operator monitor a crowd and see that something is happening is a long way from one that will let somebody recognise a person they already know, and further still from one that will let a stranger identify an individual from the footage alone. Those are not quality gradations in the loose sense; they are different installations, with different lenses, different mounting heights and different distances. The failure this catches is almost never a broken camera. It is a camera that was specified for one job, installed correctly, maintained diligently for years, and is covering a till or a doorway at a width and a distance that can only ever Observe. It works. It records. It appears on every service report as operational. And on the one occasion somebody needs a face, there is no face, and the discovery happens in the worst circumstances and far too late to do anything about it. Recording the quality achieved against the quality required turns that from an unpleasant surprise into a line item with a cost attached, which is a thing a budget can be asked for. The second half of the document exists for a related reason: the obligations that come with recording people are the ones with no symptom at all when they are breached, so they sit here, alongside the cleaning, on the only visit where anybody opens the recorder.
B. What it looks like filled in
One service across forty two cameras. The availability figure looks acceptable and the second figure is the one to read.
| Line | Value |
|---|---|
| Cameras on the register | 42: 38 operational, 3 degraded, 1 failed |
| System availability | 90 percent |
| Assessed against purpose | 42, of which 34 meet it |
| Meeting purpose | 81 percent |
| Retention achieved against policy | 31 days held against 30 stated |
| Defects raised | 6, with one data protection issue |
Ninety percent available and eighty one percent meeting purpose are not two ways of saying the same thing, and the gap between them is four cameras. Thirty eight of the forty two are operational, and thirty four meet the purpose they were installed for, which means four cameras are powered, recording, graded Operational on the register and still cannot do their job. Those four are invisible to every other way of reporting on a CCTV system. They will appear as working on a monitor wall, as healthy in a recorder's status page, and as available in any figure that counts cameras rather than capability, and the only thing that finds them is grading each one against the purpose written down in section one. The retention line is the other finding worth dwelling on, and it reads like a non-event: thirty one days held against a stated policy of thirty. One day over is not a scandal, but it is the same failure that produces ninety days against a stated thirty, and it is detectable only by checking the oldest footage the system actually holds rather than trusting the setting. A system holding personal data beyond the period it has told people it holds it for has a problem that nothing about its operation will surface. The wider condition walk of the same site is the facility inspection form, the intervals for this and every other system sit inside a PPM schedule, and where the system is serviced under contract the provider's performance belongs on a subcontractor evaluation.
Word for the version an engineer completes on site, Excel for the one that counts cameras by status, works out availability and meeting-purpose separately and holds a Service Log across visits, and PDF for the copy that goes to whoever is named as the data controller. Free, and yours to rebrand.
How do you service a CCTV system?
Write the purpose down first, then test whether the system can deliver it. Six steps.
Write down what the system is for, specifically
Crime prevention, safety, process or access control, with the stated retention period beside it. Every judgment below this depends on both.
Grade each camera against its purpose
Monitor, Detect, Observe, Recognise or Identify, achieved against required. The cameras that fail this are usually the ones that look perfectly healthy.
Play back last week's footage from every camera
Not the live view. Confirm it recorded, confirm the recorded quality matches the live quality, and confirm the time stamp is right.
Check the oldest footage the system actually holds
And compare it with the stated retention. Holding more than you said you would is a data protection failure with no symptom attached to it.
Service the cameras, and come back after dark
Lenses, housings, focus, field of view and obstructions in daylight. Illumination and night image in actual darkness, because that is when it will be needed.
Check disk health, passwords and the signage
Disk health rather than free space, default passwords changed, and signage that names the operator. Then export a clip and confirm somebody can view it.
A working camera versus a useful one
Two ways of reporting on the same forty two cameras. One of them is comfortable and the other is useful.
| Aspect | The working camera | The useful camera |
|---|---|---|
| What is tested | It is powered and recording | It can do the job it is there for |
| How it is checked | A live image on a monitor | Graded against a stated purpose |
| What it produces | An availability percentage | A capability percentage |
| When a gap is found | Immediately, by anybody | On the day footage is needed |
| What the fix costs | A repair | A different camera, or a different position |
| Who is comfortable with it | Whoever reports on the system | Whoever will have to use the footage |
Almost every CCTV report in existence answers the comfortable question, because it is the one that can be answered from a desk. Cameras up, cameras down, a percentage, a trend. It is genuine information and it is cheap to produce, and if a camera has failed it needs to be known. What it cannot tell anybody is whether the system will deliver what it was bought for, because a camera that has never failed and has been maintained faithfully for six years can have been incapable of its job since the day it was commissioned. Nothing in its service history would show that. The grading against purpose is the only check that finds it, and the reason it is rarely done is that the finding is expensive: a camera that can only Observe where it needs to Identify is not a repair, it is a different camera at a different height or a different distance, and sometimes it is three cameras. That is a capital conversation rather than a maintenance one, and it is much easier to keep reporting availability. The honest position is to report both figures side by side and let the gap between them be the argument, which is what the template does. What this page deliberately leaves out is access control and intruder alarms. They are frequently installed by the same contractor, serviced on the same visit and lumped into the same line on a contract, and they are different systems with different failure modes and different obligations, which is why they are not quietly folded in here.
When the template starts to feel limiting
The file holds one service well. Four things get difficult between visits, which is where surveillance systems quietly fail.
A recorder can fail the day after the service
The playback check proves the system worked on the day somebody looked, and nothing watches it for the rest of the year.
The camera register lives in the report
Which camera covers what, at what grading, is the thing somebody needs during an incident, and it is in a PDF from eight months ago.
Availability and purpose get blended
Two different numbers, reported together once a year, and almost always collapsed into one figure by the time anybody repeats them.
Retention drifts silently
A storage upgrade or a settings change quietly extends it, and nothing notices until the oldest footage is checked at the next visit, a year later.
What running this in Facilio looks like
The service does not change. What changes is that the register and the two figures stop living in a document.
Asset Intelligence
Cameras are assets with a purpose
Each one carries its location, its required grading and the grading it last achieved, so the gap is a property of the camera rather than a line in a report.
Ops Performance Intelligence
Degraded is not the same as failed
A camera that still records and no longer meets its purpose surfaces as its own category instead of being absorbed into an availability figure.
Work Order Intelligence
A failed disk becomes an urgent job
Disk health findings raise work against the recorder rather than waiting for somebody to read the service report.
Audit Report Intelligence
Retention and access stay evidenced
The oldest footage held, the access log and the disclosure log sit against the system, which is the form the question takes when a subject access request arrives.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is a CCTV maintenance checklist?
It is the service record for a recorded surveillance system. This one grades every camera against its purpose, carries eleven verification checks on live and recorded footage, twelve on cameras and housings, twelve on recording and network, and twelve on data protection.
It covers CCTV only. Access control and intruder alarms are different systems with different failure modes and are deliberately not folded in.
How should camera image quality be graded?
Against what the camera is there to do, using Monitor, Detect, Observe, Recognise or Identify, spelled exactly that way because the summary counts the term.
Each step demands substantially more of the image than the one below. A camera covering a till that can only Observe will never give you a face, and nobody discovers that until they need one.
Why play back recorded footage?
Because a live image on a monitor proves the camera is powered and nothing more. Recording failures are routinely invisible for months, because everything on the wall still looks right.
Playing back last week's footage from every camera is the only check that proves the system is doing the thing it exists to do.
How do you check the retention period?
By finding the oldest footage the system actually holds and comparing it with the stated policy, rather than trusting the configured setting.
A system that says thirty days and holds ninety is holding personal data beyond its stated purpose. It is invisible from the outside and it is the obligation that catches people most often.
Why check the night image in darkness?
Because a camera producing a good picture at two in the afternoon and a white bloom at two in the morning is useless for exactly the hours it was installed to cover.
Infrared illumination fails gradually, reflective surfaces appear after a refit and a new light outside the field of view can bloom the image. None of it shows in daylight.
Should disk space or disk health be checked?
Health. A recorder reporting plenty of free capacity on a failing disk will keep recording right up to the point where none of it is recoverable.
Free space tells you the system has somewhere to write. It says nothing about whether what has already been written can be read back.
Why are data protection checks on a maintenance sheet?
Because the maintenance visit is the only occasion when somebody opens the recorder, and the obligations that come with recording people have no symptom at all when they are breached.
Signage, retention, access logging, disclosure logging and privacy masking are checked here for the same reason the lens gets cleaned here: it is the visit that happens.
Is a camera that is working the same as a camera that is useful?
No, and the difference is the point of this document. A camera can be powered, recording, graded Operational and incapable of the job it was installed for.
That is why availability and meeting-purpose are reported as two separate figures. Blending them produces a comfortable number and hides the cameras that will disappoint somebody later.
In one paragraph
A CCTV maintenance checklist works when every camera is graded against the purpose it was installed for, because a camera that records is not the same as a camera that is useful and nothing about a healthy one reveals the difference. Play back last week's footage rather than trusting the live view, check the oldest footage actually held against the stated retention, check the night image in real darkness, check disk health rather than free space, and report availability and meeting-purpose as two separate figures.
Powered, recording, and no use at all
Write the purpose down, grade every camera against it, play the footage back and come again after dark. Once the register only exists in last year's report, or the two figures get blended into one, the paper version has reached its limit.