Level of information need is about fitness for purpose. It asks how much geometry, alphanumeric information, and documentation is needed for a specific exchange or decision. The goal is not to make every model more detailed. The goal is to make information useful.
Too little information creates uncertainty. The receiving team cannot coordinate, price, install, maintain, approve, or operate with confidence. Too much information creates waste. People model or enter data that nobody checks, uses, or maintains.
A useful level of information need should say what purpose the information supports. A concept-stage massing model, a coordinated design model, a fabrication model, a commissioning record, and an asset handover package need different information.
Geometry is only one part of the picture. Some decisions need shape, size, position, and clearance. Other decisions need properties, classification, system relationships, warranty data, serial numbers, maintenance intervals, or links to documents. Some exchanges need almost no geometry but very reliable asset data.
The level should be defined per object type, system, stage, use case, and exchange where practical. A blanket requirement for an entire model often causes confusion because not every element has the same importance at every phase.
Good definitions are checkable. Instead of saying a model must be detailed, define the objects, properties, tolerances, classifications, documents, or acceptance checks needed for that exchange. This helps authors produce the right information and helps reviewers avoid subjective arguments.
The BEP should explain how the level of information need is agreed, recorded, checked, and changed. It should also explain what happens when a requirement is not yet known. Unknowns should be visible rather than hidden inside assumptions.
Related: Information Requirements in BIM, BIM Execution Plan, Document Control Basics.