Role-boundary reasoning plus OPR-to-criterion conversion: classify who owns each decision, then write acceptance criteria a stranger could test.
Scenario Questions Turn on One Question First: What May the CxA Actually Decide?
Before evaluating any system detail, decide which decision belongs to the commissioning authority: verifying an observed result, documenting a deficiency, recommending a disposition, or escalating to the owner or designer. Everything else in a scenario follows from that boundary.
In commissioning practice the authority's mandate is to verify, document, and facilitate — not to design, construct, or accept work on behalf of others. Separate four verbs. Verify: check an observed result against a stated criterion. Document: record the result, its source, and its traceability. Recommend: propose a disposition while leaving the decision with the owner or designer. Escalate: route an unresolved conflict upward. A designer approves design changes; a contractor demonstrates compliance; the authority witnesses tests and records whether criteria were met.
Apply this routing habit before touching technical content. For each stem ask: who owns this decision, what evidence exists, and which written criterion applies. If equipment performs correctly but records are missing, the answer concerns documentation, not retesting. If equipment misses a criterion and the contractor proposes a workaround, the disposition belongs to whoever set the criterion, normally the owner's requirements as channeled through the commissioning process. Two-step lookup: role boundary first, system details second.
OPR, Basis of Design, Commissioning Plan, and Specifications Answer Four Different Questions
The Owner's Project Requirements state measurable intent; the Basis of Design records the designer's response; the commissioning plan defines how verification happens; specifications assign execution duties. Matching each scenario fact to the right document prevents miscategorized answers.
Trace the lineage of each document. The Owner's Project Requirements (OPR) hold measurable intent: temperature and humidity targets, reliability and efficiency aims, documentation and training expectations. The Basis of Design (BOD) records the designer's response, chosen systems, and assumptions. The commissioning plan, developed under the authority's direction, sets scope, roles, test approaches, and acceptance methods. Specifications carry commissioning duties contractually to contractors — start-up reports, notifications, checklist completion. Four questions answered: what was wanted, why it was chosen, how it will be verified, who must perform.
Drill the match with numbers. A target written in the OPR is the benchmark for acceptance. The same value appearing only in the BOD is a design assumption: you can verify against it, but you cannot treat it as owner-mandated if the OPR is silent. A scenario fact describing a duty — notify before testing, submit a start-up report — is a specification or plan item, so the answer concerns duty compliance rather than system performance.
Installation Verification, Functional Performance Testing, and Integrated Testing Are Not Interchangeable
Installation verification confirms components are installed and started correctly; functional testing exercises equipment against written criteria; integrated testing proves systems interact under realistic conditions. Confusing the three levels is the easiest way to misread a commissioning scenario.
The levels differ in trigger, evidence, and executor. Installation verification, often captured in pre-functional checklists, confirms components are installed, labeled, started, and safe to test; the contractor executes and the authority spot-checks. Functional performance testing manipulates controls and compares measured response with written criteria; the authority witnesses and approves results. Integrated systems testing runs sequences spanning several systems — HVAC interacting with power or life-safety functions — under coordinated conditions the authority helps direct.
Use cue words to classify fast. Installed, labeled, started, and safety checks present point to verification. Modulates, stages, or maintains setpoint at part load point to functional testing. Simultaneous failure, transfer, or building-wide response points to integrated testing. When a functional test fails, the response chain is fixed: document the measured result, open an issues-log entry, name the corrective party, and schedule retest after correction. Redesigning the system is not the authority's move; that decision belongs to the designer and owner.
| Stage | Question it answers | Typical executor | Authority's role |
|---|---|---|---|
| Installation verification | Is it installed, started, and ready to test? | Contractor, using checklists | Spot-checks and reviews documentation |
| Functional performance testing | Does it meet the written criterion? | Contractor or authority, per plan | Witnesses, approves criteria, records results |
| Integrated systems testing | Do systems work together in realistic sequences? | Coordinated, often authority-led | Directs conditions, witnesses, documents |
| Issues-log tracking | What is open and who closes it? | All parties | Maintains the log and verifies closure |
Worked Scenario 1: A Chilled-Water Coil That 'Runs Fine' But Misses Its Part-Load Sequence
The tempting answer passes the test because equipment operates without faults; the defensible answer holds the test open because the measured response misses the written sequence criterion at reduced load. Acceptance tracks criteria, not impressions of health.
Paper scenario: a chilled-water coil passes startup cleanly; valves stroke; the pump runs. During functional testing at reduced load, the control valve drives fully closed, yet supply air temperature stays below the sequence's target band, threatening overcooling. The tempting call is to pass the test: no alarms tripped, startup was clean, and the crew wants to close out. That substitutes an impression of equipment health for the acceptance criterion written into the plan.
The defensible call: record the measured response beside the criterion, mark the test failed at that operating point, open an issues-log entry naming the balancing or controls contractor as corrective party, and require retest at the same condition after adjustment. Results become defensible when traceable to written criteria and measured values; a pass granted on general impressions cannot survive a later dispute or a seasonal issue resurfacing. That criterion-to-measurement-to-disposition chain is the applied practice skill to rehearse.
Worked Scenario 2: A Sign-Off Request That Crosses the Authority's Role Boundary
When a contractor or designer asks the authority to certify unfinished items or approve a substitution directly, the compliant move is to decline, document, and route the request to the proper decision-maker — preserving independence and the record.
Paper scenario: weeks before acceptance, a contractor asks the authority to pre-sign verification checklists for items still in progress, and a designer emails asking the authority to accept a controls substitution on the spot. Both requests sound cooperative and schedule-friendly. The tempting move is signing to keep the project moving. But one request asks the authority to certify work it has not verified, and the other asks it to exercise design approval it does not hold.
The defensible response, in writing: verification follows completed work with evidence, so open items enter the issues log with responsible parties and dates; the substitution routes to the owner and designer, and the outcome is recorded in the commissioning log. Independence is the authority's core professional obligation: the owner's trust depends on verifying rather than vouching, and on decisions made by those empowered to make them. A signature under schedule pressure makes the authority a party to the deficiency.
A Ten-Minute Documentation Exercise: Turn One OPR Line Into a Testable Criterion
Take a single OPR sentence and rewrite it as an acceptance criterion a stranger could test: measurable value, operating condition, method, and retest rule. Then grade your draft against the rubric below before moving on.
Exercise: take the OPR line 'The conference room shall be comfortable and energy efficient' and rewrite it as a criterion a stranger could test. First drafts typically produce vague statements such as 'the system performs well' — that vagueness is exactly what this drill should reveal to you. A stronger rewrite: 'At 40–60% of design airflow, room temperature holds 72–75°F with the VAV box at minimum flow; verify by a 30-minute trend; retest after any correction.'
- Numeric or observable pass band is stated (score 0–2)
- Operating condition is specified: load, mode, season (0–2)
- Verification method named: trend, measurement, observation (0–2)
- A corrective party is identifiable if the criterion fails (0–2)
- A retest or disposition rule is stated (0–2)
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.