BAS Sequence of Operation Functional Test

It covers the core control behaviors that should match the approved sequence of operation: occupied and unoccupied schedules, reset logic, setpoint changes, emergency mode response, alarm annunciation, and return-to-normal behavior. The template is built to document what was tested, what the BAS actually did, and where a deficiency was found. It is not a point-to-point commissioning script for every device in the building. Use it when you need a focused functional test of the control narrative.

Use it during commissioning, re-commissioning, seasonal testing, after BAS programming changes, and after tenant fit-outs that affect schedules or setpoints. It is also useful after a controls retrofit or when operators report comfort complaints that suggest logic drift. If the sequence has changed, this template helps confirm the new behavior matches the approved drawings and narrative. It is less useful for purely mechanical inspections that do not involve BAS logic.

A commissioning authority, controls technician, facilities engineer, or other competent person should run the test, with the controls contractor present when programming access or live adjustments are needed. The person performing the test should understand the approved sequence of operation and the equipment being controlled. For emergency mode checks, coordinate with the owner and any required safety or operations staff before initiating the test. The template also works well when an owner’s representative is observing the results.

It supports documentation and verification practices commonly expected under OSHA general industry and construction safety programs, especially where BAS controls interact with emergency systems, lockout-tagout, or safe work conditions. It also aligns with commissioning and quality practices used in ANSI/ASSP and ISO 9001-style verification workflows. If the system touches fire-life-safety functions, coordinate with the AHJ and applicable NFPA requirements before testing. The template is not a substitute for code-required acceptance testing.

A common mistake is testing only whether the BAS screen changes, rather than verifying the actual equipment response in the field. Another is failing to document the exact setpoint, schedule time, or reset condition that was observed, which makes retesting difficult. Teams also sometimes skip holiday or override modes, even though those are frequent sources of complaints. Finally, emergency mode testing should not be done without confirming safe work controls and the correct people are present.

Yes. You can add the specific air handlers, VAV boxes, boilers, chillers, or plant loops under test, along with vendor-specific point names and graphics references. You can also expand the schedule section for 24/7 spaces, labs, healthcare areas, or tenant-specific occupancy patterns. The template is intentionally reusable, so you can tailor the test steps without changing the overall inspection flow. Keep the observable result fields intact so findings remain comparable over time.

Repeat it whenever the sequence of operation changes, after major maintenance, and on a periodic basis that matches the owner’s preventive maintenance or commissioning plan. Many teams also run it seasonally because reset logic and schedule behavior can look correct in one season and fail in another. Emergency mode checks should be repeated after any alarm point, panel, or integration change. The right cadence depends on risk, occupancy, and how often the BAS is modified.

An ad-hoc walk-through often catches obvious issues, but it usually misses whether the BAS actually follows the approved sequence under changing conditions. This template forces a repeatable test path: schedule, reset, setpoint, emergency mode, and signoff. That makes it easier to assign corrective actions and retest failed sequences. It also creates a record that can be compared across seasons, contractors, and building changes.