Make each evidence reference traceable

Associate evidence with a defined boundary, source, date, and responsible role.

For the North Quay House example, an evidence reference is useful when a reader can tell which part of the Level 3 air-handling unit it concerns, where the source came from, when it applies, and which role can clarify it. Follow approved local requirements for regulated or safety-critical evidence; this example does not set acceptance criteria.

A coordination sequence

Use the organization's approved project process for required evidence and technical decisions.

  1. 1

    Confirm the boundary

    Check the agreed system scope and identify the equipment or interface each reference concerns.

  2. 2

    Identify the applicable approved reference

    Ask the accountable domain owner which current local requirement or procedure applies.

  3. 3

    Gather the associated evidence

    Record the source and date alongside the relevant boundary element; do not infer completion from this example.

  4. 4

    Check traceability

    Confirm that a reader can connect the reference to the boundary and the responsible role.

  5. 5

    Route a gap or question

    Describe what is missing or unclear and hand it to the accountable role through the established project channel.

Completed reference example — illustrative, not an actual record

Sample entries show how references can be described; they do not claim work is complete or approved.

Evidence topic Boundary link Illustrative source reference Responsible role
Equipment identification Level 3 air-handling unit Asset schedule entry AHU-L3-01 Commissioning coordinator
Controls interface Unit controls interface Controls interface drawing reference C-14 Controls specialist
Test record Unit boundary and named controls interface Test record reference TR-07; date and outcome are recorded in the authorized project record Installing contractor lead with commissioning coordinator

Handoff for evidence questions

An evidence reference is not a submission or approval.

Describe the boundary element and the source reference in question.

Ask the accountable domain owner which approved local requirement applies.

Use the project's established channel for the clarification or record update.

No approval or task status is represented by this authored example.