Pick the doors people leave through and Egress measures every room to the nearest one — walking round the walls, not through them — then paints the result as a heat map and ranks the rooms by their worst corner. Revit's own path of travel is asked the same question beside each answer. Reading changes nothing in your model; drawing is one named transaction, and Clear puts the view back.
Travel distance is checked room by room with Revit's one-line-at-a-time tool or a scale rule, and redone from scratch every time the plan moves.
The input side is the questions you set — which doors are the way out, which of two jobs is being asked, what blocks. The output lands on the drawing and in the report.
Tap Input or Output to isolate a half — the other collapses.
Egress works one floor at a time, on the plan you have open, and refuses to guess what you didn't declare.
The first decision of every session sits under the title: People leaving — evacuation, where the deliverable is Revit's own paths of travel — or Getting something in or out — a fit check for an object of a stated width and height, whose report says so in its title, and which never claims a long object can turn a corner: clearance is necessary, not sufficient.
| Room | Name | Worst point | Share | Reading | Revit says |
|---|
Pick in model… hands you to Revit with a doors-only filter; or nominate a family marking a floor exit — the door of the protected stair, what the codes measure travel distance to — and one marking the building exit, so marking once serves every floor. With nothing chosen, Measure refuses with its reason: guessing would put a number under your name that nobody chose. What blocks is honest by default: everything on the plan is solid except what you untick — and doors never block.
Give a width and a height and every number changes meaning: routes become an object's, kept half its width clear of everything, a doorway narrower or lower stops being a way through, and the drawing adds lines where its sides go. Clear sizes come from parameters you nominate: Revit's Width is the leaf on one family and the rough opening on the next. A doorway whose height will not read is reported, not assumed shut. The report retitles itself “Route for something 1200 mm wide and 2100 mm tall”.
A fit check, not an evacuation study. The distances become the routes for an object of the size below, the drawing shows where its SIDES go, and the report says so in its title. Reading the plan still writes nothing.
A doorway’s clear width and height are read from the parameters you choose here — Revit’s own Width is the leaf or the rough opening depending on who built each family.
| Room | Name | Worst point | Share | Reading | Revit says | |
|---|---|---|---|---|---|---|
| 1.04 | Office | 18.2 m | 59% | 18.4 m | ||
| 1.09 | Store | 24.7 m | 80% | 24.9 m | ||
| 1.17 | Plant | 31.0 m | 100% | 31.3 m | ||
| 1.22 | Riser | no way out | — | no exit | — |
The confirm lists every element it will create, leftovers included — and if the model has moved since measuring, it says so before offering “Draw the old numbers anyway”.
Measure reads on the API thread, solves on a background one, and paints in one named transaction. Everything else it tells you is why you can trust it.
The floor is rasterised at a 250 mm default grid and a distance field walks it — round the walls, never through them. The table ranks rooms by their worst point; verdicts — within, close, over — appear only when you set a limit, because the limit is your jurisdiction's call, not the app's. The paint is one transaction, “BIMIO Egress — Paint evacuation distance”, and Clear the map restores the view's previous style.
| Room | Name | Worst point | Share | Reading | Revit says | |
|---|---|---|---|---|---|---|
| 1.09 | Store | 43.1 m | 108% | over | 41.8 m | |
| 1.04 | Office | 38.6 m | 97% | close | 38.1 m | |
| 1.01 | Lobby | 12.2 m | 31% | within | 12.0 m |
The Revit says column carries Revit's own path-of-travel distance beside each answer — it creates nothing, no elements, no transaction. When the two disagree by more than a few percent, the tooltip explains why that is worth a look: it usually means an obstruction that is not room-bounding. Two solvers agreeing is the cheapest audit there is.
| Room | Name | Worst point | Share | Reading | Revit says | |
|---|---|---|---|---|---|---|
| 1.07 | Meeting | 29.4 m | 74% | within | 34.9 m |
A room table answers whether a room complies. It does not say what one stair is responsible for. Every reachable point is attributed to the way out nearest on foot, so each exit gets a floor area, a furthest point, and the room it falls in — the design case. On Level 01 two floor exits carry 612 m² and 494 m²; the two building doors take 268 m² and 176 m². An exit carrying nothing reads “nothing comes this way”: either spare, or not where you think it is.
| Way out | Floor served | Furthest point | Which is in | |
|---|---|---|---|---|
| Exit marker · EX-S1 | floor | 612 m² | 43.1 m | 1.09 — Store |
| Exit marker · EX-S2 | floor | 494 m² | 38.6 m | 1.04 — Office |
| M_Single-Flush 0915 x 2134mm (312454) | building | 268 m² | 17.4 m | 1.02 — Reception |
| M_Single-Flush 0915 x 2134mm (312460) | building | 176 m² | 21.6 m | 1.28 — Refuse store |
A point belongs to whichever way out is nearest ON FOOT, around the walls — so the boundary between two of them bends round the plan rather than running straight between them. The areas add up to the whole floor that has a way out.
Every run ends with its caveats card: doors that would not read, rooms too narrow for the grid, markers living in other views, doorways whose height could not be checked — “I do not know” is not the same as “it fits”. The caveats travel into the exported report, at the top, because a page of tidy distances with no caveats gets forwarded and believed.
| Room | Name | Worst point | Share | Reading | Revit says | |
|---|---|---|---|---|---|---|
| 1.11 | Riser | not measured | — | too narrow | — |
Draw on the plan creates real path-of-travel elements steered along the measured line — native means it carries Revit's own length, can be tagged, and survives export — after a confirm that lists everything written, down to the leftover filled-region types Purge Unused will clear. The button then reads “Remove what was drawn (N)” and removes exactly those; and the suite's sync guard knows about any map left on a view, so it asks before your synchronise would carry it to the team.
The colour Measure puts on screen is an analysis display style, and Clear the map puts back whatever the view had before. What survives onto a sheet are filled regions: the area beyond the limit outlined as a native one, and the map itself redrawn as tiles whose size, tile fill and see-through you set. Five ways to draw the field, from “Colour map” to “Chequerboard” for a monochrome plot. A key goes with it, because green and red mean nothing until something says what the ramp is stretched to.
Move a partition and the routes on the sheet go on asserting yesterday's lengths — Revit has no opinion, a path of travel is just an element somebody made. Egress writes down what each plan's drawing rested on, on local disk, never in the model. Open that plan months later and it says so. Move a door on Level 03 while working on Level 07 and it names Level 03's drawing, not all six. Press Draw while stale and the button reads “Draw the old numbers anyway”.
This is an actual HTML report Egress exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Egress ships on the QA / QC panel of the BIMIO tab. Open the floor plan, pick the doors, and get the map, the table and the report. Revit 2024–2027, full trial, no card.