In every complex project, uncertainty costs money. It shows up in change orders, rework, delays, and too often, disputes. The source is usually the same: different people working from different definitions of “done.” 

For almost two decades, Building Information Modelling (BIM) practice has relied heavily on the concepts of Level of Detail (LOD) and Level of Information (LOI) to define model maturity and information progression. While these constructs played an important role in the early standardisation of BIM deliverables, their limitations have become increasingly apparent. The industry’s gradual but decisive move toward Level of Information Need. It represents not merely a change in terminology, but a fundamental shift in how information is specified, procured, and valued across the asset lifecycle.

The Problem with LOD and LOI

LOD and LOI were conceived to provide clarity: to help teams understand how geometrically developed a model element should be, and how much non-graphical information should accompany it at a given project stage. In practice, however, these measures often became blunt instruments.

LOD definitions were frequently misinterpreted as modelling instructions rather than outcomes. Designers were asked to “model to LOD 400” without sufficient consideration of why that level of geometric refinement was required or who needed it. Similarly, LOI schedules tended to grow indiscriminately, with large quantities of data requested “just in case,” rather than in response to a defined decision-making requirement.

This approach resulted in several well-documented issues:

• Overproduction of information, increasing cost and programme risk.
• Misalignment between information producers and information users.
• Ambiguity in contractual responsibilities.
• A false sense of certainty that higher LOD equates to higher value.

As BIM adoption matured, it became clear that a more precise, purpose-driven framework was needed.

The Emergence of Level of Information Need

Level of Information Need, as introduced in the ISO 19650 suite of standards and later defined within ISO 7817-1, reframes the conversation entirely. Rather than asking how detailed a model should be, Level of Information Need asks a more fundamental question: what information is needed, by whom, for what purpose, and when?

Level of Information Need is defined across three dimensions:

• Geometric information – the shape, size, and spatial relationships required.
• Alphanumeric information – properties, classifications, and attributes.
• Documentation – associated drawings, schedules, specifications, or reports.

Crucially, Level of Information Need is not a scale or maturity ladder. It is a requirement, defined in response to a specific use case such as cost planning, coordination, regulatory approval, or asset management.

Why This Shift Matters

The move to Level of Information Need reflects a broader cultural shift in BIM: from model-centric thinking to information-centric thinking.

Under an Level of Information Need approach, information is no longer produced to satisfy an abstract standard, but to support a defined decision or process. This has several important implications:

1. Reduced Waste and Greater Efficiency
   By specifying only the information that is actually needed, teams avoid unnecessary modelling and data population. This reduces effort, lowers risk, and improves predictability—particularly at early project stages where uncertainty is highest.
2. Improved Alignment Across the Supply Chain
   Level of Information Need clarifies expectations between appointing parties and task teams. Information requirements become explicit, measurable, and verifiable, reducing disputes and rework.
3. Lifecycle-Oriented Information Management
   Unlike LOD, which is largely design- and construction-focused, Level of Information Need accommodates the needs of operators and asset managers. Information can be defined with end-use in mind, supporting a smoother transition from capital delivery to operational use.
4. Better Support for Digital Automation
   Purpose-driven information requirements are far better suited to automation, validation, and data exchange. Level of Information Need enables rule-based checking and aligns more naturally with digital twins, asset information models, and analytics platforms.

A Change in Behaviour, Not Just Standards

Despite its advantages, Level of Information Need is not a simple drop-in replacement for LOD and LOI. It demands a more disciplined approach to information planning and a higher level of engagement from clients and asset owners.

Defining Level of Information Need effectively requires:

• Clear articulation of information uses and decision points.
• Early involvement of downstream stakeholders.
• A willingness to challenge legacy assumptions about “model completeness.”
• Greater collaboration between information managers, designers, and asset operators.

In this sense, Level of Information Need exposes organisational maturity. Where LOD could be applied mechanically, Level of Information Need requires intent.

Final Thought

The industry’s move away from Level of Detail and Level of Information toward Level of Information Need marks an important inflection point in BIM maturity. It acknowledges that more information is not inherently better, and that value lies in relevance, timing, and purpose.

As projects become more complex and digital delivery more integrated, the success of BIM will increasingly depend on the quality of information decisions made upstream. Level of Information Need provides the framework to make those decisions explicit, defensible, and aligned with real-world outcomes.

Ultimately, this shift is less about standards and more about mindset: moving from asking “How much can we model?” to “What information genuinely creates value?”