BIMIO Misc is the free tab that ships with every BIMIO licence: the toolbox, panel by panel, and a hub you search by typing. Measuring, renaming, tagging along a path, auditing groups, authoring fill patterns, sweeping the model clean. Every tool writes in a single named transaction, and every one tells you first whether it touches your model.
Every Revit day has a dozen two-minute chores — measure that, renumber those, find which sheet hosts this view, purge what nobody uses. Individually none justifies an add-in; together they eat the afternoon.
Lens, Synapse, Reset View, Trace, Atlas and Script sit on the BIMIO Misc tab. Each one is told in full below.
The dockable panel, free with any BIMIO licence, that follows your selection and stacks in one place everything the BIMIO suite already knows about it.
Bring your own AI, connected once for the whole suite — Claude, OpenAI, Gemini, Azure or a private self-hosted model, governed by a privacy mode.
Undo the graphic tricks on the active view — overrides, filters, hidden elements — shown first, then cleared in one undoable transaction.
Why can't I see this element here? A live checklist of every reason an element can be hidden.
A minimap of the view: see where you are and drag to move.
Run Python, C# or VB.NET on the model from your library.
Lens is the free dashboard of the BIMIO Misc tab: a panel that docks beside your model, follows every selection, and stacks in one place everything the suite knows about it — the identity Revit buries in a modal, who created it and who owns it now, and a live card from every BIMIO app with something to say about that element. No setup, no run button, nothing more to buy: it comes with any BIMIO licence, in Revit 2024–2027.
One element's story lives in six places — a modal for its id, a dialog for its warnings, a window per add-in — and none of them follow your selection.
Lens has two halves. The input is just your selection — the apps have already done their work. The output is everything they know, stacked beside the model: the facts, the cards, the brief, the memory, the file.
Tap Input or Output to isolate a half — the other collapses.
The panel docks like any Revit pane and refreshes on every selection. The only pinned controls are the scope — Project, Element or Type — a search box, the finder, one AI button and the HTML export.
The docked panel refreshes on every selection with no run button. Scope pills — Project, Element, Type — set how far it looks; the master search filters every card below; and the finder button browses the elements you can't click in the model: view templates, view filters, project information. GENERAL INFO opens the stack with the Id first — no modal to open — then where the element sits, then Authorship: Created by, Last Changed by — and Owned by, shown only while someone actually has the element checked out — each with the person's colour dot.
Select a plan view in the Project Browser — or nothing at all, so the active view is the target — and GENERAL INFO grows a View Range band: Top, Cut Plane, Bottom and View Depth, each a level and an offset. Every level except the Cut Plane's opens the same choices as Revit's own dialog, Unlimited included; each offset is a box where Enter or clicking away saves and Esc puts it back. Lens checks the order of the planes before Revit does and writes one named transaction. When a view template owns the range, the four rows turn read-only and the band names the template.
Canon's rule breaches, Ledger's keynote, the saved Select rules the element matches, Clash, Assay, Palette, Dictum, Datum, Stencil, Loop, Nest, Trace and the Misc helpers — each a card in its app's own brand. The always-on cards — Canon, Clash, Assay, Trace, Ledger — give a clean element an honest empty instead of silence; the automatic ones appear only when they have something true to say. An app you don't own shows a quiet lock with the way to change that, and Open ↗ on any card jumps into the full app — the card informs, the app acts.
A view template, a filter, a workset, Project Information: people change them, they break drawings, and there is nothing in the model to select. Find hidden elements lists the whole model by category, alphabetically — the types of each category in a “— Types” bucket of their own, and anything Revit gives no category under the class name it has inside Revit. Select an element and Inspect in Lens loads it into the panel; a workset, which is not an element, shows its recorded history right there in the finder instead. The window stays open while you browse, so you can walk a list of suspects one at a time and see, for each, who touched it and when.
Lens runs nothing of its own — the apps did the work when they ran. The only writes are the ones you click: a Canon Fix or Waive, a recorded value you restore, a view range plane you retype, the colours How it was built paints on a view until you clear them, an inspection marker you later clear.
Everything below the cards is optional depth: an AI reading of the panel, Chronicle's memory when you license it, and an HTML dossier for whoever isn't in Revit.
The pinned ✦ Explain button asks BIMIO Synapse — your connected AI — to explain everything below in plain language. The result is the AI brief card at the top of the scroll: a grounded summary you can dismiss with ✕ or open in full with “Tap for the full brief →”. It reads what the panel and its history already know, so the brief can never know more than you can verify.
The card at the top of the panel is the short answer. Opening it gives the long one, in four parts: what it is, its lifecycle with who and when, the risks it carries and what to do next. It is the same grounded material — the facts already on screen — laid out to be read rather than glanced at, and it says on its own face that it is generated: verify before acting. Nothing here is a new fact. They are the ones you already had, in a paragraph.
With Chronicle licensed, a bronze card — CHRONICLE · Activity & history — joins the stack. History is its heart: every synchronisation's created, modified and deleted rows, grouped under who made them, searchable, and narrowed by one line of chips — User, Category, Action and Date — with Auto-propagated, Hide AI noise and Deleted only beneath them. Each change reads on one line, Fire Rating : EI30 → EI60, and a click unfolds it. Beside it sit Live Activity — who is editing what, polled every 30 seconds in slices short enough never to freeze Revit — What changed since any recorded sync, and How it was built, painting the view by rework, age, author, settledness or hands. Chronicle records; Lens is where you read it, beside the selection.
A Modified row that kept its previous value carries a Restore pill. Clicking it writes nothing: Lens resolves the element and the parameter against the live model and shows the preview first — the value now, the value it would write, when that value was recorded, and a warning when it matters, such as a type parameter that changes every element of that type. It refuses, with the reason, when the element or the parameter is gone, the parameter is read-only, the number was recorded before exact values were kept, a reference no longer resolves, or the value is already that. One element, one parameter, one named transaction; Ctrl+Z undoes it, and History gains a Restored row. There is no restore-everything button, on purpose.
Also inside the Chronicle card, Journals reads this session's commands from Revit's own journal — on your machine only, never shared — and lists them newest first, under chips for warnings, dialogs answered and how long since your last sync. It reads like Revit's undo drop-down: one row per command, and the row is the button. Click one and Lens takes Revit back to just before it by posting Revit's own Undo the exact number of steps; the rows you stepped over dim, a dimmed row further up replays forward to just before itself, and ↪ Back to latest replays everything. A command that changed nothing cannot be clicked, and the reach ends where Revit's does: when Lens began watching the model, or at your last sync.
The last question in the Chronicle card is about the model, not one element. How it was built colours the active view by one of five questions: Rework (how many separate syncs changed each element), Age (when it appeared), Author (who created it), Settled (what has not been touched since tracking began, and what is still moving) and Hands (how many different people worked on it). Hide everything else while I look takes out of the view whatever the question cannot explain, with Revit's temporary hide/isolate, so nothing is saved into the model. In Rework you set where hot begins — seven syncs or more until you change it — and can hide what was never reworked. Every band in the legend carries its count and a Select; click any coloured element to read its own story. The caveat under the legend is said out loud: it counts syncs, not single edits. Clear colours puts back the graphics the view had before.
Inside the Chronicle card, Deleted elements keeps every recorded deletion: what it was, when it went, where it stood — and, for teams running BIMIO, who deleted it, recorded in the deleter's own session rather than guessed; older rows say Unknown honestly. Recreate plants a temporary marker at the last-known spot so you can see the hole before deciding, and Finish inspection removes every marker before anything reaches the file.
Revit reports a teammate as a raw Autodesk username, which is not what anybody calls them. Type a friendly name once and it replaces the raw one everywhere in Live Activity and History; the real username is still stored underneath, so nothing you rename can break a lookup later. And the history itself can be pooled: point the project at a shared folder and every collaborator's Lens publishes its own changes there and reads the others'. The path lives IN THE MODEL, so a teammate who opens it inherits the setting without configuring anything on their machine.
In the Family Editor the project cards stand down and the panel becomes the family dashboard: the Mold card sums the family in one line — category, types, parameters, shared count — and Run health grades every type on demand: unused parameters, hardcoded formulas, types with blanks, naming. The full types × parameters matrix is one Open ↗ away in Mold itself, and Nest sits beside it with the nesting story.
HTML exports what you are looking at: an element or type dossier, or — in Project scope — a self-contained dashboard with a health score out of 100, people, hotspots, deletions, the inventory and — with your connected AI — a summary written for humans, all in the language BIMIO is set to. No install, no viewer, works offline. The change audit rides a Chronicle licence; without one the report says so plainly and ships everything Lens reads for free.
This is an actual HTML report Lens exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Synapse is the suite's shared AI layer — a single settings window, not a chatbot. Enter your Claude, ChatGPT, Gemini or Azure key once, or point it at a private self-hosted model, and every BIMIO tool with AI features can use it. A privacy mode governs what may leave the machine, keys are sealed with Windows DPAPI, and the AI never writes to your model: it proposes, you approve, BIMIO writes.
Without a shared layer, every AI feature would carry its own key box, its own privacy answer and its own idea of what a valid reply is.
The input is a single settings window, filled once. The output is AI features lighting up across the suite — with a disciplined middle: schema-validated replies, privacy enforced at resolve time, and nothing landing in your model without your approval.
Tap Input or Output to isolate a half — the other collapses.
The Synapse button on the Misc panel of the BIMIO Misc tab opens the only surface there is: provider, key, model, privacy. The window itself says the contract.
Pick a provider from five — Anthropic (Claude), OpenAI (ChatGPT), Google (Gemini), Azure OpenAI, or a self-hosted private model — paste the key once, set the model and the privacy mode. The key is masked as you type — an eye at the end of the field reveals it while you are in it — and it is never shown back: open the window again and the field is empty under “API key (saved — leave blank to keep)”. Keys are sealed with Windows DPAPI on this machine, and are never written to the model, a settings file or a log.


