BIM Asset Information Handover: Checklist, Workflow and Acceptance Tests

What BIM handover should deliver to the operator

An asset information model is a structured body of information about an asset for its operation. It may include linked models, registers, documents and systems; it is not necessarily a single 3D file. The useful question is whether an operator can identify a maintainable asset, locate it, find its specification and service instructions, and see the evidence that it was installed and commissioned.

The UK BIM Framework's ISO 19650 guidance distinguishes project information management from the information needed to operate an asset. This makes the handover requirement a client-and-operator decision. The construction team should not infer the operator's needs from model geometry alone.

BIM asset handover checklist: fields, owners and acceptance

Agree which systems and components are maintainable and which fields are mandatory. A practical minimum may include a stable asset identifier, location, system, manufacturer, model, serial number, warranty, installation date, commissioning status and links to manuals or certificates. The precise fields depend on the facility-management system and contract.

Define data format, classification, naming, exchange dates, responsible originator and acceptance tests in the project information requirements and BIM Execution Plan. Decide who creates each field: designer, contractor, specialist supplier or commissioning team. If nobody owns a field, it will often be incomplete at handover.

• Identifier and location: assign a unique, persistent asset ID; reconcile it with the physical label, building, floor and room. Define who resolves any mismatch.
• Ownership and deadlines: name the supplier or contractor responsible for each field and the reviewer who accepts it at procurement, installation or commissioning.
• Technical data: agree required manufacturer, model, serial number and operational attributes with the operator. Mark a genuinely inapplicable field explicitly rather than silently leaving it blank.
• Document evidence: link each asset to its current O&M manual, warranty and commissioning record; test that the operator can open each document with their own access permissions.

Capture information progressively during construction

Plan data collection around procurement, delivery, installation, testing and commissioning. Supplier data can be requested with submittals; serial numbers and final locations are confirmed at installation; performance and test records arrive during commissioning. Waiting until practical completion creates a data-reconstruction exercise under severe time pressure.

The construction manager should connect each asset-data milestone to a work package and named owner. A field photograph or scan can help verify a physical identifier, but it does not replace an approved record. When substitutions occur, update the asset register and linked documents so design intent and installed reality do not diverge.

Validate completeness, accuracy and usability

Run automated checks for required fields, duplicate IDs, invalid classifications, broken document links and inconsistent locations. Then sample installed assets physically. Compare the label on the equipment with the register, verify access to the manual and check that the asset appears in the correct system and room.

Illustrative acceptance test: select AHU-L02-001 from the register, locate its physical label in plant room L02-PLANT, open the approved maintenance manual and retrieve the commissioning record. Record pass or fail for each step, the reviewer and any unresolved exception. The identifier is an example, not a record from a completed project. Agree the sampling scope and acceptance threshold with the client; a spreadsheet that looks complete but fails these tasks is not a successful handover.

Select digital handover software and maintain information continuity

Evaluate digital handover software against the receiving facility-management system, not a 3D demonstration alone. Test import and export of agreed fields, persistent asset IDs, validation rules, document permissions, revision history and exception reporting. Trial one complete asset from supplier submittal through installation evidence to operator retrieval before choosing the workflow. A CSV register can support a pilot; it is not a replacement for the contracted exchange format or an automated CAFM integration.

Use the sample register to define asset IDs, data owners, evidence links and acceptance status. Its two example rows are illustrative and must be replaced with verified project records. At final review, report missing mandatory fields, physical-to-digital mismatches, inaccessible documents and unresolved exceptions; record the accepted revision and owner of future updates. Download the sample BIM asset handover register (CSV)

Control dashboard

Performance metrics for project managers