It's the real thing
The element is the specific system, object or assembly that's been designed, not a generic placeholder.
Level of development
LOD 300: what it means and how to plan it
At LOD 300 a model element is the specific system, object or assembly that's been designed: its quantity, size, shape, location and orientation can be measured from the model. Teams usually ask for it at detailed design, element by element, never for the whole model at once.
Free plan, no card. Everyone you invite joins free.
app.plannerly.com
What LOD 300 means
LOD stands for level of development: how far an element's geometry and information have been thought through, and so how far the rest of the team can rely on it. The BIMForum LOD Specification describes each level, element by element. At LOD 300 three things are true:
You can measure it
Its quantity, size, shape, location and orientation can be measured from the model itself, without notes or dimension call-outs.
It's in the right place
It sits accurately relative to the project origin, so other teams can coordinate against it.
LOD 200, 300, 350 and 400, for one door
Here's how the same internal door develops:
| Level | The door in the model | What you can use it for |
|---|---|---|
| LOD 200 | A generic door, with approximate size and position | Early layouts and options |
| LOD 300 | The designed door: its actual width, height, frame and swing, where it will actually go | Detailed design, coordination and quantities |
| LOD 350 | As LOD 300, plus how it meets the things around it, such as the wall opening and the frame fixings | Detailed coordination between trades |
| LOD 400 | The door as it will be made and fitted, with fabrication and installation detail | Fabrication and installation |
Every level, with pictures, in levels of development, LOD 100 to 500.
When you need LOD 300
LOD 300 belongs to a milestone, not to the whole model. Ask for it element by element, when someone needs to rely on that element:
- Detailed design: the design is fixed enough to coordinate, so the main elements reach LOD 300.
- Coordination: other trades model against it, so its position and size must be dependable.
- Quantities and cost: counts and measured quantities come straight from the model.
- Not yet: furniture, finishes and anything still being decided can stay at LOD 200 until they matter.
Step by step
How to plan LOD 300 on your project
-
Lay out the grid
Elements down the side, broken down by a classification such as Uniclass, Uniformat or OmniClass, and the information exchange milestones across the top.
Every element, every milestone -
Set the level per cell
For each element and milestone, set the level it must reach. Not everything needs LOD 300 at the same time.
LOD 300 only where it's needed -
Add the data and an owner
Add the properties each element must carry at that milestone, and the team that models it, so every LOD 300 has a name next to it.
Who models what, by when -
Check it
Export the requirements as an IDS file for your authors, or check delivered models in Verify.
The scope becomes the checks
In Plannerly Scope
Set LOD 300 where it's needed, and nowhere else
Scope
Every element, every milestone, one level
Plannerly Scope puts your elements down the side and the milestones across the top. In each cell you set the level the element must reach, the information it must carry and the team that owns it, using the BIMForum and AIA LOD frameworks, ISO 19650's level of information need or levels of your own.
- LOD and level of information need in the same grid
- Copy one cell's level and requirements to similar cells
- Start from a template or a past project
Verify
Check the information LOD 300 should bring
Geometry still needs a reviewer's eye. The information you ask for alongside it can be checked automatically: link the model's elements to their tasks, and Verify checks every property, value and unit, element by element.
See how Verify works
Look closer
See LOD requirements set on a real scope
Free lessons
Learn to scope LOD free, one short lesson at a time
Level 1 lesson - Scope
Visualising BIM, LOD and information requirements
How the grid shows what every element needs at every milestone, so the whole team reads the same scope.
Level 1 lesson - structure
Defining your classification structure
The breakdown every element hangs on, so nothing falls between two lists.
Level 1 lesson - milestones
Defining information exchange milestones
The milestones across the top of your scope, where each level falls due.
Level 1 - free certificate
BIM Management Basics
Docs, Scope and Verify from the start, with a free certificate.
Free download
Plan your next scope from ours: a starter project and three free PDFs
Free download
Scope at Scale Survival Kit: a starter project and 3 PDFs
Everything to scope LOD and LOIN the way this page does: a starter scope with elements, milestones and requirements, and three free PDFs on combining LOD, LOIN and LOA, setting requirements and roles, and the detailed responsibility matrix.
- 1 starter project
- 3 PDFs
- Free
Scope starter project
A classified breakdown with milestones across the top, levels and requirements in the cells, ready for your own elements.
Open in Plannerly (opens in a new tab)
Free account, no card needed.
Read more
LOD, LOIN and LOA explained
Levels of development, LOD 100 to 500
What each LOD means, and how to use them on a project.
GuideLOD scales and ISO 19650
LOD numbers or plain language: the options, and when each one works.
GuideLOD, LOIN and LOA together
How the three fit together, and how IDS turns them into checks.
GuideLOIN in BIM, explained
Level of information need: geometry, information and documentation, with an example.
GuideScope LOD and LOIN at scale
The whole job, step by step, with a free starter project.
Use caseLOD 500: the as-built model
What field verified means, and what to ask for at handover.
GuideFrom the blog
Every post about LOD 300
EnglishUnderstanding LOD Scales and ISO 19650 Plain Language in BIM
Explore the ongoing LOD debate in the BIM community, where LOD scales face off against Level of Information Need! Uncover how Plannerly software backs both methods for varied project demands.
EnglishLevels Of Development (LODs): Achieving BIM Success With LODs 🚀
Understanding LOD 100-500 can be a game changer! 🔥 I will show you how to use LODs effectively to avoid over and under modeling. Plus, I'll teach you how to create a customized LOD matrix - the cherry on top! 🍒
Questions
LOD 300 questions, answered
What is LOD 300 in BIM?
A level of development where a model element is the specific system, object or assembly that's been designed, with its quantity, size, shape, location and orientation measurable from the model. It comes from the US AIA and BIMForum LOD frameworks, and it's usually asked for at detailed design. The BIMForum LOD Specification describes it element by element.
What's the difference between LOD 200 and LOD 300?
At LOD 200 an element is generic, with approximate size, shape and position: a door about here. At LOD 300 it's the door that's been designed, at its actual size and in its actual place, so other teams can coordinate against it and quantities can come from it.
What's the difference between LOD 300 and LOD 350?
LOD 350 adds the interfaces: how the element meets other systems, such as its supports, connections and openings. Teams usually ask for it where trades need to coordinate in detail, for example ceilings and building services.
Does the whole model need to be LOD 300?
No. A model is never one LOD: each element reaches its level at a milestone. Asking for LOD 300 throughout leads to over-modelling some things and arguments about others. Set the level per element and per milestone instead. How to build that matrix.
Is LOD 300 about geometry or information?
Mostly geometry, and how far it can be relied on. Recent BIMForum specifications describe geometry, with the information an element carries handled separately. Under ISO 19650 the level of information need covers geometry, information and documentation together. Plannerly lets you use either, or both.
How do I check that a model meets LOD 300?
The geometry still needs a person to review it, usually at the milestone's model review. The information you ask for alongside it can be checked automatically: in Plannerly, Verify checks every linked element's properties against your requirements, and you can export them as an IDS file for other checkers.
Plan LOD 300 element by element, not model by model
Start free, drag in a template and set the level, the information and an owner for every element at every milestone.
Free plan · No card · Everyone you invite joins free