Two modes are offered, in the app's own words: “Allow the selected provider” and “Local only — nothing leaves this PC”. Local-only is not a preference label — the provider factory refuses to build a remote adapter at all, and checks that the actual endpoint is local before a single byte moves. A third mode, ask-each-time, is deliberately not offered until its consent gate is real.


Set Privacy to “Local only — nothing leaves this PC” while Claude is still the provider, and Save does not pretend. The setting is saved — it is a safe state — but the line under the fields turns red and says exactly why no tool will get an answer: “Saved, but no BIMIO tool can use AI yet: Privacy mode is Local-only — remote AI providers are blocked. Choose the self-hosted provider or change the privacy mode.” Test connection gives the same reason and calls nobody, because it runs the same check every AI call goes through. The tools only say they are not connected; this window is where the reason is written.


Test saves the settings first, then runs the real pipeline end to end — the reply has to come back as valid, schema-checked JSON before the window prints the green line: “Connected. Anthropic (Claude) · claude-opus-4-8 · 840 ms.” A failure names itself instead of shrugging: “Test failed — …”. What you proved is exactly what every tool will use.


Switch from Claude to Azure and Claude's model and sealed key stay exactly where they were; switch back and nothing is retyped. Azure OpenAI is the only provider that asks for a Deployment and an API version (the endpoint a self-hosted model wants too), and the window checks the endpoint, the deployment and the key before it commits anything, so a rejected save leaves neither a key nor half a configuration behind: “Azure OpenAI needs a deployment name.” A save that passes names what it armed: “Saved. Every BIMIO tool can now use Azure OpenAI.”


The pipeline runs off the Revit thread and never touches the model. It hands the tool that asked a reply that passed its schema, or a named failure — and what reaches the model is that tool's own step, taken by you: Clash waits for Apply, Canon adds the rules it drafted switched off, Script lets you use, append or discard the draft.
No tool talks to a provider directly. Everything goes through the same orchestrator, the same schemas, the same privacy answer.
Lens classifies changes and writes element briefs and report copy; Canon drafts rules from your standards documents; Assay triages warnings; Clash triages interferences and writes briefs; Graft explains diffs; Quire drafts sheet plans; Script drafts, improves and fixes the script you describe — each through the same service, the same key, the same privacy answer. Connect once, and the buttons that were waiting light up everywhere.
Nothing greys out unexplained. Ask Lens to explain an element with no provider set and its status line asks you to connect one in BIMIO Synapse. Clash meets a triage click with “No AI provider is connected. Set one up in BIMIO Synapse (connect your AI once, every tool benefits), then try again.” Canon points you to Synapse and adds that the key stays on this machine, and Script's Ask AI pane says “Connect an AI provider in BIMIO Synapse settings to draft scripts here.” with Open Synapse settings as a link beneath it. Every one of those tools does the rest of its job untouched.
Connect an AI provider in BIMIO Synapse settings to use Explain.
No AI provider is connected. Set one up in BIMIO Synapse (connect your AI once, every tool benefits), then try again.
No AI provider is configured. Open BIMIO Synapse (BIMIO Misc tab, Misc panel), connect your AI (Claude, OpenAI, a local model…), then come back — your key stays on this machine and the whole suite can use it.
Failures come back typed. A 429 or a 503 is retried up to four attempts with exponential backoff, honouring the provider's own Retry-After header; a 401 is not, because waiting will not mend a rejected credential — so the window reports “Test failed — The AI provider rejected the credential (HTTP 401).” An account out of credit is named too, and not retried either: “The AI account has no credit left (HTTP 402). Top it up with the provider, or choose another provider in Synapse’s settings.” Tools also cap the AI themselves: Assay gives warning triage sixty seconds, then records “The AI provider did not answer within 60 s — warnings are in Revit's own order”. No failure writes anything.


Put the office's settings file on a workstation as its firm lock and the window goes read-only, with a banner in its own words: “Your organisation has locked the AI configuration. These settings are read-only.” Every field is disabled and Save with it; Test connection still works, against what the office set. The lock fails closed — a firm file that cannot be read leaves AI off rather than letting a seat fall back to its own provider — and it carries the provider, the model and the privacy mode, never a key: keys stay with each person, on each machine.


The tools do not just consume the connection, they display it. On a seat running a private model, Canon's Draft with AI window carries “AI: Self-hosted (private model) (llama-3.3-70b) · local — nothing leaves this PC”, and Quire's draft header “AI: Self-hosted (private model) · local · Local-only”. Point the same seat at Claude and both chips say that instead. The privacy answer does not stop at the settings window — it rides along to the moment somebody has to sign off the result.
Views accumulate tricks — an element painted red for a meeting, a category halftoned, a filter left over, thirty things hidden to tidy a screenshot. Reset View scans the active view, shows exactly how many of each it found, and clears only the kinds you tick — in one undoable transaction that keeps every annotation, dimension and tag, and keeps the view on its sheet. What it cannot reach, it tells you.
To un-trick a view by hand you spelunk the V/G dialog override by override and Reveal Hidden Elements one element at a time — or you duplicate the view and lose its identity.
The whole input half is a read-only preview — nothing writes until you pass one confirm dialog. The output is a single named transaction with a receipt you can believe.
Tap Input or Output to isolate a half — the other collapses.
The window opens scanning, and lands on the view's name, its template, and the four counts. Nothing has been touched yet.
The window opens on “Scanning the active view…” and lands on the view's name, kind and template line, with the four counts — Element, Category, Filter, Hidden. The probe checks 21 override channels, so an element whose only trick is a hidden fill pattern or a forced detail level is still caught. Sheets and schedules are declined in plain words: “Sheets have nothing to reset — open a view instead.”


“Element graphic overrides (colour, line, pattern, transparency, halftone)” is one line on screen and twenty-one questions underneath — six about lines, six about surface patterns, six about the cut, and three about the element as a whole. Five of those are the ones simpler tools skip: the four pattern-visibility tick boxes, which default to on, so an unticked one is itself an override, and a detail level forced away from the view's own. Every element in the view is asked all twenty-one.
Four kinds default on; resetting the dependent views is opt-in and only offered when dependents exist. And when the view template governs categories or filters, an amber band says so before you press anything — “reset can't clear those here; edit the template” — because clearing something the template will silently re-impose is worse than not clearing it.


