LOD is a data contract, not a rendering setting
The term Level of Development began as an AIA contract concept (AIA Document E202-2008, succeeded by E203-2013 and G202-2013 Project Building Information Modeling Protocol Form) and was then expanded by the BIMForum LOD Specification, which reissues annually. The BIMForum LOD Spec 2024 is the reference most owners and GCs now cite in Exhibit H of their contract, and it defines LOD per model element, not per model.
That distinction is where estimators get hurt. A single Revit model is rarely a single LOD. A curtain wall assembly might be LOD 350 while the back-of-house CMU partition is still LOD 200. When an estimator exports a schedule and treats every element as authoritative, the resulting takeoff is a mix of authoritative geometry and placeholder geometry — which is exactly how a number leaves the estimate with a confidence rating that was never earned.
The five LOD rungs, in the numbers that matter
Per G202 Section 1.2 and the BIMForum 2024 Spec, the five canonical LODs are 100, 200, 300, 350, 400, and 500. LOD 300 and 350 are the two that matter most for bid-stage takeoff because they bracket the transition from "design intent geometry" to "fabrication-coordinated geometry."
| LOD | Geometry | Attached data | Takeoff confidence |
|---|---|---|---|
| 100 | Symbolic or 2D. Mass or area placeholder. | Cost/SF order-of-magnitude only. | Conceptual. No quantity extraction. |
| 200 | Generic shape, approximate size/location. | Type, material category. | Schematic. +/- 20-25%. |
| 300 | Specific size, shape, location, orientation. | Manufacturer-neutral specs, assembly type. | Design development. +/- 8-12%. |
| 350 | LOD 300 plus interfaces, connections, penetrations, supports. | Coordinated connection detail, hanger/support geometry. | Coordination-ready. +/- 3-5%. |
| 400 | Fabrication-level. Shop drawing geometry. | Manufacturer data, part numbers, shop ticket. | Fabrication. +/- 1-2%. |
| 500 | As-built, field-verified. | Commissioning, O&M, warranty links. | Record. Not used for new bids. |
What actually changes between 300 and 350
LOD 300 gives you a 10-inch CMU wall modeled to the correct thickness, length, and height, with the right family tag. It does not give you the bond beams, the control joint locations, the lintel bearing details, the dowels into the slab, or the grouted cells. It does not model the vertical rebar unless the model author pushed it. In most firms' BIM execution plans, reinforcement geometry does not appear until LOD 350 or 400.
Same wall at LOD 350: the bond beam courses are present as discrete horizontal elements, the control joints are modeled at their specified spacing (typically 20-25 ft on center per TMS 402/602), the lintel bearing is shown with its dimensioned pocket, and the dowels appear as linear elements with attached size and spacing data. A quantity take from 350 reads a 15-22% higher unit count on steel reinforcement than the same wall at 300, because at 300 the reinforcement was a spec note, not geometry.
Connection detail is the 350 definition
The BIMForum 2024 Spec is explicit: LOD 350 adds interfaces with other building systems. For structural steel, that means connection plates, bolt geometry, and shear tabs are modeled. For MEP, it means hangers, seismic bracing, sleeves through rated walls, and concrete housekeeping pads. For curtain wall, it means the embed plates, anchor rods, pressure plates, and thermal breaks.
A mechanical estimator who pulled duct linear footage from an LOD 300 model will be short on hanger count by 100%, because the hangers do not exist in the model yet. The piping schedule will not carry the seismic bracing per ASCE 7-22 Chapter 13, the rated-wall sleeves per IBC Section 714, or the equipment housekeeping pads. All of that is 350-and-later scope.
Exporting a Revit schedule at DD (LOD 300) and locking the number as a GMP line item. The LOD 300 model systematically omits connections, bracing, hangers, and penetrations — every one of which carries material and labor. A 350 reconciliation during CD phase typically moves the number 4-9%, and it always moves up.
Clash detection drift and the schedule feedback loop
When coordination starts in earnest at LOD 350, the Navisworks clash report typically flags 400-1,200 clashes on a mid-size commercial job. Most resolve by re-routing, but a non-trivial fraction resolve by adding material — an extra elbow, a longer run, a support steel member, a relocated sleeve. Every one of those resolutions is additive to the quantity.
Research from Dodge Data & Analytics SmartMarket Reports on BIM coordination outcomes has repeatedly shown that 12-18% of clash resolutions add physical material to the model. If you set your takeoff baseline at LOD 300 and do not re-baseline at LOD 350-post-clash, your estimate is missing that 12-18% additive wedge entirely on the affected systems.
Reconciling model-based and 2D takeoff
Even on a BIM project, the best estimating practice is a two-track takeoff: a model-based extract (Revit schedule, IFC property set, or Navisworks quantification) compared line by line to a 2D takeoff from the sheet set. The deltas are the findings.
A typical reconciliation formula for a single CSI section:
If |Delta%| > 5% → flag for review
If |Delta%| > 10% → require model author sign-off on LOD claim
At LOD 300, the expected delta on concrete and structural steel is 3-8%, usually because the model omits curbs, thickened slab edges, pilasters, and embeds. At LOD 350, the expected delta drops to 1-3%. If your 2D takeoff and model extract disagree by more than those ranges at the claimed LOD, something is wrong — either the model is below the claimed LOD, or the 2D takeoff missed a drawing set.
Revit schedules vs. CSI division mapping
Revit organizes elements by category (Walls, Floors, Roofs, Structural Framing, Pipes, Ducts). The cost estimator needs them by CSI MasterFormat 2020 division and section. The mapping is not automatic and it is where substantial miscoding happens.
A structural column modeled as a Revit Structural Framing family needs to land in CSI 05 12 00 (Structural Steel Framing) if steel, or 03 41 00 (Precast Structural Concrete) if precast, or 03 30 00 (Cast-in-Place Concrete) if poured. A single Revit family tag does not encode the CSI section — the estimator (or the mapping layer) has to. Without an explicit mapping file, an automated extract dumps all columns into one bucket and mixes trades.
A working discipline: the BIM Execution Plan (BxP) should require a Comments or Assembly Code parameter on every schedulable element, populated with the UniFormat II or CSI MasterFormat 2020 six-digit code. Uniformat II codes (C1010 for walls, D3040 for HVAC distribution, etc.) map cleanly back to MasterFormat via a standard crosswalk maintained by the Construction Specifications Institute.
"We stopped treating the model as the number. Now we treat it as one of two numbers. The 2D takeoff is the other. The bid is the reconciled sum with a documented delta, and the LOD claim gets a line in the bid narrative."
Aisha Kelley, BIM Manager and Chief Estimator, reflecting on five years of GMP reconciliations
Closing the LOD gap on your next bid
Treat the LOD claim as something the model author owes you in writing. Exhibit H of your contract should cite the BIMForum LOD Spec 2024 and identify the LOD per model element category at each submission milestone. On bid day, capture the LOD claim in the bid narrative, set your confidence interval accordingly, and budget the reconciliation wedge (3-8% at 300, 1-3% at 350) explicitly in contingency — not in the line items. When the CD set arrives and the numbers move, you will know why and by how much, and the GMP can absorb it without a change-order fight.