Pearl · ps-cx-expected-observed-acceptance-record

Record Expected, Observed, and Accepted Test Results

Predefine acceptable performance and preserve actual conditions, results, exceptions, issue references, and dated signoff.

Construction terms explained

OEM:: original equipment manufacturer

Commissioning management

What to check before the work begins

Predefine expected results and acceptable ranges, then record actual conditions, observed results, acceptability, issue references, retest status, and dated performer and witness signoff.

Predefine expected results and acceptable ranges, then record actual conditions, observed results, acceptability, issue references, retest status, and dated performer and witness signoff.
Set expected results and acceptable ranges before execution using project-approved criteria.
Record test identity, date/retest status, system/location, conditions, observations, acceptability, and issue links.
Obtain dated performer and witness accountability on the completed record.

Use in the project example

What the sources describe

The GSA guide calls for expected and acceptable performance in the procedure and a completed record containing test identity, conditions, expected and observed results, acceptability, issues, retest status, and dated performer/witness signatures. Build Pearls converts those record elements into a gate evidence request tied to issue and restoration records. A result cannot be verified, compared, retested, or defended because conditions, expected values, observations, exceptions, or accountable signoff are missing.

Evidence to confirm

Issued test script with expected results and acceptance ranges
Commissioning authority · Before the relevant work begins
Every measured or observed step has a project-approved expected result or acceptance criterion.
Completed traceable test and retest record
Commissioning authority · Before the relevant work begins
The record includes identity, conditions, actual results, acceptability, issue references, and dated performer/witness signoff.

Conditions to resolve before proceeding

Acceptance values are added after results are known.
Evidence cannot distinguish an original test from a retest.

When this applies

Functional performance testing
Integrated systems testing
Operations acceptance and ready for service
Reliability / load demonstration

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

Limitations and context

Applies when: Test execution and final acceptance of the test record
Outside scope: The source does not provide system-specific acceptance values.
Outside scope: Project design, owner requirements, OEM criteria, and approved procedures must supply acceptance values and authority.
Project design, owner requirements, OEM criteria, and approved procedures must supply acceptance values and authority.
The source does not provide system-specific acceptance values.
A pass/fail mark and a few screenshots are enough to reconstruct what was tested and why it was accepted.

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; functional-performance test record content; Page Printed p24 and pp28–29 · Accessed: 2026-08-06
Open source

Lesson updated 2026-08-06.