Reset view is live only while three things hold together: the view carries overrides at all, the scan found something, and at least one kind is ticked. Untick all four and it greys out with the counts still on screen — 214, 3, 5 and 12, none of them at risk. The same guard covers views with nothing to reset: on a sheet the whole list greys and the live line of the header reads “Sheets have nothing to reset — open a view instead.”


A permanent card lists the Revit API's blind spots — per-edge Linework, a linked model's display settings, and overrides or Hide-in-View on elements inside links — each with its manual route: the Linework tool set to By Category, Reveal Hidden Elements, Visibility/Graphics ▸ Revit Links. The one promise Reset View refuses to make is “100% pristine”, because the API cannot keep it.


“Every annotation, dimension and tag is kept. This can be undone with Ctrl+Z.” — the dialog's own words.
One dialog stands between the preview and the write. Then a single named transaction, a receipt in a full sentence, and an immediate rescan so the counts visibly drop.
Reset view is the only button that writes, and it asks first. The question names the view it is about to touch — and counts its dependent views if you ticked them — then promises what it keeps: every annotation, dimension and tag, with Ctrl+Z as the exit. The window is modeless, so that name is your last check that it is still aimed at the view you mean. Cancel costs nothing; the preview stays on screen.
Every clear runs inside “BIMIO Reset View — reset overrides”: element, category and filter overrides reset to defaults, hidden elements revealed in a batch with a one-at-a-time fallback so one bad id never loses the rest. The view is reset in place, never duplicated — it keeps its sheet placement, its view references, its dependents. And if Revit rolls the commit back, every counter zeroes, so the summary cannot claim work that was undone — the receipt line says so instead: “Revit undid it at the last moment, so nothing was saved.”


Only category and filter graphics can belong to a view template. Per-element overrides and Hide-in-View never can — so under the strictest template in the office, the wall someone painted red still clears and the twelve things hidden for a screenshot still come back. The counts say it without arithmetic: Element 0, Hidden 0, Category still 3, Filter still 5, the amber band still up, and a receipt that names the template it refused to fight: “clear them in the template.”


The outcome is written in words, not a spinner: “Reset 214 element overrides, 3 category overrides and 5 filter overrides, and un-hid 12 elements across 1 view.” — with “Some items were skipped — see the log.” when that is true, and the template note when kinds were left untouched. The window rescans immediately, so the receipt and the evidence sit side by side: here one element refused, the sentence says 213, and the Element count still reads 1 — together, the 214 the scan found.


Nothing is bound at open time — every scan reads whatever view is active now. So one window walks a whole set: change view in Revit, then press Rescan — or click Reset View on the ribbon again, which rescans the view in front instead of only raising the window — read the four counts, reset the ones that warrant it. A reset always lands on the view of the last scan, the one the question names, and only in the model it was scanned in: with another model in front it refuses in the receipt line — “Nothing was reset” — and tells you the way back: “Switch back to it, or press Rescan.” A manual rescan clears the previous receipt rather than leaving a sentence hovering over numbers it no longer describes. And Log opens the folder each run is written to, which is where “Some items were skipped — see the log.” is sending you.


Every Revit user has lost an hour to an element that simply is not there. Trace picks the element — in the model, inside a link, or by ID — and runs its visibility checklist across any views you choose, live, in the order an expert would ask. Green means ruled out; amber and red are the app's own “possible cause” and “definite cause”. A handful of causes fix themselves in one click. Revit 2024–2027.
Revit has a dozen ways to hide something and no way to ask which one it was.
Trace is purely on-demand and read-only — no event subscriptions, no persistence. The only writes are the one-click fixes you ask for, each in its own transaction, each one Ctrl+Z away.
Pick element… hands Revit the click — “Trace: click the host element you can't see.” — and In link… Tab-cycles into linked models. Or type an ID, or just keep your current Revit selection: a whole multi-selection becomes a batch — up to 250 at once. Then choose the views: the active one, or any set of printable views from the picker. And Trace remembers which model you picked in: switch model and the pick is cleared rather than run against the wrong file.


Analyze sweeps card by card — Existence & selection before Visibility & graphics before View extent and View context — each row lighting up, then landing green, amber or red, one step at a time so the order teaches; the Fast toggle skips the animation for bulk runs. Finished views collapse, causes sort to the top, and the view's summary settles on its verdict: Found the cause.


One render walk per view asks Revit what it truly drew. When every rule lands green and the walk says drawn, Trace refuses to shrug: “No cause found — and Revit IS drawing this element here. You're likely looking at the wrong place, it's behind something, or it's off-screen.” And when temporary hide/isolate blinds that walk, Trace says so rather than guess.


On every row that lands green, amber or red, Show where opens the view and highlights the element; on a red or amber one, Fix it repairs the reversible causes — temporary hide/isolate, a category turned off, hidden in view, a hidden sub-category, workset visibility — inside one transaction, one Ctrl+Z, then re-runs just that check so you watch it flip green, and if Revit rolls the change back, the headline says so instead of claiming it. And when a view template owns Model Categories, the category fix refuses and names the template, instead of committing a change Revit would silently revert.


Select fifty elements and Analyze: every check folds its answers into one row that never implies more than it covered — “3 of 50 elements —” followed by the check's own sentence when it hits some, “Ruled out for all 50 elements.” when it clears them, and a counted note when any element could not be evaluated. Select N affected grabs the whole flagged set in the view; the per-element Fix it steps aside, so a green row can never claim it fixed a crowd.


Find a view where it shows walks the printable views for the first one where the element has geometry to draw, switches to it and zooms. Across many views the headline keeps score — “Cause found in 2 of 6 views.” — and Stop keeps the partial results, so nothing is lost to impatience. The built-in manual is generated from the same registry as the checks themselves, so it can never drift from what Trace actually tests.


