What should a digital building handover include?

A handover proves its worth on the first morning something breaks after opening. Can the operations team diagnose a fault, restore a service and get support without calling a contractor who has already left site? A digital building handover should give the operator the information, access and competence to do exactly that for the systems that were installed, and that takes more than a set of files. Asset records, in COBie or another format, are one element; where the building depends on connected technology, configuration backups, network and integration documentation, commissioning evidence, support arrangements and tested access matter just as much.

Work back from what the operator will have to do

A generic document list misses things. It is more reliable to start from the operator's tasks and work back to what each one requires:

What connected systems add

Controls, security, networks and other connected systems bring their own requirements. The handover for them should include:

• current network documentation: addressing, VLANs, firewall rules, remote-access arrangements;
• integration documentation: what each interface exchanges, over which protocol, and who owns it;
• approved control sequences, as actually commissioned;
• configuration backups for controllers, gateways, servers and network devices, with instructions for restoring them;
• software and firmware versions, licences and support terms.

NIST's guide to operational technology security, SP 800-82, recommends backing up OT systems' state, data, configuration files and programs at regular intervals, establishing processes to restore them, and periodically testing backup and restore. The handover is where that regime either starts or fails to.

Credentials need particular care. They should be transferred through a controlled, secure process, never in general handover files or a shared spreadsheet, and the operator should then replace any credentials the installers used and remove accounts that are no longer needed.

Prove it works before accepting it

Handover material is only useful if it works when needed, so acceptance should rest on demonstration. The operator retrieves documents from the agreed location and opens them, uses administrator functions with its own accounts, and carries out a representative restoration under controlled conditions, such as reloading a controller from its backup. Support contacts are confirmed. Outstanding defects and temporary arrangements are recorded, each with an owner and a closure date, so that a polished digital portal cannot hide unresolved commissioning or access problems.

Four stages of a handover

Handover information assembled in the final weeks is often incomplete and untested. It works better spread across the project. Before commissioning, the parties agree the handover structure, location, naming, file formats and the process for transferring credentials. During commissioning, documents and configuration backups are collected as each system is commissioned, while the engineers who know it are still on site, and operations staff are invited to witness key tests. Before acceptance come the demonstrations described above. After opening, during an agreed aftercare period, backups and records are refreshed after seasonal adjustments and the defects log is closed.

Training belongs in the same sequence. It should be given on the installed systems themselves, and it should record who attended and what they can now do unaided. Recording the sessions, where practical, helps staff who join later.

Put it in the contract, and keep it current

The handover content for each system, the demonstrations, the credential process and the formats should appear in the tender documents, so that contractors price them; requirements that surface only at the end are hard to enforce. How acceptance of the handover information relates to completion or another defined milestone is a question to settle with your contract advisers.

Someone also has to maintain each element afterwards: updating the asset register, refreshing backups after changes, keeping network documentation current. ISO 19650-3 addresses information management during the operational phase of assets, and even without formal adoption its principle holds: handover starts the operational record; it does not finish the job.