BIM capability
Structured LOD and LOIN milestone frameworks that define what geometry, data and documentation must exist at each project stage — not as completion percentages, but as verifiable element-level requirements.
Level of Development and Level of Information Need management defines the geometric fidelity, alphanumeric content and documentation expected from modelled elements at each project milestone. These frameworks translate employer information requirements and BIM execution plan objectives into auditable, element-specific targets that production teams can implement and verify.
LOD describes the reliability and detail of model element representation — what can be relied upon for coordination, procurement or construction at a given stage. LOIN, per ISO 19650, extends this with structured definitions of geometric and alphanumeric information need aligned to project delivery stages and appointment responsibilities.
Milestone management is not a percentage-based progress metric. A model may be 80% complete by element count yet fail milestone acceptance if critical elements do not meet their LOD or LOIN targets. Acceptance is verified through matrix-based spot checks, automated audits and formal milestone review gates.
Each milestone defines a subset of element categories with explicit geometry rules, parameter requirements and associated documentation. Verification combines sampling protocols, responsibility assignment and documented acceptance criteria signed off by the BIM manager and design lead before CDE issue.
Clients and contractors increasingly specify LOD milestones in employer information requirements to manage risk at procurement and construction interfaces. Without a managed LOD and LOIN framework, teams either over-model prematurely — wasting effort — or under-model — creating coordination failures and procurement ambiguity.
BIM coordinators maintain the LOD matrix as a living document updated when design scope, procurement strategy or construction phasing changes. The matrix links to exchange information requirements, model progression schedules and deliverable registers so all parties share a single definition of done at each stage.
LOD 500 represents as-built record information verified against field conditions; it does not constitute a digital twin. Digital twin readiness requires additional operational data structures, sensor integration and governance beyond as-built model fidelity. This distinction is maintained throughout milestone planning and handover scoping.
Element category matrix mapping LOD 200–500 requirements to project stages and appointments.
Structured geometric and alphanumeric information need aligned to exchange information requirements.
Review procedures, responsible parties and sign-off authority for each milestone acceptance.
Timeline linking LOD targets to design stages, procurement packages and construction phases.
Mapping employer information requirements to actionable element-level model targets.
Documented elements outside current milestone scope or deferred to later stages.
Statistical or risk-based sampling method for milestone compliance assessment.
Structured reporting of LOD gaps with remediation plans and re-verification schedule.
Formal process for matrix amendments when scope or procurement strategy changes.
Consistent milestone definitions across architectural, structural and MEP appointments.
As-built and record information targets for operational handover without digital twin overclaim.
Team orientation on LOD definitions, common misinterpretations and verification methods.
Extract LOD and information requirements from employer documents and BIM execution plan.
Develop element category LOD matrix with geometry, data and documentation columns per milestone.
Review matrix with design leads, contractors and client representatives for alignment.
Assign ISO 19650 LOIN codes to matrix rows linking geometric and alphanumeric need.
Embed LOD targets in master and task information delivery plans with issue dates.
Distribute matrix excerpts and worked examples to production modelling teams.
Execute sampling protocol, document findings and issue compliance report at each gate.
Track remediation of LOD gaps to re-verification and gate sign-off.
Update matrix through change control when scope, phasing or appointments change.
All in-scope element categories defined with geometry, alphanumeric and documentation requirements.
Each milestone has distinct, non-overlapping acceptance criteria without ambiguous interim states.
Progress tracking uses element-level compliance, not project-wide percentage completion metrics.
ISO 19650 LOIN references applied to matrix rows where contract requires formal LOIN framework.
Each matrix row assigns authoring and verification responsibility to named appointments.
Deferred or excluded elements listed with rationale and target milestone for inclusion.
Verification samples cover high-risk categories, interfaces and procurement-critical elements.
Findings classified as critical, major or minor with defined remediation timelines.
As-built targets limited to field-verified record information without digital twin equivalence claims.
Matrix rows linked to MIDP, TIDP and deliverable register entries without orphan references.
Matrix revisions tracked in CDE with change log and approval record.
Briefing attendance or competency acknowledgement recorded for production team members.
Air handling units
Ductwork distribution
Pipework branches
Modular plant skids
Installed switchboards
Facade penetration sleeves
| Milestone | Element | Purpose | Responsible | Geometric | Alphanumeric | Documentation | LOD / LOIN | Control | Acceptance |
|---|---|---|---|---|---|---|---|---|---|
| LOD 200 — concept | Air handling units | Spatial planning and capacity confirmation | Mechanical design lead | Overall dimensions and approximate location | Tag, nominal capacity, system type | Schematic layout drawing | LOIN 1–2 — brief to schematic | Design lead visual review | Concept stage gate approval |
| LOD 300 — coordination | Ductwork distribution | Multidisciplinary clash detection | Mechanical BIM author | Sized routes with insulation and hangers | Size, material, insulation, system assignment | Coordination plans and sections | LOIN 3 — coordination geometry | Matrix spot-check — 10% sample | Coordination milestone sign-off |
| LOD 350 — construction documentation | Pipework branches | Construction issue and procurement | Plumbing BIM author | Exact routing with fittings and slope | Size, material, insulation, valve tags | Construction issue drawings | LOIN 4 — detailed geometry | Parameter and geometry audit | Construction issue gate |
| LOD 400 — fabrication | Modular plant skids | Shop drawing and prefabrication | MEP BIM coordinator | Fabrication detail with connections | Manufacturer, model, connection data | Shop drawing package | LOIN 4–5 — fabrication to record | Full category verification | Fabrication release approval |
| LOD 500 — as-built record | Installed switchboards | Asset register and FM handover | Electrical BIM lead | Field-verified position and connections | Serial number, warranty, maintenance schedule | As-built record drawings | LOIN 5 — record information | Site survey comparison | Handover information sign-off |
| Stage transition | Facade penetration sleeves | Interface coordination between disciplines | MEP BIM coordinator | Exact sleeve size and position | Fire rating, waterproofing detail reference | Interface coordination sheet | LOIN 3 at design development | Interface checklist review | Multidisciplinary interface sign-off |
LOD and LOIN targets are set in consultation with engineering design leads so that model fidelity supports — not replaces — calculation outputs and specification development. HVAC equipment at LOD 300 must carry sufficient data for coordination without demanding fabrication detail that depends on procurement outcomes not yet determined.
Structural and architectural LOD milestones are synchronised at interface elements: penetrations, openings, ceiling voids and plant room envelopes. Misaligned milestones between disciplines create false coordination confidence where one model is detailed and the linked model remains schematic.
Procurement packaging influences LOD staging — elements in early procurement packages advance to fabrication LOD earlier than surrounding context. The matrix accommodates phased LOD progression within a single project stage when construction sequencing demands it.
AIA LOD Specification
ISO 19650-1
ISO 19650-3
BS EN 17412-1
NBS BIM Toolkit
PAS 1192-2
ISO 12006-2
buildingSMART
Client EIR
BEP
| Standard / Reference | Full title | Organization | Application area | Relevance | Edition status |
|---|---|---|---|---|---|
| AIA LOD Specification | Level of Development Specification | AIA | LOD element definitions | Primary reference for US and international LOD 100–500 element requirements. | Published edition — confirm at project start |
| ISO 19650-1 | Organization and digitization of information about buildings and civil engineering works — Part 1: Concepts and principles | ISO | LOIN framework | Level of Information Need concepts and information management principles. | Published — confirm edition at project start |
| ISO 19650-3 | Organization and digitization of information about buildings and civil engineering works — Part 3: Operational phase | ISO | Operational information need | Handover and operational phase information requirements. | Published — confirm edition at project start |
| BS EN 17412-1 | Building Information Modelling — Level of Information Need — Part 1: Concepts and principles | CEN | European LOIN standard | Formal LOIN methodology for European jurisdiction projects. | Published — confirm edition at project start |
| NBS BIM Toolkit | Digital Plan of Work and Uniclass 2015 | NBS | UK project stages | Stage-specific deliverable and information need definitions. | Published — confirm edition at project start |
| PAS 1192-2 | Specification for information management for the capital/delivery phase of construction projects using BIM | BSI | Legacy UK BIM | Reference where contract specifies PAS-based information delivery. | Published (2013) — superseded by ISO 19650 |
| ISO 12006-2 | Building construction — Organization of information about construction works — Part 2: Framework for classification | ISO | Classification | Element categorisation underpinning LOD matrix structure. | Published — confirm edition at project start |
| buildingSMART | openBIM LOIN and IDM documentation | buildingSMART | openBIM information need | Technical reference for information delivery mapping. | buildingSMART specification |
| Client EIR | Employer's Information Requirements | Project-specific | Project information specification | Primary source for milestone information requirements on each project. | Project issue — confirm at appointment |
| BEP | BIM Execution Plan | Project-specific | Project delivery planning | LOD matrix, progression schedule and verification protocol defined per project. | Project issue — confirm at appointment |
Applicable standards depend on the project jurisdiction, information requirements, contract documents, delivery method and authority requirements. The adopted editions shall be confirmed at project commencement.
Element category matrix with geometry, data and documentation requirements per milestone.
Timeline mapping LOD targets to project stages and CDE issue dates.
Review procedures, sampling method and sign-off authority documentation.
Per-milestone audit forms for geometry, parameters and documentation checks.
Issued after each gate with findings, non-conformances and acceptance status.
Tracked LOD gaps with remediation plans and re-verification dates.
Elements outside current scope with rationale and target milestone.
Worked examples and common misinterpretation brief for production teams.
Revision history with approved amendments and effective dates.
Attendance or acknowledgement of LOD framework orientation sessions.
Independent BIM manager review of LOD matrix before stakeholder workshop.
Client, contractor and design lead approval of matrix at project outset.
Verification samples selected per defined risk-based method, not ad hoc.
Non-conformances classified using agreed severity definitions across all milestones.
Open non-conformances tracked to closure with re-verification evidence.
Only authorised signatories approve milestone acceptance in CDE.
Interface element LOD targets consistent across linked discipline matrices.
As-built scope verified as record information without digital twin equivalence claims.
Current matrix revision clearly identified in CDE with superseded versions archived.
Delivery plan entries match matrix milestones without orphan deliverables.
Milestones passing gate review without critical non-conformances.
>= 85%
LOD gaps remediated within agreed timeline.
>= 95% on schedule
Days from change request to approved matrix revision.
<= 5 working days
Percentage of high-risk categories sampled at each gate.
100% of tier-1 categories
Production team members acknowledging LOD framework briefing.
100% before authoring
No. LOD defines the reliability and detail of specific element representations at a milestone. A project cannot be described as 70% LOD 300; instead, individual element categories are verified against their LOD targets.
LOD specifies element geometric and information development stages, commonly using the AIA framework. LOIN, per ISO 19650, formally structures geometric and alphanumeric information need for exchange at project stages. Projects may use both, mapped in a unified matrix.
No. LOD 500 represents as-built record information verified against field conditions. A digital twin requires operational data governance, live system integration and asset lifecycle management beyond as-built model fidelity.
The BIM execution plan defines gate authority — typically the BIM manager verifies compliance and the design lead or client representative signs off for CDE issue.
Yes, through formal change control when scope, procurement or phasing changes. Matrix amendments are versioned in the CDE with stakeholder notification.
Verification combines risk-based element sampling, automated parameter audits and documentation checks against the matrix. Results are recorded in milestone compliance reports.
Let's plan the BIM scope, information requirements, delivery standards and coordination process in line with your project lifecycle.