Home / Apps / Palette
Views panelPalette ★ Flagship

Every view, wearing the same standard.

Revit's view filters are a per-view setting pretending to be a standard. Palette turns them into one: a spreadsheet-style editor for every filter in a view, named filter sets that stamp a whole block — graphics included — into any view, and a receipt on each one, so the day someone edits a template by hand, Palette says so — and lets you approve the edit where it was meant.

Revit 2024–2027Sets carry their graphicsA receipt on every view it touchesFeeds Canon · travels with Graft
FileArchitectureStructureInsertAnnotateViewManageAdd-InsModify
The BIMIO tab: the apps, each with its own licence.
Why Palette exists

The standard lives in one hero view — and nowhere else.

Filters are Revit's least-discovered feature and its least-governed one: colours, order and visibility are set view by view, in a dialog that shows one view at a time.

Revit on its own
  • Visibility/Graphics shows one view at a time; the standard is whichever view was set up last.
  • Filter order is priority, and nothing in Revit says two views disagree about it.
  • Copying a look to forty templates is forty dialogs — and someone's afternoon.
  • When a template is edited by hand, nobody finds out until a drawing looks wrong.
The same project, with Palette
  • Every filter of a view in one grid — lines, patterns, transparency, halftone — edited in place, staged until you apply or propagate.
  • A filter set stamps a named block into any view: same filters, same order, same graphics, its header on top.
  • Palette seals a receipt on each view it writes — drift gets a name, a verdict and a one-click answer.
  • “34 views carry the old version” is one command, not a hunt.
How Palette works · input → output

Set the standard once. The model confesses when it drifts.

Palette has two halves. The manager draws the standard — the grid, the sets, the rule that says where each set belongs. Then the model wears it, signs a receipt for it, and answers for every divergence. Here is the loop, top to bottom.

Isolate:
INInput · you set it
The standardBIM Manager, once
The grid — every override in one tableFilter sets with standard graphicsCapture from a good viewA rule: where each set belongs
OUTOutput · the model wears it
✓Applied · the block lands whole — header, order, graphics
!Modified outside Palette · someone edited the view by hand — review it
•Set has moved on · the set was edited since — the views behind it, marked for one Restore
✕Missing · the sealed block has vanished from the view
34
views wear the standard after one command

Tap Input or Output to isolate a half — the other collapses.

INThe input · set the standard, once

Draw the standard the way you'd read it: as a table.

One grid for a view's filters, one page for the project's sets, one rule per set saying where it belongs. Nothing on the grid writes to Revit until you say Apply.

Who does this: BIM Manager / Coordinator

Owns the graphic standard. Draws it once; the team's views wear it.

The grid

Every filter of a view, in one table.

The Propagate page lays a view's filters out like a spreadsheet — enabled, visibility, projection and cut looks with live line previews, transparency, halftone — edited in place, several rows at once. Row order is priority in Revit, so the grid never sorts: you reorder deliberately, and you choose whether new filters land on top or at the bottom, because in a view that order is part of what gets written. And everything is staged: nothing is written to Revit until you Apply to the source, or Propagate to as many views and templates as you tick — template-locked views are flagged honestly instead of silently skipped.

Who: whoever owns the graphic standard
BIMIO · Palette — Filters & templates
Palette
Manage view filters and templates, and compare views.
Copy the source view's filters — order, graphics, visibility — to other views and templates.
Filter setsProject filtersPropagate
SourceView · Floor Plan · ARC-Working — Level 2 · 3 ticked · 2 staged
Pick source…Use a set ▾View · Floor Plan · ARC-Working — Level 2Presets ▾Compare views…
3 rows selected — edits apply to all 3
FilterOnVisProjectionCutTranspHalftone
FIL-Fire-EI60Solid / Default · 4Dash · 30%
FIL-Fire-EI30Solid / Default · 3Dash · 20%
FIL-Acoustic-55dBDash · 2Dash · 230%
FIL-ExistingSolid / Default · 1Solid / Default · 150%
4 filters in this source
Destinations41 of 41 shown · 34 ticked
OptionsNew filters on top · all 3 channels
Staged — on this page nothing is written to Revit until you Apply or Propagate.New filters goTopBottomApply 2 changes to sourcePropagate 3 filters to 34 destinations
One per value

