Skip to content
WorkStudio Help Home
Knowledge Hub

BIM Level of Information Need Explained

A plain-language guide to defining the right amount of geometry, data, and documentation for each BIM purpose.

Open Knowledge Hub ↗

Simple building model shown in stepped levels of information detail.

Information only — not legal advice.

Level of information need is a way to specify the information required for a particular purpose at a particular delivery point. It helps a team avoid both missing essential information and spending effort on detail that nobody needs.

The practical question is: “What must the receiving person be able to do with this delivery?” The answer should guide geometry, alphanumeric information and documentation together.

Begin with purpose and timing

A model used to reserve space for equipment has different needs from a package used to fabricate connections or maintain an installed asset. Identify the purpose, milestone, responsible parties and objects before deciding how much information to request.

A single label such as “LOD 300” is insufficient unless the adopted specification defines its meaning and scope. Different conventions use similar terms differently. Agree the actual requirements and acceptance criteria rather than assuming a familiar number means the same thing to everyone.

Example: one pump, three exchanges

For early spatial planning, a fictional team needs the pump's approximate envelope, connection zones, weight allowance and an explicit indication of provisional information. It does not yet need the installed serial number.

For coordinated technical design, the team needs the selected equipment's relevant dimensions, connection positions and maintenance clearances, together with performance data and the supporting specification. The exact content follows the design responsibility and intended use.

For operational handover, the owner needs verified installed identity, location, commissioning evidence and maintenance documentation. Modelling every bolt may contribute little to that purpose, while a missing identifier can make the asset record unusable.

These are illustrative exchanges, not universal stage requirements for every pump or project.

Describe the information explicitly

For geometry, state which aspects matter: size, position, shape, orientation, interfaces or clearance zones, and any relevant accuracy or representation limits. For data, define properties, units, permitted values and classifications. For documents, identify the required evidence and how it connects to objects or systems.

State exclusions as well. If small fittings are outside the coordination model's scope, the reviewer needs to know that before interpreting a clash report or quantity take-off.

Keep “unknown” visible

Do not invent precise values to make a model appear complete. Define how provisional, unavailable and not-applicable information is represented, who resolves it and when it becomes due. Use agreed states rather than mixing blanks, zeroes and arbitrary placeholder text.

An early-stage estimate may be perfectly appropriate when its basis and limitations are clear. It becomes misleading when exported as though it were a verified installed value.

Check the delivery against its purpose

Review a representative object and ask the receiving user to perform the intended task. Can they assess access, make the decision or find the supporting evidence? Automated property checks help with suitable requirements, but do not establish all geometric or engineering conclusions.

ISO 7817-1:2024 sets out concepts and principles for level of information need. The pump example and checklist here are practical illustrations, not a reproduction of its provisions. Continue with information requirements and BIM model uses.

Important information

This article provides general information and does not constitute legal advice or replace a qualified professional's assessment of your circumstances. Laws, official guidance, standards and product features can change. Check current primary sources and the requirements applicable to your jurisdiction, contract and project before making decisions. Examples illustrate the discussion; they are not official rulings or instructions for a particular case. For legal decisions, consult a qualified lawyer; for technical or other specialist matters, consult the responsible professional.

Enable JavaScript to use reading progress and usefulness ratings.