Loop hosts the suite's two Excel round trips in one window. Pick a source — Schedules or Families — take it to Excel, edit it there, and bring it back with every change reviewed against what you exported. Schedules edits values in bulk; Families renames families and types, edits their parameters and can mint new types from new rows. They are the same proven panels, hosted — and each source's badge tells you how much work the other one owes before you switch.
Schedules-to-Excel and families-to-Excel are the same loop: out, edit, bring it back under review. They used to live behind two buttons, in two windows — and the only way to know whether the other one owed you work was to open it and wait for its scan.
Loop has two halves. You pick a source and take it to Excel — that is the input. Then every change comes home through a preview you control — that is the output. Here is the loop, top to bottom.
Tap Input or Output to isolate a half — the other collapses.
Loop opens on the source you used last, with your search and filter restored. The segments at the top are the whole navigation: Families and Schedules, each with a live badge counting the work that side owes.
The BIMIO · Loop window hosts the suite's two Excel round trips behind one segmented switch. Each segment carries a live badge: how many schedules have Excel edits pending, how many families are waiting on the workbook — and hovering a segment gives you the source's own headline and how fresh its count is, so a number from an hour ago never poses as fresh. Ctrl+1 and Ctrl+2 jump straight to a source and Ctrl+Tab cycles; switching is free, because each pane is built once and kept alive — nothing rescans just because you looked away. And if one source ever breaks, it breaks alone: the other keeps working.
| Name | Category | Status |
|---|---|---|
| Door Schedule | Doors | Excel pending |
| Window Schedule | Windows | Revit changed |
| Room Schedule | Rooms | Up to date |
| Wall Types | Walls | Never exported |
The Schedules source lists every schedule in the project with a colour-coded status pill — Never exported, Up to date, Revit changed, Excel pending, Conflict, File missing — plus a per-row Configuration link and a Preserve or Itemise layout. Export to a formatted .xlsx with a frozen header, an autofilter, grey read-only cells and Yes/No dropdowns; edit anywhere Excel runs — no Revit licence needed — and a three-way diff keeps your edits distinct from whatever moved in Revit while the file was out. Unsupported schedules say why, instead of failing later.
| Name | Category | Setup | Layout | Status | |
|---|---|---|---|---|---|
Door Schedule | Doors | Configuration | PreserveItemise | Excel pending | |
Window Schedule | Windows | Configuration | PreserveItemise | Revit changed | |
Room Schedule | Rooms | Configuration | PreserveItemise | Up to date | |
Sheet List | Sheets | Configuration | PreserveItemise | Conflict | |
Coordination — Structure (linked) Includes elements from linked models — they can't be edited from the host. | Multi-category | Unsupported |
The Families source puts every family and type on a tri-state tree with the same status pills — filterable to pending sync, unplaced, placed or system families — round-tripped through the model's one canonical workbook. Rename families and types from Excel or with the rules engine (find & replace with regex, prefixes and suffixes, sequential numbering, chained steps, saved presets), edit type parameters in bulk, and add a row in the workbook to mint a new type: Revit creates it by duplicating a donor type in the same family, and the import preview marks the row as New type before anything is committed. Families are matched by name, and families themselves are never created. The naming convention is a live regex the pane checks as you type — publish it into the model and every seat adopts the same standard.
| Family / Type | Placed | Status | |
|---|---|---|---|
| Doors | |||
| Single Flushloadable | 24 | ||
| 926 × 2110 | 16 | Up to date | |
| 1010 × 2110 Accessiblewill become “DR_Single-Flush_1010x2110-ACC” | 8 | Excel pending | |
| Generic Models | |||
| Reception Deskin-place | 1 | Conflict | |
| Walls | |||
| Basic Wallsystem | 96 | Up to date |
Both sources land the same way: a cell-by-cell preview, your tick per change, one undoable transaction.
Whichever source it came from, every change passes the same gate: a cell-by-cell preview, your tick per change, one named transaction, one undo.
Before a single value is written, the Review changes dialog shows the diff: your Excel edits as old → new with a tick each, conflicts flagged and kept on the model's value unless you say otherwise, read-only edits shown but disabled, and rows that changed only in Revit listed as information. The Families preview adds its own kind column — a family or type rename, a parameter edit, a New type row, an orphan — with a tick per row and per parameter. Tick, untick, then Apply.
| ID | Element | Room | Fire Rating | Width | Comments |
|---|---|---|---|---|---|
| 300101 | D-101 · Single Flush | Main Lobby | EI30→EI60 | 1010 | →Accessible — hold-open device |
| 300103 | D-103 · Single Flush | Office 1.04 | EI60→EI30 | 926 | Fire-rated set |
| 300104 | D-104 · Single Flush | Store 1.09 | EI30 | 826→900 | |
| 300106 | +D-106 · Single Flush | Plant Room | EI60 | 1010 | New in model |
| 300107 | D-107 · Single Flush | Meeting 2.01→Meeting Room 2.01 | EI30 | 926 |
In the Schedules source, a Preserve row can stand for many elements. If they disagree on a value the cell reads <varies> — leave it, and nothing happens. Replace it with a real value and Loop stops to confirm each case before writing, telling you exactly how many elements it will overwrite. Resolve them one by one, or clear the whole queue with Yes to all / Skip all remaining.
Everything you approved is written in one named Revit transaction per sync — “BIMIO Loop — Import” for schedule values, and the families side names its action the same way — so a single Ctrl+Z rolls the whole batch back. A progress popup tracks the write and can be cancelled mid-run. Loop writes the values; it never saves the model for you, so the save stays yours.
Both sources anchor themselves to the document they opened with. Bring another model to the front and Loop refuses politely instead of guessing: the Families source names the model this panel belongs to and how to get back to it, the Schedules source declines the sync with the reason in its status chip, and the workbook's own identity is checked against the project before anything is read back. A badge is always the count of Loop's model — never whichever file happens to be active.
Loop would rather refuse a change than mis-apply it. Cells that conflict with Revit, edits in read-only columns and blanks over parameters that can't be emptied are excluded up front and listed — the rest stays applicable. Workshared elements checked out by a colleague are skipped with a warning that names them, never fought over. Every run leaves a log, and if the file is open in Excel, Loop tells you to close it instead of failing quietly.
This is an actual HTML report Loop exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Loop ships as a flagship on the BIMIO suite's Data panel. Pick a source, take it to Excel, and bring every change back under review — in a single, undoable transaction.