Set the Handover Information Requirements Early

Begin with the receiving team

Handover information should be defined by the tasks the owner or operations team needs to carry out. A detailed building information modelling (BIM) model and a folder of manuals may still leave staff unable to locate equipment or find its maintenance instructions. Define those tasks before collecting the data.

Agree the required assets, fields and receiving system before data production. Labels such as 6D or 7D do not provide a complete delivery specification because project interpretations differ. State the actual information and acceptance tests rather than relying on the label.

Identify the assets and their records

Define which maintainable items are in scope and how they are identified. Agree the relationship between an equipment tag, model element, location, system and document record. Keep equipment type information distinct from information specific to an installed instance where the receiving structure requires it.

Construction to Operations Building information exchange (COBie) provides a standard organisation of data about maintainable facility assets [1]. It connects equipment information with the records needed by the operations team. If COBie is required, specify the version, fields and validation rules. It is not required on every project, and naming a spreadsheet COBie does not demonstrate conformity.

Assign the source of each field

The model author is not necessarily the source of manufacturer, serial number, warranty or commissioning information. Identify who supplies each required field, when it becomes available and how it is verified. Carry information forward only when its source and status are known.

Do not fill unknown fields with plausible values to improve a completeness score. Follow the specified format's rules for missing and not applicable data, together with the agreed delivery requirements. Track pending values with a provider and due date. Missing required data remains outstanding unless a permitted exception is explicitly authorised; a placeholder does not satisfy the requirement.

Test the receiving system early

Prepare a small representative data package with the operations team. Confirm identifiers, allowed values, units, document links and the mapping into the receiving system. An export passing the author's checks may still fail to import or produce records the recipient cannot use.

An illustrative fan record should let the recipient distinguish the installed asset from its equipment type and find the relevant location and supporting documentation. The example is a test of the agreed relationship, not a universal list of mandatory fields. Ask the operations team to carry out the intended task using the trial delivery.

Update data as equipment decisions change

Review the asset records at meaningful milestones. Equipment substitutions, changed tags and commissioning updates should reach the correct records, not only the model geometry. Preserve the history needed to understand the current information, while keeping superseded manuals from appearing as current instructions.

At final delivery, reconcile the records with the agreed asset scope and required site, supplier and commissioning evidence. Design geometry alone does not prove installation. A model updated from verified site scans or measurements, or a digital twin linked to verified site evidence, can represent installed conditions within the recorded coverage and date. Installation evidence does not automatically establish commissioning performance or acceptance. Resolve required-data gaps or record permitted exceptions with the owner's authorised recipient. Test document links and continued access from the recipient's account, not only the author's.

A handover readiness checklist

• The operations team has agreed the asset scope and required fields.
• Identifiers and relationships between assets, locations and systems are consistent.
• Data providers and verification responsibilities are assigned.
• Missing and not applicable values follow the specified format and agreed requirements; required gaps have named owners.
• A representative delivery has been tested in the receiving workflow.
• Changes, supporting documents and final exceptions are reconciled.

SmartBuild Tech's digital asset information support can help structure this process. Acceptance remains tied to the owner's requirements and verified delivery, rather than the apparent detail of the model.