Copy findings puts the causes on the clipboard, headed “BIMIO Trace — why can't I see this element?”, ready for an issue or an RFI. Export report writes a self-contained HTML report in the language BIMIO is set to — the diagnosis and its narrative, the verdict breakdown, every check, and the full how-to-fix manual — and opens it. In Lens, the Trace card carries a Run button: pick the views and it lists only the definite and possible causes for the selected element — or tells you it shows in the views you checked.
This is an actual HTML report Trace exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Revit has no minimap: zoomed in on a large plan, finding where you are means zooming out and back in. Press Atlas and every drawing area on screen gets a card in its corner, with the whole view in miniature and a blue box over the part you are looking at. Drag the box and the view follows; pull its handles to zoom; click the thumbnail to jump. It only reads, it stays on until you press it again, and it comes free with any BIMIO licence.
Zoomed in to work on a large plan, nothing on screen tells you which part of the building you are looking at.
Atlas is a switch, not a window. It stays over the drawing while you open views, switch tabs and change model, until you press it again, and its cards close with their model.
Atlas sits on the Misc panel of the BIMIO Misc tab, right of Lens: Lens says what the element is, Atlas says where you are. Press it and each drawing area on screen gets a card in its bottom-right corner: the whole view in miniature, a blue box over the part you are looking at, and the view's name on the bar above, with its level first on a floor or ceiling plan. A tab behind another gets its card when it comes to the front. Press Atlas again and every card goes.
The box is the part of the view on screen, and it works both ways. Drag it and Revit pans with it, live; pull one of its eight round handles, or roll the wheel over the thumbnail, to zoom; click anywhere else on the thumbnail and the view jumps there. Pan or zoom in Revit and the box follows you instead. The thumbnail has the shape of its drawing area, so the box always has the shape of what you see. None of it touches the model: moving the view is not a change to the project, so Atlas never opens a transaction.
Four buttons on the bar work on the thumbnail, never on the view: − and + set how much ground it covers, the frame button brings it back to the whole view, and ⟳ redraws it with the drawing as it is now — the picture is taken when the card appears, and redraws by itself only when the crop region changes. Zoom so far into the plan that the box would shrink to a speck, and the thumbnail closes in around it by itself, then opens out again as you zoom back. Zoom out past the edges of the view and it grows around the drawing instead of chasing you.
With the window split, or Revit across two monitors, every view on screen has its own card in its own corner, with its own size and its own thumbnail zoom. Drag a card by its bar to put it anywhere, and right-click the bar to send it back to its corner; pull its edges, or Ctrl + wheel over the thumbnail, to resize it. The pin locks it where it is, and ✕ takes Atlas off that view only, until you reopen the view or switch Atlas off and on. The cards never take the keyboard, so your shortcuts keep going to Revit.
Atlas maps floor, ceiling, structural and area plans, sections, elevations, detail and drafting views, legends and sheets. On a sheet the thumbnail is the paper. If the sheet carries a 3D or realistic view, Atlas does not wait for Revit to render it: it draws the other views into their viewports and leaves that one as a crossed frame. Activate a viewport and the card stays the sheet's, with the box following you inside it. An orthographic 3D view gets a card that says why it is empty: “Atlas cannot map a 3D view. It works on plans, sections, elevations, drafting views, legends and sheets.”
Script is a library of scripts that run on the open model. C# comes first — it is compiled before a line of it runs — then Python 3.12, embedded with nothing to install, and VB.NET. Paste the Python you wrote for a Dynamo node and it runs as it is; or describe the job and BIMIO Synapse drafts it with the AI account your office connected. In Automatic mode a run is one named transaction that Ctrl+Z takes back, and a script can be sealed into the .rvt so the model carries it. Script sits on the BIMIO Misc tab, free with any BIMIO licence, in Revit 2024–2027.
Ten lines that rename, audit or export are worth keeping — and today they live in a Dynamo graph, a macro module or somebody's Downloads folder.
The input is a script in the library — typed, pasted or drafted once. The output is what the rest of the team gets: a Run button, a run they can undo, and a script that can live in a shared folder or inside the model.
Tap Input or Output to isolate a half — the other collapses.
The library is the front door; each script opens in an editor of its own.
Script opens on a list, not on an empty editor. The first time, nine starter scripts are waiting — five in Python 3.12, three in C#, one in VB.NET — each with a name, a category, tags, and a line that says what it does and whether it only reads. The two that change the model wear a “writes” badge, so a one-click Run never surprises. Search looks in the name, the description, the tags and the code itself: type ROOM_NAME and the two scripts that read that parameter are what is left. Every column but Actions filters from the funnel in its header, and Group by splits the list by category, language, tag or source when it grows.


| Name | Language | Category | Tags | Last run | Model | Actions |
|---|---|---|---|---|---|---|
Count elements by category Counts the model elements (instances, not types) per category and prints the twenty largest. Read-only. | Python 3.12 | Model info | categories, report | never | Not sealedSeal | Run |
Create a placeholder sheetwrites Writes: creates one placeholder sheet numbered from the constants at the top, inside a transaction the script opens and commits itself (Manual mode). Shows how a script manages its own transaction. | C# | Sheets | sheets, create | never | Not sealedSeal | Run |
Export room list to CSV Writes number, name, level and area of every placed room to a time-stamped CSV on your Desktop and prints the path. Reads the model, writes a file. | Python 3.12 | Export | rooms, csv, export | never | Not sealedSeal | Run |
Find unplaced rooms Lists the rooms that exist in the model but are not placed (no location, zero area). Read-only. | C# | Model info | rooms, audit | never | Not sealedSeal | Run |
List levels Prints every level with its elevation in the project's units, lowest first, and returns the count. Read-only. | Python 3.12 | Model info | levels, report | never | Not sealedSeal | Run |
Rename selected views with a prefixwrites Writes: adds the prefix at the top of the code to the name of every selected view (templates skipped). Select views in the Project Browser first; with nothing selected it does nothing and says so. One transaction, undo with Ctrl+Z. | C# | Views | views, rename | never | Not sealedSeal | Run |
Select all walls of the same type Select one wall first: the script selects every wall in the model that shares its type. Changes the selection only, never the model. | Python 3.12 | Selection | walls, selection | never | Not sealedSeal | Run |
Sheet list Prints every sheet as number — name, sorted by number, and returns the count. Read-only. | VB.NET | Sheets | sheets, report | never | Not sealedSeal | Run |
Warnings summary (pyRevit style) Groups the model's warnings by description and prints them most frequent first. Written the way a pyRevit script is (__revit__, clr.AddReference) to show that such scripts run here as they are. Read-only. | Python 3.12 | Model info | warnings, audit, pyrevit | never | Not sealedSeal | Run |
Double-click a row and the script opens in a window of its own. The language is at the top — C# first, then Python 3.12 and VB.NET — and the line under it says what you write: in C#, a method body, like a Revit macro. No class, no project, no build. Around the code is everything the list shows — name, category, tags, description — and the two answers that matter before anyone presses Run: does it write to the model, and who owns the transaction. Automatic wraps the whole run in one transaction named after the script; Manual lets the script open its own. doc, uidoc, uiapp, app and selection are already there; Print(x) writes a line and return x hands back a value. Run — or Ctrl+Enter — executes what is on screen without saving it; Ctrl+S saves, Ctrl+Shift+Enter saves and runs.
const string Prefix = "WIP - "; var views = selection.OfType<View>().Where(v => !v.IsTemplate).ToList();if (views.Count == 0){ Print("Select the views first (in the Project Browser) — nothing renamed."); return null;} int renamed = 0;foreach (var view in views){ if (view.Name.StartsWith(Prefix)) continue; try { view.Name = Prefix + view.Name; renamed++; } catch (Exception ex) { Print($"Could not rename '{view.Name}': {ex.Message}"); }}Print($"{renamed} of {views.Count} views renamed");return renamed; New script opens the editor with the Ask AI pane already out. Describe the job in plain words and BIMIO Synapse — the AI connection the whole suite shares, free on the same tab — drafts it in the language selected at the top, with a paragraph saying what it does and what it touches. Nothing lands in your code until you say so: Use this code, Append or Discard. The line under the buttons names the provider and says whether your request leaves the machine; with a self-hosted model it reads “nothing leaves this machine”. Improve changes the code you already have; Fix sends the code and the last error, and only lights up after a failed run. With no AI provider connected in Synapse, the pane says so and offers Open Synapse settings — and everything else in Script works the same.
Collects every door instance, prints the id and level of each one whose Mark is empty, and returns the count. Read-only: it changes nothing.
This is why C# comes first. Press Run and the script is compiled before any of it executes, so a mistyped name stops right there: the output says Compile, quotes the compiler, and “line 17” puts the caret on it — the line stays marked in the gutter until you edit it. A Python script cannot promise that: it fails on the line it reaches, an Automatic run is rolled back, and the traceback waits under Show details. Either way, with Synapse connected, Fix in the Ask AI pane sends the code and that error, and you read the answer before you take it.
int renamed = 0;foreach (var view in views){ if (view.Name.StartsWith(Prefix)) continue; try { view.Name = Prefix + view.Name; renamd++; } catch (Exception ex) { Print($"Could not rename '{view.Name}': {ex.Message}"); }}Print($"{renamed} of {views.Count} views renamed");return renamed; Most Python written for Revit was written for Dynamo's Python node. Pick Python 3.12, paste it, press Run: clr.AddReference('RevitServices') is accepted, DocumentManager.Instance.CurrentDBDocument is the active document, TransactionManager's calls fall inside the run's own transaction, IN[0] is whatever is selected in Revit, UnwrapElement(x) gives x back, and OUT shows as the result. A script written the pyRevit way — __revit__, clr.AddReference — runs too; one of the starter scripts is there to prove it. Python is CPython 3.12, embedded: nothing to install and no pip — the standard library, plus any folders you list in Settings. What does not come along is Dynamo itself: a reference to RevitNodes, ProtoGeometry or DSCoreNodes raises an ImportError that says so.
import clrclr.AddReference('RevitAPI')from Autodesk.Revit.DB import FilteredElementCollector, BuiltInCategoryclr.AddReference('RevitServices')from RevitServices.Persistence import DocumentManager doc = DocumentManager.Instance.CurrentDBDocumentdoors = FilteredElementCollector(doc).OfCategory(BuiltInCategory.OST_Doors).WhereElementIsNotElementType().ToElements()OUT = "{0} doors".format(len(doors))From here on nobody needs to read the code: the list says what each script does, whether it writes, and how its last run went.
Three places a script can live, one way to run it.
Run is the last column of the list, and the line at the foot of the window names the model it will land on before you press it. While the script runs, Revit and the window wait — there is no Stop — and then the drawer opens: ok or error, the time it took, what the script printed and the value it returned. If it changed the model, the header counts what was added, modified and deleted and reminds you how to take it back: in Automatic mode, the default, the whole run is one transaction named after the script in Revit's Undo list, so Ctrl+Z undoes all of it. If the script throws, that transaction is rolled back; if Revit had something to say when it committed — a warning, or the reason it refused — that is copied into the output. The list always runs the saved code, and says so when an editor holds changes it has not saved. Script itself never saves and never synchronises.
| Name | Language | Category | Tags | Last run | Model | Actions |
|---|---|---|---|---|---|---|
Rename selected views with a prefixwrites Writes: adds the prefix at the top of the code to the name of every selected view (templates skipped). Select views in the Project Browser first; with nothing selected it does nothing and says so. One transaction, undo with Ctrl+Z. | C# | Views | views, rename | just now✓ | Not sealedSeal | Run |
A script is one small file ending in .script.json. Settings lists the folders the library reads: yours first — new scripts are saved there and it cannot be removed — and any folder you add: a share, a synced SharePoint or OneDrive folder. Every script in it appears, with a “team” badge, in the list of everyone who has added that folder, and Group by Source splits the list into Mine, each team folder and This model. The same window sets the language new scripts start in, the folders Python may import from and the editor's font size, and brings back any starter script you deleted without touching the ones you edited.
The Model column answers one question per script: does the open model carry it? Seal stores a copy inside the model — one transaction, Ctrl+Z undoes it — and your file stays where it is. From then on the script goes wherever the .rvt goes: a colleague who opens the model with BIMIO finds it listed as “In model only”, runs it from there, and Keep a copy saves it to their own library. Change the code afterwards and the pill turns “Sealed · outdated” until you Re-seal. Sealed scripts are also one of the things Graft can carry from one project to the next. Projects hold them; families cannot.
| Name | Language | Model |
|---|---|---|
List levels Prints every level with its elevation in the project's units, lowest first, and returns the count. Read-only. | Python 3.12 | Not sealedSeal |
Rename selected views with a prefixwrites Writes: adds the prefix at the top of the code to the name of every selected view (templates skipped). Select views in the Project Browser first; with nothing selected it does nothing and says so. One transaction, undo with Ctrl+Z. | C# | Sealed · outdatedRe-seal |
Renumber roomswrites | C# | SealedUnseal |
A copy of the script as it is now is stored inside the model (one transaction, Ctrl+Z undoes it). It travels with the .rvt and with Graft; your file stays as it is.
| Name | Language | Model |
|---|---|---|
Renumber roomswritesmodel | C# | In model onlyUnseal |
A library that several people and several Revit sessions write to has to be careful. Delete moves the files to the library's .trash folder, where Open folder recovers them. Save notices when the script changed on disk after you opened it — another Revit, a teammate — and asks before overwriting, keeping the other version in .trash. Closing an editor with changes asks; if Revit closes it for you, the unsaved text is kept as a recovery copy, and the editor says where the next time it opens that script. A file the library cannot read is reported in a band above the list and left exactly as it is — and so is a settings file it cannot read, until you choose to replace it.
2 files move to the library's .trash folder, where Open folder can recover them. Nothing is erased.
This script was changed on disk after you opened it (another Revit or a teammate).
Overwrite it with your version? The other version is kept in the library's .trash folder. Cancel keeps your changes here, unsaved.
Every button on BIMIO Misc comes with any BIMIO licence. The story runs across the tab from left to right — Misc, Select & Find, Tags & Notes, Views, Sheets & Sets, Model, Draft — and then every tool's own window. Click a button in the ribbon above to jump straight to it.
The tab opens with the suite's free apps: Lens, Atlas, Script and Synapse, told in full above; the Hub, with the state of every BIMIO app for this project in one place; and Livery, Sugar and Vigil, stacked. Its Misc button opens the hub: a search box with every tool in it, grouped by the work it does. It matches on the words people really use — in English and Spanish, misspelled, abbreviated, and under the names of the tools it absorbed. Type “cotas” and Along Path appears; type “impacto” and IDs does — try it, this is the real catalogue. While you type it also lists the apps that moved to the BIMIO tab, such as Stencil, under Suite apps; those are bought on their own.


