Home / Guides / Canon
Setup panel

BIMIO Canon

Project standards, enforced live: rules, notifications, fixes and a compliance report.

Overview

Canon is BIMIO's live standards engine. From the moment Revit starts, it subscribes to the model's events (create, modify, delete, opening views and synchronising with central) and evaluates the rules defined for the active project. When something breaks a rule, it shows a discreet notification (toast) in the corner of the screen, often with a one-click fix button.

Beyond live monitoring, Canon includes a model health panel (Model health) that audits the whole project on demand: it lists every violation, calculates a severity-weighted compliance score, compares it with the previous scan and lets you fix in bulk, grant governed exceptions (waivers) and export a compliance report as HTML or CSV.

Rules are created without programming: a visual editor lets you describe conditions (detect a problem) or standards (enforce a workset, phase, level or parameter value), with ready-to-use starter packs and a documented JSON format that can be shared with the team or drafted with the help of an AI.

Who it's for

BIM managers and coordinators who define and monitor the project's standards, and modellers who receive the live notifications and fix violations. Rule editing is aimed at the BIM lead; the health panel and the toasts are for the whole team.

Requirements

  • Revit 2022 to 2026 with the BIMIO suite installed (Canon starts automatically with Revit).
  • An open document to scan the model or edit the project's rules (rules are associated with each project by its central or local path).
  • Write permission on the rules folder to save changes; if you use a shared network folder, that folder's permissions decide who can edit the team's rules.
  • For workset rules, a model with worksharing enabled.

Where to find it

BIMIO tabSetup panelCanon button

The button opens the BIMIO · Canon — Model health window for the active project. From there, the Edit rules button opens the rules window.

The live engine always runs from Revit start-up, even if you never open a window: if the project has active rules, toasts appear on their own.

If the window is already open, pressing the button brings it to the front instead of duplicating it.

Key concepts 14 terms

Rule
An intention of the BIM lead expressed in a structured way: when it is evaluated (trigger), which categories it applies to, what is checked and what notification is shown. There are two types: Detect (detect a problem) and Enforce (enforce a standard).
Detect (detect a problem)
A condition-based rule: for example, an empty parameter, an element hidden in the view, an unpinned link or a duplicate value. It can offer a one-click fix in the notification.
Enforce (enforce a standard)
A rule declaring that a property (workset, phase, level or a parameter) must have a specific value, with standard rows of the form if this criterion is met, the value must be X. It can fix automatically (Auto-fix) or leave the fix one click away for the user.
Trigger
The gesture that launches the live evaluation: always (recommended), on create, on modify, on opening a view or sheet, on delete or on synchronising with central.
Severity
The weight and intent of the notification: Info (blue), Warning (amber), Error (red) and Success (green, for positive-reinforcement rules; not scored). It colours the toast and weights the compliance score. The visual editor offers Info, Warning and Error; Success is only assigned by editing or importing the rules JSON.
Toast
Canon's pop-up notification at the bottom of the screen. Informational ones appear at the bottom right and let clicks pass through (they block nothing); those offering a fix appear at the bottom left and are clickable. They are grouped by rule (one toast with an element count, not a shower of notifications) and close by themselves after a few seconds; hovering the mouse over one pauses the countdown.
Cooldown
A quiet period per rule-element pair (30 minutes by default) so the same notification is not repeated. Directly editing the element or reopening the view shows it again.
Waiver (governed exception)
A recorded acceptance of a specific violation: a rule-element pair, with reason, author and date. The element stops generating notifications and counts as compliant in the score, but the report lists it as an accepted exception. It can be revoked at any time.
Compliance score
A 0-100 percentage calculated on each scan: the average compliance per rule weighted by severity (Error weighs 3, Warning 2, Info 1; Success rules are not scored). Canon keeps a history of up to 60 scans and shows the trend against the previous one.
Milestone gate
The scan's milestone verdict: PASS when no open Error-severity violation remains (waived ones do not count), FAIL otherwise.
Rule ID
A readable, stable identifier per severity, of the form #W007 (I=Info or Success, W=Warning, E=Error). Use it to refer to the rule in reports and conversations; it is reassigned if you change the rule's severity.
Rule conflict
Two active rules that may write different values to the same property in the same categories. Canon detects this while editing, and any outstanding conflict blocks the Accept button; conflicts where both rules have Auto-fix are additionally flagged as critical (in red) because they would cause a loop of fixes.
Discipline
An optional tag per rule (ARQ, EST, MEP…) and per workstation (My discipline). Live, each workstation only receives toasts for rules of its own discipline (or untagged ones); the health panel scan always shows everything.
Starter pack
A curated set of rules ready to apply in one click: model hygiene, worksharing and coordination, room and door data completeness, and ISO 19650-style sheet numbering grammar.

