How we deliver · Digital
Build it twice. Once on a screen.
A clash found in the model costs an hour of a coordinator's time. The same clash found after installation costs a fortnight. That arithmetic is the entire business case for our BIM team.
Read the arithmetic in fullFrom model to building, in five moves
- 01
Federate
Every discipline model — ours and every subcontractor's — is federated weekly. Model quality is a subcontract deliverable with payment attached; goodwill alone never fixed a model.
- 02
Detect
Clash rules are tuned so a hanger brushing a conduit is noise and a fire damper missing its opening is a hold point. Untuned rules produce 40,000-line reports nobody reads.
- 03
Resolve
Every genuine clash gets an owner and a date. We target 99% resolved in-model; the difference between 95% and 99% is roughly 80 days of site disruption on a mid-size build.
- 04
Construct
Setting-out points, fabrication drawings and installation sequences come out of the same model the clashes were resolved in — not a redrawn version of it.
- 05
Hand over
As-built model plus asset data, updated progressively through construction. The client receives a model they can actually operate the building from.
What coordination does not catch
Clash detection catches geometry. It does not catch sequence. A model can be perfectly clash-free and still describe a building you cannot physically construct in the order you planned — because the crane cannot reach, or the room cannot be closed until something inside it is commissioned.
So we run a separate constructability review alongside clash detection, with the site team in the room rather than the design team. It finds a different class of problem, early enough to matter.
Toolchain & standards
- Authoring
- Revit, Civil 3D
- Federation & clash
- Navisworks, Revizto
- Common data environment
- ACC / BIM 360
- Reality capture
- Terrestrial laser scan, drone photogrammetry
- Programme linkage
- 4D sequencing on projects > SAR 100M
- Standard
- ISO 19650 information management