Creating a commissioning checklist

What you should be able to do

Write commissioning items that connect an approved requirement to a test, an actual result and retained evidence.

Teaching narration

A useful checklist is more than a column of checkmarks. It tells the next person exactly what was checked, against which requirement, and what remains unresolved. Build it from the approved design, equipment instructions and system-specific acceptance plan. The template below is an original training aid, not an official manufacturer or code form.

Define the item

Identify the asset and one function or requirement. “Camera works” is too broad. “CAM-097 recorded-video playback” identifies a narrower test whose evidence can be reviewed. Enter the required outcome and its source before testing. If the criterion is missing, request clarification; do not invent a passing threshold after seeing the result.

Choose the method

Record the approved test method and prerequisites, including any coordination or permitted test window. Commissioning can affect occupied buildings and connected services. Arrange required authorization and notifications before a test that could interrupt operation. A worksheet does not authorize bypassing protection or changing a live system.

Collect evidence

Enter the actual observation, measurement or report reference, along with the tester and date. Where instruments are used, record the relevant instrument identification, settings and calibration status required by the test plan. Keep evidence tied to the correct device or cable ID.

Manufacturer examples explain why scope matters. AXIS Installation Verifier provides system-performance verification and documentation for an Axis installation. Use its report for what the tool actually evaluates; additional project requirements still need their own evidence. Fluke Networks cautions that a PASS report alone does not necessarily establish cable compliance. Review the selected test limit and report details for the actual installed cable and required scope, rather than treating the word PASS as universal approval.

Worked through

Requirement: retrieve recorded video from CAM-097 for the approved test interval. Observation: live video is visible; no playback test has been performed. Evidence: a live-view screen capture. Status: NOT TESTED for recorded-video playback. Action: the assigned technician performs the approved playback check during the agreed test window and records its result. A successful live view cannot answer the separate playback question. This example does not establish retention duration or test every surveillance function.

Reusable checklist row

Item ID / asset / location: Requirement and source revision: Acceptance criterion: Test method / prerequisites: Tester / date / relevant instrument: Actual result and units where applicable: Evidence file or report reference: Status: Exception / owner / action / retest date: Retest result and evidence: Reviewer and disposition:

Practice

Create three distinct items for a fictional camera installation: asset identification, live view and recorded playback. Give each an acceptance criterion and evidence field. Leave all execution results NOT TESTED until the tests actually occur.

Knowledge check

Sources