Prepare for the CBCP by studying the commissioning process as a chain of decisions: requirements documents drive test criteria, test results drive issues log entries, and issues drive phase transitions and reporting. Work through paper scenarios where you must name the governing document, classify the commissioning type, justify pass/fail reasoning, and state what evidence belongs in the record.
Owner's Project Requirements versus Basis of Design: which document controls a dispute
The OPR states what the owner needs the building to do; the Basis of Design records how the design team intended to meet those needs. When they conflict, the OPR governs acceptance decisions.
In commissioning practice shaped by frameworks like ASHRAE Guideline 0, the OPR is the owner-facing benchmark: required temperatures, humidity ranges, ventilation rates, reliability expectations, energy targets, and operability preferences. The BOD is the design narrative explaining component selections, calculated loads, and control philosophies. A commissioning provider tests against the OPR and verifies the design intent captured in the BOD, so knowing which document a scenario is pointing to changes your answer.
Train this distinction with a drill: for each exam statement, ask 'Is this a requirement the owner stated, or an engineering decision made to satisfy it?' 'Maintain 40-55% relative humidity in the archive room' is OPR language. 'The dedicated outdoor air unit uses a desiccant wheel because chilled water alone cannot reach the design dew point' is BOD language. If a scenario says the installed system meets the design but not the owner's stated range, the correct action references the OPR, because the design is a means, not the acceptance criterion.
New construction, retro-commissioning, and re-commissioning: classifying the process you are being asked about
New-building commissioning verifies delivery against the OPR; retro-commissioning improves an existing building never commissioned; re-commissioning repeats testing on a building previously commissioned. The classification determines the starting documents and scope.
This classification matters because each type begins from a different evidence base. New construction commissioning starts from design-phase OPR and BOD documents and proceeds through installation verification, startup support, functional testing, and seasonal or warranty-period activities. Retro-commissioning starts from the building as-found: current facility requirements and a systems manual may not exist, so the provider often must help reconstruct them before meaningful testing benchmarks exist. Re-commissioning reuses the original OPR and prior commissioning records as the baseline for retesting.
In scenario questions, look for the clues: an occupied 20-year-old hospital with comfort complaints and no commissioning history points to retro-commissioning; a five-year-old office whose energy performance drifted and which has a commissioning report on file points to re-commissioning; a building in design development with an OPR under review points to new construction commissioning. Choosing the wrong type in your answer usually cascades into wrong recommendations, because retro-commissioning options do not include design-phase reviews, and new construction options do not start with an as-built investigation. Practice classifying before you evaluate anything else in a scenario.
| Attribute | New construction Cx | Retro-commissioning | Re-commissioning |
|---|---|---|---|
| Starting documents | OPR, BOD, design documents | Current facility requirements (often created during the project) | Original OPR and prior Cx report |
| Typical trigger | Project delivery of a new or majorly renovated building | Persisting comfort, energy, or operational problems | Performance drift after prior commissioning |
| Phase emphasis | Design and construction review through functional testing | Investigation, diagnostic testing, corrective measures | Retesting against established baselines |
| Common exam clue | OPR being developed or reviewed | No prior commissioning history | Existing commissioning report referenced |
Worked scenario: a functional performance test fails under partial load
A system passing at design load but failing at part load has not passed the test; the correct action is to record the deficiency, diagnose, and retest, not to declare success.
Scenario: during functional testing, a variable air volume system holds supply air temperature and duct static pressure at design airflow, but when the test simulates low-load operation at roughly 30% airflow, the minimum outdoor air delivery drops below the ventilation requirement and the zone overcools. A plausible mistake is to accept the result because 'the system performs at design conditions and part-load behavior is a tuning matter.' That reasoning confuses capacity verification with control sequence verification; the functional test exists to confirm the system responds correctly across the operating range the OPR describes, not only at one point.
The better decision treats this as a documented deficiency: record the observed sequence behavior in the issues log with the test conditions and readings, identify the likely cause (a minimum-position reset sequence or static pressure setpoint logic error), require the controlling contractor to correct it, and repeat the functional test under the same simulated conditions before sign-off. This matters because part-load hours dominate operation in most climates; a system verified only at design load can fail the owner's requirements for most of its life. Practice rewording test results so they state conditions, observed response, expected response, and disposition, since a strong scenario answer depends on precisely that structure rather than vague acceptance language.
Worked scenario: an unresolved issues log item at substantial completion
An open deficiency that affects a system's ability to meet the OPR is a condition to resolve or formally accept with owner sign-off; it is not something to quietly carry into the commissioning report.
Scenario: the project reaches substantial completion, and the issues log still shows an unresolved item: the laboratory exhaust system's fail-safe mode was tested and the sash sensors respond slowly, but the contractor argues the sequence is 'functionally acceptable.' A plausible mistake is to close the item with a note like 'addressed' or to leave it open with no owner decision. Both undercut the documentation chain: the issues log is the traceable record connecting each deficiency to its verification, responsible party, and resolution evidence.
The better decision is to classify the item by consequence: does it prevent the system from meeting an OPR requirement, or is it a minor punch-list quality matter? If the delayed sensor response could compromise exhaust during an alarm event, the item remains a functional deficiency with retest required before acceptance. If the owner, fully informed of the risk and cost, elects to accept it, the log records that decision with the owner's authorization. This matters because the commissioning report's credibility rests on every issue having a traceable disposition. When you practice scenarios, write the disposition sentence you would put in the log; if you cannot state who decided, on what evidence, and what retesting occurred, your answer is incomplete.
Documentation that survives scrutiny: the commissioning report, systems manual, and verification records
Defensible commissioning documentation links each requirement to a test, each test to an observation, and each observation to a disposition. Learn the documents by their distinct purposes, not as interchangeable paperwork.
The commissioning report summarizes the process: what was tested, when, by what methods, what deficiencies were found, how they were resolved, and what remained open with owner decisions. The systems manual is the operator-facing deliverable, containing operation and maintenance information, control sequences, and the design intent narrative the operations staff will need after the commissioning team departs. Functional test records sit underneath both, capturing the specific setpoints simulated, sensor readings, and response observations. A precise answer names the right document for the right purpose.
A useful exercise: take a single scenario event, such as a chilled water plant that failed its low-load staging test in August, and write the three documentation traces it generates. The test record shows the simulated loads and observed chiller response; the issues log entry records the deficiency, responsible party, and resolution plan; the report notes that seasonal retest is pending at winter conditions. If your three write-ups contradict each other on any fact, you have found an inconsistency worth fixing before it shapes your scenario answers. Rebuild until the chain from requirement to test to observation to disposition is consistent and traceable.
- Test record: conditions simulated, expected response, observed response, instrument identity.
- Issues log entry: deficiency description, classification, responsible party, target resolution, final disposition evidence.
- Commissioning report: scope executed, deficiencies and resolutions, items accepted with owner authorization, recommendations.
- Systems manual: sequences of operation, O&M procedures, design intent summary for operators.
Seasonal and warranty-period verification: a paper exercise you can run this week
Systems commissioned in one season may fail under opposite-season conditions; seasonal verification and warranty review exist to catch this. Practice planning them on paper with a rubric.
A heating plant tested in July has never demonstrated its sequence at freezing conditions, and an economizer tested in January has never been exercised in cooling season. Commissioning practice addresses this with scheduled seasonal performance verification during the warranty period, plus a warranty review near its end so deficiencies surface while contractual remedies remain available. To sharpen your judgment, add a rule to your scenario drills: whenever a scenario states the test date or climate, write down which modes that season can and cannot verify, and mark every unverified mode as a planned follow-up with its required conditions. A test performed in the wrong season is a scheduled obligation, not a closed item.
Run this exercise on any building you know, using paper and observation only, with no valve turning or control changes. Pick one air-handling system. From the sequence of operations, list three modes it should exhibit (occupied cooling, occupied heating, economizer) and note which are verifiable now versus which require the opposite season. Walk the space and observe: are zone temperatures consistent with the mode you believe is active? Do the terminal units' visible indicators match the sequence? Score yourself on a rubric: 3 points if you correctly identified the governing sequence document, 3 if you separated verifiable-now from seasonal items, 2 if your observations were specific (readings, positions, times) rather than impressions, 2 if you wrote a follow-up plan naming the season and conditions required. A self-check under 7 out of 10 tells you to repeat the exercise on a second system.
A preparation sequence from concepts to exam-style judgment
Sequence your study in four passes: vocabulary distinctions, process phases, scenario drills, and timed documentation practice. Each pass should produce written artifacts you can re-check.
Pass one: build a distinctions sheet pairing terms that are easy to conflate, such as OPR versus BOD, commissioning versus testing-adjusting-balancing, verification versus functional performance testing, and the three commissioning types. For each pair, write one sentence stating how a decision would differ depending on which concept applies. Pass two: map the commissioning process phases for new construction (pre-design through warranty period) and for existing buildings, and note which deliverables mark each transition. Keep this grounded in widely used frameworks such as ASHRAE Guideline 0 and Standard 202 rather than inventing your own phase names.
Pass three: write your own scenarios. Take a system type (VAV, chilled plant, laboratory exhaust, dedicated outdoor air unit), invent a test result, and answer four questions: which commissioning type is this, which document sets the criterion, does the result pass, and what is the disposition? Check your answers against the distinctions sheet from pass one; contradictions reveal where your understanding is thin. Pass four: practice writing dispositions and log entries under time pressure, holding your work to a self-study standard in which every answer names the governing document, states the observed and expected conditions, and ends with a concrete disposition. Treat any self-assigned milestone score as a learning indicator, not a prediction of exam results. For administrative matters such as eligibility requirements and scheduling, rely on AEE directly.
- Weeks 1-2: distinctions sheet and phase maps, reviewed against ASHRAE-based frameworks.
- Weeks 3-4: classification drills on building types; three self-written scenarios per session.
- Weeks 5-6: documentation practice, writing test records and issues log dispositions to a rubric.
- Final week: timed scenario sets; re-check every answer names the governing document and states a disposition.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.