Make the handover a usable building record.

Name the recipients before work begins

Identify the owner or manager receiving the record, the project contact checking completeness and the qualified providers supplying documents. Include the incoming service team where its role is known. Ask what delivery format will be usable in the building record system.

A handover sent only to a departing construction contact can leave the operating team without the information. Put recipients and document responsibilities in the accepted scope.

Agree a document schedule

The qualified team establishes what applies. This administrative schedule is not a universal legal checklist or a replacement for required project documents.

Reconcile the final revision

Compare the final package with approved changes and the accepted work boundary. Ask the responsible team to explain missing areas or discrepancies. A tender drawing left in the folder should not silently become the installed record.

• Document title and revision.
• Areas and equipment represented.
• Source and issuing party.
• Status and stated limitations.
• Related change or completion reference.

Keep connected-system evidence visible

Vancouver’s integrated-testing bulletin explains that separate systems and their interconnections need a coordinated verification basis where its requirements apply. Use that local example to ask the actual project team who supplies the interface records and how applicability is established.

File sprinkler, alarm and other connected documents with links between them. Several separate reports do not automatically explain how a changed interface was addressed.

List exceptions rather than hiding them

Use one open-item list for missing documents, unfinished work and unresolved decisions. Give each an exact description, responsible party and next step. Ask the qualified team what an omission means for project use or acceptance.

Do not mark the package complete because the last invoice was paid. A commercial payment record and the evidence of technical completion have different purposes.

Work through a handover with two missing records

Consider a fictional renovation where the installation provider delivers its work records and equipment information, but the final drawing package and a connected-system document remain outstanding. The useful status is a package with two named exceptions. It is not “complete except for paperwork” without an explanation of what the documents establish. Ask the responsible team about the significance of each gap and the appropriate next action. Keep the original scope and its document schedule available so the request can be precise.

Create one row for the final drawings, identifying the issuing party, project areas, expected revision and the unresolved question. Create another for the connected record, identifying the responsible provider and the interface it represents. A shared inbox can hold both requests, but the responsibilities may be different. Ask the coordinator to reconcile the deliverables and retain the responses. The owner should not prepare an unofficial final layout to stand in for a missing professional record, nor assume that an unrelated report closes the interface.

When a document arrives, preserve it intact and update the index. Check its administrative identity: project, issuer, date, revision and stated coverage. Ask the appropriate professional about discrepancies or limits. If the new drawing excludes an area that changed during construction, keep that question open. This gives the operating team a truthful package rather than a folder whose title says “final” while its contents still describe different versions of the project.

Copyable exception request: “Our handover index for [project/scope] lacks [exact drawing or connected-system record]. The agreed document schedule is [reference], and available information is [issuer/revision]. Please identify the responsible issuer, represented areas and current status, then provide the applicable document or explain the remaining task. Clarify what this gap means for the project’s actual completion or acceptance basis.” Keep each exception as its own reference. An answer about one missing drawing should not close an unrelated interface record. Retain the source response and give the eventual document to the operating recipient.

Use a handover review that future staff can repeat

Start the review from the accepted document schedule and authorized changes. Invite the roles needed to explain incomplete or inconsistent items. The meeting’s purpose is to reconcile the package and assign the remaining work, not to conduct technical acceptance testing through a conversation. Use document names and references that a new manager can search for. An index organized by issuer alone may be difficult to use when several providers have records covering the same area or connected function.

For each package item, record received, awaiting clarification, missing or superseded. Add the corresponding source document and responsible respondent. Do not convert a received document into a general statement that the whole system is ready; ask what its scope establishes. Where the provider identifies a technical issue, keep its actual explanation and response separate from the administrative completeness status. This distinction helps the property contact communicate correctly with the owner and retain the original professional conclusions.

End with a clear operating handoff. Confirm the document location, person maintaining the index, service contacts and open-item recipient. Where an authorized procedure or training record applies, identify the responsible source and record without reproducing it as an owner-written operating checklist. Ask the incoming team to acknowledge the unresolved items it receives. That closes the administrative loop and prevents a missing record from vanishing when construction staff leave, while keeping the qualified assessment and actual acceptance decisions with the appropriate roles.

Make the operating handoff explicit

Confirm who can find the documents and which qualified roles handle ongoing work. Record contact changes and the location of authorized building arrangements without publishing access codes or security-sensitive details.

Use the handover checklist to organize the package and the record tracker for exceptions. Keep original provider documents intact.

References and scope

1. Integrated testing of fire and life safety systems — City of Vancouver. December 7, 2022 bulletin, listed in the current municipal directory. Local integrated-testing and coordination context; establish applicability and current requirements with the actual jurisdiction. Link reviewed 2026-10-02.
2. Sprinkler fitter — trade description — Red Seal Program. Trade scope; does not establish a specific company’s qualifications or provincial licensing. Link reviewed 2026-09-30.

Review dates identify source-link checks, not professional certification or a building-specific determination. Confirm current jurisdiction and exact-model requirements for actual work.