If you install CCTV for a living, you already know the truth: most jobs don’t overrun because the kit is “bad”. They overrun because a handful of small commissioning steps get missed, then you spend the last 2 hours firefighting on a ladder with a laptop balanced on your knee.

A proper commissioning routine is how you keep your day profitable. It cuts call-backs, reduces “can you just…” requests, and stops you bleeding labour on the stuff nobody priced in. Even if you’re fitting straightforward IP CCTV Systems, a checklist-based approach is the difference between leaving site calm… and leaving site annoyed.

Below is a practical, on-site-friendly set of checklists you can use for cameras, NVRs, and the network. Use it as a template and tweak it for your typical jobs.

The real “time sinks” you’re trying to avoid

Before you get into checklists, it helps to be honest about what usually eats your time:

• IP address clashes, unknown network ranges, or a router you’re not allowed to touch

• PoE issues (wrong switch, wrong budget, long runs, dodgy terminations)

• Cameras left on default settings (or default passwords)

• NVR recording set wrong (continuous vs motion, wrong stream, wrong retention expectations)

• Remote access not agreed (who owns the app login? What email? what ports?)

• The customer only mentions the “one extra camera angle” at the end

None of that is complicated. It’s just expensive when you discover it late. So your goal is simple: front-load decisions, then verify in a fixed order.

Pre-commissioning: 15 minutes that saves you hours

Do this before you start deep-diving into menus.

Quick site/hand-off checklist

• Confirm what’s in scope today (camera count, viewing points, remote access, handover time)

• Agree where the NVR and network kit will live (power, ventilation, physical security)

• Confirm cable routes and any “no-go” areas

• Confirm who provides the network details (you or their IT)

• Confirm monitoring expectations: live view only, playback, mobile app, alarms, push notifications

• Confirm retention expectations (how many days they think they’re getting)

If the customer wants proactive deterrence (sirens, spotlights, voice warnings), agree that now and point them at Active Deterrence Cameras early — it changes how you set motion rules and schedules.

Network commissioning checklist (because most problems start here)

Even the best IP CCTV Cameras will look “faulty” if the network is messy.

1) Physical layer checks (don’t skip these)

• Label both ends of every run (camera location + port number)

• Test every run (continuity + basic performance if you’ve got the tester)

• Check terminations are consistent (T568B, no split pairs)

• Confirm cable type and environment rating (especially externals and trunking routes)

• If you’re extending anything over structured cabling, confirm the right product and distances

If you’re buying per job, it’s worth keeping your go-to bits bookmarked, like Cable options and the everyday tools/consumables that get forgotten until you’re on site.

2) PoE power checks (the classic silent killer)

• Confirm PoE standard needed (PoE / PoE+ / PoE++)

• Confirm total PoE budget vs camera draw

• Confirm long-run requirements (any runs pushing distance limits?)

• Confirm uplink speed (Gigabit where needed)

• Confirm switch layout makes sense for servicing and fault-finding

If you’re running a dedicated CCTV LAN, keep it simple and predictable with proper POE Switches. And for small add-ons or awkward locations, having a POE Injector option can save you ripping out a plan because you’re 1 port short.

3) IP plan (write it down, don’t “wing it”)

• Decide the IP range (and confirm it doesn’t clash with the site LAN)

• Decide DHCP vs static (static is usually cleaner for CCTV)

• Set a clear numbering system (e.g., 192.168.50.21 = Front gate)

• Record every IP, username, and password in your job sheet

• Confirm gateway and DNS (especially if remote access is needed)

If the customer has IT, get them to confirm the above in writing. It’s not about blame — it’s about avoiding a 6pm “we can’t give you admin access” surprise.

Camera commissioning checklist (get the image right once)

Whether it’s Internal CCTV Cameras in a retail unit or externals on a yard, camera setup is where you can lose loads of time by making tiny adjustments repeatedly.

1) Mounting + aim checks

• Confirm you’re capturing the objective (faces? plates? wide overview?)

• Avoid pointing into direct sunlight where possible

• Avoid mounting too high for identification (unless it’s purely overview)

• Confirm lens choice suits the distance (don’t rely on digital zoom later)

• Confirm the camera is secure and weatherproofed properly

If the brief includes vehicle ID at an entrance, don’t “hope” a standard camera will do it. Use a purpose-built option like License Plate Recognition Cameras and set expectations on range and positioning from the start.

2) Image settings (lock these in methodically)

• Set resolution and frame rate to what the NVR will actually record

• Set shutter/exposure suited to the scene (especially entrances and headlights)

• Set WDR sensibly (too much can look worse)

• Set day/night behaviour properly (IR, white light, dual illumination)

• Confirm focus and zoom (then physically lock it)

Tip: Do your image tuning at the same time of day the customer cares about. “It looked fine at 11am” doesn’t help if the incident happens at 7pm.

3) Camera security + housekeeping

• Change default passwords (every single time)

• Set correct time zone and time sync method

• Update firmware if needed (ideally before site, but confirm versions)

• Name cameras properly (locations that match labels and IP plan)

• Confirm audio settings if applicable (and customer permissions)

If you need the little “saves your life” parts for mounts, glands, junction boxes, and extras, keep a standard commissioning box stocked from Camera & NVR Accessories. It’s cheaper than burning an hour driving for a £3 part.

NVR commissioning checklist (where overruns love to hide)

Your recorder should be boring. The more “set and forget” it is, the fewer call-backs you’ll get.

Start with a solid base like IP CCTV NVRs that match the job spec (channels, throughput, PoE ports if needed, storage, analytics).

1) Core setup

• Update admin password and create named user accounts

• Set date/time and NTP sync

• Confirm video standard/encoding settings (H.265 vs H.264 as required)

• Set output resolution for the monitor being used

• Name the system clearly (site name + address/postcode for your records)

2) Storage and retention

• Confirm drives are detected and healthy

• Initialise/format drives correctly

• Set overwrite behaviour (recording should not stop because storage is full)

• Confirm retention expectation vs reality (resolution + FPS + motion settings impact this massively)

3) Recording rules (avoid the “why didn’t it record?” moment)

• Decide continuous vs motion vs schedules per camera

• Set motion zones properly (don’t include trees, roads, reflections)

• Set pre-record and post-record time

• Confirm camera streams (main stream for recording, sub stream for remote viewing where appropriate)

• Test playback on at least 2 cameras before you leave

4) Remote access and alerts

• Decide who owns the app login and recovery email

• Confirm network rules needed (if any) and who approves them

• Set push notifications only where they’re genuinely useful (false alerts cause complaints)

• Test remote live view and playback on-site, on mobile data and Wi-Fi

Final handover checklist (protects your time after the job)

This is where you prevent the slow drip of unpaid support.

• Walk the customer through live view, playback, and exporting footage

• Confirm how long footage is retained (in plain language)

• Provide a simple “what to do first” fault guide (power, internet, monitor, etc.)