A parameter with thirty values is thirty filters — colour-coded, in one pass.

Pick the categories, pick a parameter, and Palette creates one rule-based filter per distinct value it finds in the model, each with its own colour and its element count beside it — optionally applied to the active view as a solid surface fill and a projection-line colour in the same gesture. Everything arrives ticked, with two deliberate exceptions: a value whose filter already exists wears a “created” badge, and “(no value)” starts unticked, because the absence of a value is not one of the values. Tick “Also read loaded links” and it samples the links too — but never for element-valued parameters, whose rule stores an element id, and an id sampled inside a link means nothing in this model. It also names the trap that would otherwise look like a Palette bug: a filter of this model only paints linked elements where the link's visibility in the view is “By host view”.

New to Revit: a colour-coded legend for a parameter, built from what the model actually contains.
Palette — Create filters by value
Pick categories and a parameter — one colour-coded filter is created per distinct value.
1 · Categories1 ticked
Search categories…
Walls
Floors
Ceilings
Doors
2 · Parameter
Common to the ticked categories.
Search parameters…
Fire Ratingtext
Commentstext
Structuralyes/no
Unconnected Heightnumber
3 · ValuesTick missingSelect none
Also read loaded links
⚠A filter of this model only paints linked elements where the link's visibility in the view is “By host view”. With “By linked view” the link decides, and nothing changes.
2 of 3 links read — 1 is not loaded.
⚠You are about to create 27 project-wide filters — untick what you don't need (ctrl/shift+click sweeps a range, and one tick then sets the whole selection).
33 of 33 shown · 27 ticked · 5 already created
EI-120— 41 elementscreated
EI-30— 412 elements
EI-60— 288 elements
EI-90— 96 elements
(no value)— 17 elements
Name pattern
{cats}_{param}_{value}
e.g. “Walls_Fire Rating_EI-30” — name clashes get a (2), (3)… suffix.
Apply to “ARC-Working — Level 2” with colours
Colour surface pattern (solid fill)
Colour projection lines
27 filters will be created and applied to “ARC-Working — Level 2” with colours.CancelCreate 27 filters
A set, not a memory

Name the block. Give it a band. It stops being folklore.

A filter set is a named, ordered group with a level — View specific, View control or Basic, because a band is a position, not a label — a version, and the whole graphic recipe stored per member: lines, patterns, transparency, halftone, visibility. Applying it stamps the block into a view under its own header — “***VIEW CONTROL · FIRE RATINGS***”, asterisks first so it sorts to the top of Revit's own dialog. The page lists the sets band first, and its Drift column sums up, set by set, what the model has done to each one since. Compose one from scratch, or capture it from your best view.

New to Revit: filter standards with a name, a version and their graphics inside — not a screenshot on a wiki.
Who: the manager names the standard
BIMIO · Palette — Filters & templates
Palette
Manage view filters and templates, and compare views.
Named, ordered groups of filters. Palette stamps each set into a view as one block — its group header on top, in the band its level asks for.
Filter setsProject filtersPropagate
RefreshReview drift…Capture from a view…Import…Export…New set
SetLevelFiltersApplied inDriftVersionApply⋯
Facadeby ruleView specific69 viewsas appliedv1To views…
AcousticView control518 views1 accepted as divergentv2To views…
Fire ratingsby ruleView control834 views1 modified · 1 out of date · 1 not applied yetv3To views…
Existing / demofilters missingBasic431 views1 missingv4To views…
4 sets · 4 applied somewhere · 1 modified · 1 out of date · 1 missing · 1 not applied yet · 1 accepted as divergent · 1 set names filters this project hasn't got · scanned 10:42Not staged — creating, editing, renaming, duplicating, deleting and importing sets all write to the model as soon as you confirm.
Where a set comes from

