User guide · Handover readiness · 8 min guide

Digital twin handover checklist for asset, route, and evidence records.

A handover digital twin is strongest when the evidence, asset tags, access routes, ownership notes, and update responsibilities are agreed before teams leave site. This checklist helps project and FM teams scope what the handover record should contain.

65%digital twin adoption context

Handover twins are more useful when evidence, tag ownership, and repeatable update rules are decided before the project closes.

15%maintenance downtime benchmark

Maintenance value depends on whether the handover record explains assets, access, and known constraints clearly enough for future work.

01

Define the handover questions the twin must answer

The scan should not become a passive archive. Decide which questions future teams will ask, such as where an asset is, how it is reached, what changed during works, which evidence supports the claim, and who owns the next action.

List the handover use cases before capture.
Prioritise spaces with hidden services, access constraints, or future maintenance needs.
Agree whether the twin supports FM, client review, defects, training, or contractor mobilisation.
02

Attach evidence where the issue appears

Drawings, photos, certificates, O&M extracts, and notes are more useful when connected to the relevant room, route, asset, or zone. This prevents future users from matching disconnected files to an unfamiliar site.

Pin evidence to the asset, space, or route it explains.
Use consistent file labels and short summaries.
Separate confirmed handover evidence from items that still need review.
03

Assign ownership and update rules

A digital twin becomes outdated if no one owns updates. Handover should define who maintains tag notes, who can request changes, and which events trigger a refresh, such as refurbishment, replacement, inspection, or route change.

Nominate the owner for tag and route updates.
Record known assumptions and unresolved items.
Set review triggers for works, asset changes, or safety updates.

Reference table

Checklist AreaHandover RiskWhat To Capture
Asset identityFuture teams cannot match records to the real site.Tag code, title, location, surrounding view, and access note.
Route contextMaintenance or inspection teams arrive without the right access plan.Entrances, stairs, lifts, keys, restricted areas, permits, and known blockers.
Evidence ownershipDocuments become detached from the place they explain.Pinned files, evidence status, owner, date, and update trigger.
Guide FAQs

Questions teams usually ask when applying the guidance.

When should handover tagging be planned?

Plan it before capture where possible. Early planning helps decide which assets, zones, evidence items, routes, and ownership notes the receiving team will need after project completion.

Can unresolved items be shown in the twin?

Yes, provided they are clearly labelled as open, draft, review required, or owner pending. This helps prevent uncertain information being mistaken for completed handover evidence.

Who maintains the handover twin after completion?

That should be agreed during handover. A named owner or review process is important because access routes, asset status, and documentation can change after project teams leave.

Plan this on your site

Turn the guidance into a site-specific scan plan.

If this guide matches a current site challenge, Astagio can help map the assets, routes, safety notes, and briefing layers needed for your building or worksite.