If you've worked on a BIM project, you've likely encountered the term "LOD" or "Level of Detail." But what does it actually mean, and more importantly, how much detail does your project really need? Getting this specification right from the outset can save significant time, cost, and confusion during design, construction, and handover phases.
Understanding LOD requirements is essential for engineers, project managers, and anyone procuring BIM services in the UK. This guide explains the LOD framework and helps you determine the appropriate level for your project stage and discipline.
Level of Detail, sometimes called Level of Development, is a standardised framework that defines how much geometric and non-geometric information a BIM element contains at various project stages. The system helps all stakeholders understand what can be relied upon in a model at any given point.
The LOD specification was developed by the American Institute of Architects (AIA) and is now widely adopted in the UK construction industry. It ranges from LOD 100 (conceptual representation) through to LOD 500 (as-built verification), with incremental steps at LOD 200, 300, and 400.
It's important to note that LOD isn't just about visual detail—it also encompasses the reliability of information. A highly detailed-looking element isn't necessarily a high LOD if the information hasn't been verified or specified properly.
At LOD 100, model elements are represented symbolically or generically. Think of this as placeholder geometry—a box representing a plant room, or a simple volume indicating where a piece of equipment will eventually sit.
This level is appropriate during feasibility studies and early concept design when you're establishing spatial requirements, approximate quantities, and overall project massing. No specific dimensions or performance characteristics are specified at this stage.
LOD 200 introduces approximate sizes, shapes, locations, and orientations. Elements are modelled as generic systems or assemblies with approximate quantities and basic performance criteria.
For mechanical services, this might mean showing an air handling unit as a correctly sized box in the right location, but without specific manufacturer data or detailed connections. For structural elements, you'd see beam and column locations with approximate sizes, but not final sections or connection details.
This level suits developed design stages where coordination is beginning and spatial conflicts need identifying, but final specifications haven't been locked down.
At LOD 300, elements are defined with precise geometry, specific dimensions, exact locations, and orientations. This is where generic placeholders become specific systems with sufficient detail for coordination and fabrication preparation.
For M&E contractors, LOD 300 models include specific equipment makes and models, accurate ductwork and pipework routing with correct sizes, and interface points for other trades. This level enables proper clash detection and design coordination.
Most UK construction projects require LOD 300 for coordination and construction issue. It provides enough detail for contractors to understand what's required without the time investment of full fabrication-level detail where it isn't needed.
LOD 400 takes precision further to include fabrication, assembly, and installation detail. Elements are modelled with complete information including connections, supports, fixings, penetrations, and any assemblies needed for construction.
This level is essential for fabricators producing shop drawings—steel detailers creating connection details, or ductwork manufacturers preparing cut sheets. The model contains sufficient detail that fabrication can proceed directly from it.
Not every element on every project needs LOD 400. It's typically specified for complex prefabricated elements, specialist systems, or where design-for-manufacture-and-assembly (DfMA) approaches are being used.
LOD 500 represents verified as-built conditions. Elements are modelled as actually constructed, with field verification of size, location, and orientation. This creates the as-built record for facilities management and future modifications.
Achieving true LOD 500 requires site surveys, often using laser scanning technology to capture what was actually built rather than what was designed. The resulting point cloud data is then used to verify or update the BIM model.
This level supports COBie data delivery at handover and provides the foundation for digital twins and ongoing facilities management systems.
Different elements in the same project can—and often should—have different LOD levels depending on design stage, complexity, and procurement route. Your BIM Execution Plan (BEP) should clearly define LOD requirements for each discipline and project stage.
Consider what decisions need to be made at each stage and what information is required to make them confidently. Avoid over-specifying LOD requirements, as creating unnecessary detail wastes time and budget without adding value.
For UK projects following the PAS 1192 framework (now superseded by the ISO 19650 series), LOD specifications should align with RIBA work stages and information exchange milestones defined in your project protocols.
When outsourcing BIM modelling work, clearly communicating LOD requirements is essential. Ambiguity about expected detail levels is one of the most common causes of rework and dissatisfaction.
Experienced BIM providers like Outsource CAD work with UK engineering firms to establish appropriate LOD specifications at tender stage, ensuring deliverables match project requirements without unnecessary over-modelling. This approach balances detail with efficiency and keeps projects on programme.
Providing reference examples, template elements, or clearly marked-up models helps ensure everyone shares the same understanding of what each LOD level means in your specific context.
Understanding LOD specifications is fundamental to successful BIM delivery. By clearly defining what level of detail is required at each project stage, for each discipline and element type, you avoid wasted effort whilst ensuring the model supports informed decision-making.
Remember that higher LOD isn't always better—it's about right-sizing the information to match project needs. Specifying this correctly in your BEP and procurement documents sets clear expectations and helps your internal teams and external partners deliver efficiently.