The three checks
Three checks. One score each, never averaged.
Each check answers one question about the data in a trade model. Each point to correct says how many elements, which property, and which document or rule pack asks for it.
Check 1
Project data
Does the model carry the data your project asks for? The rules come from your own documents and from rule packs.
- Your documentsThe BIM plan, the owner standard, a specification section, a schedule. You approve each requirement before it runs.
- Rule packsIDS 1.0 rule sets, the US owner requirements pack and model health checks.
- What it looks atNames, systems, levels, classification codes, type marks: the values a coordinator would check by hand.
- 21 duct fittings have no classification codeAsked by the owner asset data standard, 2.3New
- 18 diffusers and grilles have no levelAsked by the project BIM plan, 4.4Still open
- 12 ducts have no system nameAsked by the project BIM plan, 4.2Still open
- 3 fire dampers have no type markAsked by the project BIM plan, 4.6Still open
Check 2
Code data
Does the model carry the data a code reviewer will look for, and do simple values agree? Each rule cites the standard and the section.
- Rule packsIBC 2021, the 2010 ADA Standards, NFPA 101 and NFPA 13. Data rules only.
- What it looks atFire ratings, door widths, occupancy, sprinkler temperature ratings: present, filled and consistent.
- Example, mechanical version 4The fire dampers in the ducts carry a fire rating (IBC 2021, 717.3): met. No sprinklers in this model, so the NFPA 13 rules do not apply.

Check 3
Handover
Is the asset data complete enough to hand the building over? What the owner's facility team needs at the end, element by element.
- Rule packsCOBie (NBIMS-US), your owner standard and your equipment schedules.
- What it looks atAsset tag, manufacturer, model number, warranty, classification and spaces.
- 9 VAV boxes have no model numberAsked by the VAV box schedule, sheet M-601New
- 4 air handling units have no manufacturerAsked by the owner asset data standard, 3.1Still open
- Equipment has a serial number fieldOwner asset data standard, 3.4Met
Reading a result
Every requirement ends in one of three words
A rule that does not apply is left out of the score, never counted against the model.
Met
Every element the rule reads carries the value it needs.
To correct
Some elements miss the value. The point says how many, and who asks for it.
Does not apply
The model has no element the rule reads. It is shown, and left out of the score.
What a check does not do
Said plainly, so you can trust the rest.
- It never changes your model. The trade makes the change in its own tool.
- It does not detect clashes. Clash detection compares geometry. Keep your coordination tool for that.
- It does not guess. A requirement that needs geometry, such as a clearance or a slope, goes to "Cannot be checked automatically".
- It is not a code approval. A check of model data, not a code approval.
Photos: Unsplash · Adrien Olichon
See the three scores on your own model.
Drop a model, or use the sample. No account to try it.