Fence a run once and choose any combination of outputs: an ordered dimension chain, by-category tags on everything crossing the corridor, spot elevations / coordinates plus room tags, family instances distributed every X mm (or N spread evenly), and perpendicular sections named in sequence. Dimensions, tags and spots run in plans and in sections / elevations; placing families and cutting sections need a level-based plan. Every pass shares the same picked line and commits in one transaction, with per-pass totals reported — and if Revit rejects the run the whole gesture rolls back untouched.
IDs takes any pasted list of element ids and selects them, finds what owns them, or asks Revit what a delete would take with them. View Locator says which sheet hosts the active view and jumps to any sheet. Find & Replace changes text across the model — notes, sheet and view names, rooms, parameters — after showing every change, before and after. And Measure, which you reach from the hub, now gives every point's coordinates as well as the legs: from the internal origin, the project base point or the survey point.


A ruler that remembers. Pick point after point — in a 3D view they snap onto geometry, in a plan or section they land on the view's work plane — and press Esc when you are done. You get every leg with its straight distance, its run in plan and its ΔX, ΔY and ΔZ, plus the total walked and the straight line from the first point to the last, and every point's coordinates from the internal origin, the project base point or the survey point (shared coordinates) — one point alone is enough for those. Every number is in the project's own units, and the whole table copies to the clipboard in one click. Read-only: it draws nothing, writes nothing and leaves no undo step.
Along Path fences one run and lays dimensions, tags, spot elevations, families and sections along it, every ticked pass in one transaction. Tidy batch-edits the tags in a view — swap the type, force leaders on or off, find the orphans — and its Tags tab now lists room, area and space tags too; its Arrange tab lines up the annotation you select. Link Keynote fills the user keynotes Revit's own command placed, from a memory kept inside the model, and Room Dimensions draws one chain per axis round the rooms you pick.


Revit's API cannot create a user keynote: a tag's Key Source (which mode it is in) is read-only, so it can never be switched into user mode from code, and an existing tag's link reference cannot be re-pointed either — every route to CREATING one from the API is a dead end. Only Revit's own “User Keynote” command can place one. So Link Keynote does not try to place anything: place the (blank) tag with Revit's own command, and this tool fills its code — reading the family/type of whatever the tag points at, linked or in this model, and looking it up in a memory that lives inside the .rvt, so it travels with the model and the whole team inherits it. Sweep the active view, fill just the tags already selected, or turn on auto-fill and every user keynote gets its code the instant it is placed. Anything the memory has never seen opens the Learn panel once — Revit's own keynote dialog never appears.
Datum Tools sets the heads and extents of grids and levels across views, with a live preview of where each head lands, and now does section lines too: head, tail or nothing at each end, by screen side or as this view shows them, and this view's line ends copied to the rest. Revit lets only its own mouse set those per view, so the views are opened one by one and driven for you. Choose the views with Views I pick…, keep a setup as a preset in the project, and the window opens as you last applied it. Category Switch, Template Diff and the Navigator drop-down — Same spot everywhere, Model health, bookmarks — share the panel with Reset View and Trace, told in full above.


