IFC delivery and ISO 19650
Turning model quality into an agreed routine: ISO 19650 checks, BEP clauses, acceptance criteria and what to hand over with a model.
All 4 guides on this topic
"This model is unusable" versus "the model is fine" is an argument with no ending. A one-page acceptance table, agreed before the first delivery, turns it into a five-minute check with a documented outcome.
Most BEPs say models must be "of suitable quality" and nothing else — which is why quality arguments never end. Four short clauses, written to be pasted, that turn an opinion into a testable condition.
A delivery is a claim: this model is fit for this purpose at this revision. Evidence is what turns the claim into something the receiver can check without repeating your work — and what stops the same argument happening twice.
ISO 19650 specifies information requirements for BIM deliveries. Here is what that means for your IFC files — from filename conventions to embedded project metadata — and how to verify compliance before submission.
Tools for this topic
- IFC Validator — 44 quality rules and a Health Score, in your browser — the file is never uploaded.
- IFC Viewer — Open IFC files in the browser: properties, sections, point clouds, map context.
- Viewer SDK — Embed the viewer in your CDE or app and drive it with postMessage.