Start with a camera and responsibility list
Keep a simple record of each camera name, location, purpose, recorder channel, expected field of view, and the person responsible for reviewing the system. Names such as “CAM 07” are hard to use under pressure; “Rear receiving door — facing inbound” tells a manager what the view should show.
The list should also identify the recorder, storage drives, network switch or PoE source, remote-viewing platform, installer or support contact, and where approved configuration records are kept. Do not store passwords in an unsecured maintenance sheet.
Walk every physical view
Compare the live image with the scene in front of the camera. Renovations, new shelving, banners, plants, parked trailers, seasonal decorations, spider webs, dirt, and a camera nudged during other work can quietly block the event the system was meant to capture.
Clean housings and lenses using the equipment manufacturer’s method. Check mounts, weatherproof boxes, exposed cable, conduit, seals, and signs of water entry or corrosion. Do not reposition a camera until its approved purpose and privacy boundaries are understood.
Review day, night, and the difficult lighting transition
A view that looks sharp at noon may lose faces when a door opens to bright sun or turn white from infrared reflection at night. Review stored clips from daylight, after dark, and the hours when headlights, dock doors, window glare, or exterior lighting create the hardest conditions.
Check whether the subject is large enough in the frame to answer the intended question. A wide parking overview can show movement without showing a useful face or plate. Maintenance cannot replace a dedicated identification view when the original layout asks one camera to do two incompatible jobs.
Prove that every channel is recording
Choose a recent known event on each channel, such as a person walking through a doorway, and find it in playback. Confirm the schedule covers the expected hours, motion or event recording triggers reliably, and the timeline does not contain unexplained gaps.
Look beyond the newest clip. Search near the oldest date the business expects to retain and confirm that storage duration still matches the approved plan. Adding cameras, raising resolution, increasing frame rate, or changing continuous recording can shorten retention without anyone changing the hard drive.
Check time, camera names, and export before an incident
Compare recorder time with a trusted current clock and confirm the correct time zone and daylight-saving behaviour. A system that is several minutes or an hour wrong creates confusion when footage is compared with access logs, transactions, alarms, or police reports.
Have the responsible person export a short clip and play it on a separate authorized computer. Verify that the file includes the intended time range, uses a format the recipient can open, and does not accidentally include unrelated footage. Document the export steps without exposing administrator credentials.
Review storage health and failure warnings
Check the recorder’s storage status, error log, drive warnings, temperature or fan alerts where supported, and available capacity. A live camera can continue streaming while the recorder fails to save new footage. Repeated restarts are not a repair and may create more risk when important data is already unstable.
Recorders and drives have finite service lives, but replacement should follow condition, support status, workload, and risk—not a made-up universal age. When a drive shows errors or playback disappears, preserve relevant evidence and arrange proper diagnosis before formatting or resetting the system.
Treat accounts and updates as maintenance items
Remove accounts belonging to former staff and limit each user to the access their role requires. Use individual accounts where the platform supports them, strong unique passwords, and multi-factor authentication when available. Review phones, browsers, vendor portals, and shared email accounts that can reach the system.
Check manufacturer security notices, firmware support, recorder compatibility, and configuration backups before updating. The Canadian Centre for Cyber Security advises organizations to manage IoT devices, apply security patches, protect networks, and change default credentials. An unsupported internet-connected camera or recorder deserves a replacement or isolation plan rather than permanent exposure.
Keep privacy controls in the same checklist
Confirm that each camera still serves the documented business purpose, its field of view remains limited, public notice is present, footage access is restricted, and routine overwrite follows the approved retention policy. More footage and more users are not automatically improvements.
The Office of the Privacy Commissioner of Canada advises private-sector organizations to secure recordings, limit access, destroy images when no longer required, document disclosure, train operators, and periodically evaluate whether surveillance is still needed. Maintenance should test those controls along with the hardware.
A simple schedule that businesses can actually follow
Front-line staff can glance at channel status daily without being made system administrators. A responsible manager can test playback, time, alerts, and recent exports monthly. A fuller physical, night-view, storage, account, privacy, and update review can be scheduled quarterly and after renovations, network changes, power events, incidents, or repeated camera loss.
The interval should reflect the site’s risk and operating requirements. The important part is ownership: record the date, person, exceptions, corrective action, and retest. An unchecked box is better than a checked box for a test nobody actually performed.
Official guidance used
These sources support the general planning information. Privacy, legal, and technical requirements still depend on the property, organization, equipment, and intended use.