Revit has no idea what your practice's standards are. Canon does — it watches the model as you work, catches drift the moment it happens, and turns compliance into a number the team can trust.
Standards live in a document and a good intention, so drift stays invisible until it's expensive. Canon puts the rule book where the work happens.
Canon has two halves. The BIM Manager inputs the standard; the whole team gets the output — live, as they model. Here is the whole loop, top to bottom.
Tap Input or Output to isolate a half — the other collapses.
The first time Canon opens, the manager turns the practice's standards into live rules — from a starter pack, drafted by AI from the BEP, or written by hand.
A fresh project isn't an empty rule set. From Starter packs the manager applies a curated set in one click — appended, duplicates skipped, editable afterwards — and unless Add disabled, for review is unticked, its rules arrive switched off, to be read before they notify anybody. Every pack is real, built from Canon's own checks — eight of them, reaching as far as window data, type-name grammars, wall constraints and project decisions.
Every office has a BEP, and it is prose: forty pages of “walls shall be placed on the ARC worksets”, written for humans. Turning that into rules is the job nobody has time for, which is why most standards live in a PDF nobody opens. With an AI provider connected in Synapse, paste the document — or load the PDF straight in — and BIMIO reads it and drafts Canon rules from it. They arrive as drafts, in a list you review one by one, and they land SWITCHED OFF: nothing starts governing your model because a machine read a paragraph. You turn on the ones you meant.
Each rule carries its id, a severity, the categories it watches and an Active box; funnels on Severity, Name and Categories narrow a long book, and every row has its own Test and Edit. Tick several to enable, disable, duplicate or delete them in one go. The footer holds the rules folder, this seat's discipline and the one switch that turns Canon off for the whole project.

| ID | Severity | Active | Name | Categories | Actions | |
|---|---|---|---|---|---|---|
| #E001 | Error | Doors need a Fire RatingThis door has no Fire Rating — set it. | Doors | TestEdit | ||
| #W001 | Warning | Workset standardWorkset should be ARC-Partitions | Walls | TestEdit | ||
| #W002 | Warning | Revit links must be pinnedThis Revit link is not pinned — pin it so it can't be moved by accident. | RVT Links | TestEdit | ||
| #W003 | Warning | Room dataRoom Name is empty | Rooms | TestEdit | ||
| #W005 | Warning | Sheet numberingNumber breaks ISO 19650 grammar | Sheets | TestEdit | ||
| #W007 | Warning | Mark presentMark is empty | Doors | TestEdit | ||
| #I004 | Info | Model hygiene — imported CADImported CAD found in view | any category | TestEdit |
“When I modify a door, if its Fire Rating is empty, warn me as an Error — and offer a one-click fix.” The editor is structured, so an invalid rule can't be authored, and the message the team sees is written right here. Starting a new rule with an AI provider connected, a strip at the top — ✨ Draft this rule with BIMIO AI — fills the fields from one sentence, with your model's real categories and parameters, for you to review and adjust before you press Done.
An Enforce rule says a property must hold — the workset, phase, level or a parameter. Turn on Auto-fix and Canon corrects drift silently. Tag it with a discipline and seats set to another discipline are never nagged live. And when the standard is a dimension, the number means what the project shows — 200 is 200 mm in a millimetre project — and the rule records that unit when it is saved, so it keeps its meaning if the project's units change.
A rule written on a Tuesday afternoon reads perfectly and catches four hundred things nobody intended. Test, on the rule's row, runs it against the model you have open — even while it is switched off — and lists what it would flag; and a row is not a report line, it is the element: click it and Revit selects it, or take them all at once and look. The answer you want is often the empty one, and it says that plainly rather than showing you a blank table — and when the rule reached nothing at all, it says that too, because a rule that checked nothing has not passed.
Rules are written one at a time, months apart, often by different people — and two of them can end up driving the same property of the same elements to different values. Canon works that out from the rule DEFINITIONS, before anything runs: same target, overlapping categories, different possible values. Two that merely contradict each other are a warning — the last one evaluated wins. Two that BOTH auto-fix are critical, because each undoes the other in a loop and Revit can freeze. An amber pill in the Rules window counts them, OK will not close the window while they remain, and Canon keeps that rule book out of the model so nobody else picks it up. The dialog says exactly how to resolve them: make the scopes exclusive, or turn Auto-fix off on one.
Point every seat at one shared rules folder and they all read the same book, with the folder's own permissions as the lock: a seat that cannot write there opens the Rules window read-only, and says so. The book rides inside the model too. When an edited Rules window closes with no conflict left, Canon writes it into the .rvt, so a colleague who opens the model on another machine — even without your folder — works to the same rules straight away. Closing a window you did not change never replaces the copy a model already carries, and rules that reached the model while yours was open are kept alongside your changes, with a toast to say so. Canon never synchronises for you: the book reaches the team in your own sync.
Everything below is driven entirely by the input above.
Info advises, warnings carry their fix, errors hold the gate — and the standards you mark non-negotiable simply fix themselves.
Everything Canon has to say arrives as a quiet toast in the corner — colour-coded by severity, grouped so a burst of hits is one card, never a shower. Info, warning, error — and a fourth, green voice reserved for praise. The mistake owns up on the spot, and most of the time it brings its own remedy.
Advises quietly — clicks pass straight through it, so it never gets in your way.
Carries its own one-click fix — choose the value and carry on.
Weighs 3× in the score — and holds the milestone gate until it's gone.
Enforce a standard — workset, phase, level or a parameter — and switch on Auto-fix: Canon puts the value right the moment it drifts, and the toast is just a receipt of what changed. When a standard allows several values, it won't guess — the choice comes to you instead.
That wall breaks the rule on purpose. Instead of switching the rule off for the whole team, you waive this one element — with a reason, logged under your name and the date, for good or for 30, 90 or 180 days. Honest, auditable, and reversible whenever you like. And when a fix simply can't land — the element is read-only, locked, or the rule no longer reaches it — Canon waives it for you with the reason it found, tagged “Canon (auto)” so you can review or revoke it. The exception travels, too: waivers ride inside the model itself, so once you save and synchronise, every seat inherits them — nobody is nagged about an exception the manager has already accepted, and revoking one travels the same way.
Canon doesn't keep the rule book to itself. Lens shows a selected element's Canon findings live — fix or waive without opening a scan. Palette can turn a view filter into a rule (“this filter must capture nothing”), and Canon takes it in or refuses — it never approximates. Plot checks the standard before sheets go out of the door, Loop's Families source renames types against Canon's naming grammar, Graft can carry the whole rule book into your next project, and Quire judges the sheets and views it is about to create against the same standard.
At a milestone, scan the model. Canon lists every open violation grouped by the rule it breaks — the rule and its message head each group, with Show all to select the whole rule in Revit and, where the rule has a fix, Fix all — and each row carries its inline fix, a waive and a jump-to-element. Tick a batch and fix — or waive — them in one go. Compliance comes back as a score with a trend, a milestone gate gives one honest yes-or-no — zero open errors is a PASS — and the severity counts beside it filter the table. Close the panel and the list is waiting when you reopen it — no rescan to pick up where you were.

