Objective. Students will conduct a complete system walk-test on a fully installed mock site, complete industry-standard commissioning documentation, and deliver a structured verbal handover briefing to a simulated customer.
This lesson, its worked examples and its practice questions has not yet been verified by a credentialed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Installing hardware is only half the job. A system that is physically complete but never properly tested, documented, or explained to the customer is a liability — for the occupant, for you, and for your license. Commissioning is the formal process of proving that every component works exactly as programmed, recording that proof in writing, and transferring operational knowledge to the end user. ESA and ALOA both treat commissioning as a professional standard, not an optional step. Your state alarm or locksmith license may also carry legal obligations around documentation and customer notification, so treat every item on the commissioning checklist as a compliance requirement, not busywork.
Before you trigger a single sensor, place the panel in walk-test mode. This built-in diagnostic function allows zones to be tripped and logged without dispatching central station or sounding an extended exterior alarm. Never conduct a zone test in full-live mode — an unexpected dispatch wastes emergency responder time and can result in false-alarm fines for the customer.
To enter walk-test mode, follow the panel manufacturer's procedure (typically a master-code command sequence). Confirm on the keypad display that walk-test is active before proceeding. Work through every zone in order — door contacts, motion detectors, glass-break sensors, smoke detectors, and any CCTV motion-trigger inputs — triggering each one individually. After each trip, verify three things on the keypad:
1. The correct zone number appears.
2. The zone descriptor (the text label you programmed) matches the physical location.
3. The status returns to normal (restored) after the device resets.
Record pass or fail for each zone on your commissioning checklist before moving to the next. Do not skip a zone and plan to return — sequence discipline prevents missed entries. Any failed zone must be diagnosed and corrected immediately. Common causes include a reversed tamper loop, a loose end-of-line resistor, incorrect zone type programming, or a disconnected conductor at the device. Correct the fault, re-test the zone, and update your checklist entry before proceeding.
A complete commissioning documentation package has three components.
As-built zone list. Record every zone number, its programmed descriptor, the device type, and its physical location (room name or address). "As-built" means you are documenting what was actually installed, not what the design drawing showed. If anything changed during installation, the as-built reflects reality.
Cable-run log. For each cable run, record the cable type (for example, 22-gauge 4-conductor, RG-59 coax), the measured length, the origin point, and the termination point. Measured length — not estimated — is required. Use a tape measure or a cable-counter reel. Accurate cable records allow a future technician to troubleshoot impedance issues, verify code compliance, and plan expansions without tearing open walls.
Panel programming summary. Document the panel model, firmware version, entry and exit delay settings, each user code slot in use (user name, not the PIN itself), communicator path (cellular, IP, or dual), and central station account number. Leave no required field blank. A blank field on a legal document is an error; write "N/A" only when a field genuinely does not apply.
Inspect your work before calling the instructor over. Cross-reference your zone list against your checklist — every zone that passed walk-test should appear on both. Store all completed forms together in a single package; loose, unlabeled sheets are unprofessional and easy to lose.
The handover is a structured, face-to-face session — not a quick walk-away explanation. You have ten minutes maximum, so prepare a mental outline beforehand. Cover these five topics in order:
1. Arming and disarming — demonstrate the full sequence at the keypad; let the customer repeat it.
2. Entry and exit delay — explain what the countdown means and what happens if the code is not entered in time.
3. Adding and deleting a user code — show the keypad steps; explain why unique codes per user are important for accountability.
4. False alarm response — tell the customer exactly what to do if they accidentally trigger the system: enter the code, answer the central station call with the correct password, and contact you if the situation repeats.
5. Questions — invite and answer questions calmly and completely.
Use plain language. Avoid jargon like "EOLR" or "EOL supervision" with a residential customer. If a customer asks something you are not certain about, say so honestly and commit to finding the answer — never guess about system behavior.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.