Purpose before number
Choose LOD from what the model must do.
A starting recommendation for concept, documentation, coordination, fabrication and handover—followed by the scope question that matters next.
LOD decision helper
Start with why the model exists. Then define geometry, information and reliance separately.
Interfaces and connections become explicit enough to improve cross-discipline coordination.
Next scope questionDefine clash rules, zones, issue ownership and review cadence.
How to use the result
Turn the output into a better project question.
- 01
Choose the model’s primary intended use at the decision milestone.
- 02
Read the suggested LOD as a starting point, not a universal prescription.
- 03
Define geometry, information, tolerances, reliance and responsibility for each scoped element.
Check before relying
The inputs that change the answer.
- Different systems may need different development levels
- LOD and Level of Information should be defined separately
- Fabrication reliance needs trade input and approval routes
- Handover value depends on maintainable asset information, not maximum geometry
We review each tool against the decision it helps someone make, the clarity of its assumptions and how people use the result. Tell our team what would make this tool more useful.
Start with the deliverable
Need an element-by-element model specification?
Send the project stage, intended uses and required outputs. We can help translate them into a practical delivery scope.