| Tender & mobilisation |
Scope, responsibilities, and information requirements are not yet fixed, and early assumptions can carry through the whole delivery. |
Review of EIR/AIR, BEP drafting, responsibility matrices, and CDE setup before mobilisation. |
Draft BEP, MIDP/TIDP structure, responsibility matrix, and CDE workflow. |
Clearer scope boundaries and information requirements agreed before delivery starts. |
| Design |
Design information can progress across multiple models and disciplines without early visibility of interfaces. |
Federation, model audits, constructability review, and coordination issue tracking through design development. |
Federated coordination reviews, model QA/QC reports, and issue registers. |
Design issues surfaced and closed earlier, before they reach site. |
| Preconstruction |
Subcontractor deliverables, shop-drawing scope, and construction-stage responsibilities are not yet aligned to the coordinated model. |
Subcontractor deliverable planning, shop-drawing workflow setup, and 4D sequencing review. |
Deliverable schedules, shop-drawing register, and construction-sequencing model. |
Construction-stage information workflows agreed before mobilisation to site. |
| Construction |
Interfaces and subcontractor information must follow current work fronts, not a fixed design-stage plan. |
Workfront-led coordination, deliverable control, issue closure, and site verification. |
Federated reviews, issue records, construction models, verified drawings, and progress information. |
Fewer unresolved interfaces and decisions tied more closely to site priorities. |
| Commissioning & handover |
As-built conditions, asset data, and closeout records can diverge from what was modelled and specified. |
As-built verification, COBie and asset-information checks, and digital handover assembly. |
Verified as-built models, COBie datasets, and structured closeout records. |
Usable handover information rather than a document set assembled at closeout. |
| Operations support |
Handover information can go unused once the project team disbands if it is not structured for operational use. |
Asset-data support and structured information access for the operations team, where contracted. |
Operational asset records and structured data access. |
Handover information remains usable after project closeout. |