A view already has the answer. Capture it as a set instead of rebuilding it.

Somebody spent an afternoon getting one view right. That view is the specification — and Palette reads it: point at a view or a template and it proposes one set per block of filters it finds. What you do next is the part that matters. You name the block, and you give it a BAND, which decides what it can and cannot overrule: the top band is whatever this one view needs and outranks everything below it; the middle is the office layer that drives how a view reads; the bottom is the always-on background, and it can never quietly outrank a decision taken above it. Every graphic the set will carry is shown before it is written, and editable there — unticking a filter leaves it out of the set without touching the filter itself.

New to Revit: a standard extracted from the view that already got it right.
Palette — Capture filter sets
Source
View · ARC-Working — Level 2
No separators found — the whole list (8 filters) is proposed as one set, in the order the view has it.
Choose view…
Proposed sets
Fire ratings
8 filters · view control
no separator
Set name
Fire ratings
Band
View specificView controlBasic
Separator
***VIEW CONTROL · FIRE RATINGS***
Written into every view this set is applied to, always first in the block and always disabled.
Filters, in the order this view has them
#FilterOnVisProjectionTranspCutHalftoneState
1FIL-Fire-EI120Solid / Default · 50%Solid / Default · 4
2FIL-Fire-EI90Solid / Default · 40%Solid / Default · 3
3FIL-Fire-EI60Solid / Default · 40%Solid / Default · 3
4FIL-Fire-EI30Solid / Default · 30%Solid / Default · 2
5FIL-Fire-DoorsSolid / Default · 30%Solid / Default · 2
6FIL-Fire-DampersSolid / Default · 20%Solid / Default · 1
7FIL-Fire-CompartmentSolid / Default · 20%Solid / Default · 1
8FIL-Fire-Escape routeSolid / Default · 20%Solid / Default · 1
1 of 1 proposed set ticked · 8 filtersCancelCreate set
Change it in one place

Change the standard in the set — and every view learns it fell behind.

A set's look is edited in the set itself. Double-click it, or Edit… on its row, and every member is a row of the editor: click Projection, Cut or Transp to open Edit look, tick On, Vis and Halftone in place. A member that says nothing about graphics wears a “no look” badge, and applying the set then leaves that filter's graphics in each view as they are — which is how a filter added from All project filters arrives, and the editor says so. Or take a whole look from a view that already has it right, with Adopt graphics from a view… on the set's row. Saving a new look moves the version on — v2 → v3 — so every view stamped with the old one reads Set has moved on, and Update the views that fell behind… opens the drift review on exactly those views, marked for one Restore.

New to Revit: a graphic standard you edit once, with a version that tells every view it fell behind.
Palette — Edit filter set
Set name
Fire ratings
Band
View specificView controlBasic
Separator
***VIEW CONTROL · FIRE RATINGS***
Always the first line of the block, always disabled — a label, never a filter.
v2 → v3
Where this set belongs· Floor plans and Sections templates coarser than 1:100 whose name contains “WORKING”.
Source
All project filtersChoose view…This source carries no graphics — ticking adds the filter with no look. Choose a view to capture one.Search filters…
#FilterOnVisProjectionTranspCutHalftoneBelongs to
FIL-Acoustic-55dBRules · Floors, Walls
Acoustic
FIL-Fire-EI120Rules · Doors, Walls
in this set
FIL-Fire-EI90Rules · Doors, Walls
in this set
FIL-Fire-ShuttersRules · Specialty Equipment
Add to setRemove from setIn this set — top of the block firstAlt+↑ / Alt+↓
#FilterOnVisProjectionTranspCutHalftoneState
1FIL-Fire-EI120Solid / Default · 50%Solid / Default · 4
2FIL-Fire-EI90Solid / Default · 40%Solid / Default · 3
3FIL-Fire-EI60Solid / Default · 40%Solid / Default · 3
4FIL-Fire-EI30Solid / Default · 30%Solid / Default · 2
5FIL-Fire-DoorsSolid / Default · 30%Solid / Default · 2
6FIL-Fire-DampersSolid / Default · 20%Solid / Default · 1
7FIL-Fire-CompartmentSolid / Default · 20%Solid / Default · 1
8FIL-Fire-Escape routeno look
8 filters in this set · 41 in the projectCancelSave set
Where it belongs

