Quick Start
RoomBridge is built for consultant, planning, equipment, interiors, BIM/VDC and other downstream Revit models that genuinely require native Revit Rooms while the architectural model remains the source of truth.
- Open the host Revit model and make sure the designated architectural source link is loaded.
- Set linked models to Room Bounding where their geometry is intentionally needed to enclose host Rooms.
- Choose JW Garage → Advanced Tools → Manage Source Links and configure the architectural link whose Rooms should govern RoomBridge.
- Run JW Garage → Synchronize Rooms.
- Review the condition RoomBridge reports and approve only the controlled actions you intend to make.
- Run Synchronize Rooms again. The desired destination is a synchronized, geometrically healthy model. When no changes are required, the audit should make no unnecessary model writes.
Why Native Host Rooms?
RoomBridge does not merely copy linked Room Name and Number values into parameters on other elements. It creates and maintains actual native Revit Room elements in the host model and preserves their relationship to the architectural source as the project changes.
Native host Rooms can participate directly in schedules, tags, room-aware families, equipment relationships, automation, data extraction, QA/QC and discipline-specific workflows. The difficult part is not creating those Rooms once; it is maintaining them through architectural renaming, renumbering, movement, deletion, enclosure changes and ongoing coordination.
Is RoomBridge the same as Revit Copy/Monitor?
No. RoomBridge is an independent JW Garage add-in purpose-built for native Revit Room coordination. It addresses the workflow many Revit users describe as Copy/Monitor for Rooms by creating actual native host Rooms and maintaining persistent relationships to Rooms in a designated architectural link.
RoomBridge extends that Copy/Monitor-style lifecycle with Room-specific handling for NEW Rooms, source changes, local edits, movement, geometry, orphaned relationships, Levels, Phases, Boundary Assist, readback validation and protected writes.
Multi-Level and Phased Projects
RoomBridge is designed for projects containing multiple Revit Levels and Phases. Each bridged source Room is resolved to its appropriate host Level, and new native Rooms are created in the corresponding mapped host Phase rather than depending on the active view's phase.
Level and Phase are part of the Room's coordination context. Similar or overlapping XY locations on different floors or in different phases do not automatically represent the same Room condition.
Synchronize Rooms does not require you to synchronize one floor at a time. RoomBridge can audit the configured source population while evaluating each Room in its proper Level and Phase context.
Source Management
Use Advanced Tools → Manage Source Links to configure the Revit link whose Rooms should govern RoomBridge synchronization.
- RoomBridge persists the intended source instead of silently switching to another available link.
- Additional linked models may remain Room Bounding when their geometry is needed for enclosure without becoming RoomBridge Room sources.
- If the expected source is unloaded, deleted or otherwise unavailable, RoomBridge reports the condition rather than substituting another link.
- Intentional source changes should be handled deliberately through Manage Source Links and then reviewed through the normal RoomBridge workflows.
Synchronize Rooms
Synchronize Rooms is the primary everyday command. It audits the designated source against the native host-Room population and determines what requires attention.
Typical states
- Synchronized and healthy: persistent identity, tracked information and geometry remain valid; no unnecessary writes are performed.
- NEW: an eligible architectural source Room does not yet have a persistently bridged native host Room.
- Source change: tracked architectural information changed while the established identity still resolves.
- Local edit: a native host Room changed independently from the established synchronized state.
- Move / geometry condition: the Room relationship still exists but the physical source-to-host condition changed.
- Orphaned: a host Room still carries RoomBridge identity but its expected source relationship can no longer be resolved normally.
- Boundary Assist stale: managed supplemental geometry no longer represents the current expected source footprint.
RoomBridge separates detection from execution. New Rooms, changes, moves, orphans and boundary repairs are surfaced and routed to the appropriate review or controlled action rather than being blindly applied.
Review Issues
Review Issues contains focused diagnostic tools. They support the hero workflow; they are not a checklist that must be run before every synchronization.
Advanced Tools
Advanced Tools contains setup, write, recovery, migration and specialist commands that are intentionally separated from normal day-to-day use.
Boundary Assist — Real-World Model Resilience
In an ideal workflow, linked Room Bounding geometry would always reproduce the source Room perfectly in a downstream model. Real projects include wall offsets, small gaps, incomplete enclosure conditions, unusual linked geometry, phasing, and other conditions that can prevent a native host Room from reproducing the expected footprint.
Boundary Assist provides managed supplemental Room-separation geometry when ordinary linked enclosure geometry is not sufficient. RoomBridge tracks the geometry it owns so it can understand which assisted segments belong to which bridged Rooms, which segments are shared, and which geometry is stale after an architectural revision.
Shared ownership
Adjacent assisted Rooms may share a managed segment. RoomBridge can retain a shared boundary when one Room still requires it rather than deleting the segment simply because another Room changed.
Stale assisted footprints
When source geometry changes, Synchronize Rooms can identify that the existing assisted footprint is stale and route the condition into the refresh workflow. The repair plan can determine which managed segments should be kept, deleted or created.
Validation before commit
Drawing Room Separation Lines is not itself proof of success. RoomBridge reads the resulting Room state back from Revit and validates the expected footprint before the protected repair is committed.
Persistent Identity and Room Lifecycle
Room Number and Name are project data, not sufficient identity. They can change. RoomBridge maintains a persistent relationship between the designated source Room and its native host Room so that renaming, renumbering, movement and other revisions can be treated as changes to an established relationship rather than as unrelated copy operations.
Current Room creation writes persistent identity as part of the same protected operation that creates the native Room. Newly created RoomBridge Rooms normally do not require a separate Stamp Identity step.
Source change vs. local edit
A source change originates in the architectural model. A local edit originates in the host model. RoomBridge distinguishes these conditions so the user can understand where the divergence began before applying a write.
Movement and transformed links
RoomBridge treats Room location separately from Room data and evaluates linked-model movement and rotation in the host-model coordinate context rather than assuming identical document coordinates.
Orphans
An orphaned Room still carries persistent RoomBridge identity but its expected source relationship can no longer be resolved normally. Investigate the cause before resolving it. A genuine source deletion, an unloaded source, a source-configuration change and a disrupted link identity are different conditions.
Safety, Readback and Rollback
RoomBridge is designed around controlled automation rather than blind bulk mutation.
- Detect first: many audits and review tools inspect the model without changing it.
- Review before consequential writes: creation, semantic changes, movement, Boundary Assist repair and lifecycle actions can be presented before execution.
- Readback validation: RoomBridge compares the requested state with what actually exists in Revit afterward.
- Protected write groups: related writes are treated as one logical operation.
- Rollback: when required validation fails, protected operations are designed to roll back rather than intentionally leave a partially updated condition.
- No silent source substitution: uncertainty is surfaced rather than guessed.
MODEL WRITES: 0
This means RoomBridge inspected and reported model state without modifying the project during that operation. A healthy audit with zero writes is a positive result.
Typical Production Workflows
Receive an architectural update
Reload or replace the architectural model through the project's normal Revit coordination process, then run Synchronize Rooms. Resolve the conditions RoomBridge reports and run Synchronize Rooms again until the project is healthy.
Architecture adds a Room
Synchronize Rooms identifies the source Room as NEW, presents the proposed creation, creates the native host Room on the appropriate Level and Phase after approval, establishes identity, and validates the result.
Architecture renames or renumbers a Room
The persistent relationship can remain valid. RoomBridge treats the visible difference as a source change rather than automatically creating another Room.
Someone edits a host Room locally
RoomBridge surfaces the local edit instead of blindly overwriting it. The project team decides whether the source value should be reapplied.
Architecture moves a Room
Synchronize Rooms can identify the geometry condition, Review Moves can inspect it, and Apply Moves can perform the approved relocation with verification.
Architecture deletes a Room
The host relationship can become orphaned. Investigate the reason before using Resolve Orphans; deletion is not automatically the correct response.
A Room stops enclosing correctly
Use Synchronize Rooms and Check Geometry. Where ordinary Room Bounding cannot reproduce the source footprint reliably, use the managed Boundary Assist workflow instead of unexplained manual separation lines.
Best Practices
- Use Synchronize Rooms first.
- Configure the architectural source intentionally.
- Keep source identity separate from Room Bounding.
- Review meaningful differences before applying them.
- Avoid deleting and recreating healthy bridged Rooms just because something changed.
- Use the RoomBridge relocation workflow rather than manually chasing architectural moves.
- Treat local edits deliberately.
- Avoid unmanaged Room Separation Lines as a quick fix for assisted Rooms.
- Investigate orphans before resolving them.
- Pay attention to readback results.
- Re-run Synchronize Rooms after corrective work.
- Keep normal project QA/QC in place; RoomBridge supports coordination but does not replace professional review.
Troubleshooting
The configured source is unavailable
Confirm that the intended Revit link is loaded and available. Do not immediately select another architectural-looking link. If the project intentionally changed sources, use Manage Source Links deliberately.
A new architectural Room is not appearing
Confirm the designated source, source Room Phase, expected Level/Phase relationship and source availability. Use Review Rooms or Scan Rooms as appropriate before creating anything manually.
A newly created Room is not enclosed
Check host Level, mapped Phase, linked Room Bounding geometry, source enclosure, offsets/gaps and whether Boundary Assist is required.
The Room Number or Name is different
Run Synchronize Rooms and Review Changes to determine whether the difference is a source change or local edit before applying anything.
A Room appears to have moved
Run Synchronize Rooms, then Review Moves. Apply Moves only after a valid move plan exists.
Apply Moves is blocked
A blocked operation means RoomBridge does not currently have a safe valid relocation to execute. Return to Synchronize Rooms and Review Moves rather than guessing.
RoomBridge reports an orphan
Investigate whether the source is loaded, whether the original source Room still exists, whether the source was intentionally replaced, and whether link identity changed. Resolve only after the cause is understood.
Geometry is wrong but Number and Name match
Semantic data and geometry are separate concerns. Use Check Geometry to investigate placement, footprint or enclosure conditions.
Boundary Assist is stale
Let Synchronize Rooms route the condition to refresh. RoomBridge evaluates which managed segments should remain, be removed or be created, then validates the resulting Room before commit.
Rooms overlap in plan but are on different Levels or Phases
RoomBridge evaluates them in Level + Phase context. Similar XY coordinates do not automatically mean they are the same Room condition.
An older RoomBridge model lacks current identity
Use Scan Rooms to understand the model population. Use Stamp Identity only for legitimate migration/backfill conditions.
Command Reference
Installation and Updates
RoomBridge is installed as a Revit add-in and appears on the JW Garage ribbon tab. RoomBridge v1.2 targets Autodesk Revit 2025, 2026 and 2027.
Before installing or updating, close affected Revit sessions, follow the supplied installer or deployment instructions, then reopen Revit and verify the installed version under Advanced Tools → About RoomBridge.
Do not replace RoomBridge program files while Revit is actively using the add-in.
Support
For RoomBridge support, contact support@jwaectools.com. Include the RoomBridge version, Revit version, command used, dialog text or screenshot, what you expected to happen, affected Level/Phase where relevant, and whether the Room uses Boundary Assist.