BIMIO is not a plug-in with a hundred buttons. It is focused apps on the BIMIO tab, grouped by the stage of the job they belong to, and a second tab, BIMIO Misc, with the free apps and the toolbox — every one of them written to the same rules about your model.
A Revit with a dozen add-ins is a Revit where nothing agrees: every tool invents its own window, its own idea of a warning, its own place to keep what it learned. You end up doing the integration yourself, in your head, every day.
Panels follow the job: set the project up, work on families, move data, check quality, prepare views and sheets — and a second tab, BIMIO Misc, that comes free.
BIMIO puts two tabs on the ribbon, right after Revit's own Add-Ins. On the BIMIO tab, Setup is what you do to a project once. Family Editor is where families are made and inspected. Data moves information in and out. QA / QC is everything that checks. Views and Sheets prepare what gets issued. A star marks a panel's flagship — the app most people open first — and it stands first, with the rest in alphabetical order; not every panel has one, and QA / QC and Views have two. Beside it, the BIMIO Misc tab holds the free apps and the everyday tools, in panels named after what they work on.
The rule is the tab. Every app on the BIMIO tab is one you buy, each under its own licence. Everything on BIMIO Misc comes with any of them: Lens, Atlas, Script, Synapse, Reset View, Trace, the Hub, the everyday tools — most with a button of their own, and all of them one search away in the toolbox — and the three that quietly change how Revit behaves. It is not a second purchase, and it stays for as long as your licence does.


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.
The first time Revit starts with BIMIO, a 14-day trial starts, and during it every app on both tabs opens. After that, a licence key decides: the apps it covers, and everything on BIMIO Misc with them. About › Licence, on either tab, shows where you stand — the days left, or what your key covers and when it renews — and takes the key: paste it, press Activate. Open an app your key does not cover and the same window says so by name instead of failing. The key checks in online every three days and keeps working offline for up to fourteen; and a glitch in the check itself — a licence file it cannot read, say — never blocks a click.
Lens, on BIMIO Misc, is a dockable panel with a card per app. Click a wall and Canon says which rules it breaks, Clash what it hits, Assay what is wrong with it, Ledger which keynote it carries. Each card is that app's own finding, and the card of an app you have not bought says so instead of guessing. This is what one suite buys you that a dozen plug-ins cannot.
Views to pick, worksets to take, sheets to print: across BIMIO a list is drawn as the same table, with the same header, the same ticks and the same rows. Its named columns carry a funnel that works like Excel's — sort A to Z or Z to A, search the values, tick the ones to keep, group the rows by that column — and a tick column has one of its own, to show only what is ticked. Ctrl or Shift picks several rows, and one tick reaches all of them. And where a picker has a Presets button, a selection you will want again is saved by name: in the model, so the team has it after your next synchronise, or on this computer, for you alone.
| View | Type | |
|---|---|---|
| Level 01 | Floor Plan | |
| Level 02 | Floor Plan | |
| Level 03 | Floor Plan | |
| Roof | Floor Plan | |
| Section A | Section | |
| Section B | Section |
One installer puts BIMIO into every Revit version you have, each with the build compiled for it — .NET Framework for 2024, .NET 8 for 2025, .NET 10 for 2026 (from its 2026.5 update) and 2027. It reads the computer and ticks the versions it finds, so the usual case is one click on Install. When a newer BIMIO is out, a notice says so at your next click, and About › Updates shows what is new and fetches the installer, which downloads only the parts that changed. Your settings, your rules and your project store follow you across versions.
About sets the whole suite, once, from either tab. Language: English, Español, or Auto, which follows Revit's own. Change it and every open window relabels on the spot — the ribbon too, its buttons, panel titles and tooltips, with no restart — and the reports the apps write come out in the same language. Only the names of the apps stay as they are: Clash is Clash in both. Theme: Light, Dark, or Auto, which follows Revit; pick Light or Dark and BIMIO sets Revit to match, so the ribbon and the windows never disagree. With several Revits on one taskbar, each one running BIMIO carries its year on the icon — R26 — and a second switch writes the year onto the Windows shortcuts too, after asking how many it will touch. And a window you resize opens next time where you left it. All of it lives in your Windows profile, not in the model, so none of it imposes itself on whoever opens the file after you.
An add-in that synchronises on your behalf is an add-in that can put half-finished work in front of the whole team. So no app in BIMIO does it — not as a setting you can switch on, not as a convenience at the end of a batch. There is not a single call to Revit's synchronise API anywhere in the suite. Where its name does appear in working code, it is on a list of things to recognise or to refuse: Sugar knows the dialogs that ARE the synchronisation, so it can tell the moment you press it — it watches the sync, it never performs one — and the AI that drafts scripts is told never to write that call. Taking ownership counts as writing to the central too, so it happens only where taking ownership IS the tool — Worksets, on BIMIO Misc — when you press Take Ownership, or for a saved set you armed yourself to be taken again after your own syncs on this computer; never as a side effect of something else. And when an app opens another model from disk — Graft reading a source — it opens it DETACHED from its central, which does not merely decline to sync: it makes syncing impossible.


| Name | Kind | Editable | Owner | Opened | |
|---|---|---|---|---|---|
| ARC-Ceilings | User-Created | No | Yes | ||
| ARC-External walls | User-Created | Yes | jsmith | Yes | |
| ARC-Partitions | User-Created | No | Yes | ||
| MEP-Ductwork | User-Created | No | r.okonjo | Yes | |
| Shared Levels and Grids | User-Created | No | Yes | ||
| STR-Frame | User-Created | No | h.whitfield | No |
Every app in the suite writes to the same log: one file per day, for every Revit version you have open, with the app and the Revit year as columns, so filtering to one is a search and collecting all of them is nothing at all. It opens with the session's version and the Revit year, names the document as it changes, and each line carries its thread — which matters more than it sounds, because only what runs on the UI thread can freeze Revit, and a freeze leaves a scope that was entered and never left. That is a signature you can search for; and a step that takes ten seconds or more closes as a warning, marked slow. Two things are worth saying plainly: nothing is ever deleted, only archived by month; and the file names your models, your paths and your Windows username, so it is yours to share, not telemetry that leaves on its own.
07:31:52.410 WARN bg#7 2026 Updates startup update check could not read the feed; will retry on next start07:36:15.298 INFO ui 2026 Opes ▶ sweep links07:37:09.882 WARN ui 2026 Opes ◀ sweep links — 54584 ms [mem 2140 MB] ⏱⏱ slow — 412 MEP runs from 3 links
Every licence brings the free BIMIO Misc tab with it, and every app you add joins the BIMIO tab, the same inspector and the same project store.