BIM from authoring to handover: LOD 100–500 models in Revit and Civil 3D, federated coordination and clash resolution in Navisworks with BCF issue tracking, 4D programme and 5D quantities, ISO 19650-aligned information management, and COBie and digital-twin handover — for developers, contractors, consultants and public clients.
BIM is how we keep design, cost, programme and site in one coordinated source of truth, so problems are found on a screen, not in a slab.
BIM is often described as 3D modelling, but the geometry is the least valuable part. Every wall, duct and beam carries data — material, cost, supplier, warranty, maintenance interval — that follows the project from concept to operation. Without that discipline, design happens in silos, clashes surface on site instead of on screen, and the result is rework, a flood of RFIs, variations and delay that no contract clause fully recovers.
Our approach starts with a BIM Execution Plan, not a modelling brief: who models what, to which LOD, checked how often. We federate weekly and push every clash into a BCF issue with a named owner and a due date. Programme and cost sit alongside the model, not behind it. Because we also build software, we extend your CDE with dashboards, issue trackers and, for construction teams, our CivilHub product.
A model nobody coordinates is just an expensive drawing. We run the model like a project: owners, deadlines, closed issues.— Qubit engineering team
From the first Revit model to the last COBie sheet, these are the capabilities we bring in-house to a BIM commission — not outsourced to a subcontractor you never meet.
We author architecture, structure, MEP and infrastructure models in Revit and Civil 3D — corridors, junctions and bridge geometry included. Discipline templates, shared parameters and Revit families are set up before modelling starts, so every model checks cleanly against the agreed LOD for its stage, from concept massing to fabrication-level detail.
We bring every discipline model together in a federated Navisworks model, run clash matrices by discipline pair and tolerance-based rules rather than blanket detection, and log every real clash as a BCF issue. Weekly coordination meetings work the issue list until it closes, not until the deadline arrives.
Model elements link directly to Primavera P6 or MS Project activities, so the sequence is something you can watch, not just read. We build logistics and crane simulations, spot sequencing clashes before they hit site, and produce short look-ahead films the site team can walk into a Monday meeting with.
Quantities come off the model, not off a ruler on a PDF — take-off structured by Uniclass or CSI codes, checked against the design intent behind every element. When a design changes, we can price the impact in hours, not days, because the model already knows what moved.
We review your EIR, write the BIM Execution Plan, and set up the CDE — Autodesk Construction Cloud, BIM 360 or Trimble Connect — with naming conventions, folder structures and a MIDP/TIDP that people actually follow. Model audits check compliance against ISO 19650 before it becomes a claim.
Point clouds from laser scans become as-built models, checked against what was actually built rather than what was designed. We validate COBie datasets, build asset registers, and connect the result to your FM or CMMS system — with a Qubit-built dashboard on top so the data gets looked at, not archived.
Five stages, one accountable team — from the first EIR review to the COBie file your FM system actually loads.
We review the EIR and OIR, confirm the BIM uses that matter for this project, and agree an LOD matrix by stage and by element — so nobody is modelling to a standard nobody asked for.
Roles, responsibilities, naming conventions and a federation strategy go into a signed BIM Execution Plan. We configure the CDE — folders, permissions, workflows — so the first model upload already follows the rules.
Discipline teams model to the agreed LOD by stage. We federate weekly and run automated model health checks — naming, units, duplicate elements — before anyone spends time reviewing geometry that shouldn't exist.
Clashes get resolved through owned, dated BCF issues, not meeting notes. We link the programme for a 4D sequencing film and take off quantities for a 5D BoQ, so cost, time and geometry finally agree.
We deliver the as-built model, a validated COBie dataset and an asset register mapped to your FM or CMMS, with a digital-twin link where the project calls for one — so day one of operations isn't day one of data entry.
Running a clash detection isn't the hard part — software does that in minutes. The hard part is making sure every real clash becomes an owned issue that gets fixed and stays fixed. We run clash matrices by discipline pair, filter tolerance from real problems, and review the burn-down with the design team every week.
A programme is easier to defend when you can watch it happen. We link model elements to Primavera P6 or MS Project activities, run logistics and look-ahead simulations before the site does, and take off quantities straight from the model by classification. Design changes get priced in hours, in the same meeting.
A model handed over as a single federated file is not a handover, it's an archive. We validate COBie sheets against your CMMS structure before the file leaves our hands, link O&M documents to their elements, and build the dashboards that put the data in front of the people who run the building.
Every deliverable is versioned in your CDE and handed over in the format you asked for — native Revit and Civil 3D files alongside open IFC, so you're never locked to one vendor's software. You own everything we produce, with full revision history, so anyone can trace a decision back to the model state it came from.
The codes and platforms behind every model we federate, and the exchange formats that keep your data out of one vendor's silo.
What we model, coordinate and hand over against.
The platforms our modellers and coordinators work in daily.
How data moves between your team, ours, and your CDE.
Across Qubit BIM engagements, 2021–2026. Illustrative until replaced with audited figures.
Six sectors where a clash on screen is far cheaper than a clash on site.
Clinical, plant and structure share ceiling voids that leave no room for error. We coordinate MEP-heavy hospital models where a missed clash means a wall opened after fit-out.
Multi-building campuses need one coordinated model across faculties, phases and decades of extensions — plus handover data your estates team can maintain long after we've left.
Dense services risers and tight floor-to-floor heights make coordination non-negotiable. We federate architecture, structure and MEP early enough to fix the clashes that matter.
Process equipment, structure and services compete for the same headroom. We model to fabrication-level detail where a pipe route genuinely can't move once poured.
Bridges, stations and depots in Civil 3D and Revit together, coordinated against survey and utility data so buried services stop becoming site surprises.
Schools, courts and civic buildings that answer to a public client and a public budget — modelled and handed over to a standard an auditor can follow.
Anonymised examples. We're happy to walk through the full story on a call.
A 40,000 m² hospital campus with three towers and a shared plant deck needed architecture, structure and MEP coordinated to LOD 350 before steel was ordered. We ran weekly federation from design development through construction issue, tracked every clash as an owned, dated BCF issue, and closed the list before the first slab was poured.
A three-block garment factory needed cost certainty before the client would release funding for the next block. We took off quantities straight from the model by Uniclass classification, ran a 4D sequence to de-risk a tight fit-out programme, and handed over a validated COBie dataset so facilities could load it into their CMMS on day one.
Can't find your answer? Drop us a line — we usually reply within a day.
Talk to usWe work to the BIMForum LOD Specification, agreed element-by-element in the LOD matrix, not as one blanket number for the whole project. A concept model might sit at LOD 200 while a structural steel package needs LOD 400. The matrix is signed off before modelling starts, so nobody discovers a gap at coordination.
Yes — ISO 19650-2 shapes how we run delivery, from the exchange information requirements through to the BEP, the MIDP/TIDP and CDE naming conventions. Where a client mandates BS EN 17412-1 or a specific Uniclass scheme, we work to that too. Where no mandate exists, we still run the same discipline, because it's simply better practice.
Revit, Civil 3D and Tekla Structures for authoring; Navisworks Manage and Solibri for coordination; Synchro 4D for sequencing. We exchange in IFC 4 (or 2x3 where needed), BCF for issues, COBie for handover, and NWD/NWC, RVT and DWG for native review. If your consultants standardise on something else, we'll match it.
Yes. We rebuild models from 2D CAD or PDF drawings where none exist, and run scan-to-BIM from laser scans or drone photogrammetry for as-built and refurbishment work. Point clouds are registered, cleaned and modelled to the LOD the project needs — lower for fabric you won't touch, higher for anything you'll alter.
We chair a weekly (or fortnightly, for smaller jobs) coordination meeting around the federated model and the open BCF issue list. Every consultant sees the same clashes, owners and due dates — no separate spreadsheets, no "I didn't get that drawing". We run these meetings even when we didn't author every model.
Yes — Civil 3D corridors, bridge geometry and drainage networks are as much our world as Revit buildings. It's why our Engineering Design & Consultancy and Intelligent Transport Systems teams sit next to our BIM team, not in a separate division. Horizontal infrastructure gets the same LOD discipline and federation approach as any building.
Send us your EIR, a set of drawings, or just a description of the problem — we'll tell you honestly what LOD, platform and process fits, and what it would cost to run it properly.