Students often picture BIM as "modeling, then clash detection, then done" — the reality spans several distinct stages, each with different goals, different LOD expectations, and different people responsible. Here's the full picture, stage by stage.
The full lifecycle, stage by stage
| Stage | What happens | Typical LOD | Who's primarily responsible |
|---|---|---|---|
| Concept design | Massing, basic spatial layout, early design options | LOD 100-200 | Architect/Designer |
| Schematic/preliminary design | Refined layout, structural/MEP concept coordination begins | LOD 200 | Architect + discipline leads |
| Detailed design | Full model development across all disciplines | LOD 300-350 | All disciplines + BIM Coordinator |
| Coordination/clash resolution | Federated model review, systematic clash detection and resolution | LOD 350 | BIM Coordinator/Manager |
| Construction documentation | Final drawings, schedules, specifications issued | LOD 350-400 | All disciplines |
| Construction phase | Site queries, model-based RFI resolution, fabrication detail (steel/rebar) | LOD 400 | BIM Engineer/Coordinator + contractor |
| Handover/FM | As-built verification, COBie/asset data delivery | LOD 500 | BIM Manager/Information Manager |
Why understanding the full sequence matters, not just your own stage
A common beginner mistake (covered in our beginner mistakes guide) is focusing entirely on the modeling stage you're personally responsible for, without understanding how your work feeds the next stage. A structural model built without considering downstream MEP coordination needs creates problems for someone else later — and that someone else is often you, a few months on, in a different role.
Where most projects actually lose time
In my experience, the coordination/clash resolution stage is where projects either run smoothly or fall behind, because it's the stage most dependent on cross-discipline communication rather than individual technical skill. A project with strong individual modeling but weak coordination process will still run into the same site clashes a poorly-modeled but well-coordinated project would avoid.
How the EIR and BEP/IPP frame this whole sequence
The stage-by-stage LOD expectations and responsibilities shown above should be explicitly defined in the project's EIR (see our EIR writing guide) and the delivery team's response in the BEP/IPP — without that documentation, teams often have mismatched assumptions about what "done" means at each stage, which surfaces as friction later rather than being addressed upfront.
What this means for career planning
Different stages of this workflow favor different strengths — concept/schematic design rewards design judgment, detailed design and coordination reward technical and process skill, and handover/FM rewards data discipline and standards literacy. Understanding the full sequence helps you recognize which stage you're naturally drawn to, and plan your skill-building accordingly.
Our plans map directly onto this lifecycle — Foundation for early design-stage modeling, Structure for detailed design and coordination, Apex for the process layer spanning the full lifecycle. Full curriculum on the Programs page.
