Why implement BIM now
BIM has moved from a competitive advantage to a baseline requirement. Public clients across the UK, US, the Gulf and Australia increasingly mandate BIM deliverables; contractors expect federated models for coordination; and the cost of clash-driven rework on site dwarfs the cost of coordinating in a model. A firm still working in 2D CAD is not just less efficient — it is increasingly locked out of the projects that specify BIM.
The good news: implementation no longer means a risky big-bang transition. The phased approach in this handbook lets a firm adopt BIM project-by-project while continuing to deliver.
Start with a BIM Execution Plan (BEP)
The BIM Execution Plan is the single most important document in any BIM project. It defines, before modeling starts, who models what, to what level of detail, in which software, and how models are shared and coordinated. A project without a BEP drifts into duplicated elements, mismatched origins and coordination chaos.
A workable BEP answers: project information requirements, model ownership by discipline, LOD per element per stage, file naming and the coordinate system, the coordination/clash schedule, and software versions. It does not need to be 80 pages — a clear 6-page BEP that everyone follows beats a comprehensive one nobody reads.
ISO 19650 in plain language
ISO 19650 is the international standard for managing information across the lifecycle of a built asset. Stripped of jargon, it asks three practical things: name your files consistently, control who can edit what and when (the common data environment workflow of Work-in-Progress → Shared → Published → Archived), and define information requirements upfront. You do not need certification to benefit — adopting the naming convention and the WIP/Shared/Published states alone removes most coordination errors.
Understanding LOD (Level of Detail / Development)
LOD describes how much geometric and information detail an element carries at a given stage. Getting it right prevents both under-modeling (useless for coordination) and over-modeling (wasted hours):
- LOD 100 — conceptual; massing and area only.
- LOD 200 — generic systems with approximate size and location.
- LOD 300 — specific elements with accurate geometry; suitable for documentation.
- LOD 350 — LOD 300 plus interfaces between systems; suitable for coordination.
- LOD 400 — fabrication-level detail.
- LOD 500 — verified as-built.
Specify LOD per element per stage in the BEP. Most coordination work lives at LOD 300–350.
The Common Data Environment (CDE)
The CDE is the single source of truth where all project information lives. It can be BIM 360 / Autodesk Construction Cloud, a structured SharePoint, or another platform — the tool matters less than the discipline. Every model and document moves through defined states (Work-in-Progress, Shared, Published, Archived), so everyone always knows which version is current and approved. A shared CDE is what turns separate discipline models into a coordinated project.
Team roles and responsibilities
BIM introduces roles that 2D CAD did not need. You do not need to hire for all of them immediately, but someone must own each function:
- BIM Manager — owns standards, templates and the CDE across projects.
- BIM Coordinator — runs clash detection and coordination on a given project.
- Discipline Modellers — produce the Architecture, Structural and MEP models.
- Information Manager — ensures ISO 19650 compliance on larger projects.
Smaller firms often combine these or outsource the modelling capacity while keeping the manager role in-house — a pragmatic way to scale BIM without a large permanent team.
Choosing your software stack
A typical BIM stack centres on Autodesk Revit for authoring, Navisworks for clash detection and coordination, and a CDE such as BIM 360 / ACC. AutoCAD remains useful for legacy and 2D work, and visualization tools (Enscape, Lumion, Twinmotion) plug into the model. Resist the urge to buy everything at once — start with Revit and a coordination tool, and add as real needs emerge.
A phased rollout roadmap
The lowest-risk path to BIM is incremental:
- Phase 1 — Pilot: run one low-risk project in Revit, with a simple BEP, while CAD continues elsewhere.
- Phase 2 — Standardise: build your template, family library and naming standard from pilot lessons.
- Phase 3 — Coordinate: introduce federated models and clash detection on multi-discipline projects.
- Phase 4 — Scale: make BIM the default; use outsourced capacity to absorb peaks.
- Phase 5 — Optimise: add automation, dashboards and lifecycle/digital-twin workflows.
Most firms reach Phase 3 within a year. Outsourcing the modelling capacity during Phases 1–3 lets you learn BIM on live projects without betting the practice on a single big hire.
Key takeaways
- BIM is now a baseline requirement, not an advantage — but adoption can be phased, not big-bang.
- The BIM Execution Plan is the most important document; a clear 6-page BEP beats an unread 80-page one.
- You can benefit from ISO 19650 without certification — adopt the naming convention and WIP/Shared/Published states.
- Specify LOD per element per stage; most coordination work lives at LOD 300–350.
- A disciplined Common Data Environment is what turns separate models into a coordinated project.
- Outsource modelling capacity during early phases to learn BIM on live projects without a risky permanent hire.
Frequently asked questions
How long does BIM implementation take?
Most firms run a successful pilot within the first quarter and reach full multi-discipline coordination within a year. A phased rollout means you keep delivering throughout — there is no period where the practice stops working to "switch to BIM".
Do we need ISO 19650 certification to do BIM?
No. Certification can help on certain public contracts, but most of the value of ISO 19650 comes from simply adopting its file-naming convention and the Work-in-Progress / Shared / Published / Archived workflow, neither of which requires certification.
What software do we actually need to start?
Start with Autodesk Revit for authoring and a coordination tool such as Navisworks, plus a common data environment to share models. Add visualization and automation tools later as real needs emerge — buying the whole stack upfront is a common and costly mistake.
Can we implement BIM without hiring a full BIM team?
Yes. Keep the BIM Manager function in-house to own standards and the CDE, and outsource the modelling capacity. This is how many small and mid-size firms scale BIM without committing to a large permanent payroll before the work justifies it.
What is the difference between LOD 300 and LOD 350?
LOD 300 elements have accurate geometry suitable for documentation. LOD 350 adds the interfaces and connections between systems, which is what makes a model genuinely useful for multi-discipline clash detection and coordination.
Ready to put this into practice?
Share your project and we will respond with a scope, timeline and fixed fee within 24 hours — or download our capability brochure to evaluate us first.