BCxA ACP common mistakes
BCxA ACP · Understand the traps and how to avoid them.
Treating commissioning as a standalone inspection activity that begins after construction, and answering questions about when the Cx provider should first be engaged with 'at the start of construction' or 'at substantial completion' rather than during pre-design/design.
Many candidates come from field-testing or contracting backgrounds where commissioning is experienced as a construction-phase activity, so they anchor on their own experience instead of the process model the exam tests, in which the owner's project requirements and the Cx plan are developed before design is complete.
What to do instead
Memorize the phase sequence (pre-design, design, construction, acceptance, occupancy/warranty) and for each phase be able to state the Cx provider's deliverable and the owner's decision point. Practice mapping every activity to its earliest legitimate phase, and default to 'earlier' when an activity could occur in more than one phase.
Confusing the owner's project requirements (OPR) with the basis of design (BOD), for example saying the commissioning authority writes the BOD or that the OPR is a contractor submittal.
Both documents describe what the building should do, so candidates skim the definitions and rely on the words 'requirements' and 'design' rather than on who authors each document and what it is used for.
What to do instead
Build a two-column comparison: OPR is owner-authored (with Cx facilitation), states measurable programmatic and performance needs, and is the benchmark for all later verification; BOD is design-team-authored, records assumptions, calculations, and system selections, and must be checked for traceability back to the OPR. Answer authorship questions from that table, not from memory.
Writing or evaluating commissioning specifications that assign the Cx provider responsibilities that compromise independence, such as approving contractor submittals, directing means and methods, or serving as the installing contractor's quality-control function.
Candidates conflate the Cx provider's verification role with the design team's or contractor's execution role, and they pick the answer that sounds most helpful or most efficient rather than the one that preserves the Cx provider's objectivity and avoids conflicts of interest.
What to do instead
Learn the independence principle explicitly: the Cx provider verifies and documents, does not design, install, or approve. When a question offers an option where the Cx provider 'ensures compliance' by directing work, reject it in favor of options where the provider observes, tests, documents, and reports to the owner.
Skipping or compressing pre-functional checklists and start-up documentation and moving straight to functional performance testing, or accepting contractor-completed checklists without verification.
Functional testing is the most visible and interesting part of commissioning, so candidates underweight the readiness steps and answer as if FPT can compensate for unverified installation.
What to do instead
Treat pre-functional checks as the gate to FPT. In scenario questions, look for the answer that requires completed and reviewed checklists, documented start-up, and corrected deficiencies before FPT begins, and be able to explain that FPT results are unreliable if installation has not been verified.
Designing or interpreting functional performance tests that verify individual component operation rather than integrated system performance under seasonal or part-load conditions, or that omit pre-defined acceptance criteria and test procedures.
Candidates default to the equipment-focused tests they have seen on site and forget that FPT is meant to demonstrate the interacting systems meet the OPR across modes of operation, including off-design conditions.
What to do instead
For any FPT question, check three things: were acceptance criteria written before testing, does the test exercise systems in an integrated way across modes (occupied/unoccupied, economizer, part load, emergency), and are seasonal or deferred tests scheduled. Choose answers that include these elements and reject tests that only confirm a device turns on.
Treating the issues log as a passive record rather than a managed tracking tool, for example failing to assign responsibility and resolution dates, or closing items without documented verification of correction.
Candidates see documentation as paperwork rather than as the control mechanism for the process, so they choose answers that describe recording issues instead of driving them to verified closure.
What to do instead
Remember that every issue entry needs an owner, a responsible party, a target date, a status, and evidence of resolution. In questions about deficiencies, prefer the option that requires retesting or re-verification before closure and that escalates unresolved items to the owner.
Underestimating the O&M and training deliverable, for example accepting generic manufacturer manuals as the O&M manual or treating a single walkthrough as adequate operator training.
These activities occur late, when budgets and attention are stretched, and candidates often answer from a compliance mindset ('manuals were provided') rather than from an operational-readiness mindset.
What to do instead
Know the components of a project-specific O&M manual (as-built information, schedules, setpoints, troubleshooting, maintenance tasks) and of effective training (needs assessment, hands-on sessions, recorded sessions, verification of trainee competence). Choose answers that tie training to the installed systems and that include evaluation of whether learning occurred.
Mishandling the Cx provider's reporting relationship and authority, such as routing deficiency reports only to the contractor or assuming the Cx provider can stop work.
Candidates import authority assumptions from construction management or inspection roles and are unsure where the Cx provider sits in the contractual hierarchy.
What to do instead
Fix the principle that the Cx provider reports to the owner (or owner's representative) and has no contractual authority over the contractor. Answers should show issues communicated through the owner and the design team, with the contractor responsible for correction and the Cx provider responsible for verification and documentation.
Ignoring the human and communication side of scenarios, for example failing to identify the need for a commissioning kickoff meeting, a roles-and-responsibilities matrix, or early involvement of facility staff in design reviews.
Candidates focus on technical procedures and treat coordination meetings and role clarity as administrative overhead, so they miss questions that test whether the process was set up for collaboration.
What to do instead
For any scenario, ask who needs to know, when they need to know it, and how the decision is recorded. Prefer answers that establish roles and responsibilities early, include O&M staff in design and acceptance, and document decisions and communications in the Cx plan or meeting records.
Answering ethics and professional-conduct items with the commercially convenient option, such as agreeing to alter test results, test only a sample while implying full coverage, or accept a Cx role on a project where the firm also installed the work without disclosing the conflict.
Exam items in this area are written to tempt efficiency- or client-pleasing answers, and candidates do not consistently apply disclosure, independence, and truthfulness as decision rules.
What to do instead
Apply three checks in order: is the action truthful and fully documented, is any conflict disclosed and managed, and does it preserve independent verification. Any option involving undisclosed conflicts, selective reporting, or pressure to change results should be eliminated before evaluating technical merit.