LOD 200, 300, and 400 describe different expectations for the development and reliability of modeled elements. They should be assigned by element and project use, not applied as one vague label to an entire model.
A useful BIM scope identifies what will be modeled, which LOD applies at each milestone, what information accompanies the geometry, what others may rely on, and who reviews and approves the result.
Start with the intended model use
Ask why the model is being produced. Design communication, coordination, quantity review, documentation, visualization, fabrication, and asset handoff can require different elements and information. A higher number does not automatically make a model better for every purpose.
BIMForum publishes the Level of Development Specification to help project teams define and communicate model-element development. The specification is a planning and communication reference. The project agreement, BIM execution plan, discipline standards, and responsible professionals still control the actual deliverable.
Compare the levels carefully
The BIMForum 2025 LOD Specification Part I gives detailed definitions and element examples. In simplified scoping terms:
| Level | Model-element expectation | Scope question |
|---|---|---|
| LOD 200 | Approximate or generalized element representation with information suitable for the defined use | Which quantities, size, shape, location, orientation, or nongeometric information may remain approximate? |
| LOD 300 | Specific element geometry and information sufficient for the reliance described by the specification and project plan | Which dimensions, location, orientation, and attributes must be modeled from approved design information? |
| LOD 400 | Detail and information sufficient for fabrication, assembly, or installation for the defined element and responsible party | Who supplies and approves fabrication information, and which trade or manufacturer standards govern it? |
This summary does not replace the specification. Element tables, project requirements, and contracts provide the detail needed for the project scope.
Assign LOD by element
A model can contain walls at one LOD, equipment at another, and placeholder objects that remain below either level. Different milestones may advance selected elements while others remain unchanged.
Create an element matrix with the discipline, element group, current source, required LOD, milestone, model author, responsible reviewer, permitted use, and required information. This prevents a whole-model label from hiding uneven expectations.
For example, a coordination milestone may require reliable locations for major equipment and distribution routes while decorative objects remain generalized. The matrix should state that difference rather than calling the complete file "LOD 300."
Separate geometry from information
A detailed-looking object may still lack required identity, classification, performance, asset, or scheduling information. A simple shape may carry the information needed for an approved use. Review geometry and nongeometric information against the element's requirement.
The brief can identify parameters, classification, naming, units, phase, system, material, status, and other data that the receiving workflow expects. It should also say which fields come from approved client sources and which party resolves conflicts.
Do not ask a production team to infer technical values from appearance. Missing design or manufacturer information should become an issue for the responsible discipline, not an invented model property.
Define coordinates, files, and exchanges
LOD alone does not establish the BIM workflow. Record authoring software and version, coordinates, levels, grids, segmentation, worksets, linked models, family standards, naming, common data environment, exchange formats, issue-management method, and review milestones.
If a native file and an exchange file are both required, state which is authoritative for each receiving use. Record export settings and known limitations. A visually similar export may not retain every property or relationship used in the authoring model.
Plan coordination and issue ownership
A model review can identify apparent clashes, missing inputs, inconsistent coordinates, or elements that do not meet the agreed requirement. The issue record should identify the model version, viewpoints or element IDs, affected disciplines, due owner, status, and resolution authority.
The modeler can update geometry after approved direction. Responsible professionals and trades decide acceptable technical resolutions. A clash-free report does not prove code compliance, constructability, or design approval.
Scope LOD 400 with the responsible fabricator
LOD 400 is tied to fabrication, assembly, or installation detail for the defined element. Confirm who authors that information, which manufacturer or trade standards apply, what is approved design input, and who accepts the result.
Do not assume that advancing an architectural or engineering design model to LOD 400 is a routine detail increase. Fabrication workflows may require specialized content, connections, tolerances, product data, and shop-level responsibility outside the production modeler's assignment.
Write the handoff around permitted use
The final package should identify the model version, element matrix, source references, completed checks, unresolved issues, exchange files, and limitations on use. Receiving teams need to know what they can rely on and what remains approximate or pending.
Brownsofts provides BIM Modeling for LOD 200 to 400 as remote production support under the client's approved sources and review structure. Brownsofts is not the architect or engineer of record. The client's licensed or otherwise qualified professionals retain design, calculations, code interpretation, professional approval, sealing, fabrication authority, and construction responsibility where applicable.
The element matrix ties each modeled element to a purpose, milestone, source, reviewer, and usable reliability level.