MODEL STANDARD REVIEW · Workflow idea
For supported building project files you are authorized to inspect, compare extracted data with approved spreadsheet rules and prepare an error summary and quantity tables. Automated checks can miss design intent or flag acceptable exceptions, so keep the rule version and source file visible, protect project data, and treat findings as review prompts. An engineer or project owner must resolve exceptions and approve any changes before the model is revised or delivered.
01 / The starting point
A supported project file and a current, owner-approved standards sheet
“Identify possible naming, structure, attribute, or completeness issues without changing the project file.”
02 / The work
Helps project teams compare building model data with documented standards and review possible issues.
Check file ownership, supported format, and which project standards apply.
Record the rule sheet version and who authorized it.
Keep each reported issue linked to its source field and applicable rule.
Check whether results reflect project intent, units, and accepted deviations.
Require an engineer or project owner to decide how each finding is handled.
03 / The result
A findings report and quantity tables linked to source and rule versions.
Reviews & approvals · Example outcome
A findings report and quantity tables linked to source and rule versions.
Automated checks are not an engineering certification. Validate rules, units, and exceptions, keep the original unchanged, and require a qualified reviewer to approve any correction or compliance decision.
04 / Make it yours
A few choices shape the work around your team.
Document rule owners, scope, field definitions, and review dates.
Preserve source files and keep reports in approved project storage.
Route uncertain or safety-relevant findings to qualified staff.
Name who signs off on corrections and any compliance statements.