| Severity | Category | Element | Id | Fix | Actions | |
|---|---|---|---|---|---|---|
| #I004 Model hygiene — imported CAD6Imported CAD found in viewShow all | ||||||
| #W001 Workset standard6Workset should be ARC-PartitionsFix allShow all | ||||||
| Warning | Walls | Basic Wall: INT 100 | 400009 | ARC-Partitions | ||
| Warning | Walls | Basic Wall: INT 100 | 400010 | ARC-Partitions | ||
| Warning | Walls | Basic Wall: INT 140 | 400011 | ARC-Partitions | ||
| Warning | Walls | Basic Wall: INT 90 | 400013 | ARC-Partitions | ||
| Warning | Walls | Basic Wall: INT 140 | 400014 | ARC-Partitions | ||
| Warning | Walls | Basic Wall: INT 100 | 400015 | ARC-Partitions | ||
| #W003 Room data8Room Name is emptyFix allShow all | ||||||
| #W005 Sheet numbering3Number breaks ISO 19650 grammarShow all | ||||||
| #W007 Mark present1Mark is emptyFix allShow all | ||||||
| Warning | Doors | Door-Single: D-INT-01 | 400018 | type the value | ||
Fix selected writes the whole batch in one go and then says exactly what happened — fixed, auto-waived, gone, need a value, unfixable, can't be fixed as the rule stands. When the rule itself is the problem — a rule book that came from another project names a workset this model doesn't have — the rows stay in the list, unwaived, and Canon says what to correct. When Revit rolls the batch back, nothing is counted as fixed and the rows you picked are left as they were. And the list only ever writes into its own model: open Model health on one project, switch to another's tab, and Fix refuses rather than write into the wrong file.
Every scan exports as a self-contained HTML dashboard (or CSV), written in the language of your BIMIO interface: the score, the gate, the severity distribution, every rule's compliance, the full list of violations and how many exceptions were accepted. It opens in any browser, works offline, and it's yours to send.
The model is 94.2% compliant (severity-weighted). 24 open issues across 5 active rules — 0 errors, 18 warnings. The biggest offender is #W003 Room data (8 elements). Most issues sit in Rooms.
| Rule | Severity | Applicable | Violations▼ | Compliance |
|---|---|---|---|---|
| #W003 Room data | Warning | 63 | 8 | |
| #W001 Workset standard | Warning | 214 | 6 | |
| #I004 Model hygiene — imported CAD | Info | 120 | 6 | |
| #W005 Sheet numbering | Warning | 42 | 3 | |
| #W007 Mark present | Warning | 88 | 1 |
This is an actual HTML report Canon exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Canon runs from the moment Revit starts — try it on your own model. Full trial, no card.