Build the camera record while the work is visible
CCTV closeout information is easiest to capture during installation and commissioning. A camera label, switch port, field of view, and recorder channel may all be obvious to the installer today but difficult for a service technician to reconstruct six months later.
Assign one person to maintain the project record, use the same camera names everywhere, and update the documentation whenever a device moves or a configuration changes. The finished package should let someone unfamiliar with the job locate a camera, trace its connection, understand its purpose, and confirm how it was tested.
Project, site, and system scope
Start with the identifiers and boundaries that give every later record context. A short scope summary prevents an inventory or photo folder from being mistaken for a complete account of the system.
- Customer, project name, site address, job number, building, floor, and work phase
- Primary customer, IT, security, general-contractor, and after-hours contacts
- New cameras, relocated cameras, reused equipment, owner-furnished devices, and excluded areas
- Required coverage objectives, retention expectations, integrations, and approved alternates
- NVR, DVR, VMS, cloud platform, monitoring, and remote-access responsibilities
- Milestone dates for installation, aiming, commissioning, training, and closeout
“Replace 18 exterior cameras, add four loading-dock cameras, retain the existing VMS server, and provide 30 days of recording at the approved quality settings” is far more useful than “camera upgrade.”
Camera inventory and device information
The camera inventory is the system index. It should connect a unique camera name to its location, purpose, model, serial number, network identity, recorder assignment, and installation status.
- Camera ID and display name exactly as used on drawings, labels, VMS views, and reports
- Manufacturer, model, serial number, firmware version, lens, and camera type
- Building, floor, room, exterior elevation, pole, or other precise physical location
- Coverage purpose, scene description, privacy masking, analytics, and special configuration
- MAC address, IP address, hostname, recorder or VMS assignment, and license status
- Install date, warranty information, replacement status, and customer-owned spares
Use a name such as B1-L2-CORR-EAST-03 and keep it unchanged across the label, drawing, switch-port record, VMS, test sheet, and photo filename.
Camera location, mounting, and field of view
A camera can be online and still fail its operational purpose. Record the installed height, mount, orientation, scene, and approved field of view so later service or replacement work can restore the intended coverage.
- Mounting height, mount type, bracket, back box, pole, pendant, or specialty hardware
- Final pan, tilt, roll, focal length, zoom, and focus position where useful
- Target scene, critical areas, expected identification distance, and known blind spots
- Obstructions, glare, backlighting, reflections, vegetation, and environmental exposure
- Weather sealing, drip loops, surge protection, grounding, and heater or blower information
- Approved overview image or screenshot showing the final field of view
Capture one image showing the installed camera and a separate exported still showing the final scene. Name both with the camera ID so the physical device and its view remain connected.
IP, network, switch, and PoE information
Network details explain how the camera communicates and receives power. Document enough for support teams to identify the correct VLAN, switch, port, addressing method, and power budget without publishing active credentials.
- IP address, subnet, gateway, DNS, VLAN, hostname, and static or reserved address method
- Switch name, closet, switch port, port description, speed, duplex, and link status
- PoE class, measured draw where relevant, injector or midspan information, and available budget
- NTP source, certificate status, required ports, firewall rules, and network ownership
- Remote-access method, responsible support team, and secure credential handoff location
- Network changes, temporary addresses, and outstanding IT dependencies
A record that ties Camera C-214 to IDF-2-SW3 port 18 and VLAN 142 can save hours when the camera is moved, replaced, or unexpectedly loses power.
NVR, DVR, VMS, and recording configuration
Recorder and VMS records should show where video is stored, how each camera is assigned, and which settings were accepted. These values affect storage, playback quality, bandwidth, and incident response.
- Recorder, server, appliance, or cloud tenant name, location, model, serial number, and version
- Camera-to-channel or camera-to-server assignments and failover relationships
- Resolution, frame rate, codec, bit rate, stream profiles, and recording schedule
- Continuous, motion, event, or analytics-based recording behavior
- Retention target, calculated storage, observed retention, and archive or export method
- User roles, health alerts, time synchronization, backup, and configuration-export records
Record both the agreed target and the observed result: “Target 30 days; 34 days available at handoff using H.265, 15 fps, and continuous recording.”
Cable routes, terminations, and labeling
Camera documentation should trace each connection from the device to its final network or recorder termination. Consistent labels make failures easier to isolate and reduce accidental disconnections during later work.
- Cable ID, cable type, rating, color, approximate length, and test-report reference
- Camera endpoint, intermediate enclosure or patch point, and final rack or recorder destination
- Pathway through tray, conduit, sleeve, riser, exterior route, or wireless bridge
- Patch panel, port, switch, injector, media converter, fiber strand, or coax input
- Labels at both ends and any intermediate points, matching the camera inventory
- Spare, abandoned, damaged, repaired, or rerouted cable status
Image verification, testing, and commissioning
Commissioning proves that the installed cameras meet the project’s operational expectations. Test more than connectivity: verify the scene, image quality, recording, playback, exports, timestamps, alerts, and day/night behavior where appropriate.
- Live-view image quality, focus, exposure, white balance, glare, and compression artifacts
- Field of view, identification areas, privacy masking, analytics zones, and orientation
- Day/night transition, infrared illumination, supplemental lighting, and nighttime scene where required
- Recording, playback, search, export, watermark, timestamp, and user-permission functions
- Motion, analytic, alarm-input, health, storage, and camera-offline alerts
- Test date, technician, witness, software version, result, exception, and retest evidence
Do not mark “night test passed” based only on the camera entering monochrome mode. Confirm that the target area remains usable and that IR reflection, insects, vehicle headlights, or nearby lighting do not defeat the scene.
Deficiencies, photos, as-builts, sign-off, and closeout
Closeout should preserve unresolved issues and demonstrate how corrected items were retested. Reconcile the final camera inventory, drawings, switch-port records, VMS names, screenshots, and completion photos before customer turnover.
- Deficiency number, location, impact, responsible party, correction, date, and retest result
- Overview and close-up photos showing device location, label, mount, sealing, and cable entry
- Final plans, camera schedule, network details, rack or recorder layout, and approved field changes
- Training topics, attendees, configuration backup, licenses, manuals, and spare equipment delivered
- Technician, project-manager, customer, and witness sign-off with documented exceptions
- Final folder structure, revision date, delivery method, and customer receipt confirmation
A consistent field record
Standardize documentation without slowing the work.
A repeatable camera documentation process reduces missing device details, inconsistent names, and incomplete commissioning evidence. It also gives future service technicians a reliable starting point instead of forcing them to rediscover the system.
View the CCTV Documentation Pack