BIM Level of Development Guide: Aligning Model Detail with Project Requirements.

Understanding LOD

Level of Development (LOD) is a project-control tool that helps a team agree what a model element represents, how reliable it is at a particular stage and which decisions or deliverables it can support. LOD is not simply a measure of visual detail.

Requirements should align with the project stage, model use, discipline responsibilities, information exchanges, coordination needs and construction or handover requirements. The interpretation should be confirmed through the appointment, client information requirements, contract and agreed project standards. Not every element needs the same LOD.

LOD should be managed as a live project control rather than a label applied once. When the scope, authoring team, delivery stage or information exchange changes, the element requirements and permitted reliance should be reviewed. This is particularly important where models are federated across several disciplines or handed from design teams to contractors and specialists.

Geometry and information

Geometry describes size, shape, position, orientation and interfaces. Information can include classification, specification, performance, asset data, manufacturer details, approval status and verification. These dimensions do not always develop at the same rate.

A visually detailed object may still be unsuitable for reliance if its information, responsibility or approval status is unclear. Imported manufacturer content should not be treated as verified only because it looks precise.

LOD 100–500

The following descriptions are a practical guide. Exact meanings may vary by client, project standard and appointment. The same coordinated building-services zone is used throughout the sequence so the change in development can be understood clearly.

LOD 100

Conceptual representation used to communicate broad massing, areas, system intent and approximate project requirements.

LOD 200

Generic systems and assemblies represented with approximate size, shape, location and orientation. It supports preliminary layouts without implying fabrication detail.

LOD 300

Project-specific elements developed with defined size, shape, location and orientation for agreed design and documentation purposes. Interfaces can be reviewed more reliably, but fabrication readiness is not automatic.

LOD 350

Developed elements show interfaces with adjacent systems, including openings, supports, access requirements and coordination clearances where required.

LOD 400

Fabrication or installation-level information developed within an agreed contractor, subcontractor, fabricator or specialist-supplier scope. It may include fittings, supports, connections, assembly information or spool segmentation.

LOD 500

Field-verified record information representing installed conditions and agreed asset data where included in the handover scope. Verification procedures and permitted uses should be agreed before modelling begins.

Selecting the correct LOD

Start with the decision the model must support, then define the minimum reliable development for that decision. Consider stage deliverables, coordination, quantities, construction planning, fabrication boundaries, operation and maintenance requirements and contractual obligations.

Model only to the level required to support the agreed project purpose. Over-modelling can increase file size, slow authoring, create false confidence, generate unnecessary coordination effort and exceed the agreed scope.

A useful requirement table identifies the element, the stage, the expected geometry, the information fields, the intended use and the responsible party. This makes it clear whether a model is being used for design review, spatial coordination, drawing production, quantity assessment, fabrication or handover.

LOD by project stage

Concept and feasibility studies commonly use massing and system intent. Schematic and developed design may need generic or defined elements for option selection, discipline interfaces and agreed documentation. Detailed design and construction support may require coordinated openings, supports and access zones. Fabrication and installation information normally sits within the relevant specialist scope. Record or handover information requires a separate agreement on verification and asset data.

These relationships are typical rather than automatic. A project may require different development levels for different packages, zones or elements at the same stage. The BEP and information requirements should state when an element becomes suitable for a particular use and who confirms that status.

Before an exchange, the team should also confirm whether the model is for information, review, coordination, construction support, fabrication or record purposes. A clear suitability status makes it easier for downstream users to understand what they may rely on and what still requires discipline review or specialist confirmation.

Discipline examples

Coordination and documentation

Higher reliability improves clash detection, access reviews, opening coordination, maintenance checks and construction sequencing. Increasing visual detail without reliable positioning, ownership or status does not improve coordination.

Model content should be checked against drawings, schedules, specifications, details and issue status. A detailed model does not automatically become contractual or fabrication information. Quantities are useful only when the relevant elements, classifications, parameters, exclusions, status and measurement rules are agreed.

Coordination reviews should focus on the interfaces that matter at the current stage: structural penetrations, ceiling zones, risers, plant-room access, fire and life-safety interfaces, drainage falls, marine utility corridors or other project-specific constraints. Issue records should identify the affected element, author, reviewer, status and next action so that a high-LOD view does not create false confidence.

For quantity extraction, confirm the model boundary and measurement rules before issuing numbers. A model can support a quantity assessment without being a complete bill of quantities, and a record model can contain verified asset information for selected maintainable elements rather than every object.

Responsibilities and acceptance

LOD does not transfer responsibility. The model author, reviewer, approval status and intended use must remain defined through the project appointment, responsibility matrix and information requirements.

Responsibility should also identify who supplies specialist content, who checks interfaces, who approves suitability for exchange and who verifies installed conditions. Coordination responsibility does not remove the originating discipline’s design responsibility, and a downloaded manufacturer family is not automatically an approved or installed product.

LOD acceptance checks

Accept an element only after checking geometry completeness, parameter completeness, coordination status, responsibility, exchange format, drawing consistency, review status, suitability or approval status and permitted use. An element should not be accepted only because it appears detailed.

Common mistakes

• One LOD for everything: requirements should be element- and purpose-specific.
• Visual detail equals reliability: confirm geometry, information, status and permitted use.
• LOD 400 without a specialist boundary: fabrication responsibility must be agreed.
• LOD 500 without verification: record information needs a defined survey or verification process.
• Ignoring non-graphical information: classification, specification and asset fields may be essential.
• Over-modelling too early: unnecessary detail can slow authoring and coordination.
• Unverified manufacturer content: downloaded geometry is not proof of approval or installation.
• Model and drawing mismatch: issue status and exchange dates should be aligned.

Practical checklist

• Agree model uses and stage requirements.
• Define element-specific geometry and information.
• Assign authors, reviewers and status.
• Confirm exchange dates, formats and coordination needs.
• Align drawings, schedules and quantities with model status.
• Define fabrication boundaries and handover requirements.
• Set review, acceptance and permitted-use criteria.

Conclusion

LOD is most useful when it aligns expectations, responsibilities and reliance. The right level is the one that supports an agreed project decision or deliverable with appropriate confidence—not the highest number available.

Related services and resources

See BIM & Digital Engineering, the Technical Resources library and our BIM Execution Plan Guide. To discuss a requirement, visit Start a Project.

Discuss Your BIM or Engineering Requirement

Trueform Engineering Consultants provides project-based BIM modelling, multidisciplinary coordination and technical engineering support for consultants and contractors. We would be pleased to review your project requirements and respond accordingly.

Discuss Your Project