Studying commissioning involves more than memorizing terms: the concepts demand process decision logic — recognizing which phase a scenario describes and choosing the action the process calls for at that point. A workable approach: before touching any answer options, anchor each practice scenario to two questions — 'Which phase is this?' and 'What do the documented Owner's Project Requirements say?' Build fluency in named deliverables such as the OPR, Basis of Design, issues log, and systems manual, drill deficiency responses, and close with a self-scored rubric. This guide teaches those moves through worked scenarios, a decision table, and an adaptable study sequence.
Telling Verification Apart from Functional Performance Testing
Verification confirms that installed components and subsystems match contract documents and the OPR, typically through inspection and pre-functional checklists. Functional performance testing then exercises complete systems and sequences under realistic operating conditions.
Verification is component- and subsystem-oriented: it asks whether equipment was installed correctly, connected as designed, and ready for system-level work, with pre-functional checklists documenting that readiness. Functional performance testing is system-oriented: it operates equipment through startup, part-load, changeover, and failure-response sequences, often spanning multiple interacting systems, and records how the whole responds rather than how a single component behaves.
In scenario questions, use the distinction to eliminate options: if the stem describes a completed system being run through seasonal or emergency modes, functional testing language applies; if it describes equipment before systems are complete, verification language applies. An option that jumps to full-system testing while subsystems remain unchecked — or that keeps running component checks after systems are operational — usually misplaces the activity within the process.
Matching Commissioning Actions to the Correct Project Phase
ASHRAE guidance describes commissioning as a process spanning pre-design, design, construction, occupancy, and ongoing operation. Each phase carries distinct deliverables, and a scenario's correct action depends on identifying its phase first.
Pre-design centers on developing the Owner's Project Requirements. Design-phase work includes reviewing the Basis of Design and drawings against those requirements and writing commissioning specifications into the contract documents. Construction shifts to verification and functional performance testing. Occupancy and operations bring deferred or seasonal testing, staff training, the systems manual, and later ongoing commissioning activities such as monitoring-based approaches.
Train one habit: before reading the options, label the stem's phase. A question about reviewing design documents is not answered by 'perform an FPT'; a question about a building in its third year of operation is not answered by 'review the Basis of Design.' Phase labels also clarify who acts: the commissioning provider reviews design documents, contractors perform work under the commissioning plan, and the owner sustains the requirements after turnover.
Anchoring Every Judgment in the Owner's Project Requirements
The OPR documents what the owner expects the facility to do; the Basis of Design records how the design intends to meet it. Scenario disputes usually resolve by tracing back to these documents.
Treat the OPR as the reference point for nearly every judgment: whether a test passed, whether a design change is acceptable, whether a deficiency actually matters. The Basis of Design explains the intent behind equipment selection, setpoints, and sequences, so a sequence that looks odd may still be deliberate. Design review comments gain force when they cite a specific documented requirement the design does not satisfy, rather than general opinion.
When two answer options both sound reasonable, prefer the one tied to documented requirements over one based on preference or general best practice. A proposed improvement that contradicts the OPR — say, a control strategy the owner already rejected for maintainability reasons — is not an upgrade. In practice notes, name the OPR expectation each decision depends on; tracing decisions to documented requirements is precisely the judgment the commissioning process demands, and rehearsing it in writing makes that habit automatic.
Responding to a Failed Functional Performance Test
A failed FPT calls for documentation, root-cause evaluation, correction by the responsible party, and a retest of the original sequence. Improvising adjustments or quietly narrowing the test breaks the process's traceability.
Scenario 1: during an air-handler FPT, the economizer changeover sequence fails because mixed-air control drifts at low outdoor temperature. A plausible mistake is adjusting setpoints at the controller until the sequence appears to pass, then moving on. That undocumented tweak can mask an interaction with a second unit or an underlying sensor fault, and nothing records why observed behavior differed from the documented sequence of operation.
The stronger response logs the deficiency in the issues log with the observed behavior, coordinates correction with the controls contractor, and retests the original sequence unmodified. If the triggering condition cannot occur until winter, the test is deferred and formally tracked as a seasonal item. Traceability matters because a later reviewer must be able to connect each deficiency to its resolution and to the verified, unchanged sequence.
| Observation during testing | Weaker response | Stronger response | Why it matters |
|---|---|---|---|
| Sequence passes only after an on-the-spot setpoint change | Accept the pass and proceed | Log a deficiency, correct the cause, retest the original sequence | An undocumented change hides true system behavior from later reviewers |
| An interlocked exhaust fan also misbehaves during the test | Ignore it as outside this test's scope | Record it as a separate issue and evaluate its impact on the tested system | Deficiencies in one system can invalidate conclusions about another |
| Required test conditions cannot occur in the current season | Force the condition roughly and test anyway | Defer the test, document required conditions, schedule a retest | Formally tracked deferred items are less likely to be forgotten at turnover |
| Two contractors each blame the other's scope for the failure | Pick a side based on familiarity | Use the documented sequence and verification records to locate the fault | Documentation, not opinion, resolves scope disputes |
Choosing the Entry Point for Existing-Building Commissioning
Existing-building work begins with assessment and developing current facility requirements alongside owner expectations. Without a documented baseline, observed performance cannot be judged deficient, efficient, or acceptable in any defensible way.
Scenario 2: the owner of a mid-size office reports high energy bills and asks what to replace first. A plausible mistake is recommending equipment upgrades or launching tests immediately. The better sequence: perform an assessment to establish current facility requirements — how the building is actually used and operated — document owner expectations as the baseline, gather operating and energy data, then prioritize findings against that benchmark.
Why it matters: the same supply-air temperature could be a fault in one building and a deliberate choice in another; only a documented baseline distinguishes them. Existing-building commissioning also differs from new-building work in deliverables — findings reports and an ongoing monitoring plan replace construction-phase checklists — so keep the two sets of phase actions separate when drilling scenarios.
Closing the Loop: Issues Log, Systems Manual, and Training
Documentation carries the commissioning process beyond construction: the issues log tracks deficiencies to closure, the systems manual transfers operating knowledge, and verified training prepares operators. A scenario can test whether you complete this loop.
An issues log is a living record: each entry needs the deficiency, the responsible party, the required correction, and closure criteria confirmed by retest or verification — not a verbal assurance. In scenario stems, an answer claiming an issue is 'resolved' without documented retest is weaker than one demanding confirmation. The log also feeds the systems manual, so unresolved items surface in the operating documentation handed to the owner.
The systems manual consolidates design intent, sequences, setpoints, maintenance guidance, and the record of what was verified, so operators can run the building as commissioned. Training verification confirms operators actually received and absorbed instruction on those systems, typically scheduled near occupancy or as systems are completed. Treat 'training was provided' as incomplete evidence; the process asks for evidence the training achieved its purpose.
A Study Sequence and Readiness Checks You Can Self-Score
Study the process phase by phase, then drill scenario decisions, then assess yourself against a written rubric. Treat self-check scores as learning milestones for your study, not as predictions of any exam outcome.
An adaptable sequence: first, build a one-page map of the phases and each phase's deliverables from memory, then check it against your references. Second, drill term pairs — OPR versus Basis of Design, verification versus FPT, new-building versus existing-building deliverables. Third, work scenario sets where you classify the phase and trace the decision to a requirement before reading options. Fourth, rebuild Section 4's deficiency-response table from memory. Administrative details such as scheduling and eligibility are maintained by ASHRAE; its website is the place to confirm them.
Score each readiness check below 0–2 (absent, partial, complete). A consistent 2 across all checks suggests you are ready to move to timed scenario practice; any 0–1 item points to what to restudy before moving on. Re-run the rubric weekly in your final phase of preparation, and use the gap between your written answers and your references — not a running total of correct answers — as your measure of progress.
- Write the five phases and two deliverables each, from memory, in ten minutes.
- Classify a practice scenario's phase, then name one phase-mismatched option and why it fails.
- Justify a scenario decision by citing an OPR expectation rather than personal preference.
- Reproduce the four-step deficiency response — document, evaluate, correct, retest — unprompted.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.