Coordinate the test record and the people around it

This page supports coordination; it is not a technical or safety-critical test procedure.

For the fictional Level 3 air-handling unit, coordinate who owns the scope, which approved local procedure and prerequisites apply, where the authorized record will be kept, and how observations will be routed. Only appropriately authorized roles should determine or perform technical work under the applicable local process.

Illustrative coordination sequence

  1. Define the test scope

    Identify the system boundary and the specific interface covered by the authorized test reference.

  2. Align relevant roles

    Confirm which commissioning, contractor, controls, and owner-operations roles need to coordinate.

  3. Check prerequisites against approved procedures

    The accountable trained role confirms applicable prerequisites through the current approved local procedure.

  4. Capture the authorized record

    The responsible role records the work using the organization's established project record process.

  5. Route observations and questions

    Describe affected boundary, source, and responsible role; use the approved process for technical or safety-critical observations.

Worked coordination example

A record reference can clarify scope without implying a passing result.

Traceable reference

Connect the interface record to the unit boundary

In this fictional example, a controls-interface record is associated with the Level 3 air-handling-unit boundary and reference C-14.

  • The record reference identifies the interface in scope.
  • The accountable roles are named for coordination.
  • No test outcome is asserted on this page.
Open question

Route a neighboring-interface question

If the record raises a question about a neighboring interface outside the agreed boundary, record the question for its accountable domain owner instead of treating it as a pass.

  • Name the neighboring interface and affected scope.
  • Identify the source reference and the clarification needed.
  • Use the project's established follow-up channel.

Role-based coordination handoffs

Commissioning coordinator
Maintains the coordination view of boundaries, evidence references, and follow-up roles
Installing contractor lead
Coordinates contractor-side records and routes questions through the established project channel
Controls specialist
Clarifies controls-interface references through the approved project process
Owner-operations representative
Explains receiving-team context and identifies operational handover questions