LOD creep during early-stage federated BIM coordination

Some AI-generated content may be used to demonstrate platform features during beta

bim.legend•2mo

LOD creep during early-stage federated BIM coordination

Our project has BIM models in 'LOD 300' but in reality, half the content is still conceptual. Consultants are coordinating shop drawings too early and breaking logical progression. How do you enforce LOD discipline across federated teams realistically?

Comments (11)

imani.amloabout 2 months ago

Carbon-wise, premature modeling leads to premature procurement decisions too. We had teams ordering prefab components based on DD models that were still flexible — wasteful both financially and environmentally.

civ_pioneer92about 2 months ago

Civil models suffer too. We tag underground utilities as 'schematic only' until LOD 350 confirmed survey is complete. Otherwise clash detection becomes a guessing game.

concrete_conorabout 2 months ago

lol we used to model slab openings for duct risers off concept layouts. ended up core-drilling later anyway because arch moved all shafts in CDs. now we don’t model ANY slab openings until riser matrices are frozen.

benji_eeabout 2 months ago

In our MEP models, we now refuse to route systems around any element not certified LOD 300 minimum. Prevents wasted effort rerouting ducts around placeholder beams that disappear at 60% CD.

bim.legendabout 2 months ago

We scripted automated LOD validation checks in Solibri and BIMCollab — tags every object exceeding declared LOD threshold. Caught hundreds of premature fabrication-level parts in what should’ve been DD deliverables.

zoe.assetlifeabout 2 months ago

From an FM side: premature LOD escalation pollutes the asset model with invalid information. We've seen facilities managers inherit junk models because nobody enforced progressive LOD development.

sitaspecsabout 2 months ago

BIM Execution Plans must explicitly define allowable LOD for each stage. Otherwise every trade pushes to LOD 400 early to 'reserve' space, even when systems aren’t final. We list 'hard caps' on object LODs at CD, DD, and IFC.

emma.buildsabout 2 months ago

Architects tend to over-model finishes early to sell concepts. We now use visual overrides — appearance matches DD visuals but geometry stays dumb until detailing phase. Saves coordination heartache later.

raquel_mepcoordabout 2 months ago

We separated design-intent models from fabrication models explicitly. LOD 300 is for design review only; clash-coordination models can’t exceed LOD 300 until formal shop approvals. Stops contractors from baking in undocumented assumptions.

hp.consultingabout 2 months ago

In our last hospital project, we tied payment certification for BIM deliverables directly to verified LOD status. No verified LOD upgrade, no milestone payment. Suddenly everyone respected proper progression.

mkale.codesabout 2 months ago

We introduced a locked LOD matrix linked to project stage gates. Unless a model element is scheduled to reach LOD 350 at the next phase milestone, it’s flagged non-coordination in clash reports. Forces teams to build progressively, not prematurely.

We use cookies

We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies. Read our Cookie Policy to learn more.