Information requirements
Information requirements are lists of what must be delivered, for a decision someone has to make. They are not a contents page for a model.
Four names, four audiences
- Organisational — what the appointing organisation needs across its projects. Asset registers, space data, carbon fields.
- Asset — what operators need after handover so they can maintain the thing. Valve tags, warranty dates, not presentation views.
- Project — what this project needs at each stage to make a decision. Planning geometry is not construction geometry.
- Exchange — the tender or appointment document that tells an appointed party which of the above they must produce, in which format, by when.
A worked test
If a requirement says “LOD 300 architecture model”, it has not said which rooms need areas, whether door fire ratings are mandatory, or who accepts the container. Rewrite it as a decision: at Stage 3 the cost plan needs gross internal area by function, from a Shared model, accepted by the lead appointed party.
Templates exist from the UK BIM Framework. Use those for a live appointment. This page only sorts the words.
How to use the figure in a review
Quote the inputs with the result. A pad pressure without the load and the area cannot be reviewed. A peak flow without the coefficient, the intensity and the area cannot be reviewed. A gear ratio without the tooth counts cannot be reviewed. The page is the screen. The project document is the limit.
Do not paste the result into a published container as design information. Published means the project state, not this site. A preliminary number stays preliminary until the appointed party issues it under the appointment.
Last checked 3 October 2026. Official requirements stay in ISO 19650 and the UK BIM Framework. This is original guidance.