The set knows its own views.

A scope rule rides on the set, in its own editor: view types, views or templates, scale coarser or finer than a threshold, a name fragment. It turns “somebody remembered to apply it” into “the model says whether it is applied” — any qualifying view that does not carry the set shows up in the drift review as Not applied yet. The rule never writes anything; it only reports. And it travels with the set, through export and through Graft.

New to Revit: coverage as a fact the model states — not a checklist someone keeps.
Palette — Edit filter set
Set name
Fire ratings
Band
View specificView controlBasic
Separator
***VIEW CONTROL · FIRE RATINGS***
Always the first line of the block, always disabled — a label, never a filter.
v3
Where this set belongs· Floor plans and Sections templates coarser than 1:100 whose name contains “WORKING”.
Report views that should carry this set and do not
ViewsAny type · 2BothViewsTemplatesScalecoarser than1:100NamecontainsWORKING
Floor plans and Sections templates coarser than 1:100 whose name contains “WORKING”.
The standard is drawn — now it goes into the model, and every view it touches signs a receipt.

Everything below is Palette reading the model back against what it wrote.

OUTThe output · the model wears it

Apply it — and let every view answer for itself.

Applying writes the block and seals a receipt in the same gesture. From then on, drift has a name, a verdict, and a button that says which way it writes.

Who lives this: the whole team's views

The manager reviews drift; Restore and Update are one-click answers.

Apply

The block lands whole — and signs for it.

Apply a set and every ticked view and template gets the header, the filters in order, the graphics, visibility and enabled state — one named transaction, one undo. In the same gesture Palette seals a receipt on the view: which set, which version, which fingerprint. The receipt is written only when Palette writes; reading the model back never touches it. Then the result counts what landed — destinations, filters added, group headers written — and lists each destination with what it received.

Who: one click — many views
Set applied
Set applied
«Fire ratings» → 34 destinations. 306 added (272 filters + 34 group headers).
34 destinations306 added
PER DESTINATION 34
ARC-GA Plans — 9 added (8 filters + 1 group header)
ARC-Sections 1-100 — 9 added (8 filters + 1 group header)
ARC-Working — Level 1 — 9 added (8 filters + 1 group header)
ARC-Working — Level 2 — 9 added (8 filters + 1 group header)
ARC-Working — Level 3 — 9 added (8 filters + 1 group header)
ARC-Working — Level 4 — 9 added (8 filters + 1 group header)
ARC-Working — Level 5 — 9 added (8 filters + 1 group header)
OK
Drift has a name

Edited by hand? Palette says so — and asks which way to write.

The drift review reads every receipt back against the model and gives each view a verdict, worst first: Modified outside Palette, Missing, Not applied yet where the set's rule says it belongs, and Set has moved on where nobody touched the view but the set was edited since. Every answer names its direction before it writes: Accept approves the difference where it is — the next beat shows how finely — Restore writes set → view, and where only the look was edited by hand, Make standard writes view → set. On a Missing row the first button reads Stop tracking, because there is nothing left to re-seal. And Update the views that fell behind…, on the set's row, opens this review with those views already marked.

