BIM Modelling & Coordination Services
Building Information Modelling services — architectural, structural and MEP modelling, coordination and clash detection — for design and construction teams.
Running a project through BIM only pays off if the model is properly coordinated — architectural, structural and services models that actually align, clashes caught before they reach site, and a model built to the LOD the project actually needs at each stage. A BIM process that exists in name only, with each discipline modelling in isolation and coordination happening informally over email, delivers little of the benefit BIM is supposed to provide, while still carrying the full modelling overhead — arguably the worst of both worlds.
What This Service Covers
We provide BIM modelling and coordination across architectural, structural and MEP disciplines, primarily in Revit, including clash detection, Revit family creation and point cloud/scan-to-BIM conversion for existing buildings and structures.
Models are built to an agreed Level of Development (LOD) for the project stage — concept, design development or construction — so the model stays a useful coordination tool rather than an overbuilt one that wastes modelling effort on detail nobody needs yet, or an underbuilt one that can't actually support the coordination decisions the project needs to make.
Clash Detection and Custom Family Creation
Coordination work includes running clash detection across combined discipline models (typically in Navisworks) and issuing clash reports the design team can action before issue-for-construction. A clash report is only useful if it's prioritised sensibly — a hard clash between a structural beam and a duct matters far more than a soft clearance clash that's easily resolved on site, and we structure reports so the important issues aren't buried in noise.
Custom Revit family creation is a recurring need on projects using non-standard equipment or fittings, and we build families that behave correctly when scheduled and tagged, not just families that look right in a 3D view — a family that reports the wrong quantity or the wrong parameter in a schedule causes exactly the kind of downstream error BIM is meant to prevent.
Inherited Models and Coordination as a Process
For projects inheriting an existing, poorly structured model, we can assess and rebuild problem areas rather than starting over entirely, which is usually faster and cheaper than a full rebuild while still fixing the coordination issues that made the model unreliable in the first place.
BIM coordination is as much a communication process as a technical one — a clash report that lands in someone's inbox with no context or prioritisation tends to get triaged poorly or ignored under deadline pressure. We run coordination as a structured, recurring process rather than a single event, with clear ownership assigned to each open issue so nothing falls through the gap between disciplines.
Planning for Model Handover Early
Model handover at project close-out is worth planning for from the start, not treated as an afterthought once construction is finished. A facilities team inheriting a BIM model for ongoing asset management needs different information — accurate equipment data, warranty references, maintenance access notes — than a design or construction team needed during delivery, and we scope this handover requirement early if it's part of the project brief.
What You Get
- Architectural, structural and MEP BIM models
- Revit models to agreed LOD
- Clash detection reports
- Custom Revit families
- Scan-to-BIM / point cloud conversion
- Coordinated federated models
- Model-derived drawing sheets
- BIM execution plan input and model health checks
Where This Is Used
- Multi-disciplinary design coordination
- Construction documentation
- Existing building/structure documentation from scan data
- Renovation and retrofit projects
- Facilities and asset documentation
- Model auditing and rebuild for legacy projects
How It Works
- 01
Model brief
Discipline, LOD target and any existing model or scan data confirmed upfront, along with which coordination decisions the model needs to support.
- 02
Scope & quote
Deliverables, software and coordination workflow agreed before starting, including how often clash detection will run through the project.
- 03
Modelling
Discipline model(s) built or updated to the agreed LOD, with families and parameters set up to schedule correctly, not just display correctly.
- 04
Coordination & clash detection
Models federated and checked for clashes, with reports issued for resolution and prioritised by severity rather than listed in raw, unsorted order.
- 05
Delivery
Coordinated model and any derived drawings delivered with revision tracking.
Software We Use
Industries We Support
Related Projects
Multi-Discipline BIM Clash Detection
Illustrative example: federated model coordination and clash detection across architectural, structural and MEP models.
View projectPoint Cloud to BIM — Existing Building
Illustrative example: converting laser scan data of an existing building into a working Revit model for a renovation project.
View projectFrequently Asked Questions
- 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.
Get a Quote for BIM Modelling & Coordination
Tell us what you need and our team can review the project requirements.