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.
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.
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.
Tap Input or Output to isolate a half — the other collapses.
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.
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.

| Filter | On | Vis | Projection | Cut | Transp | Halftone | |
|---|---|---|---|---|---|---|---|
| FIL-Fire-EI60 | Solid / Default · 4 | Dash · 3 | 0% | ||||
| FIL-Fire-EI30 | Solid / Default · 3 | Dash · 2 | 0% | ||||
| FIL-Acoustic-55dB | Dash · 2 | Dash · 2 | 30% | ||||
| FIL-Existing | Solid / Default · 1 | Solid / Default · 1 | 50% |
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”.
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.

| Set | Level | Filters | Applied in | Drift | Version | Apply | ⋯ |
|---|---|---|---|---|---|---|---|
| Facadeby rule | View specific | 6 | 9 views | as applied | v1 | To views… | |
| Acoustic | View control | 5 | 18 views | 1 accepted as divergent | v2 | To views… | |
| Fire ratingsby rule | View control | 8 | 34 views | 1 modified · 1 out of date · 1 not applied yet | v3 | To views… | |
| Existing / demofilters missing | Basic | 4 | 31 views | 1 missing | v4 | To views… |
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.
| # | Filter | On | Vis | Projection | Transp | Cut | Halftone | State | |
|---|---|---|---|---|---|---|---|---|---|
| 1 | FIL-Fire-EI120 | Solid / Default · 5 | 0% | Solid / Default · 4 | |||||
| 2 | FIL-Fire-EI90 | Solid / Default · 4 | 0% | Solid / Default · 3 | |||||
| 3 | FIL-Fire-EI60 | Solid / Default · 4 | 0% | Solid / Default · 3 | |||||
| 4 | FIL-Fire-EI30 | Solid / Default · 3 | 0% | Solid / Default · 2 | |||||
| 5 | FIL-Fire-Doors | Solid / Default · 3 | 0% | Solid / Default · 2 | |||||
| 6 | FIL-Fire-Dampers | Solid / Default · 2 | 0% | Solid / Default · 1 | |||||
| 7 | FIL-Fire-Compartment | Solid / Default · 2 | 0% | Solid / Default · 1 | |||||
| 8 | FIL-Fire-Escape route | Solid / Default · 2 | 0% | Solid / Default · 1 |
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.
| # | Filter | On | Vis | Projection | Transp | Cut | Halftone | Belongs 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 |
| # | Filter | On | Vis | Projection | Transp | Cut | Halftone | State | |
|---|---|---|---|---|---|---|---|---|---|
| 1 | FIL-Fire-EI120 | Solid / Default · 5 | 0% | Solid / Default · 4 | |||||
| 2 | FIL-Fire-EI90 | Solid / Default · 4 | 0% | Solid / Default · 3 | |||||
| 3 | FIL-Fire-EI60 | Solid / Default · 4 | 0% | Solid / Default · 3 | |||||
| 4 | FIL-Fire-EI30 | Solid / Default · 3 | 0% | Solid / Default · 2 | |||||
| 5 | FIL-Fire-Doors | Solid / Default · 3 | 0% | Solid / Default · 2 | |||||
| 6 | FIL-Fire-Dampers | Solid / Default · 2 | 0% | Solid / Default · 1 | |||||
| 7 | FIL-Fire-Compartment | Solid / Default · 2 | 0% | Solid / Default · 1 | |||||
| 8 | FIL-Fire-Escape route | no look |
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.
Everything below is Palette reading the model back against what it wrote.
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.
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.
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.
| ✓ | View / template | Set | Verdict | What changed | Action |
|---|---|---|---|---|---|
| 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 |
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.
| ✓ | View / template | Set | Verdict | What changed | Action |
|---|---|---|---|---|---|
| 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 | |
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.
| Filter | In A | In B | Difference | Action |
|---|---|---|---|---|
| FIL-Existing | ✓ | ✓ | differs in: projection lines, surface pattern | A → B |
| FIL-Fire-EI60 | ✓ | — | accepted · differs in: visibility | — |
| FIL-Zone-Retail | ✓40% | — not applied | only in A | 🔒✓ Accept |
| FIL-Structural-Grid | ✓ | ✓ | identical | — |
| FIL-Demolition | — not applied | ✓ | only in B | 🔒— |
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.
| Source | Dest. | Name | State |
|---|---|---|---|
| — | via template ARC-Detail Std · 4 views | 🔒via template | |
| TemplateARC-GA Plans12 views | applied | ||
| ViewARC-Working — Level 2 | applied≠ source | ||
| ViewARC-Working — Level 5 | not applied |
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.
| Keep | Include | Filter | Rules | Used in |
|---|---|---|---|---|
4 exact duplicates4duplicate2 → «FIL-Fire-EI60» · 12 views repointedMerge | ||||
| FIL-Fire-EI60keeps | 2 | 1 place · 300 views | ||
| Fire rating 60 | 2 | 9 views | ||
| FIL-Fire-60min | 2 | 3 views | ||
| FIL-Fire-EI60 copyleft alone | 2 | unused | ||
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 | 3 | 18 views | ||
FIL-Acoustic-52dBSame rules as: «FIL-Acoustic-55dB», except one rule tests the same parameter with a different operator | 3 | 2 views | ||
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.
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.
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.