LOIN Explained: Defining the Level of Information Need
Level of Information Need (LOIN) defines exactly what information is required at each stage of a project under ISO 19650 — and it addresses a common challenge on construction projects across the Middle East.
A contractor asks, “How detailed should the asset information be?”
The project team responds, “As detailed as possible.”
The contractor delivers everything — and nothing useful.
This is the problem that LOIN (Level of Information Need) is designed to solve.
What Is LOIN?
LOIN defines the required level of detail, dimensionality, and documentation for each piece of information at each project stage. It answers a simple but critical question:
What level of information do we actually need to make informed decisions?
Not what is possible to provide — but what is genuinely required.
The LOIN Framework
LOIN operates across multiple dimensions to ensure information is fit for purpose:
- Geometrical information: How detailed must the 3D model be? Are exact dimensions required, or are approximate volumes sufficient?
- Alphanumerical information: What specifications, properties, and attributes must be captured to support decision-making and operations?
- Documentation: What supporting documents are required — such as O&M manuals, warranty certificates, or commissioning reports?
Each dimension must be defined deliberately, not assumed.
The Stage-Based Approach
LOIN is not static. It evolves as the project progresses:
- Design stage: Sufficient detail to support design decisions and reliable cost estimates.
- Construction stage: Sufficient detail to coordinate, build, and commission the works effectively.
- Handover / operational readiness stage: Sufficient detail to operate, maintain, and manage the asset throughout its lifecycle.
Defining LOIN at each stage prevents both under-delivery and unnecessary over-delivery.
Why This Matters
Without clearly defined Level of Information Need, contractors face two common problems:
- Over-delivery: Time and money are spent capturing unnecessary detail that adds cost but no operational value.
- Under-delivery: Critical information is missing because requirements were not specific enough.
Both outcomes create risk. Over-delivery wastes resources. Under-delivery creates operational gaps that persist long after handover.
The Middle East Challenge
Across the region, many projects specify vague requirements such as “Provide complete asset information.” But complete for what purpose? At what level of detail? And at which project stage?
This ambiguity leads to contractor confusion, inconsistent deliverables, and ultimately, incomplete or unusable operational data.
The Solution
Define Level of Information Need (LOIN) clearly for each asset type at each stage of the project. Be specific. Be unambiguous. Align LOIN with actual operational requirements — not theoretical possibilities.
When contractors know exactly what is required, they can price it accurately and deliver it completely.
Is your project’s LOIN clearly defined? Or are you relying on contractors to interpret what “enough” looks like?
Review your project’s LOIN requirements with an operational lens.
Book a consultation