Pearl · ps-cx-return-normal-in-every-script

Include Initial Configuration and Return-to-Normal in Every Test Script

Define the initial configuration and verify restoration to normal operation in every functional test procedure.

Construction terms explained

OEM:: original equipment manufacturer

What to check before the work begins

Define the safe initial configuration, test-state changes, project-approved contingency where applicable, and witnessed return-to-normal checks before execution.

Define the safe initial configuration, test-state changes, project-approved contingency where applicable, and witnessed return-to-normal checks before execution.
Record the required initial configuration and who verifies it.
Make each deliberate state change and affected dependency visible in the script.
Define observable return-to-normal criteria and final signoff.

What the sources describe

The GSA guide says written procedures include step-by-step system configuration for the test and return to normal operation. Build Pearls adds a visible initial-state, contingency, and witnessed recovery register around that setup-and-restoration requirement. The test finishes with an interlock, alarm, mode, bypass, setpoint, or dependency left in an unintended state.

Evidence to confirm

Issued script with initial-state and restoration sections
Commissioning authority · Before the relevant work begins
The script defines setup, state changes, restoration steps, expected normal state, and witnesses.
Completed return-to-normal verification record
Commissioning authority · Before the relevant work begins
Modes, alarms, interlocks, bypasses, setpoints, and dependencies match the accepted normal state.

Conditions to resolve before proceeding

The script ends at the expected failure response.
Restoration says only 'return system to normal' without observable checks.

When this applies

Functional performance testing
Integrated systems testing

Assess each lesson against your project, equipment, and local requirements with the people responsible for the work.

Limitations and context

Applies when: Approval of any functional or integrated script that changes system state
Outside scope: Abort and contingency planning is Build Pearls' operational translation, not a direct claim from this locator.
Outside scope: Project safety rules, OEM instructions, and approved procedures govern the recovery method.
Abort and contingency planning is Build Pearls' operational translation, not a direct claim from this locator.
Project safety rules, OEM instructions, and approved procedures govern the recovery method.
Once the stimulated response is observed, the system will automatically recover to its intended normal state.

Where the lesson comes from

Sources

Use the original material to understand the evidence, scope, and context behind this Pearl. Suggested project actions are Build Pearls’ interpretation.

GSA Building Commissioning Guide
U.S. General Services Administration · Source date: 2020-09-02 · Written Test Procedures — configuration for test and return to normal operation; Page Printed p24 · Accessed: 2026-08-06
Open source

Lesson updated 2026-08-06.