Build and maintain CxP Team cohesion and cooperation

Jeremy Curtis

Published: Aug 18, 20269 min read

Purpose of the step

Step 4 exists to establish us as active team leaders, build the structured working guidelines that prevent dysfunction from accumulating across the team, and maintaining those guidelines throughout Pre-Design and beyond. This implements ASHRAE Guideline 0-2019, Section 5.2.1.6(g), which assigns the CxP formal responsibility for actively managing team working relationships.

An important clarification sits underneath that mandate: our role is that of a diplomat and objective advocate, not an inspector general. The Commissioning Stakeholders Guide, Chapter 1, Section 1.1.5, is explicit that we do not have the authority to overrule the designer, and that we operate through consensus-building rather than enforcement.

That posture is not a constraint on our effectiveness; it is the foundation of it. A CxP who operates aggressively or positions themselves as an adversary of the design team will produce a commissioning process the team tolerates rather than one they participate in. The governance structures this step establishes exist to make consensus the default, and formal escalation the exception. Are we set up to build that kind of team governance before the first meeting runs?

In practical terms, this step ensures that:

✅ Escalation is automatic: The escalation path from open issue to Owner decision is defined, documented, and triggers automatically rather than informally .

✅ Authority is on the record: Every CxP Team member's authority level is on the record, so no one is making decisions they do not have the power to make .

✅ Reporting is reliable: Progress reporting runs on a defined cadence, tied to the CxP Team meeting cycle, so the Owner is never in the dark on commissioning status .

✅ Dysfunction is addressed: Persistent problems, whether non-attendance, authority gaps, or proxy attendance without decision-making power, are handled formally rather than accommodated silently .

✅ Independence is protected: The CxP's independence from design and construction entities is preserved structurally, including in the escalation path itself, so that independence is never eroded by the way the team happens to work day-to-day .

Inputs and Outputs

Required Inputs

Expected Outputs

Signed CxP appointment with defined scope, deliverables, and independence statement [Stage 1, Step 1]

Structured communication and escalation guideline document, formally accepted by the Owner's Representative

Named commissioning team, accepted Cx Organization Chart, and written authority confirmation from each team member's organisation [Stage 1, Step 2]

Confirmed escalation path from working-level open issue to Owner decision, with a defined timeframe and a direct CxP-to-Owner route to preserve independence

Documented meeting structure, agreed agenda rules, distribution lists, and minute guidelines established at [Stage 1, Step 3]

Documented meeting cadence and reporting schedule, confirming the baseline of one Commissioning Progress Report per four CxP Team meetings.

Requirement from [Stage 1, Step 3] to issue formal meeting records and use reporting as a live governance tool rather than an informal update mechanism

Verified authority confirmation records for each CxP Team member, or documented gaps with an escalation record to the Owner.

Initial meeting-and-reporting controls that reveal, through attendance and participation, where decision-making authority is weak or missing

Documented process for handling persistent non-attendance and unauthorised proxies via formal Owner escalation, rather than informal workarounds

Step Checklist

