Managing multiple Tenant Improvement (TI) projects in Revit inside a single base building model is standard practice in most BIM teams. The challenge is always the same: keep models lightweight, maintain precise alignment, and preserve your company template standards without introducing coordination errors.
Most teams lose hours fixing misaligned links or cleaning bloated files. This workflow removes that problem.
TL;DR — What Actually Works
- Use the base building model as the coordinate authority
- Treat each TI model as a satellite model
- Start TI projects from a clean template, not from “Save As”
- Use Internal Origin to Internal Origin for first link placement (strict)
- Use Acquire Coordinates or Publish Coordinates (depending on setup)
- Use Copy/Monitor for levels only (grids case-by-case)
- Link back using Auto – By Shared Coordinates
- Always set links to Overlay, not Attachment
The Problem with Revit Multi-Project Workflows
When starting a new TI project, many BIM managers use “Save As” from the base building model. It keeps alignment, but creates:
- Heavy files filled with irrelevant geometry
- Outdated views and sheets
- Broken or duplicated schedules
- Performance issues in Revit 2026 despite improvements
Starting from a clean template solves the bloat, but creates another issue:
- No reliable positioning
- Manual alignment errors
- Inconsistent updates when links change
This is where most coordination issues start.
Best Practice: Shared Coordinates Strategy in Revit
The reliable approach is simple:
- The base building = Source of Truth
- The TI model = Satellite / Recipient
You don’t move models to match each other. You align their coordinate systems.
Important nuance in Revit 2026 workflows:
- The base building often already contains shared coordinates tied to site/topography
- Your TI model must inherit—not redefine—this system
Step-by-Step Revit TI Workflow (Field-Proven)
1. Establish the Link (Strict Positioning Rule)
Open your TI project (from your company template).
- Link the base building model
- Use Internal Origin to Internal Origin ONLY
Do not rely on Center to Center.
Technical reality in Revit 2026:
- Center is calculated from non-hidden geometry
- Any distant element shifts the center unpredictably
This step ensures a clean, deterministic starting point.
2. Coordinate Strategy (Acquire vs Publish — Critical Distinction)
This is where most coordination problems start if done incorrectly.
Base rule:
- The TI model must become a satellite of the base building
Case A — Standard TI Setup (Most Common)
- Base building already has valid shared coordinates
- TI model starts empty
Workflow:
- Link base building (Internal Origin aligned)
- Use Acquire Coordinates
Result:
- TI model inherits the coordinate system
- Safe for most single-base workflows
Case B — Federated / Multi-Host Environment (Advanced)
If your TI model will be inserted into a master federated model that already hosts the base building:
- Prefer Publish Coordinates from the base model into the TI model, OR
- Ensure strict dependency: base building = primary coordinate authority across all files
Why this matters:
- Avoids conflicts between multiple coordinate definitions
- Prevents misalignment when linking into ACC or federated environments
Key rule:
- Never create competing coordinate systems across models
3. Copy/Monitor Strategy (Use with Intent)
Don’t blindly copy everything.
Levels (Mandatory)
- Use Copy/Monitor for Levels
- Ensures vertical control (ceilings, floors, sections)
- Triggers Coordination Review when modified
Grids (Case-by-Case)
Copying all grids from a large building into a small TI project can:
- Overload views
- Reduce clarity
- Impact performance
Expert approach:
- Option 1: Do not copy grids, use linked model visibility
- Option 2: Copy only relevant grids (local zone)
Use Copy/Monitor for grids only if:
- You need annotation control locally
- Or grid modifications must be tracked
4. Phase Mapping for Tenant Improvements
TI work happens inside an existing building.
Set your phases correctly:
- Match base building phases (e.g., Existing, Phase 1)
- In the linked model settings:
- Use Phase Mapping
- Map building “Existing” → TI “Existing”
Without this:
- Elements may not display correctly
- Demolition/new work views become unreliable
5. Federated Model Setup (Back-Linking)
To coordinate multiple TI projects:
- Link TI models back into the base building or master model
- Use Auto – By Shared Coordinates
Because coordinates were handled correctly earlier:
- Each TI model lands in the correct location
- No manual adjustment
- No drift over time
This is the backbone of a clean federated BIM environment.
Cloud Workflows in Revit 2026 (ACC / BIM Collaborate Pro)
In Revit 2026, most projects run on Autodesk Construction Cloud (ACC).
Key differences vs local files:
- Links are managed as External Resources
- Models are accessed via Cloud Models, not file paths
- Coordination happens across teams in real time
Implications for this workflow:
- Shared Coordinates still behave the same
- But:
- Reloading links depends on cloud sync
- Model ownership and publishing affect visibility
- Coordination must be validated after each publish
Best practice:
- Define one authoritative model for coordinates (usually base building)
- Ensure all teams follow the same linking protocol
- Validate placement after cloud publishes
Performance Control in Revit 2026
Even with improvements in Revit 2026, linked models can slow things down.
Use:
- Specify Worksets when linking
- Close:
- Furniture
- MEP systems not needed
- High-detail fabrication content
This keeps TI models responsive and stable.
Common Mistakes That Break Coordination
- Using Save As instead of a template
- Using Center to Center for placement
- Moving models manually instead of managing coordinates
- Misusing Acquire vs Publish Coordinates
- Copying all grids without filtering
- Linking with Attachment (nested link issues)
- Ignoring cloud coordination rules in ACC
Each of these creates problems later in coordination.
FAQ: Revit Multi-Project Workflow (Real-World Answers)
Should I use Overlay or Attachment for Revit links?
Use Overlay.
Attachment creates:
- Nested links
- Circular dependencies
- Hard-to-debug coordination issues
What is the safest first placement method?
Always:
- Internal Origin to Internal Origin
Do not use:
- Center to Center
- Manual alignment
When should I use Acquire vs Publish Coordinates?
- Acquire Coordinates → TI inherits from base (standard case)
- Publish Coordinates → used in controlled environments where base model enforces coordinates across multiple linked models
Rule:
- One model defines coordinates
- All others follow
Should I Copy/Monitor grids in TI projects?
Not always.
- Levels → Yes (mandatory)
- Grids → Only if needed
Otherwise, use linked visibility.
Why does my model shift when linking?
Most common causes:
- Use of Center to Center
- Multiple coordinate systems
- Incorrect initial placement
Fix:
- Reinsert using Internal Origin
- Reapply Shared Coordinates workflow
Does this workflow work in Revit 2026 Cloud projects?
Yes.
- Same coordinate logic
- Different file management (ACC)
You must:
- Validate links after publish
- Maintain a single coordinate authority
Can multiple TI projects be managed safely in parallel?
Yes, if:
- All models inherit from the same base coordinates
- Linking strategy is consistent
- No manual repositioning occurs
Final Notes from Practice
This workflow is not optional on complex projects.
What matters is not just using Shared Coordinates, but using them with:
- A clear hierarchy (base → satellite models)
- A consistent linking method (Internal Origin first)
- Controlled use of Acquire vs Publish
Set it up correctly once:
- Every TI project aligns automatically
- Coordination stays stable
- You stop fixing positioning issues late in the project
That’s how experienced BIM teams keep multi-project environments under control.