Building Automation Point-to-Point Verification

It covers the full BAS point list from setup through final sign-off, including point identification, analog input and output checks, digital input and output checks, and documentation of deficiencies. The template is designed to compare the controller database, graphics, and field device response so you can confirm each point behaves as intended. It is useful for commissioning and turnover, not for routine maintenance rounds.

Run it during commissioning, after controls installation is complete, after major programming changes, and before owner acceptance. It is also useful after point additions, controller replacement, or graphics/database updates that could affect mapping or scaling. It is not the right tool for a quick preventive maintenance check because it is built to verify each point individually.

A controls technician, commissioning agent, or qualified BAS inspector should run the template, with access to the approved point list and sequence of operations. The person performing the check should understand the system logic, field devices, and safe test conditions. For interlocks and life-safety-related sequences, coordinate with the commissioning team and any required trade or AHJ oversight.

This template supports commissioning and quality verification practices commonly used under building controls and energy management projects, and it can help document conformance with project specifications and owner requirements. Where BAS points affect fire-life-safety, smoke control, or emergency shutdown functions, coordinate with applicable NFPA codes and the Authority Having Jurisdiction. It also fits well within ISO 9001-style quality records and formal commissioning workflows.

It often surfaces swapped point addresses, mislabeled graphics, reversed analog scaling, unstable digital inputs, and outputs that do not drive the intended device. It also catches fail positions that were programmed incorrectly, overrides that do not release, and alarm logic that does not change state when the field condition changes. These are the kinds of defects that are easy to miss if you only review the screen without testing the field device.

Yes. You can adapt the point naming, controller channel fields, graphics references, and device-specific response checks for the BAS platform in use. The core structure stays the same: identify the point, verify the controller data, operate the field device, and record the result. That makes it easy to tailor for HVAC, lighting controls, or specialty systems without changing the inspection logic.

An ad hoc walk-through usually checks only visible operation, which can miss mapping errors, scaling drift, or logic problems that do not show up at a glance. This template forces a point-by-point comparison between the database, the controller, and the physical device response. That creates a cleaner turnover record and makes it easier to assign corrective actions when a non-conformance is found.

Have the approved point list, sequence of operations, and control drawings on site, along with calibrated test equipment and a system placed in commissioning mode or another approved test condition. You should also confirm work authorization and identify the inspector before testing begins. Without those inputs, it is hard to prove whether a mismatch is a field defect, a programming issue, or a documentation problem.