The CxP has briefed the Owner and PM on their leadership role and independence, and that position is clearly visible in how meetings are run.
Authority levels for every CxP Team member verified against the Cx Organization Chart and on record before the first CxP Team meeting.
A written communication and escalation guideline document has been produced, covering email expectations, agenda circulation times, and minute turnaround, and has been accepted in writing by the Owner's Representative.
A documented escalation path exists from open issue to Owner decision, with a defined timeframe for each stage. It explicitly includes a direct CxP-to-Owner route that does not require routing through the PM (where the PM is acting as Owner's Representative), preserving CxP independence.
Persistent non-attendance and proxy-without-authority issues have been addressed by the CxP with formal written escalation to the Owner, rather than managed through informal workarounds.
The reporting cadence is agreed and documented; one Commissioning Progress Report per four CxP Team meetings as the standard baseline [Guideline 0-2019, Section 5.2.7.2].
The stage closeout report requirement is confirmed; a report documenting Cx status must be issued at every stage gate.
The team can challenge and disagree in meetings without the discussion becoming personal or defensive, and disagreements are resolved against the OPR, scope, or Cx Plan rather than personality or rank alone.
FM/O&M personnel and other non-dominant voices report that their concerns are being heard early enough to influence the work, rather than being noted after decisions are already fixed.
The communication and escalation guidelines are cross-referenced and confirmed as consistent with the meeting and reporting structure established at [Stage 1, Step 3], and the Cx Plan is updated to reflect these guidelines for acceptance at [Stage 1, Step 11].

How to

This section covers the sequence for establishing the communication structures, verifying authority, and building team cohesion across five sub-steps. Work through them in order to ensure the team governance is functioning correctly before any substantive Pre-Design commissioning activity begins.

Quick reference:

✅ 4a: Confirm authority before the first meeting convenes

✅ 4b: Establish and document the escalation path

✅ 4c: Set the reporting cadence and stage closeout requirement

✅ 4d: Manage non-attendance and proxy-without-authority formally

✅ 4e: Produce and obtain acceptance of the communication and escalation guideline document

The most common cause of team dysfunction is people making decisions they cannot officially make, or avoiding decisions because they believe authority sits elsewhere. This can stall decisions that need to be made and issue resolution.

Securing written confirmation of each member's decision-making responsibilities before the first meeting helps everyone operate from an agreed baseline and establishes genuine project buy-in.

Retrieve the written authority confirmations obtained at [Stage 1, Step 2] and cross-reference them against the accepted Cx Organization Chart, flagging any discrepancies to verify binding authority before the first meeting convenes.
Cross-reference these confirmations against the accepted [Stage 1, Step 2] Cx Organisation Chart and flag any discrepancies.
Confirm and document whether the Project Manager holds delegated Owner authority for commissioning decisions.
If a member cannot provide written authority before the first meeting, document the gap and escalate it to the Owner in writing immediately rather than waiting for it to resolve itself.
Raise any unresolved authority gaps as a formal agenda item at the first CxP Team meeting, recording the Owner's agreed resolution path and timeline.

Assuming nomination equals authority. This leads to proxy attendees sitting in meetings for weeks without actual decision-making power, while unbinding decisions are being permanently logged in the project record.

Common Issues

IssuesWhat it looks like in practiceWhy it causes trouble

Authority treated as implied by nominationCxP Team members attend meetings and make commitments, but no written authority confirmation has been obtained. When a commitment is challenged, the organisation denies its representative had authority to make it.Decisions made without confirmed authority are contestable. At the first substantive dispute, claimed agreements unravel, and the commissioning process falls back to informal negotiation rather than documented governance.

CxP operating as inspector general rather than objective advocateThe CxP approaches design team reviews and team meetings as an auditor looking for compliance failures rather than a diplomatic facilitator building consensus around OPR delivery. Review comments are framed as findings against the design team rather than shared issues for the team to resolve.The design team becomes defensive and disengaged. Commissioning governance is tolerated rather than supported. The CxP's ability to build the required cooperative working environment is undermined from the first interaction.

Escalation path routes through parties with a conflict of interestThe PM acts as both Owner's Representative and the primary contact for the design team. The escalation path runs through the PM, so the CxP cannot raise concerns about the design team's commissioning compliance without the PM's involvement.The CxP's independence is structurally undermined. Issues about design team performance either go un raised or produce an adversarial dynamic the PM is not experienced to manage.

Reporting cadence treated as discretionaryProgress reports are issued when the CxP has significant news or time, rather than on the required standard cadence. Reports cluster around problems and go quiet during periods that appear stable.The Owner loses visibility of slowly accumulating problems. By the time a report is issued, the issues it documents have already moved to the next stage and are significantly more expensive to resolve.

Issues Log used as a blame record rather than a collaborative toolThe CxP frames Issues Log entries as findings attributed to the design team, with language that positions the log as evidence for future financial or contractual disputes rather than a shared record of issues being worked toward resolution.The design team stops engaging with the log openly and starts managing their exposure to it instead. Issues go undisclosed or are resolved off the record to avoid appearing in what is now perceived as an adversarial document. The log loses its function as a commissioning governance tool.

Non-attendance managed informallyConsistent non-attendance by a key CxP Team member is raised verbally by the CxP and managed through individual conversations. Nothing is documented. The attendance pattern continues.The informal approach produces the appearance of management without the substance. The non-attending party knows the issue will be handled conversationally and has no formal consequence. Governance gaps embed and persist.

Guideline document produced retrospectivelyThe communication and escalation guideline is drafted several weeks into Pre-Design, after the team has established working patterns. The document describes what the team has been doing, rather than what was agreed before they started.Drift that has already occurred is recorded as a guideline. The document provides no correction mechanism because it was not in place before the patterns it describes were established. Issues that arose before the document was produced have no formal governance basis.

CxP independence not confirmed in the escalation structureThe escalation path is documented, but the direct CxP-to-Owner route is not explicitly stated. In practice, the CxP routes all communications through the PM.When the CxP needs to escalate a concern about a decision the PM has made, there is no established route to do so. The independence that supports the CxP's ability to close out issues, direct testing, and require remediation is not structurally preserved.

Stage closeout reports conflated with progress reportsThe CxP issues one Commissioning Progress Report at each stage gate and treats it as satisfying both the regular reporting cadence and the stage closeout requirement.The two documents serve different governance functions. A progress report tracks ongoing status; a stage closeout report confirms that stage acceptance conditions have been met. Conflating them produces a document that does neither function properly.

Key Terms

Objective advocate

A person who represents another party’s interests impartially, using evidence and agreed requirements to assess outcomes, identify issues, and recommend action without allowing personal interests or external pressures to influence their judgment.

Escalation path

The documented route by which a decision that exceeds a team member's authority is passed upward to a party who can resolve it, within a defined timeframe.

Direct CxP-to-Owner route

An agreed communication and reporting path that allows the Commissioning Provider (CxP) to present findings, risks, recommendations, and unresolved issues directly to the owner, without filtering through project managers, designers or contractors, supporting independent advice and timely owner decisions.

Binding authority

The power to make decisions, issue instructions, or enter agreements that legally or contractually commit another party. Unlike an advisory role, it allows a person to act on that party’s behalf within the applicable limits of their authority.

Buy-in

Acceptance of, and willingness to actively support, a plan, decision, or approach. It means those involved understand its purpose and are prepared to help put it into practice, rather than simply acknowledge it.

Commissioning Progress Report ( CxPR)

The formal written report issued by the CxP on a scheduled cycle summarising commissioning activities, Issues Log status, actions outstanding, programme alignment, and upcoming milestones; distinct from general project progress reports. A structured summary requiring an executive overview; not a data dump of raw checklists or test records. Issued every four CxP Team meetings as the standard baseline; not to be confused with the Issues Report, which is issued at every meeting.

Communication and escalation guideline document

A document defining how project information is shared, who communicates with whom, and when issues must be escalated. It sets communication channels, responsibilities, escalation triggers, response times, and the authorities responsible for resolving issues or making decisions.

Proxy attendance

Attendance at a meeting by an appointed representative on another person’s behalf. The representative communicates that person’s position and participates within agreed authority limits, which may or may not include making decisions or commitments.

Decision Points

This table highlights the key decisions to establish a working control structure for this step.

DecisionWho decides

Whether the PM holds delegated Owner authority for commissioning decisions, or whether that authority sits directly with the Owner's RepresentativeOwner / Representative

Whether an unresolved authority gap from [Stage 1, Step 2 ]requires immediate escalation to the Owner before the first OPR sessionCommissioning Provider

Whether the direct CxP-to-Owner escalation route is confirmed, and on what terms the CxP may use it without first seeking the PM's agreementOwner / Representative

Whether a CxP Team member's persistent non-attendance or proxy-without-authority requires formal written escalationCommissioning Provider

Whether a formally delegated alternative arrangement for a non-attending party satisfies the project's governance requirementsOwner / Representative

Whether a comment on the draft guidelines document that cannot be resolved within the team requires Owner escalationCommissioning Provider

Formal acceptance of the communication and escalation guidelines document as the binding governance framework for Pre-DesignOwner / Representative

Timing and sequencing

Step 4 begins immediately after the meeting and reporting guidelines are established at [Stage 1, Step 3]. It continues actively throughout Pre-Design and beyond. The structures this step establishes are not pre-OPR preparation, but they are the controls under which all subsequent commissioning activity runs.

Earliest start: Immediately after the Cx Organization Chart is accepted [Stage 1, Step 2] and meeting guidelines are documented [Stage 1, Step 3].
Latest acceptable start: Before the first CxP Team meeting convenes. Authority confirmation, the escalation path, and the reporting cadence must all be in place before the first meeting, not established progressively as meetings proceed.
Dependencies: [Stage 1, Step 2] must have produced named team members with initial authority mapping. [Stage 1, Step 3] must have produced the meeting structure, distribution list, and reporting schedule. Step 4 operationalises both. If [Stage 1, Step 3] is materially incomplete when Step 4 is due to begin (no confirmed meeting structure, no distribution list, or no reporting schedule), do not proceed on the basis that the gap will be resolved in parallel. Document the specific deficiency in writing to the Owner, state which Step 4 actions cannot be completed without it, and defer those actions until Step 3's outputs are confirmed. Attempting to run Step 4 governance on an unconfirmed [Stage 1, Step 3] foundation produces a guidelines document that conflicts with the meeting structure when [Stage 1, Step 3] is eventually closed.
OPR workshop milestone: The communication and escalation guidelines document must be accepted by the Owner's Representative before the OPR workshop [Stage 1, Step 7] is scheduled; the workshop is the first commissioning activity where team governance will be tested under real working conditions.
Issues Log integration: The escalation path must be cross-referenced with the Issues Log procedure when [Stage 1, Step 6] is reached: the path must embed into the log procedure so it triggers automatically when an issue misses its correction date.
Continuing obligations: Stage closeout reports are a continuing obligation: one must be issued at every stage gate through the full commissioning process. The cadence established here runs through to project handover.

Roles and Responsibilities

RResponsible

Confirms PM's authority level in writing. Receives formal escalation of authority gaps and non-attendance. Confirms the direct CxP-to-Owner escalation route. Accepts the communication and escalation guidelines document in writing.

AAccountable

Accountable for authority structure decisions and for the integrity of the CxP's independence in the escalation path. Final approval of the guidelines document.

CConsulted

Consulted on acceptable alternative arrangements for non-attending team members.

IInformed

Informed of all CxP Team meeting records and of any agenda items that could not be resolved due to absent or unauthorised proxies.

Documents Produced

This table summarises the main records this step should generate, who owns them, what they contain, and where they are used later.

Format / contentThe [Stage 1, Step 2] written authority records, formally cross-referenced against the accepted Cx Organization Chart to flag discrepancies and confirm binding authority before the first meeting convenes. Filed alongside the Cx Organization Chart.

Where it is usedReferenced throughout Pre-Design when decision authority is questioned. Used at [Stage 1, Step 8] and [Stage 1, Step 11] to confirm that acceptance decisions were made by parties with genuine authority. Referenced in the Pre-Design Closeout Report [Stage 1, Step 20].

ASHRAE References

DocumentRequirement / practical use in

ASHRAE Guideline 0-2019Section 5.2.1.6(g)

Assigns the CxP formal responsibility for actively managing team working relationships throughout Pre-Design and beyond. The primary governing clause for Step 4.

ASHRAE Guideline 0-2019Section 5.2.6.1

Requires an Issues Report to be generated at least for each CxP Team meeting: this is a separate and more frequent obligation than the Commissioning Progress Report. The Issues Report drives meeting agendas by showing every open issue, its status, its owner, and required next action. Underpins the Issues Report cadence established in this step.

ASHRAE Guideline 0-2019Section 5.2.7.2

Requires the CxP to issue one Commissioning Progress Report per four CxP Team meetings as the standard reporting cadence baseline. Distinct from the Issues Report required at every meeting.

ASHRAE Guideline 0-2019Section 5.2.4

Requires the Cx Plan to include the communication guidelines and escalation process established in this step: the guidelines document produced here feeds directly into the initial Cx Plan at [Stage 1, Step 10].

ASHRAE Guideline 0-2019Section 5.2.5

Governs Issues Log use across all project stages: the escalation path established in this step must be embedded in the Issues Log procedure at [Stage 1, Step 6] so it triggers automatically when an issue misses its target correction date.

ASHRAE Guideline 0-2019Section 5.3

Pre-Design Stage acceptance conditions: Stage 1 cannot close without the governance structures established in this step being operational and confirmed. The stage closeout report requirement applies at every stage gate.

ASHRAE Guideline 0-2019Section 5.2.1.1

Dictates that team members must hold binding decision authority for their organisations. Provides the direct ASHRAE mandate for Step 4 strict rules against proxy-without-authority and the requirement to verify authority records before the first meeting.

ASHRAE Standard 202-2024Section 13

Governs the Issues Log's ongoing tracking, review cadence, escalation procedure, and close-out requirements across all project stages: the escalation path established in this step is the upstream governance structure Standard 202-2024 Section 13 depends on.

ASHRAE Standard 202-2024Sections 5.2.11 and 17.2

Mandates the development, use, and Owner review of Commissioning Progress Reports. Provides the normative backbone for the reporting obligations and the ongoing communication loop established in this step.

ASHRAE Commissioning Stake Holders Guide-2019Chapter 1, Section 1.1.5

Describes the CxP's required characteristics: diplomat, consensus-builder, and objective advocate. Explicitly establishes that the CxP does not have the authority to overrule the designer. Underpins the behavioural posture described in Section 1 of this article and the common error regarding CxP operating as inspector general.

ASHRAE SSPC 300 Informative Annex 07-2022Figure 07-01

Provides an authoritative ASHRAE organisational chart illustrating the direct CxP-to-Owner reporting line. Use this figure as documentary support when a PM asserts that all commissioning communications must route through them: the chart demonstrates that the CxP's direct Owner access is an ASHRAE-documented structure, not a project-specific preference.

ASHRAE SSPC 300 Informative Annex 21-2024Full Annex

Provides supplementary guidance on commissioning team roles and their integration into project contracts, including the CxP's authority to direct testing and close out issues. Supports the role descriptions and authority structures established in this step.

ASHRAE SSPC 300 Informative Annex 19-2022Section 19.2.6.e

Lists minimising adversarial relationships as a qualifications-based selection criterion for the CxP: the selection process itself is expected to identify providers whose working approach supports team cohesion rather than undermining it. Aligns with the diplomat and objective advocate posture required throughout this step.

ASHRAE SSPC 300 Informative Annex 03-2022Section 03.0

Establishes that success depends on each team member's understanding of what is expected of them and obtaining their buy-in: this is the ASHRAE framing for the authority confirmation process in Section 4a of this article. The section also provides supplementary guidance on team structure, communication guidelines, and the governance expectations for the early commissioning process.

ASHRAE SSPC 300 Informative Annex 03-2022Section 03.2.2

Specifically advises that the initial Cx Plan must define the team's "communication protocol," directly supporting the core output of this step.