Level of Development (LOD)

What does Level of Development actually promise?

Level of Development (LOD) is a stated promise about how far a single element inside a BIM model may be relied upon for a specific purpose at a specific point in the project, not a rating of how polished or realistic the model looks. An LOD value attached to a wall, a beam, or a duct run tells the next person in the chain, the cost estimator, the structural engineer, the contractor, exactly what they may safely assume about that element's size, position, and properties, and what they must still verify elsewhere. Confusing a good-looking model with a reliable one is the single most common misunderstanding non-technical clients bring to a BIM conversation.

Because LOD is a promise rather than a fixed software setting, the same geometric shape, say a rectangular box representing a window, can carry a different LOD depending on what data sits behind it and what stage of the project produced it. A box with no confirmed dimensions is LOD 100 even if it is rendered with photorealistic glass; a box with a manufacturer's part number, frame profile, and installation tolerance is LOD 400 even if it is drawn as a plain rectangle.

What do the LOD 100 to 500 levels mean?

The widely used ladder runs from LOD 100, a conceptual massing block, to LOD 500, a field-verified as-built element, with each rung adding a specific, named increment of reliability rather than simply more polygons.

How is Level of Development different from Level of Detail?

Level of Detail describes how graphically rich an element looks; Level of Development describes how far you may rely on what that element claims, and the two routinely diverge in opposite directions. A door drawn as a single flat plane can already carry a confirmed fire rating, hardware set, and supplier reference, which is high Level of Development wrapped in low graphical detail. Conversely, a beautifully rendered kitchen with visible cabinet handles and grain texture is still LOD 200 if none of those objects have confirmed dimensions or specifications behind them.

This distinction matters most at handover between people. A client who judges progress by how real the walkthrough looks can be reassured by a model that is, in data terms, still provisional. Asking directly what LOD a given element has reached is a more useful question than asking how finished the visualization appears.

Why is quoting a price off an LOD 200 model the classic expensive mistake?

Because an LOD 200 element is placeholder geometry, a generic wall or window standing in for a decision not yet made, and treating its quantities as a firm bill of materials imports an assumption as if it were a fact. Window openings sized for a standard product, a roof pitch chosen for early massing, or a floor buildup guessed before the structural engineer has weighed in can all shift materially once the design reaches LOD 300. A contractor who prices from an LOD 200 export, or a client who commits to a budget from one, is pricing a hypothesis.

The practical discipline is simple: whoever hands over quantities or a cost estimate should state the LOD of the source model alongside the numbers, and whoever receives them should ask. This single habit prevents the most common and most expensive category of dispute between architect, engineer, and contractor.

How does LOD map onto the Slovak design phases?

Each Komarch design phase carries a de-facto LOD ceiling, because the deliverable defined for that phase is what the architect's fee actually buys, not a number written into a standard contract.

Where does LOD 350 fit, and why isn't there a level between every pair of numbers?

LOD 350 exists specifically to describe interfaces and connections between building systems, the point at which a structural beam and a ventilation duct need to agree on exactly where they meet, and it sits deliberately between 300 and 400 rather than replacing either of them. It was added to the original 100 to 500 sequence precisely because coordination and clash detection needed a defined checkpoint that plain LOD 300 did not cover and full LOD 400 fabrication detail was not yet warranted for.

No other gaps in the sequence carry a similarly defined intermediate level. Talk of a project being "LOD 250" partway through design development is shorthand for progress, not a defined rung, and should not be treated as one in a contract or a handover.

Who decides the required LOD, and where is it written down?

The required LOD for each element and phase is set out in a BIM execution plan or an equivalent brief agreed between the architect, engineers, and client, not inferred afterward from whatever the software happened to produce. On a residential project without a formal BIM appointment, the phase itself sets an implicit ceiling: nobody expects fabrication-level duct routing at the concept stage, and nobody should accept placeholder geometry at handover.

Data exchanged between disciplines typically travels as open files so the receiving party can check what LOD actually arrived, rather than trusting the sender's label.

What does LOD mean practically for a solo residential practice in Slovakia?

For most single-family houses, the useful range stops at LOD 300 to 350: enough to confirm quantities for permitting and to coordinate structure with MEP routing, without paying for fabrication-level detail the project does not need. Pushing to LOD 400 makes sense selectively, for a prefabricated timber frame or a complex glazing system where the manufacturer needs exact interface data, not as a blanket target for the whole house.

LOD 500 is worth budgeting for deliberately rather than assuming it happens automatically at handover. Unless someone is contracted to verify the model against the finished building, what a client receives at the end is still a design model with construction-stage edits, not a true as-built record.