Three questions, one window, and a live preview of the active view so you SEE every head land before touching anything. WHICH datums: the current selection, a pick in the model, or all grids/levels. WHAT to do: show/hide heads per SCREEN side (top, bottom, left, right — with one-click corner presets), copy this view's 2D extents across, reset dragged 2D extents back to the model, or stretch the 3D extents to cover the whole model. WHERE: this view, every sheet, sheets by number prefix, sheets you pick, or views you pick — on a sheet or not. Sides are re-translated per view, so a level keeps its head on the correct end in the north AND the south elevation. SECTION LINES work the same way, with what is theirs: at each end the head, the tail or nothing — by screen side, or as this view shows it — and the line's ends where this view has them. Revit keeps that per view and only its own mouse controls set it, so the views are opened one by one and driven for you, and the result says what could not be set and why.
Titles lines up viewport titles and edits title blocks across sheets, and like Datum Tools keeps presets in the project and remembers its last setup. Viewports syncs viewport positions across sheets — by title block, by sheet coordinates or, new, by model coordinates, so the same point of the building lands on the same spot of every sheet — and swaps their views. Check runs the pre-issue checks on a sheet set and answers GO or NO-GO; Sheet Graphics adds scale bars, key plans and QR codes in one pass; Batch Revision assigns or removes a revision across many sheets and can now delete its clouds with it. The sheet picker they share keeps named selections as presets — in the model for the team, or on this computer.