New to Revit: view templates with an audit trail — and a one-click way back to the standard.
Palette — Set drift
Palette leaves a receipt on every view and template it applies a set to. These are the ones that no longer match it — read what changed, then answer each row: the buttons name which way they write.
AllModified outside PaletteSet has moved onMissingNot applied yet5 rowsSearch views and sets…Re-check
✓View / templateSetVerdictWhat changedAction
ViewARC-Working — Level 2
Fire ratingsVIEW CONTROL
Modified outside Palette
1 added · reordered+ FIL-Fire-Shutters
AcceptRestoreset → viewMake standardview → set
ViewARC-Detail — Plant room
Existing / demoBASIC
Missing
all 4 filters of the block are gone, separator includedwas: FIL-Existing, FIL-Demolished, FIL-Temporary, FIL-New
Stop trackingRestoreset → view
TemplateARC-Working Plans 1-200
Fire ratingsVIEW CONTROL
Not applied yet — rule
applying it would add 8 filters and its group headerwould add: FIL-Fire-EI120, FIL-Fire-EI90, FIL-Fire-EI60, FIL-Fire-EI30 +4 more
AcceptRestoreset → view
TemplateARC-GA Plans
Fire ratingsVIEW CONTROL
Set has moved on · v1 → v3
the set is at v3; this view carries v1restoring would add 2 (FIL-Fire-Dampers, FIL-Fire-Escape route)
AcceptRestoreset → view
ViewARC-Detail — Stair core
AcousticVIEW CONTROL
Accepted · keeps its look
left as it is, on purpose · accepted by AJones · 22 Sep 2026its filters are exactly what the set lists
AcceptRestoreset → view
Examined 96 of 96 views and templates that own their filters · 92 carry a Palette receipt. 2 sets have a rule, covering 41 sides; 40 already carry what the rule asks for. A view whose filters come from a template is judged on that template.
Accept markedRestore marked (set → view)Mark all shownClear marks5 divergences · 1 accepted in earlier sessions · 4 outstanding · 2 markedClose
Approve it where it is

A hand edit can be right. Approve it, field by field — and keep watching the rest.

Select a drifted row and a panel opens under it with every field that differs from the set, filter by filter: “3 fields differ from the set. Tick the ones you approve as this view's own; the rest stay governed by the set.” Nine fields can differ — projection and cut lines, surface and cut patterns, transparency, halftone, visibility, filter enabled and detail level — and only what the set actually states is compared. Tick a line and Accept: that field becomes this view's own, Restore and a later apply both leave it alone, and a later hand edit of the same field shows up again. Accept with nothing ticked keeps the whole view's look instead, until a Restore takes it back. Accept itself changes nothing in the view — it writes the receipt — and the row stays on the report, counted, as Accepted as divergent or Accepted · keeps its look.

New to Revit: a standard that allows a deliberate exception without going blind to the next one.
Palette — Set drift
Palette leaves a receipt on every view and template it applies a set to. These are the ones that no longer match it — read what changed, then answer each row: the buttons name which way they write.
AllModified outside PaletteSet has moved onMissingNot applied yet5 rowsSearch views and sets…Re-check
✓View / templateSetVerdictWhat changedAction
ViewARC-Working — Level 2
Fire ratingsVIEW CONTROL
Modified outside Palette
1 added · reordered+ FIL-Fire-Shutters
AcceptRestoreset → viewMake standardview → set
3 fields differ from the set. Tick the ones you approve as this view's own; the rest stay governed by the set.
FIL-Fire-EI60 · Projection linesSet: weight 4 · View: weight 6
FIL-Fire-EI60 · Cut patternsSet: pattern <Solid fill> · View: pattern Diagonal crosshatch
FIL-Fire-EI30 · VisibilitySet: on · View: off
ViewARC-Detail — Plant room
Existing / demoBASIC
Missing
all 4 filters of the block are gone, separator includedwas: FIL-Existing, FIL-Demolished, FIL-Temporary, FIL-New
Stop trackingRestoreset → view
TemplateARC-Working Plans 1-200
Fire ratingsVIEW CONTROL
Not applied yet — rule
applying it would add 8 filters and its group headerwould add: FIL-Fire-EI120, FIL-Fire-EI90, FIL-Fire-EI60, FIL-Fire-EI30 +4 more
AcceptRestoreset → view
TemplateARC-GA Plans
Fire ratingsVIEW CONTROL
Set has moved on · v1 → v3
the set is at v3; this view carries v1restoring would add 2 (FIL-Fire-Dampers, FIL-Fire-Escape route)
AcceptRestoreset → view
ViewARC-Detail — Stair core
AcousticVIEW CONTROL
Accepted · keeps its look
left as it is, on purpose · accepted by AJones · 22 Sep 2026its filters are exactly what the set lists
AcceptRestoreset → view
Accept markedRestore marked (set → view)Mark all shownClear marks5 divergences · 1 accepted in earlier sessions · 4 outstandingClose
Two views that drifted

