What Actually Makes a Digital Twin Useful After Handover

A lot of projects deliver a 'digital twin' at handover that's really just a design model with a new label on it. It looks complete, it renders nicely in a walkthrough, and then it sits unopened in the facilities team's archive because it doesn't answer any of the questions they actually have day to day.

The gap is almost always structured data, not geometry. Facilities teams don't need a beautifully modeled ceiling void — they need to know which asset it belongs to, when it was installed, and where the maintenance record lives. If that data isn't structured and linked at handover, no amount of visual detail makes the twin useful.

The projects where the twin actually gets used are the ones where asset data requirements were defined early, alongside COBie or an equivalent structured format, and validated against what the FM team's software could actually ingest — not assumed to work because the model looked right.

A digital twin earns that name by being opened six months after handover, not by how good it looks on delivery day.