The interface

Canon has two windows and a pop-up notification. The main window, Model health, is everyone's view: it shows what the model is breaking right now, the compliance score and the tools to fix, accept exceptions and export the report. The second window, Rules, is the BIM lead's workbench: the project's rule list with search, bulk actions, starter packs, import/export and the shared-folder and discipline settings. From it you open the rule editor, a modal dialog that builds each rule with drop-downs (no code to write).

Toasts appear at the bottom of the screen while you work. They sort errors on top, group the affected elements by rule and, when there are more than four per side, collapse them into a +N pill so as not to flood the screen (click the pill to expand the hidden ones).

BIMIO · Canon — Model health window after a scan: header with Compliance 87.4% and Milestone gate FAIL, table with violations sorted by severity (red and amber pills), Fix, Go to and Waive buttons on the rows, and the toolbar with Scan model, Waivers…, Export…, Fix selected and Edit rules.
assets/shots/canon/fig-02.pngBIMIO · Canon — Model health window after a scan: header with Compliance 87.4% and Milestone gate FAIL, table with violations sorted by severity (red and amber pills), Fix, Go to and Waive buttons on the rows, and the toolbar with Scan model, Waivers…, Export…, Fix selected and Edit rules.
BIMIO · Canon — Model health window after a scan: header with Compliance 87.4% and Milestone gate FAIL, table with violations sorted by severity (red and amber pills), Fix, Go to and Waive buttons on the rows, and the toolbar with Scan model, Waivers…, Export…, Fix selected and Edit rules.
Model health — headerModel health title, project name, compliance line (Compliance 87.4% with the change against the previous scan), milestone gate verdict (PASS/FAIL with the number of open errors), status text and a progress bar while scanning.
Model health — toolbarScan model button (runs the full audit), global search box (id, category, rule, message), Waivers… button (view and revoke exceptions), Export… (HTML or CSV report, enabled after a scan), Fix selected (N) (bulk-fixes the ticked rows) and Edit rules (opens the rules window).
Model health — violations tableOne row per violation with: a tick box (only on fixable rows; the header tick box ticks all visible ones), severity pill, category, element, rule, message and id. The Severity, Category, Element, Rule and Message columns have an Excel-style filter (funnel with a search box and tick boxes). Each row also adds: a Fix control (a direct button or a drop-down of permitted values), a Go to button (selects and zooms to the element in Revit) and a Waive button (accept as an exception with a reason).
Rules — toolbarRule search box, bulk-actions box for the ticked rules (Enable, Disable, Duplicate, Delete), amber conflicts indicator (only shown if there are any; click to see the detail), Refresh parameters button (re-reads categories and parameters from the model after loading families) and + New rule.
Rules — rules tableTick box with a select-all header, ID (#W007), severity pill, Active tick box (enables/disables the rule), Name with the message beneath it, Categories, a Test button (evaluates the rule against the current model) and an Edit button (opens the editor). Click, Ctrl+click and Shift+click highlight rows in blue so you can act on several at once.
Rules — footerSummary (total, active, errors and warnings) and selection counter; Rules folder chip (local or shared rules folder), My discipline field (limits this workstation's live toasts), Starter packs / Import rules / Export rules box; Canon active in this project master switch and the Accept button to close.
Rule editor (modal)From top to bottom: rule name, optional disciplines, type selector (Detect a problem / Enforce a standard) and collapsible cards: Applies to categories (list with a search box, Only selected, Select all and Clear), Conditions (Detect only: When I… trigger, match ALL/match ANY toggle and condition rows with subject, operator and value), Standard (Enforce only: Workset/Phase/Level/Parameter target, Auto-fix switch, standard rows with list of options, empty allowed and an optional criterion), Notify (severity and message) and Fix (Detect only: one-click fix with Fixed value, Options or Free text modes). At the bottom, Cancel and Done.
ToastsTranslucent cards with a severity-coloured bar, title, message and element count. Informational ones (bottom right) do not intercept the mouse; actionable ones (bottom left) show a Fix button, a values drop-down with Apply or a text field, depending on the rule.

Step-by-step workflows 10 workflows

1

Scan the model's health

4 steps

Goal. Get the full picture of what the model is breaking right now and the compliance score.

  1. Open the project in Revit and press the Canon button (BIMIO tab, Setup panel).The BIMIO · Canon — Model health window opens with the project name and a message inviting you to scan.
    Model health window just opened, with no results, with the Scan model button highlighted.
    assets/shots/canon/fig-03.pngModel health window just opened, with no results, with the Scan model button highlighted.
  2. Press Scan model.The button changes to Scanning… and an indeterminate progress bar appears. The audit runs on the Revit thread, so Revit (and the window itself) stay busy until it finishes.
  3. Review the header when it finishes.You will see the Compliance line with the percentage and the change against the previous scan (▲/▼), and the Milestone gate verdict: PASS if no open errors remain, FAIL with the number of errors.
    Panel header with Compliance 91.2% ▲ +3.1 vs previous and Milestone gate PASS.
    assets/shots/canon/fig-04.pngPanel header with Compliance 91.2% ▲ +3.1 vs previous and Milestone gate PASS.
  4. Read the violations table.Rows arrive sorted by severity (errors first) and then by category. The footer summarises: N issues · N errors · N warnings · N info.
Result. A complete, measurable list of violations, a compliance score with a trend and the milestone verdict, all referring to the current state of the model.
  • Repeat the scan after fixing or granting waivers: the score and the report always reflect the latest scan.
  • Detect rules without conditions only act live; the scan ignores them. For a rule to appear in the audit it must have at least one condition.
  • The panel scan does not filter by discipline: the lead always sees the full picture, even if their workstation has My discipline set.
2

Locate a violation and jump to the element

3 steps

Goal. Find specific rows among hundreds of results and see them in the model.

  1. Type in the search box on the toolbar.It filters live by element id, category, element name, rule or message.
  2. Use the funnel on the Severity, Category, Element, Rule or Message columns for Excel-style filtering.The popup has a search box, Select all and Clear, and a tick box per value. Column filters combine with each other (logical AND) and with the global search. The funnel turns blue when the filter is active.
    Filter popup for the Category column with several categories ticked.
    assets/shots/canon/fig-05.pngFilter popup for the Category column with several categories ticked.
  3. Press Go to on the row you are interested in.Canon selects the element in Revit and zooms to it. If the element no longer exists (it was deleted after the scan), the status will ask you to rescan.
Result. The table is narrowed down to what you are looking for and you can inspect each offending element directly in the model.
  • When you change filters, Canon automatically unticks rows that become hidden: Fix selected only acts on what you can see.
  • Sort by any column by clicking its header.
3

Fix violations in bulk from the panel

4 steps

Goal. Apply one-click fixes to many rows at once.

  1. Tick the boxes of the rows you want to fix.Only fixable rows show a tick box. The header tick box ticks or unticks all visible fixable rows (it respects the filters).
  2. On rows with a drop-down in the Fix column, choose the value to apply.These are rules whose fix accepts several permitted values. If you have several rows selected in blue (extended selection) and they all belong to the same rule, the chosen value is propagated to the others; those that do not accept that value are left untouched and Canon lets you know.
    Table with several rows selected in blue and a Fix column drop-down open.
    assets/shots/canon/fig-06.pngTable with several rows selected in blue and a Fix column drop-down open.
  3. Press Fix selected (N).Canon applies all the fixes to Revit in a single batch. Fixed rows disappear from the list; if any could not be applied (a read-only parameter, a deleted element…), it remains and a notice tells you how many failed.
  4. For a one-off case, press the Fix button on the row itself.It fixes only that element using the same mechanism. Note that this is equivalent to ticking only that row and applying: any boxes you had ticked on other rows are unticked.
Result. Fixable violations are resolved in the model and leave the list; the status shows how many were fixed and how many need manual intervention.
  • Action fixes (showing a hidden element, removing a graphic override, unflipping, re-enabling Room Bounding or pinning) need no value: just tick and apply.
  • After a batch of fixes, rescan to update the score and re-enable the report.
4

Accept a governed exception (waiver) and manage them

5 steps

Goal. Record that a specific violation is acceptable, with a reason and traceability, instead of disabling the whole rule.

  1. Press Waive on the violation's row.The Accept as exception dialog opens, asking why it is acceptable for that element to break that rule.
    Accept as exception dialog with the reason field and the Waive button.
    assets/shots/canon/fig-07.pngAccept as exception dialog with the reason field and the Waive button.
  2. Type the reason and press Waive.The reason is mandatory: it is recorded together with your username and the date. The row disappears from the list and that element stops generating live notifications for that rule.
  3. To review the exceptions, press Waivers… on the toolbar.The dialog lists each active waiver: rule, element id, reason, author and date.
    Accepted exceptions (waivers) dialog with two exceptions listed and their Revoke buttons.
    assets/shots/canon/fig-08.pngAccepted exceptions (waivers) dialog with two exceptions listed and their Revoke buttons.
  4. Press Revoke on a waiver to withdraw it.The element will be checked again on the next scan and live.
  5. Rescan the model.After granting or revoking waivers, the Export… button stays disabled until a new scan re-synchronises the score with the list.
Result. The exception is governed: it stops bothering you, counts as compliant in the score and appears in the report as an accepted exception, with its audit trail.
  • A waiver is per rule-element pair: it does not affect other elements or other rules on the same element.
  • Model-level violations (for example, the Revit warnings count) cannot be waived: fix them or disable the rule.
  • Waivers are saved on your machine; each workstation manages its own.
5

Export the compliance report

3 steps

Goal. Turn the latest scan into a shareable deliverable: an HTML dashboard or a CSV log.

  1. With a scan done, press Export… on the toolbar.The button is only enabled after scanning (and is disabled if you grant waivers, until you rescan).
  2. Choose the format and name in the save dialog.HTML report (default) or CSV (Excel). The suggested name is canon-compliance-YYYYMMDD-HHMM.
  3. Press Save.Canon writes the file, confirms the path and opens it automatically. The HTML is a self-contained dashboard (no external dependencies, works offline): score ring, severity distribution, rule and violation tables with search, sorting and filters, and light/dark mode. The CSV uses semicolons (Excel-friendly with Spanish regional settings) and includes a summary block, a per-rule table and the violations log.
    HTML report open in the browser with the score ring, the severity doughnut and the violations table.
    assets/shots/canon/fig-09.pngHTML report open in the browser with the score ring, the severity doughnut and the violations table.
Result. A self-contained file with the scan's compliance snapshot: score, trend, milestone gate, accepted exceptions, per-rule detail and the full violations log.
  • The report reflects the latest scan, not the live state: scan just before exporting.
  • If the scan was cancelled or left incomplete, the report says so explicitly.
6

Create a Detect rule (detect a problem)

8 steps

Goal. Define, without programming, a check of the kind notify me when something is wrong.

  1. In Model health press Edit rules and, in the Rules window, press + New rule.The editor opens with a draft rule. The rule is only added to the list if you finish with Done; Cancel discards it entirely.
  2. Type the rule name and, if applicable, the disciplines.The name is mandatory and unique. Disciplines (for example ARQ, EST, MEP) is optional: if you fill it in, live notifications only go to workstations of that discipline; the panel scan always shows it.
  3. Leave the type as Detect a problem.Detect = it notifies you when your conditions are met. The other option, Enforce, is explained in its own workflow.
  4. In Applies to categories, tick the model categories it applies to.There is a search box, Only selected, Select all and Clear. With none ticked, the rule applies to any category (noisier and heavier: use with care).
    Applies to categories card in the editor with the Doors category ticked.
    assets/shots/canon/fig-10.pngApplies to categories card in the editor with the Doors category ticked.
  5. In Conditions, choose the trigger in When I… and add conditions.Triggers: always (recommended: on create, edit and opening views), on create, on modify, on opening a view, on delete and on synchronising. Each condition combines a subject (Parameter, Flip, Override, Hidden, Workset, Pinned, Link or Model), an operator (is empty, equals, contains, matches pattern, greater than, duplicate…) and a value. The + and × buttons add or remove conditions, and the match ALL / match ANY toggle decides whether all must be met or one is enough.
    Conditions card with the condition if parameter Fire Rating is empty and the match ALL toggle.
    assets/shots/canon/fig-11.pngConditions card with the condition if parameter Fire Rating is empty and the match ALL toggle.
  6. In Notify, choose the severity and write the message.Info, Warning or Error. The message is the text the user will see in the toast: write it as a clear instruction.
  7. Optional: in Fix, enable Offer a one-click fix in the toast and configure it.Specify the parameter to write (by default, the one from the condition) and the mode: Fixed value (a fixed value), Options (a list of values the user chooses from) or Free text (the user types). If the parameter is a Yes/No type, Canon detects it and offers the Yes/No drop-down automatically. For action subjects (Hidden, Override, Flip, RoomBounding) the fix is automatic and there is nothing to configure.
  8. Press Done.Canon validates the rule (unique name, named parameters, complete standard rows…) and adds it to the top of the list with its ID (#W007). Changes are saved automatically: there is no save button.
Result. An active rule that watches the model live and appears in the health panel audit, with its one-click fix if you configured one.
  • Before trusting a new rule, try it out with the Test button on its row.
  • A Detect rule without conditions fires on every gesture on those categories and the scan ignores it: always add at least one condition.
  • Parameter names auto-complete with those from the real model; if you have just loaded families, press Refresh parameters.
7

Create an Enforce rule (enforce a standard)

7 steps

Goal. Declare that a property must have a specific value and let Canon fix it on its own or in one click.

  1. Create a new rule and select Enforce a standard as the type.The Conditions card is replaced by the Standard card.
  2. Choose the target in Enforce that the: Workset, Phase, Level or Parameter.If you choose Parameter, type or select the parameter name. The target is single for the whole rule.
  3. Define the standard rows: the value the target must have.In each row you choose the expected value (a drop-down with the model's real worksets, phases or levels, or free text for parameters). The list of options tick box turns the row into a list of permitted values (the user will choose when fixing); empty allowed makes an empty value also count as compliant. With + add standard row you add more rows; the cross on each row removes it.
    Standard card with a row the workset must be EST-Estructura and a criterion if Category is Walls.
    assets/shots/canon/fig-12.pngStandard card with a row the workset must be EST-Estructura and a criterion if Category is Walls.
  4. Optional: add a criterion to each row with + add a condition.That way a single standard discriminates by case: if Category is Walls, the workset must be X; if Category is Doors, it must be Y. The first row whose criterion is met wins, so order matters; if two rows can overlap, the editor shows an amber warning.
  5. Decide whether to enable Auto-fix.With Auto-fix, Canon fixes the violation automatically and the toast only reports what changed. Without Auto-fix, the toast offers the Fix button. The switch is disabled automatically if any row is a list of options: choosing between several values requires a human decision.
  6. Complete Notify (severity and message) and press Done.
  7. If the amber conflicts indicator appears in the Rules window, press it and resolve them.Two rules writing different values to the same target in overlapping categories contradict each other; if both have Auto-fix, the conflict is critical (a loop of fixes). The window's Accept button will not close while any conflict remains, critical or not.
    Rules window with the amber 1 conflict button visible next to Refresh parameters.
    assets/shots/canon/fig-13.pngRules window with the amber 1 conflict button visible next to Refresh parameters.
Result. A living standard: elements that deviate are fixed on their own (Auto-fix) or arrive as a notification with a one-click fix, and the audit measures them just like any other rule.
  • Start without Auto-fix and enable it once you trust the rule: automatic fixes write to the model without asking.
  • Canon includes a live firewall: if an element auto-fixes too many times in a few seconds (conflicting rules), it stops auto-fixing it and records it in the log.
8

Test a rule against the model (Test)

4 steps

Goal. See how many and which elements a rule flags before signing it off.

  1. In the Rules window table, press Test on the rule's row.Canon evaluates only that rule against the active model, even if it is disabled (you are testing it), using the same engine as the real audit.
  2. Review the results dialog.It shows N elements break this rule and a list with element name, category and id.
    Test rule dialog with 14 elements break this rule and the list of elements.
    assets/shots/canon/fig-14.pngTest rule dialog with 14 elements break this rule and the list of elements.
  3. Click any row to select that element in Revit, or press Select all in Revit to select them all.
  4. Close with Close and adjust the rule if needed.
Result. A faithful preview of the rule's scope: you will know whether it flags what you expect before it starts notifying the whole team.
  • The test respects the active view for view-dependent checks (hidden, override).
  • After editing a rule and pressing Done, test it again: Test always evaluates the saved version of the row, including your latest changes.
9

Apply starter packs and enable rules in waves

5 steps

Goal. Start a project with curated standards and enable them gradually rather than all at once.

  1. In the Rules window press Starter packs (in the footer, or Starter packs… in the empty state if there are no rules yet).A dialog opens with the available packs: Model hygiene (imported CAD, in-place families, warnings, unpinned links), Worksharing & coordination (pinned links and datums, shared coordinates), Data completeness (room name and number, door Fire Rating and Mark) and Sheet naming (ISO 19650-style sheet numbering grammar).
    Starter rule packs dialog with the four packs, their rule counts and the Add buttons.
    assets/shots/canon/fig-15.pngStarter rule packs dialog with the four packs, their rule counts and the Add buttons.
  2. Decide whether to leave the Add disabled, for review tick box ticked (on by default).With it, the pack's rules arrive disabled so you can review them before they start notifying.
  3. Press Add on the packs you want.The rules are added at the end (exact duplicates are skipped) and the button changes to Added ✓.
  4. Close the dialog and review the added rules: edit messages, categories or thresholds to taste.For example, the sheet numbering grammar comes with an example pattern that you must adapt to your project code.
  5. Enable them in waves: tick several with the tick boxes (or highlight a range with Ctrl/Shift+click and tick one box so it propagates to the whole group) and press Enable in the bulk-actions box.Disable, Duplicate and Delete work the same way on the selection. That way you can, for example, enable only the errors first and leave the warnings for the following week.
Result. An operational set of standards in minutes, enabled at the pace you decide, without starting from a blank list.
  • Applying a pack twice does not duplicate rules: duplicates by content are skipped.
  • The Active tick box on each row allows fine-tuning rule by rule after enabling in waves.
10

Share the rules with the team and exchange them as JSON

5 steps

Goal. Have the whole team read the same rule set and be able to carry rules from one project to another (or draft them with an AI).

  1. Press the Rules folder chip in the footer of the Rules window.A folder picker opens: paste a path (for example, a network one: \\servidor\BIM\Canon\rules) or use Browse. Empty means the default local folder. The dialog validates the path live.
    Folder picker dialog with a network path pasted and the existing-folder check mark.
    assets/shots/canon/fig-16.pngFolder picker dialog with a network path pasted and the existing-folder check mark.
  2. Confirm with Use this folder: every workstation pointing at that folder will read the same rules.The folder's permissions act as file-level access control: whoever has write access saves their changes; without write permission, Canon cannot save to that folder and that workstation's changes are not persisted.
  3. To take the rules with you, press Export rules and choose the destination for the JSON.The exported file is self-documenting: alongside the rules it includes a guide (_README, _schema, _examples) and, if a model is open, the project's real categories and parameters (_available). With that, an AI or a colleague can draft valid rules without opening the editor.
  4. To bring rules in, press Import rules and choose the JSON file.Canon asks whether to add them to the current ones (Add) or replace everything (Replace all). If it detects rules identical to the ones you already have, it offers to skip the duplicates or add them anyway. When finished it shows a summary of added, updated and skipped rules.
    Import dialog asking Add or Replace all with the file's rule count.
    assets/shots/canon/fig-17.pngImport dialog asking Add or Replace all with the file's rule count.
  5. If you re-import a previously exported file (round trip), rules with the same Id are updated in place instead of being duplicated.This is the circuit designed for editing rules outside Canon: export, tweak the JSON (by hand or with an AI) and re-import.
Result. A single rule set per project, shared via a folder with permissions, and a portable, documented JSON format for office templates or assisted authoring.
  • The My discipline field in the footer is per workstation: type ARQ, EST, MEP… to receive live only the toasts for your discipline (empty = all). It does not affect the panel scan.
  • The Canon active in this project switch turns off all the project's rules at once without deleting them.
  • Changing the rules folder applies instantly: the live engine reloads from the new location on the next event.

Options reference 16 options

OptionWhat it does
Canon active in this project (master switch)Turns all the active project's rules off or on. With the switch off, Canon evaluates nothing in that project (neither live nor in the scan).
Active (per rule)A tick box on each row of the rules table: enables or disables the rule without deleting it. If several rows are highlighted in blue, the change propagates to the whole group.
Rules folderThe folder where the per-project rule files live. Empty = the default local folder (the user's AppData). A shared network path turns the rules into a team resource, and its permissions decide who can edit. Change it from the chip in the footer of the Rules window; it is saved instantly.
My disciplineThis workstation's discipline (ARQ, EST, MEP…), saved per machine. Live, only toasts for rules that are untagged or tagged with your discipline are shown. Empty = you receive everything. It does not affect the health panel scan.
Disciplines (per rule)Optional tags in the rule editor that narrow which workstations the rule notifies live. Empty = all workstations.
Rule type: Detect / EnforceDetect defines conditions that detect a problem; Enforce declares the value a workset, phase, level or parameter must have.
Trigger (When I…)When the live engine evaluates the rule: always (recommended), on create, on modify, on opening a view or sheet, on delete (the deleted-elements threshold only) or on synchronising with central.
match ALL / match ANYHow the conditions of a Detect rule are combined: all must be met (AND) or one is enough (OR).
SeverityInfo, Warning or Error per rule. It colours the toast and the pills, sorts the results and weights the score (3/2/1). Success exists for positive-reinforcement rules, is not scored and can only be assigned via JSON (the visual editor does not offer it).
Offer a one-click fix in the toast (Detect)Enables the one-click fix. Modes: Fixed value (a fixed value), Options (a list of permitted values, the user chooses) and Free text (the user types the value in the toast itself). With Yes/No parameters, Canon offers the Yes/No drop-down automatically.
Auto-fix (Enforce)With Auto-fix, Canon fixes the deviation automatically and the toast only informs. Not available when any standard row is a list of values (the fix requires a choice).
list of options / empty allowed (standard row)list of options turns the expected value into a list of permitted values; empty allowed makes an empty value also count as compliant.
Add disabled, for review (packs)When applying a starter pack, the rules arrive disabled so you can review them and enable them in waves. On by default.
Import: Add / Replace all and duplicatesWhen importing a JSON you choose whether to add to what exists or replace everything; if there are identical rules, you can skip them or force them in.
Refresh parametersRe-reads from the model the categories, parameters, worksets, phases and levels that feed the editor's drop-downs. Use it after loading families or creating parameters.
CooldownMinutes (advanced, JSON)Minutes of silence per rule-element pair before a toast repeats. 0 = the default 30 minutes. Not exposed in the visual editor; adjust it by editing the rules JSON.

What you get out

  • Live notifications (toasts) with severity, message, a grouped element count and, depending on the rule, a one-click fix (button, values drop-down or text field).
  • HTML compliance report: a self-contained dashboard (no external dependencies) with score, trend, milestone gate, charts by severity, rule and category, and tables with search and filters.
  • Semicolon-separated CSV compliance report: a summary block, a per-rule table (applicable elements, violations, % compliance) and the full violations log.
  • An exportable, self-documenting rules JSON file (a _README/_schema/_examples guide and the project's real data in _available) to share, version or draft with an AI.
  • A local score history (up to 60 scans per project) that feeds the trend shown in the header.
  • A local waiver log (accepted exceptions) with reason, author and date, viewable and revocable from the panel.

Pro tips 6 tips

Scan regularly (for example, before each deliverable): the score with its trend turns compliance into a management metric, not just a list of errors.
The milestone gate is a clear milestone criterion for the team: zero open errors = PASS. Waived exceptions do not block it.
Hovering the mouse over a toast pauses its countdown; informational toasts let clicks pass through, so they never get in the way of your work.
Use clear rule names and messages written as instructions: they are what the modeller will see in the notification.
The OnSync trigger turns every synchronisation with central into an automatic quality checkpoint.
Everything is saved automatically in the Rules window: Accept simply validates (it blocks if there are conflicts) and closes.

Good to know

The panel scan runs on the Revit thread: while it lasts, Revit is busy and it cannot be cancelled from the window (the progress bar is indeterminate).
Detect rules without conditions only act live; the panel audit ignores them. Conversely, some gesture checks (for example, the moved- or deleted-elements threshold) are live-only and the report lists them as not covered.
Rules for hidden elements or graphic overrides are view-dependent: live, they are limited to the active view (with a cap on candidates in very busy views) and are excluded from the OnSync check; the panel scan covers them in full.
The OnDelete trigger can only evaluate the deleted-elements threshold (the elements no longer exist for other checks).
Auto-fix is not available when a standard row accepts several values: the fix becomes a user choice.
Waivers and the score history are local per machine (not shared with the team); rules, however, can be shared via a folder.
After granting or revoking a waiver, the report is disabled until you rescan, so that the score and the list stay consistent.
The rule editor does not expose the toast cooldown (the default value of 30 minutes is inherited unless you edit the JSON).
At most 4 toasts are shown per side; the rest are grouped into a +N pill. Each toast closes by itself after 4 to 15 seconds (depending on the message length).
Rule names must be unique within the project and changes are auto-saved: there is no undo.

FAQ 8 questions

I am not getting notifications even though I am breaking a rule — what should I check?
In order: that the Canon active in this project switch is on; that the rule is active (Active tick box); that its trigger and categories match what you are doing; that your My discipline field does not exclude it (if the rule carries another discipline's tag, your workstation does not receive it); and the cooldown: the same notification for the same element is silenced for 30 minutes, although directly editing the element or reopening the view shows it again. If there is a waiver on that element and rule, it will not notify either.
What is the difference between a Detect rule and an Enforce rule?
Detect describes a problem with conditions (an empty parameter, an unpinned element, a duplicate value…) and notifies you when they occur; it can optionally offer a one-click fix. Enforce declares the correct value of a property (workset, phase, level or parameter) through standard rows, and can fix on its own (Auto-fix) or in one click. If your intent reads as this must be X, use Enforce; if it is notify me when Y happens, use Detect.
How do I share the rules with the whole team?
Point the Rules folder chip on every workstation to the same shared folder (for example, a network one). Everyone will read the same per-project rules file, and the folder's permissions act as access control: only those with write access can save changes to the shared rules. For templates or one-off handovers, use Export rules and Import rules with the JSON file.
What happens if two rules contradict each other?
Canon detects them while editing: an amber button appears with the number of conflicts and the detail of which rules clash and why. The Accept button will not close the window while any conflict remains; if both rules automatically fix the same target with different values, the conflict is also critical (in red), because it would cause a loop of fixes. And at run time there is a firewall: if an element auto-fixes too many times in a few seconds, Canon stops auto-fixing it and notes it in the log.
Does a waiver distort the compliance score?
No: the waived element counts as compliant, but the scan records how many accepted exceptions there are and the report lists them separately, with reason, author and date. The picture stays honest: you can see the compliance and also how much of it comes from governed exceptions. Bear in mind that waivers are local to each machine.
How is the compliance percentage calculated?
On each scan, each rule gets its own compliance (compliant elements out of the elements it applies to). The overall score is the average of those rules weighted by severity: Error weighs 3, Warning 2 and Info 1; Success rules and rules that applied to no elements do not count. The result is stored (up to 60 scans) and the header shows the change against the previous scan.
Can I write the rules outside Canon, for example with an AI?
Yes. Export rules generates a self-documenting JSON: it includes a complete guide to the format (_README, _schema with every enum and _examples) and, if a model is open, the project's real categories and parameters (_available). Any person or AI can draft valid rules against that guide and you bring them back with Import rules; rules that keep their Id are updated in place instead of being duplicated.
Won't the toasts interrupt me constantly?
They are designed to intrude as little as possible: informational ones let clicks pass through (you cannot press them and they do not cover buttons), bursts of hits are grouped into a single notification with a count, each rule-element pair is silenced for 30 minutes after notifying, at most 4 toasts are visible per side (the rest fold into a +N pill) and they close by themselves after a few seconds. In addition, with My discipline you only receive the notifications for your own scope.