Revit can show you one view's filters. Never two, against each other.

A plan and its sibling were the same last month. Someone tweaked a colour here, switched one off there, and nobody can say what the difference IS — only that the drawings no longer match. Compare views puts the two side by side, names the drift channel by channel (projection lines, surface pattern, cut lines, transparency, halftone, visibility) and lets you choose, per row, which side wins — or ✓ Accept: the two views are allowed to differ there, nothing is copied, and the row stays, counted as accepted, until either side changes. Everything is staged: a tinted row holds an action and nothing changes in Revit until you Apply. A padlock means a direction is not available — the side without the filter has nothing to copy, and a view driven by its template cannot be written to, so the diff reads the template's filters instead. Compare a drifted view…, on a set's row, opens it on a view whose block no longer matches.

New to Revit: a difference you can read and reconcile, instead of hunting it.
Palette — Compare views
See where two views' filters drifted apart and reconcile row by row — everything below is staged; nothing changes in Revit until you Apply.
View A
AView · Floor Plan ·ARC-Working — Level 2
vs
View B
BView · Floor Plan ·ARC-Working — Level 3
All filtersOnly differences5 filters · 1 identical · 1 accepted· 3 differentSearch filters…🔒 direction lockedstaged action
FilterIn AIn BDifferenceAction
FIL-Existing✓✓differs in: projection lines, surface patternA → B
FIL-Fire-EI60✓—accepted · differs in: visibility—
FIL-Zone-Retail✓40%— not appliedonly in A🔒✓ Accept
FIL-Structural-Grid✓✓identical—
FIL-Demolition— not applied✓only in B🔒—
Stage A → B on every different rowStage B → A on every different rowClear actionsCloseApply 2 actions
Every look it wears

One filter, every view — and a letter for each look it wears.

Across views takes a single filter and lays it over every filter-capable view and template in the project, then does the arithmetic Revit never offers: it groups the placements by their actual configuration — overrides, visibility and enabled state together — and gives each group a letter. A is the biggest group, so “34 placements · 3 configurations” means two pockets of the project have quietly drifted, and the letters say exactly which views are in which. Template-locked views never get a row of their own pretending they can be written: they fold under the template that governs them, behind a “12 views” chip. Pick any row marked applied as the source and the divergence localises itself — a “≠ source” chip per view, an amber tint per channel — then propagate to as many destinations as you tick, adding the filter where it was missing. And Export report writes the whole analysis as one HTML file, in the language the interface speaks.

New to Revit: a where-and-how-used answer for one filter, across the whole project, in one screen.
Palette — Across views
Analyzed filters · 6Export report
Search analyzed filters…
Filter
FIL-Fire-EI60ABCduplicate
34 placements · 3 configs
FIL-Acoustic-55dBA
18 placements · 1 config
Fire rating 60Aduplicate
9 placements · 1 config
FIL-Existingunused
not applied anywhere yet
A = dominant configuration — more letters = drift · placements = direct + via template
FIL-Fire-EI60ABCduplicate34 placements · 3 configurations — compare against the source, then propagate
Search views…Include views that don't use it yet41 of 41 shown · 2 ticked
Tick the ones that apply itTick the ones missing itClearGraphics detail ▾
SourceDest.NameState
—via template ARC-Detail Std · 4 views🔒via template
TemplateARC-GA Plans12 viewsapplied
ViewARC-Working — Level 2applied≠ source
ViewARC-Working — Level 5not applied
What to propagateGraphic overridesVisibility (on/off)Enabled state
Source: ARC-GA Plans · 2 destinations ticked · 1 will have the filter addedClosePropagate to 2 destinations
The twins

Three filters, one meaning — merge them and repoint every view that used the others.

