Pearl · ps-cx-prerequisites-before-functional-test

Close Explicit Prerequisites Before Functional Performance Testing

Put system and assembly prerequisites in the script and evidence them before functional test release.

What to check before the work begins

List each system and assembly prerequisite in the script and release the test only when its evidence is accepted or explicitly dispositioned under project rules.

List each system and assembly prerequisite in the script and release the test only when its evidence is accepted or explicitly dispositioned under project rules.
Define measurable prerequisites for the system, dependencies, utilities, controls, and safety state.
Link every prerequisite to evidence and an accountable owner.
Record authorized disposition for any unmet item before release.

What the sources describe

The GSA guide states that a written test procedure identifies the system and assembly prerequisites required before the test is performed. Build Pearls turns the written-prerequisite requirement into an evidence-linked release decision with visible project-authorized disposition. Testing starts against an incomplete prerequisite and produces unsafe, invalid, or non-repeatable results.

Evidence to confirm

Approved prerequisite register linked to the issued test script
Commissioning manager · Before the relevant work begins
Every prerequisite has accepted evidence or an authorized, visible disposition.
Dependency and safety-state readiness confirmations
Commissioning manager · Before the relevant work begins
Upstream, downstream, controls, utility, and safety dependencies match the test's required initial state.

Conditions to resolve before proceeding

Prerequisites appear only in meeting notes, not the issued script.
An unmet prerequisite is described as minor without named acceptance authority.

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: Functional performance or integrated test release
Outside scope: The source does not say every project deficiency blocks every test.
Outside scope: Prerequisites, deferment authority, and acceptance remain project-specific.
Outside scope: Federal/GSA guidance is not automatically a mandatory project standard.
Federal/GSA guidance is not automatically a mandatory project standard.
Prerequisites, deferment authority, and acceptance remain project-specific.
The source does not say every project deficiency blocks every test.
A scheduled test date means the system, dependent systems, controls, utilities, and safety conditions are ready.

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 — prerequisites for performance of each test; Page Printed p24 · Accessed: 2026-08-06
Open source

Lesson updated 2026-08-06.