Executive answer
What construction leaders need to know
- Useful digital handover starts with the operator's decisions and asset information requirements, not with whatever data happens to be in the design model.
- Capture and validate asset identifiers, locations, maintainable components, documents and commissioning evidence progressively during construction.
- Acceptance should include a test of whether facilities staff can find, trust and use the information for a real maintenance task.
Management workflow
From requirement to controlled delivery
- 01Agree asset requirements
- 02Map maintainable assets
- 03Capture site evidence
- 04Validate data and links
- 05Test operator use
- 06Accept and transfer
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.
Digital handover software comparison: choose the workflow you need
Start a shortlist by identifying the decision the operator needs to make. A closeout document package, a workflow for collecting asset information and a configured import into a facilities system each solve a different part of the handover. The examples below summarise supplier documentation reviewed on 9 November 2026. Confirm the applicable product, configuration and commercial terms with the supplier, then run the same operator-led pilot for each shortlisted workflow.
Document closeout packages with Autodesk Forma Build
Autodesk describes As-built Export for projects with Forma Build as a way to produce a ZIP package of project information, including supported files, sheets, RFIs and submittals. The documentation specifies which references are supported and how local links work in the exported package.
For a pilot, give the exported package to the intended receiver on a separate test device. Open the required manuals and referenced files using the documented viewer and folder arrangement. Autodesk identifies limitations on local linking, including unsupported asset references, so include the references your operator actually needs in the test. Record any missing or unusable item against the agreed handover requirement.
Autodesk As-built Export documentation
Collect and review asset information with Dalux Handover
Dalux documents asset templates and properties, required information at handover and review-manager roles. Its setup guide also describes exporting handover data to a COBie Excel file and a separately arranged connection to Dalux FM. Identify the required collection, review and receiving-system workflow before selecting a configuration.
Trial one asset with a required property left blank. Check the configured status transition, the reviewer’s access to the submission and the correction route. Then verify the exported fields and document references with the receiving team. Treat the documented export option and the operator’s successful use of the delivered information as separate checks.
Dalux Handover templates, properties and export documentation
Configure receiving-system field mapping with Planon BIM Exchange
Planon’s BIM Exchange guide describes mapping XML nodes to business-object fields. It sets conditions for asset locations and units, and explains default-value behaviour for Boolean fields. These details belong in the receiving system’s mapping review, alongside the agreed source format and asset identifiers.
Ask the receiving-system administrator to trace one test asset through the configured mapping. Check its location, units and maintenance-related Boolean values. Where the source omits a value, record the configured default and ask the operator to confirm the intended outcome before acceptance. Retain the tested mapping revision and evidence of the resulting asset record.
Planon BIM Exchange field-mapping documentation
Worked pilot: follow one air-handling unit through the exchange
Hypothetical exercise: use an air-handling unit with an agreed test identifier, location and current maintenance manual. Record the source value and receiving field for each required property. Deliberately omit one required value and correct it through the agreed review process. The receiver then retrieves the corrected asset record and its manual using the intended access arrangement.
If a package opens but the receiver cannot find the manual or reconcile the asset identifier, record the failed requirement, correction owner and retest evidence. An agreed default also needs a documented decision. Use the six software-trial checks and downloadable review checklist below to record the result for each candidate. The asset information checklist helps establish the fields and ownership before the trial.
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.
Digital handover software: a practical trial before procurement
Compare shortlisted systems with the same small pilot and the same operator account. Agree the asset information requirements, exchange format and receiving computer-aided facilities management (CAFM) system first. Use a maintainable asset with linked evidence; a polished model viewer alone does not establish a usable handover.
- Asset identity and field mapping. Import the agreed asset ID, location, serial number and units into the receiving system. Pass evidence: The operator can find the same asset without a duplicate ID or a silently changed value.
- Missing and invalid information. Omit one mandatory field, then submit an intentionally invalid value using a test record. Pass evidence: Both exceptions are visible to the reviewer; they cannot silently become accepted information.
- Operator access to evidence. Use an operator account to retrieve the maintenance manual, warranty and commissioning evidence. Pass evidence: The intended user opens the agreed current documents without relying on a supplier account.
- Revision and exception control. Correct a rejected test value and submit it again through the agreed approval workflow. Pass evidence: The reviewer can trace the old value, correction, responsible person and acceptance decision.
- Transfer to the receiving system. Export the pilot data and import it into the nominated facilities system or its agreed test environment. Pass evidence: Asset counts, agreed field values and document references reconcile; any mapping loss is recorded.
- Exit and continued ownership. Export the accepted pilot package and test retrieval outside the supplying application. Pass evidence: The agreed data and evidence remain usable; the owner, format and process for future updates are documented.
Record Pass, Fail or Not tested for every check, with a reviewer and an evidence reference. Agree which checks are decision gates before the trial. A failed or untested gate needs a recorded resolution and retest before acceptance; a high overall score must not hide it. Record any additional licensing, migration, support and training costs separately using confirmed supplier quotations.
Download the digital handover software trial checklist (CSV)
Use one copy per candidate system. The file contains test instructions and blank results, not vendor ratings or evidence from a delivered project. Keep the existing asset register for asset-level records and use this checklist for the software trial decision.
The UK BIM Framework guidance assigns final information review and acceptance to the asset owner/operator and connects the accepted information with the receiving enterprise systems. See Guidance Part 3, Edition 2 (February 2021), section 3.3.3. The tests above are an original practical aid, not a reproduction of the standard or a certificate of compliance.
For earlier delivery stages, connect the handover requirements to the BIM construction workflow and work-package release register so that missing information is addressed while the responsible team is still engaged.
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
Mandatory-field completeness
Accepted in-scope assets with every mandatory field populated and validated, divided by all in-scope assets. Completeness alone does not establish accuracy.
Physical-to-digital match
Sampled assets whose label, location and record agree on site.
Document-link integrity
Required manuals, certificates and warranties that open correctly.
Operator task success
Whether facilities staff can complete agreed information-finding tasks.
Frequently asked questions
Is a BIM model alone enough for facility-management handover?
Usually not. The operator also needs validated asset attributes, identifiers, locations, documents, commissioning evidence and a way to maintain that information.
When should asset information be collected?
Requirements should be set early. Data should then be captured at procurement, installation and commissioning milestones, with validation before close-out.
What is the difference between a project information model and an asset information model?
The project information model supports delivery decisions; the asset information model supports operation. Information is selected, validated and transferred according to the operator's requirements.
Primary technical sources
- UK BIM Framework — ISO 19650 guidance: information management concepts
- NIBS — BIM Use Definitions: Manage Assets
Project-specific contracts, appointments, regulatory requirements and approved standards always govern actual delivery.