Palette sees the twins Revit's own filter list cannot — “Same categories and rules as: …” — and Consolidate is the half that acts on them: keep one, repoint every view that used the others, delete what is left over. A filter set that named a merged-away filter follows the merge; where a merged-away filter sits in one set and the survivor already belongs to another, that group is left out and named, because a filter can only belong to one set. Exact duplicates arrive ticked, because merging them changes nothing on screen; near-duplicates arrive unticked with the difference spelled out on each line, because “their rules differ. Merging them changes what the repointed views affect.” The survivor is pre-chosen by reach rather than by count of placements — a filter sitting on a single template reads “1 place · 300 views”, so the one commanding the project is never the one deleted by default. Where the merge disturbs a block Palette had sealed, the receipt is re-sealed with it, so Set drift does not report your tidy-up as somebody's hand edit — except where re-sealing would erase a finding that was already there, which it names instead. And if any part of the model could not be read when the window opened, nothing is deleted at all: the views are repointed and the filters stay, because absence only proves “unused” if you managed to look everywhere.

New to Revit: a duplicate merge that repoints the views instead of leaving them pointing at the corpse.
Palette — Consolidate filters
Merge equivalent filters into one and repoint every view that used the others.
Exact duplicates catch the same elements, so merging them changes nothing on screen. Near-duplicates do NOT — their rules differ — so they arrive unticked and say what the difference is.
KeepIncludeFilterRulesUsed in
4 exact duplicates4duplicate2 → «FIL-Fire-EI60» · 12 views repointedMerge
FIL-Fire-EI60keeps21 place · 300 views
Fire rating 6029 views
FIL-Fire-60min23 views
FIL-Fire-EI60 copyleft alone2unused
2 near-duplicates2similarnot mergedMerge
These filters do NOT catch the same elements — their rules differ. Merging them changes what the repointed views affect. Check the difference on each line before ticking this group.
FIL-Acoustic-55dBkeepsSame rules as: «FIL-Acoustic-52dB», except one rule tests the same parameter with a different operator
318 views
FIL-Acoustic-52dBSame rules as: «FIL-Acoustic-55dB», except one rule tests the same parameter with a different operator
32 views
2 filters deleted · 12 views repointedCancelMerge 2 filters into 1 · repoint 12 views
A filter as an office rule

This filter must catch nothing — so Canon watches it.

Some filters exist to catch mistakes: unrated walls, unnamed rooms. Right-click one and make it a Canon rule — “must catch nothing”. Palette translates the categories and conditions into Canon's language, and from then on anything the filter would catch becomes a Canon finding, with severity, waivers and the health scan the office already reads. And when a rule cannot be translated faithfully, Palette refuses and names the condition, rather than shipping a rule that means something else.

New to Revit: a graphics tool and a standards engine agreeing on one definition of wrong.
Palette
FIL-Walls-NoFireRatingRules · Walls
Edit rules…
Across views (this filter)…
Across views (ticked filters)…
Compare views using it…
Select matches in active view
Isolate matches (temporary)
Make it a Canon rule — must catch nothing…
Duplicate
Rename…
Delete
→
Canon
This element matches «FIL-Walls-NoFireRating», which should catch nothing
from the Palette filter «FIL-Walls-NoFireRating»
Warning
The standard travels

Next project, same bands.

Sets export as portable .json and publish to Graft — which filters, what order, which band, which graphics — matched by identity, not by name, so a rename never orphans a view. The receipts deliberately stay behind, and with them every difference approved in this model: a receipt for a view that was never stamped would be fiction. Lens completes the circle, answering “why is this element painted like that?” straight from the element's card.

The standard, read elsewhere
GraftCarries the sets to the next model — filters, order, band and look; receipts never travel.
transfers
LensAnswers “why is this element painted like that?” from the element's card.
reads

One standard. Every view.

Palette ships as a flagship on the Views panel of the BIMIO tab. Capture a set from your best view and let every other view wear it. Revit 2024–2027, full trial, no card.

← PreviousOpes