The last gesture before you print: pick the package — a print set, sheet collection or filter — and every cheap, read-only pre-issue check runs in one pass. Viewport titles (collisions, off-sheet drift, gap and length deviations, dishonest custom scales), set integrity (references leaving the package, temporary view modes, views without a template, empty sheets) and revisions (sheets missing the document's latest revision) all fold into one combined report. One verdict — GO or NO-GO — and every finding's Show button jumps straight to the culprit.
Warnings lists every warning Revit keeps in the model, one row each, in a window that stays open while you work: pick a category from the pills, double-click a row or press Go to and Revit selects and shows its elements, and in a workshared model it says who last changed them. It never writes — Revit offers no way to resolve a warning from outside. Clean counts the model's junk before it sweeps it, now including links that are not placed or whose file is missing. Renumber, Worksets, Match — with its own Apply beside Preview — DWG Manager, Group Audit and Make Pattern complete the panel.


Every warning Revit keeps in the model, one row each, as in Review Warnings — but in a window that stays open while you work. Pick a category from the pills over the table, or filter and sort any column from its header. In a workshared model it also says who last changed the elements of each warning, read in the background while you work. Double-click a warning, or press its Go to, and Revit selects and shows its elements; pick several rows to show or select them together, copy their ids, or export what is shown to Excel — every row, and the same rows counted by kind. It never changes the model: Revit offers no way to resolve a warning from outside, so it takes you to the elements and you fix them.
Draft holds the tools that act directly on model elements and have not yet earned a permanent home; where each one settles is still open. Recast turns floors into toposolids and back with the same outline, shape-editing points, level and offset, merges several into one, takes heights or subdivides — and checks every piece before anything is built. The Draft drop-down adds Hide in Views (elements of a linked model included, through Revit's own Hide in View), Referenced Elements (from tags and dimensions to what they point at), Merge Styles (one style replaced by another wherever it is used), Walls, Replace Materials, Region Tools and Attached Detail Groups.


Four ways to work with the floors and toposolids you pick. Convert each turns each one into another floor or toposolid type, keeping its outline, every shape-editing point, the split lines, the level and the offset. Merge into one folds several into a single element. Take heights edits one existing floor or toposolid in place so it follows the surfaces of the others where they lie over it — its id, tags and sub-divisions stay. Subdivide gives one toposolid a sub-division per other element, from its outline clipped to the host. Every row says what happens to that element and, when something is wrong, which element causes it; the result is measured after it is built. One transaction, never synchronised.
Every button on the tab, panel by panel in the ribbon's order, each with its own window drawn as it really is — its tabs, its lists, its buttons — and the tools only the hub reaches beside the panel of their kind. Both come from the app itself: the catalogue from the registry that builds the hub in Revit, the windows from each tool's own interface. Each one says whether it only reads your model or modifies it.
One window for the whole suite: a health header (score, sync cadence, insights from the shared project store) plus a tile per app — schedules pending sync, tables needing refresh, open clashes, standards violations, review progress — each with an Open button. Where Lens reads the selected element, this reads the whole project; export the shareable HTML report from the window, and nothing leaves this machine.
With three models open, every tab looks the same and one wrong click lands in the wrong model. Livery gives each model a colour and puts it on every one of that model's document tabs, full strength on the view you are in.


The sugar sachet with something printed on it.


Watches the folders that matter — deliveries, links, a Desktop Connector path — and tells you what was added, changed, renamed or deleted since you last looked, both live while you work and as a summary when you open the model. It doubles as an explorer inside Revit: double-click anything to reveal it in Windows, and the watched paths belong to the project and can be sealed into the model so the other models find them too.




| Where | Name | Size | File date | Who | Spotted |
|---|---|---|---|---|---|
| Added2 | |||||
| Deliveries \ 2026-08-28 Structure | MT-STR-Block A-Ground floor.rvt | 246 MB | today 09:12 | H. Okonjo | 18 min ago |
| Survey \ Point clouds | Marina-quay-survey.dwg | 9.7 MB | 26 Aug 11:05 | L. Fairweather | 2 days ago |
| Modified2 | |||||
| Links \ Architecture | MT-ARC-Block A.rvt | 312 MB | today 08:47 | R. Whitlock | 42 min ago |
| Deliveries \ Schedules | Door schedule — issue P03.xlsx | 268 KB | today 07:55 | — | 3 h ago |
| Renamed1 | |||||
| Deliveries \ Drawings | MT-A-1201 Ground floor plan.pdf | 4.2 MB | yesterday 17:30 | — | yesterday |
| Deleted1 | |||||
| Links \ Services | MT-MEP-Block A-Level 02.ifc | 88 MB | — | — | 2 days ago |


| Name | File date | Who | Size |
|---|---|---|---|
| Drawings | yesterday 17:30 | 126 files | |
| Point clouds | 26 Aug 11:05 | 4 files | |
| MT-STR-Block A-Ground floor.rvt | today 09:12 | H. Okonjo | 246 MB |
| MT-A-1201 Ground floor plan.pdf | yesterday 17:30 | R. Whitlock | 4.2 MB |
| Door schedule — issue P03.xlsx | today 07:55 | L. Fairweather | 268 KB |
| Marina-quay-survey.dwg | 26 Aug 11:05 | L. Fairweather | 9.7 MB |
One box, three questions.






Instantly shows which sheet (number, name and detail number) hosts the active view — or, if the active view is a sheet, lists everything placed on it.


Revit can rename one thing at a time.


| Context | Before | After | |
|---|---|---|---|
| Text notes2 | |||
| L01 — Floor Plan | Drawn by Hadley & Roe | Drawn by Hadley Roe Architects | |
| L02 — Floor Plan | © Hadley & Roe 2026 | © Hadley Roe Architects 2026 | |
| Sheet names3 | |||
| Sheet A-101 | Hadley & Roe — Ground floor | Hadley Roe Architects — Ground floor | |
| Sheet A-102 | Hadley & Roe — First floor | Hadley Roe Architects — First floor | |
| Sheet A-140 | Hadley & Roe — Roof plan | Hadley Roe Architects — Roof plan | |
A ruler that remembers.


| Leg | Distance | In plan | ΔX | ΔY | ΔZ |
|---|---|---|---|---|---|
| 1 → 2 | 4200 mm | 4200 mm | 4200 mm | 0 mm | 0 mm |
| 2 → 3 | 5100 mm | 5100 mm | 0 mm | 5100 mm | 0 mm |
| 3 → 4 | 3900 mm | 3600 mm | 2400 mm | -2683 mm | 1500 mm |
| Point | X | Y | Z |
|---|---|---|---|
| 1 | 12000 mm | 8000 mm | 0 mm |
| 2 | 16200 mm | 8000 mm | 0 mm |
| 3 | 16200 mm | 13100 mm | 0 mm |
| 4 | 18600 mm | 10417 mm | 1500 mm |
Fence a run once and choose any combination of outputs: an ordered dimension chain, by-category tags on everything crossing the corridor, spot elevations / coordinates plus room tags, family instances distributed every X mm (or N spread evenly), and perpendicular sections named in sequence.


One window, two tabs.






Revit's API cannot create a user keynote: a tag's Key Source (which mode it is in) is read-only, so it can never be switched into user mode from code, and an existing tag's link reference cannot be re-pointed either — every route to CREATING one from the API is a dead end.




| Family (or category) | Type | Keynote code | Keynote text | Actions |
|---|---|---|---|---|
| Walls | Blockwork 140 — Fair faced | F10.110 | Blockwork wall, 140 mm, fair faced | Remove |
| Walls | F10.100 | Blockwork wall — general | Remove | |
| M_Single-Flush | 0926 x 2040 mm | L20.120 | Internal flush door, single leaf | Remove |
| Floors | Screed 75 mm on insulation | M10.210 | Cement and sand screed, 75 mm | Remove |
| Ceilings | Plasterboard on MF grid | K10.220 | Suspended plasterboard ceiling, MF system | Remove |
Pick exactly which rooms to dimension (a room picker, like the sheet picker) and the aligned dimension TYPE to create, then Room Dimensions draws a dimension chain across each axis just outside each room.


Three questions, one window, and a live preview of the active view so you SEE every head land before touching anything.


Pick one or several categories or subcategories (e.g.


Pick two view templates and get every difference listed and grouped: which parameters each one controls; core settings (scale, detail level, discipline, display style); per-category visibility plus the graphic overrides people actually chase — halftone, transparency, detail level and projection/cut line weights; and the filters each applies.


Two tabs, one window.




Work on the viewports of many sheets from one window.




| SHEET | View 1 | View 2 | View 3 |
|---|---|---|---|
| A-101 Ground floor plan | DN 1 · Ground Floor Plan · Floor Plan | DN 2 · Ground Floor — Colour Scheme · Floor Plan | DN 3 · Entrance Canopy · Detail |
| A-102 First floor plan | DN 1 · First Floor Plan · Floor Plan | DN 2 · First Floor RCP · Ceiling Plan | — empty — |
| A-103 Second floor plan | DN 1 · Second Floor Plan · Floor Plan | — empty — | — empty — |
| A-201 Sections | DN 1 · Section A-A · Section | DN 2 · Section B-B · Section | — empty — |
| A-301 Bathroom details | DN 1 · Bathroom Plan · Detail | DN 2 · Bathroom Elevations · Elevation | — empty — |
The last gesture before you print: pick the package — a print set, sheet collection or filter — and every cheap, read-only pre-issue check runs in one pass.


| Kind | Finding | Where | Actions |
|---|---|---|---|
| Viewport titles4collisions, off-sheet drift, gap/length deviations, dishonest custom scales | |||
| OVERLAP | “Ground Floor — General Arrangement” title collides with viewport of “Ground Floor — Setting Out” | A-101 | Show |
| LENGTH | “First Floor — General Arrangement” line 182.0 mm | A-102 · viewport width 210.0 mm | Show |
| GAP | “Section A-A” gap 3.2 mm | A-104 · standard 5 mm (±1.5) | Show |
| SCALE | “Roof Plan” scale text ‘1:50’ | A-105 · view is 1:100 | Show |
| Set integrity4references leaving the package, temp view modes, missing templates, empty sheets | |||
| TEMP MODE | “Site Plan” is in Temporary Hide/Isolate — hidden elements will NOT print | A-100 | Show |
| NO TEMPLATE | “Ground Floor — General Arrangement” has no view template — graphics are unguarded | A-101 | Show |
| callout | “Stair Core — Section” points to “Detail 04 — Balustrade Fixing” | A-103 · NOT ON ANY SHEET | Show |
| EMPTY SHEET | No views and no schedules placed | A-106 | Show |
| Revisions3every sheet should carry the latest revision (seq 3 “Tender issue”) | |||
| NO REV | “A-104 — Sections” does not carry the latest revision | latest is seq 3 “Tender issue” | Show |
| NO REV | “A-106 — Door Schedule” does not carry the latest revision | latest is seq 3 “Tender issue” | Show |
| LEGEND CLOUD | A revision cloud sits on the legend “Drawing Notes” | a cloud on a legend does NOT put the revision on the sheet the legend is placed on | Show |
Every sheet overlay in one window: coordinate grid rulers, graphic scale bars, the section-locator mini plan, the cover mosaic, real-view key plans, per-sheet QR codes and automatic match lines.








| Sheet | Base view | Scale |
|---|---|---|
| A-101 — Ground floor plan | FloorPlan: KEYPLAN_Site | 1 : 100 |
| A-102 — First floor plan | FloorPlan: KEYPLAN_Site | 1 : 100 |
| A-103 — Second floor plan | FloorPlan: KEYPLAN_Site | 1 : 100 |
| A-201 — Sections A-A and B-B | Section: KEYPLAN_Long section | 1 : 200 |
| A-301 — East and west elevations |


Close the issue in one gesture: pick the sheets (active sheet or any set, including real print sets), pick the revision — or stage a new one, created inside the same Apply transaction — and assign it to or remove it from every ticked sheet at once.


| Number | Name | Revisions | |
|---|---|---|---|
| A-101 | Ground Floor Plan | Seq 2 · Tender issue | |
| A-102 | First Floor Plan | Seq 2 · Tender issue | |
| A-103 | Second Floor Plan | — | |
| A-201 | Elevations — North & East | Seq 1 · Planning · cloud | |
| A-202 | Elevations — South & West | Seq 1 · Planning · cloud Seq 2 · Tender issue | |
| A-301 | Sections A-A & B-B | Seq 2 · Tender issue |
Shows the count of each junk family BEFORE touching anything: views, legends and schedules placed on no sheet, unplaced rooms, view templates nobody uses, filters applied nowhere, links not placed or whose file is missing, and the same unused families/types list as Revit's native Purge Unused.


Every warning Revit keeps in the model, one row each, as in Review Warnings — but in a window that stays open while you work.


| Warning | Elements | Category | Last changed by | Element ids | Actions |
|---|---|---|---|---|---|
| Highlighted walls overlap. One of them may be ignored when Revit finds room boundaries. | 2 | Walls | a.rivera | 1048211, 1048236 | Go to |
| Room is not in a properly enclosed region | 1 | Rooms | m.chen | 1051730 | Go to |
| Elements have duplicate 'Mark' values. | 3 | Doors | a.rivera | 1052004, 1052011, 1052019 | Go to |
| There are identical instances in the same place. This will result in double counting in schedules. | 2 | Furniture | j.okafor | 1060412, 1060413 | Go to |
| Highlighted floors overlap. | 2 | Floors | m.chen | 1048302, 1048355 | Go to |
One numbering tool for everything.




| Element | old → new | status |
|---|---|---|
| M_Single-Flush · 0926 x 2040mm #1284531 | D-04 → D-01 | OK |
| M_Single-Flush · 0926 x 2040mm #1284604 | — → D-02 | OK |
| M_Double-Flush · 1526 x 2040mm #1284712 | D-02 → D-03 | DUP |
| M_Single-Flush · 0826 x 2040mm #1284788 | D-09 → D-04 | CLASH |
| M_Sliding-2 Panel · 1800mm #1284801 | D-11 → D-05 | HAS VALUE |
| M_Sliding-2 Panel · 1800mm #1284846 | — → D-06 | LOCKED |
Everything ownership in one window, four tabs.


| Name | Kind | Editable | Owner | Opened | |
|---|---|---|---|---|---|
| ARC-External walls | User-Created | Yes | jsmith | Yes | |
| ARC-Partitions | User-Created | Yes | jsmith | Yes | |
| ARC-Ceilings | User-Created | No | Yes | ||
| MEP-Ductwork | User-Created | No | r.okonjo | Yes | |
| STR-Frame | User-Created | No | h.whitfield | No | |
| Shared Levels and Grids | User-Created | No | Yes | ||
| Project Info | Project Standard | No | Yes |


| Group type | Instances | Owner | |
|---|---|---|---|
| Toilet pod — accessible | 12 | jsmith | |
| Kitchenette — Type A | 8 | jsmith | |
| Stair core — Block A | 4 | ||
| Reception desk assembly | 2 | r.okonjo | |
| Window bay — repeat unit | 34 | ||
| Plant skid — AHU 01 | 6 | h.whitfield |


| Option set | Option | Primary | Owner | |
|---|---|---|---|---|
| Entrance canopy | Glazed canopy | Yes | jsmith | |
| Entrance canopy | Solid canopy | jsmith | ||
| Level 04 layout | Open plan | Yes | ||
| Level 04 layout | Cellular | r.okonjo | ||
| Roof plant screen | Louvred | Yes | ||
| Roof plant screen | Perforated mesh |


| User | Holding | What exactly | |
|---|---|---|---|
| r.okonjo | 3 worksets · 412 elements | MEP-Ductwork, MEP-Pipework, MEP-Containment | |
| h.whitfield | 1 workset | STR-Frame | |
| a.brennan | 86 elements | Basic Wall: SW-215, Door: FD30S single, Floor: Screed 75 | |
| s.mahoney | 2 worksets · 14 elements | ARC-Ceilings, ARC-Roof — Ceiling: MF suspended |


| Rule | Workset | What happens | Order | ||
|---|---|---|---|---|---|
| #1 External walls | ARC-External walls | 248 to move · 96 already there | ↑ ↓ | ✕ | |
| #2 Internal partitions | ARC-Partitions | 1204 to move · 12 skipped (8 in groups, 4 owned by others) | ↑ ↓ | ✕ | |
| #3 Ceilings and soffits | ARC-Ceilings | 312 to move · 41 claimed by an earlier row | ↑ ↓ | ✕ | |
| #4 Ductwork | Pick a workset | ↑ ↓ | ✕ | ||
| #6 Site and levels | ARC-Site | Off — 74 matched, left to the rows below | ↑ ↓ | ✕ |
Pick a source element, then the destinations: the current selection, clicked or box-selected in the model, whole categories, or a list for views and sheets.




| Categories | Source parameter | Target parameter (writable) | Actions | |
|---|---|---|---|---|
| Doors | Type Mark (type) | Mark | Remove | |
| Windows | Type Comments (type) | Comments | Remove | |
| Walls, Floors | Assembly Code (type) | Mark | Remove | |
| 3 categories | Fire Rating (type) | Comments | Remove |


The full inventory of CAD in the model — imported (embedded) and linked (external) — in one window.


Revit gives you no way to know whether the 40 identical flats, the 200 hotel rooms or the 30 “same” plant rooms are still the same.


| Instance | Where | Verdict | Missing | Extra | Got in | Params | Hosts | Mirrored | Notes |
|---|---|---|---|---|---|---|---|---|---|
| 482116 | Level 01 · Bedroom 04 | divergent | 2 | 1 | excluded members (Revit) | ||||
| 482350 | Level 02 · Bedroom 12 | divergent | 3 | ||||||
| 482233 | Level 01 · Bedroom 05 | divergent | 1 | ||||||
| 482467 | Level 02 · Bedroom 13 | identical | |||||||
| 482584 | Level 03 · Bedroom 20 | identical |
| Member | Detail | This instance | The others | |
|---|---|---|---|---|
| missing members2 | ||||
| Doors · Single-Leaf 926 × 2040 | Not present in this instance. | absent | 1 in 11/12 instances | |
| Lighting Fixtures · Downlight 120 mm | Not present in this instance. | absent | 1 in 10/12 instances | |
| differing parameters1 | ||||
| Doors · Single-Leaf 926 × 2040 | Fire Rating reads 30/30 here and 60/60 in 11 of 12 instances. | differs | 60/60 in 11/12 instances | |
Revit can only import fill patterns, never draw them.


Four ways to work with the floors and toposolids you pick.


| Element | Level | Height offset | Shape points | Verdict | |
|---|---|---|---|---|---|
| Concrete 250 · Floor · 1048211 | Level 00 | 0 mm | 86 · 2 split lines | Ready — 86 points, same outline, level and offset | Show |
| Concrete 250 · Floor · 1048236 | Level 00 | -150 mm | Flat | Ready — Flat, same outline, level and offset | Show |
| Paving 120 · Floor · 1048302 | Level 00 | 0 mm | 112 | Too deep — its lowest point is 420 mm below level + offset | Show |
Start from one element or many, then say where: tick views in the suite's view picker, or pick sheets — which here means the views placed on them.


| View | Type | |
|---|---|---|
| L01 — General Arrangement | Floor Plan | |
| L02 — General Arrangement | Floor Plan | |
| L03 — General Arrangement | Floor Plan | |
| Section A-A | Section | |
| L01 — Furniture layout | Floor Plan | |
| 3D — Coordination | 3D View |
Start from annotations — tags of any category, room, area and space tags, dimensions, spot elevations, coordinates and slopes — and it gathers every element they refer to.


Line styles, line patterns, filled region types, fill patterns, dimension types and text types, each listed with how many places use it and with the others that are the same style under another name.


| Style | What it is | Uses | Same as | Replace with |
|---|---|---|---|---|
| A-Thin dashed | W1 · RGB 0,0,0 · Dash | 1,204 | Dashed thin | Keep |
| Dashed thin | W1 · RGB 0,0,0 · Dash | 37 | A-Thin dashed | A-Thin dashed |
| Setting-out red | W2 · RGB 255,0,0 · Solid | 412 | Keep | |
| Red line (old) | W2 · RGB 230,0,0 · Solid | 9 | Setting-out red | |
| Hidden lines 2 | W1 · RGB 0,0,0 · Hidden | 0 | Keep |
Three wall gestures Revit makes hard.






Pick the categories to sweep, scan them to see which materials are really in use, then replace one material with another in a single transaction: material parameters on instances and on types, and the layers of wall, floor, roof and ceiling types.


Union two or more filled regions into one, cut them with straight lines or with another region, or move their boundaries onto a different line style — the merge Revit never shipped.








Revit only reveals an attached detail group one model group instance and one view at a time, through a dialog, so on a unit-plan job the annotation never gets turned on.




| Current name | New name | Verdict |
|---|---|---|
| Unit A — Kitchen dimensions | Flat A — Kitchen dimensions | Ready |
| Unit A — Door tags | Flat A — Door tags | Name taken |
| Unit A — Ceiling notes | Flat A — Ceiling notes | Ready |
| Unit B — Kitchen dimensions | Unit B — Kitchen dimensions | Unchanged |
| Core — Stair setting out | Core — Stair setting out | Unchanged |


| Current name | Name of the copy | Verdict |
|---|---|---|
| Unit A — Kitchen dimensions | Unit A — Kitchen dimensions — option 2 | Ready |
| Unit A — Door tags | Unit A — Door tags — option 2 | Ready |
| Unit A — Ceiling notes | Unit A — Ceiling notes — option 2 | Name taken |
| Unit B — Kitchen dimensions | Unit B — Kitchen dimensions — option 2 | Ready |
| Core — Stair setting out | Core — Stair setting out — option 2 | Ready |
Everything on BIMIO Misc comes with any BIMIO licence — one app, a bundle or the suite — and with the trial: the toolbox, Lens, Atlas, Script, Synapse, Reset View, Trace, the Hub, Livery, Vigil, Sugar and Navigator. Buy one app and all of it comes with it, on every Revit you install. The apps that started here and moved to the BIMIO tab, such as Stencil, are sold on their own.
This is an actual HTML report Misc exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
BIMIO Misc ships free with any BIMIO licence — the whole tab: the toolbox, Lens, Atlas, Script, Synapse, Reset View, Trace, the Hub, Livery and the rest. Revit 2024–2027, full trial, no card.