ASHRAE BCxP common mistakes
ASHRAE BCxP · Understand the traps and how to avoid them.
Treating commissioning as a construction-phase activity that starts when the contractor mobilizes, and answering questions about the Cx team's involvement as if the Cx provider first appears at pre-functional checklists.
Many candidates come from field-testing backgrounds where Cx is experienced as TAB, startup, and FPT; the early-phase planning, OPR, and design review work is abstract and gets skimmed.
What to do instead
Memorize the phase sequence and the Cx provider's deliverable in each phase (initiation/planning, OPR, BOD, design review, specs/procurement, construction, FPT, seasonal, training/systems manual, final report), and for any scenario question ask 'which phase is this and what is the Cx deliverable here?' before choosing an answer.
Confusing the roles of the commissioning authority (CxA), owner, design team, contractor, and commissioning team, and selecting answers where the CxA assumes design responsibility or directs contractor means and methods.
The authority/oversight distinction is subtle and the exam deliberately offers plausible answers where the CxA 'approves' or 'designs' rather than reviews, verifies, and documents.
What to do instead
Build a role matrix (who authors, who reviews, who verifies, who approves, who documents) for OPR, BOD, specs, submittals, FPT, and the final report; default to the principle that the CxA verifies and reports to the owner and never takes design or construction responsibility.
Writing or selecting OPR content that is really a restatement of the design (equipment capacities, sequences) instead of measurable owner program requirements such as environmental criteria, occupancy schedules, redundancy, maintainability, and training needs.
Candidates conflate the OPR with the BOD because both describe the facility; the OPR's 'measurable, owner-authored, design-basis-setting' character is easy to lose under exam pressure.
What to do instead
For every OPR question, test the statement against 'is this the owner's need and is it measurable?' If it describes how a system is configured, it belongs in the BOD; if it states a need or criterion the design must satisfy, it belongs in the OPR.
Performing a design review as a code-compliance check or a general peer review, and missing the Cx-specific review objectives: constructability, accessibility for maintenance, testability, clarity of the design intent, and OPR traceability.
Candidates default to their engineering-review habits and overlook that the Cx design review is about whether the design can be commissioned, operated, and maintained as intended.
What to do instead
Use a fixed review checklist (OPR/BOD alignment, basis-of-design clarity, sequences testable, access and clearances, sensor and test-port locations, controls points list, TAB provisions, training and O&M requirements) and answer design-review questions by naming which checklist item is at stake.
Treating the commissioning specification as a generic 'Cx shall be provided' clause and failing to recognize required content: scope, roles and responsibilities, submittal and RFI coordination, pre-functional checklist and FPT requirements, schedule impacts, documentation, training, and the CxA's authority and reporting lines.
Candidates underestimate how much enforcement power lives in the spec; they answer from memory of a short template rather than the full required content.
What to do instead
Memorize the spec's required sections and be able to identify which missing section would cause which downstream failure (e.g., no FPT acceptance criteria means disputes at acceptance; no CxA authority means issues go unresolved).
Assuming the low-bid contractor's standard submittal process satisfies Cx submittal requirements, or that Cx review replaces the design team's submittal review.
The division of review responsibility between contractor, A/E, and CxA is a common exam trap, and candidates pick the answer that sounds most efficient rather than the one that preserves each party's role.
What to do instead
State the rule explicitly: the A/E reviews for design conformance, the CxA reviews for commissionability and OPR/BOD traceability, and the contractor remains responsible for means, methods, and coordination. Choose answers that keep those reviews parallel, not substituted.
Skipping or superficially treating pre-functional checklists and startup documentation and jumping straight to functional performance testing in scenario answers.
FPT is the visible, exciting part of Cx, and candidates want to get to the test; the readiness prerequisites feel like paperwork.
What to do instead
For any FPT scenario, first verify readiness: equipment installed per BOD, startups complete and documented, TAB complete, controls point-to-point checks done, pre-functional checklists signed, and deficiencies corrected. If a prerequisite is missing, the correct answer is usually to resolve it before testing.
Writing or interpreting functional performance tests without pre-defined, measurable acceptance criteria and test conditions (modes, loads, setpoints, tolerances, pass/fail), and accepting 'system operated satisfactorily' as a result.
Candidates describe tests procedurally ('verify the AHU works') rather than as a scripted test with objective criteria, which is exactly what the exam tests.
What to do instead
For every FPT question, require four elements in the answer: documented test procedure, specified test conditions, objective acceptance criteria tied to the OPR/BOD, and recorded results with pass/fail and deficiency tracking.
Treating seasonal testing as optional or as a repeat of FPT, and failing to address deferred testing, off-season conditions, and the schedule/documentation obligations that go with it.
Seasonal testing is a small part of the body of knowledge but a reliable exam topic, and candidates often have no field experience with it.
What to do instead
Remember that seasonal/deferred testing verifies performance under conditions not available during initial FPT (e.g., design heating or cooling load, changeover), must be planned and specified up front, and must be completed and documented before the final report is closed out.
Omitting or under-scoping training, the systems manual, and the final commissioning report in scenario answers, or treating the final report as a narrative summary rather than an issues log with resolution status and outstanding items.
These closeout deliverables are treated as administrative afterthoughts, and candidates underestimate how specifically the exam tests their required content and timing.
What to do instead
Memorize the closeout triad: training (verification of effectiveness, not just delivery), systems manual (as-built, O&M, sequences, setpoints, Cx records), and final report (executive summary, issues log with resolution, deferred/seasonal results, outstanding items, and recommendations). For any closeout question, name the deliverable and its required contents.