Pearl · ps-cx-test-plan-parties-witnesses

Name Test Performers, Witnesses, and Responsibilities Before Release

Release a test procedure only when authorship, direction, execution, witnessing, documentation, and acceptance roles are explicit.

Commissioning management

What to check before the work begins

Do not release the procedure until the writer, test director, performers, witnesses, recorder, issue owner, and acceptance authority are named with clear responsibilities.

Do not release the procedure until the writer, test director, performers, witnesses, recorder, issue owner, and acceptance authority are named with clear responsibilities.
Name the procedure author, director, performers, witnesses, and evidence recorder.
State who may pause or abort the test and who authorizes restart.
Confirm acceptance and deficiency-disposition authority before release.

What the sources describe

GSA written-test guidance identifies required parties and responsibilities, and DOE/FEMP describes a functional testing and monitoring plan. Build Pearls uses that source basis to require a named test-role and witness schedule before release. A result is disputed or unsafe because execution, witness, documentation, or acceptance responsibility was ambiguous.

Evidence to confirm

Test responsibility and witness schedule
Commissioning manager · Before the relevant work begins
Every execution and acceptance function has one named accountable role and an available representative.
Approved test procedure signature and distribution record
Commissioning manager · Before the relevant work begins
The issued revision identifies performers, witnesses, recorder, stop authority, and acceptance authority.

Conditions to resolve before proceeding

Witnesses are invited but not assigned acceptance responsibilities.
The procedure names a vendor but not the individual directing the test.

When this applies

Factory acceptance testing and submittals
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: Test procedure approval, release, or execution briefing
Outside scope: The sources do not prescribe which customer, vendor, contractor, or operator roles apply to every project.
Outside scope: Federal/GSA recommended process is not a universal acceptance standard; project specifications and approved procedures govern.
Federal/GSA recommended process is not a universal acceptance standard; project specifications and approved procedures govern.
The sources do not prescribe which customer, vendor, contractor, or operator roles apply to every project.
The people attending the test already understand who directs, records, witnesses, accepts, and stops it.

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.

Commissioning Process for Federal Facilities
U.S. Department of Energy, Federal Energy Management Program · Step 2 — Investigation; functional testing and monitoring plan · Accessed: 2026-08-06
Open source
GSA Building Commissioning Guide
U.S. General Services Administration · Source date: 2020-09-02 · Written Test Procedures and specification responsibilities; Page Printed p24 · Accessed: 2026-08-06
Open source

Lesson updated 2026-08-06.