BIM Modelling & Coordination Services

Building Information Modelling (BIM) is the process of creating a data-rich 3D model of a building or structure that documents design, coordination and construction information, typically in Revit.

Combined architectural, structural and services models are checked against each other (commonly in Navisworks) to identify physical clashes before construction, with a report issued for the design team to resolve, prioritised by which clashes actually matter.

Yes — see our Scan to BIM service for converting laser scan or point cloud data of an existing building or structure into a working Revit model.

This is agreed per project and project stage — we scope modelling depth against the LOD your project actually needs rather than defaulting to the highest level, since over-modelling wastes time just as much as under-modelling causes coordination gaps.

Yes, and we build them to schedule and tag correctly, not just to look right in a 3D view, since a family that reports incorrect data undermines the point of using BIM in the first place.

Yes, assessing and rebuilding problem areas in an inherited model is a common request, and it's usually faster than starting from scratch while still resolving the underlying coordination issues.

By running coordination as a structured, recurring process with clear ownership assigned to each open issue, rather than issuing a single large report and hoping it gets actioned without follow-up.

Yes, if facilities and asset management handover is part of the brief, we scope this early so the model carries the equipment data, warranty references and maintenance information a facilities team actually needs, not just what a design and construction team needed.

Yes, where a project needs a structured coordination process, we can maintain an issue log alongside clash reports, tracking who owns each open item and when it was resolved.

Yes, this is a core reason Navisworks-based federation exists — models built in Revit, Tekla, Civil 3D and other platforms can be combined into a single coordination view without requiring every discipline to use the same authoring software.

This depends on project pace and how frequently discipline models are being updated — we agree a sensible cadence with you upfront, since running it too rarely risks a large, unmanageable clash list building up unnoticed.

Yes, a coordinated federated model demonstrating design resolution can be a valuable part of a tender submission, and we scope this specifically if that's the intended use.

Yes, inconsistent or duplicated families across discipline models is a common, avoidable source of coordination confusion, and we check for this as part of federating and reviewing a combined model.

Yes, a coordinated model makes it easier to visualise the knock-on impact of a proposed change across disciplines, which is useful input when a value engineering review is being considered.

Yes, coordination can be run at a faster, more frequent cadence to match a compressed design-and-build programme, prioritising the highest-risk interfaces first.

Yes, where models are structured with quantity take-off in mind, reliable quantities for major building elements can be extracted directly rather than measured manually from 2D drawings.

We can prepare and structure models to feed into a 4D or 5D workflow run by your project's scheduling or cost team, coordinating model structure with their specific software requirements.

Yes, translating a technical clash report into a plain-language summary of what's been found and resolved is something we can provide alongside the full technical report for less technical stakeholders.

Yes, federation and clash detection can include specialist models — fire services, vertical transportation, façade — alongside the core architectural, structural and MEP models, provided those models are supplied in a compatible format.

Yes, walking the design team through a federated model and clash findings directly can resolve ambiguity faster than a written report alone, particularly for complex or contested clashes.

Yes, coordinating new fit-out elements against an existing building's structure and services — captured either from existing drawings or scan data — is a common and slightly more constrained coordination task.

Yes, cloud-based Revit worksharing and structured issue tracking mean coordination isn't dependent on all parties working in the same time zone, provided a clear process for issuing and resolving clashes is agreed upfront.

Yes, a summary report confirming the status of all raised clashes — resolved, accepted, or deferred with reasoning — is a valuable document to issue alongside the final coordinated model before construction begins.

Yes, where a project runs a formal CDE for document and model control, we work within its structure and naming conventions rather than maintaining a separate, parallel file system.