Commissioning Specifications, Contracts, and Procurement
Commissioning specifications translate the Commissioning Plan into enforceable contract requirements. They define the contractor's obligations: submittal review participation, controls point-to-point verification, startup documentation, functional performance testing support, training, and as-built and systems manual deliverables. The candidate must know where Cx requirements belong - typically Division 01 (General Requirements) plus system-specific sections - and that they must be consistent across all divisions and trade contracts.
Procurement considerations: the CxA may be engaged directly by the owner or as a subconsultant; independence matters. Contracts should clearly allocate responsibility for scheduling tests, providing temporary utilities, correcting deficiencies, and bearing retest costs. A frequent trap is vague language that lets a contractor claim testing is "not in my scope" or that retests caused by contractor-caused deficiencies are owner-funded.
Watch for: (1) conflicting requirements between general conditions and technical sections; (2) missing language on who pays for retesting; (3) no requirement for contractor participation in the Cx kickoff; (4) absence of a pre-functional checklist requirement. Also confirm warranty and training requirements are stated, and that acceptance is tied to successful functional performance testing.
Rule of thumb: every Cx responsibility named in the plan should appear as an enforceable obligation in a contract document. Worked example: if the plan requires trend data logging during functional tests, the specification must require the controls contractor to provide trending capability and export data, or the test cannot be executed.