The LOD framework — Level of Development, as defined under the AIA's Document G202-2013 and the BIM Forum's LOD Specification — gives architecture firms a shared language for communicating model geometry and information completeness to their consultants. In theory, it coordinates expectations across the project team. In practice, LOD 350 is where coordination responsibility sharpens from "we'll figure it out" to "this is what we're building."
Most architecture firms get the LOD definitions approximately right in their BIM Execution Plans. The misapplication happens in how they structure their coordination process around each LOD threshold — specifically the transition from LOD 300 to LOD 350. That transition is not just about adding more detail to the model. It is about accepting that the geometry is construction-intent, not design-intent, and that every clash at LOD 350 is a real problem, not a placeholder.
What LOD 350 Actually Means in Practice
The BIM Forum LOD Specification defines LOD 350 as: model elements are modeled as specific assemblies accurate in terms of size, shape, location, quantity, and orientation, with non-geometric information including all information to allow coordination with adjacent elements. Critically, it adds that connections between elements must be included.
That last clause — connections must be included — is what separates LOD 350 from LOD 300 for coordination purposes. A structural beam at LOD 300 might show the beam profile and approximate length. At LOD 350, it should show the connection plates, the embed geometry, the anchor bolt pattern. An HVAC duct at LOD 300 shows the duct dimensions and approximate routing. At LOD 350, the elbows, transitions, access doors, and hangar attachment points are modeled. These are the elements that cause the real-world installation conflicts — and they are exactly what LOD 300 omits.
When a firm runs clash detection against a LOD 300 federated model, they are catching a subset of the eventual LOD 350 clashes. Some are genuine routing conflicts. Others are artifacts of the LOD gap: the duct fits at LOD 300 because the connection plate that would block it has not been modeled yet. Running coordination at LOD 300 and declaring it complete is the single most common mistake firms make when managing consultant coordination.
The LOD Mismatch Problem
Architecture firms managing multiple consultants on a medium-to-large project almost always encounter LOD mismatch between disciplines. This is not negligence — it reflects the different production schedules of different disciplines. Structural engineers typically advance to LOD 350 earlier than MEP, because structural design tends to lock before mechanical layouts are finalized. MEP consultants often stay at LOD 300 until the architectural ceiling heights are confirmed. The result is a coordination session where the structural model is at LOD 350 and the HVAC model is at LOD 300, and every clash detected needs to be evaluated with that mismatch in mind.
The practical consequence: a LOD 350 structural beam with full connection details will generate clashes with a LOD 300 duct route that would not exist at matched LOD levels, because the duct route at LOD 300 does not yet account for the connection hardware that the structural model already shows. Reporting those as coordination issues sends the MEP consultant on a wild chase for non-existent routing problems.
The discipline coordination protocol that handles this correctly includes a documented LOD status per discipline per coordination round. Before each clash detection run, the BIM Coordinator notes each discipline's current LOD and flags the clash report accordingly. Clashes between LOD 300 and LOD 350 elements are categorized as "preliminary — confirm at matched LOD" rather than "confirmed conflict." This sounds obvious; most firms do not do it.
What the BEP Should Specify About LOD
A BIM Execution Plan that handles LOD-based coordination correctly specifies three things that many BEPs omit:
- LOD milestone schedule per discipline: not just "LOD 350 at Construction Documents" but "Structural LOD 350 by SD+4 weeks; MEP LOD 350 by DD complete; Architectural LOD 350 at 100% CD." These dates let the BIM Coordinator know when clash detection results become reliable for each discipline pairing.
- LOD tolerance for coordination acceptance: at what LOD level does a clash count as a mandatory issue versus a preliminary flag? Many projects set this at LOD 300 for routing coordination and LOD 350 for connection/clearance coordination — the two different types require different resolution paths.
- Who validates LOD status: the BIM Coordinator cannot independently verify that the structural engineer's model is actually at LOD 350. Each discipline lead signs off on LOD status before each coordination round. Without that attestation, the coordinator is making assumptions about model completeness that may not hold.
Over-Modeling at the Wrong Phase
There is a counterintuitive failure mode: firms that push consultants to LOD 350 too early, before the design is stable enough to support that level of commitment. This happens more often on competitive fee structures where firms commit to LOD 350 deliverables at SD to differentiate their proposal, then find their mechanical consultant modeling LOD 350 duct runs against architectural ceiling heights that change in three iterations.
When the ceiling height changes by 6 inches, every LOD 350 duct route that was coordinated against the previous ceiling height is now potentially invalid. The coordination work done at LOD 350 does not carry forward cleanly — the high-detail model must be re-coordinated against the updated geometry. Firms that had stayed at LOD 300 for that same period would have a much simpler path back to coordination because the LOD 300 model abstracts away the specific clearances that LOD 350 captures.
This is the under-appreciated discipline cost of premature LOD escalation: it creates coordination debt that compounds with design changes. The coordination efficiency gain from higher LOD only materializes when the design is stable enough that the detailed model represents construction intent, not aspirational intent.
We are not saying firms should delay LOD advancement — LOD 350 is genuinely the right target for coordination before construction documents are issued. The point is that the timing of LOD advancement must follow design stability, not a fixed calendar date or a competitive commitment made before the project scope was fully understood.
The Structural Steel Edge Case
Structural steel coordination deserves specific attention because it is where LOD misapplication causes the most expensive errors. Structural steel members at LOD 350 include connection plates, stiffeners, and embed plates for attachments — details that take significant re-engineering time if a clash requires changes post-fabrication bid. When a detailer has priced the steel package against the LOD 350 structural model, and the MEP consultant later discovers that their original routing is blocked by an embed plate that was not in the LOD 300 model they coordinated against, the result is a coordination failure that costs money and schedule.
Consider a scenario at an early-stage commercial mixed-use project: structural steel modeled to LOD 350 includes moment frame connections at the building core. The MEP consultant's Level 4 mechanical room has three main trunk ducts routed through the core at a floor elevation that puts them in direct conflict with a moment frame gusset plate — a connection element that exists only at LOD 350. If the initial coordination was run at LOD 300, that conflict was invisible. By the time it surfaces during steel detailing, the mechanical layout has been coordinated around other constraints and the only resolution is a duct reroute that adds four elbows and crosses two other runs.
The protocol that prevents this: any clash detection run that includes structural steel elements should require that the structural model be at LOD 350 before the run is treated as coordination-complete. If the structural model is at LOD 300, the run is labeled "preliminary — structural connection elements not included" and no routing decisions should be locked based on its output.
Coordination Checkpoints Built Around LOD Milestones
The most effective coordination workflows tie their meeting cadence to LOD milestones rather than calendar intervals. Monthly coordination meetings are a calendar-interval approach. LOD-milestone meetings look different: a coordination sprint when structural advances to LOD 300, another when MEP advances to LOD 300, a full round when all disciplines reach LOD 300, and a final confirmation round at LOD 350 before CD issue.
The tradeoff is that LOD-milestone coordination requires more upfront alignment with consultants about their production schedules. Calendar-interval coordination is easier to schedule but wastes analysis cycles on models that haven't advanced. Most firms default to calendar intervals because consultant schedule visibility is limited. The firms that invest in better schedule alignment with their consultants — even informally, via a shared tracking sheet — find that LOD-milestone coordination eliminates the most frustrating category of "phantom clashes": conflicts that appear at one coordination round and disappear at the next because the model detail hadn't stabilized.
The cleanest coordination deliverable at the CD stage is a clash report that shows zero open issues at LOD 350, with every discipline signed off at that level and every resolved clash logged with the responsible discipline and resolution description. That document is the coordination record the GC uses when field questions arise, and it is the record the architecture firm uses when defending against RFI liability claims. Getting there requires managing LOD not as a compliance checkbox but as the core variable in your coordination strategy.