Synchronizing with
Central
Learn how Revit's worksharing model keeps your team's work in sync, how to synchronize with central, and how to resolve conflicts like a professional.
What Is Worksharing?
Worksharing is Revit's collaboration framework that allows multiple team members to work on the same project simultaneously. It splits a single BIM model into worksets: named groups of elements that individual users can "check out" and edit.
Central vs Local Models
Why Synchronizing Matters
Without regular synchronization, team members work in isolation: their changes remain invisible to everyone else. This leads to design conflicts, duplicated work, and data loss when changes finally collide.
The Sync Lifecycle
Element Borrowing & Ownership
When you edit an element that belongs to someone else's workset, Revit borrows it temporarily. You gain exclusive edit rights until you synchronize or relinquish the element. No one else can modify it while you hold the lock.
Editing Requests & Permissions
When another user holds an element you need, Revit lets you place an editing request. The current owner sees a notification and can grant or deny access. Understanding permissions prevents team bottlenecks.
SWC vs Reload Latest
| Synchronize with Central | Reload Latest | |
|---|---|---|
| Direction | Push your changes + Pull theirs | Pull theirs only |
| Your Edits | Published to central | Remain local |
| Borrowing | Releases borrowed elements | Keeps your borrows |
| Conflicts | Must resolve conflicts | No conflict dialog |
| Shortcut | SS (or Collaborate tab) | RL (or Collaborate tab) |
How to Synchronize: Step by Step
Resolving Conflicts
A conflict occurs when two users edit the same element between syncs. During SWC, Revit presents a dialog listing each conflicting element and asks you to choose which version to keep.
Example 1: A Clean Sync
You spent the morning adding interior partition walls in your local copy. No one else touched those walls. When you Synchronize with Central:
Example 2: A Conflict Scenario
You moved Wall-042 east by 1 meter. Meanwhile, your colleague moved the same wall north by 0.5 meters. Neither of you synced in between.
Example 3: Workset Ownership Clash
The MEP designer took exclusive ownership of the "Mechanical" workset to batch-update ductwork. You need to add a fire damper to a duct on that workset. Here's how to handle it:
Common Mistakes
More Pitfalls to Avoid
Quick Reference Summary
| Action | What It Does | When to Use |
|---|---|---|
| Synchronize with Central | Push your edits + pull theirs | Every 30-60 min, before breaks |
| Reload Latest | Pull others' edits only | Before starting new work area |
| Relinquish All | Release all borrowed elements | At end of day or on break |
| Place Editing Request | Ask owner to release an element | When blocked by another user |
| Save to Central (detach) | Creates a standalone copy | Archiving, external sharing |
Question 1 of 5
What is the primary difference between Synchronize with Central and Reload Latest?
Question 2 of 5
When a conflict arises during synchronization, what should you do first?
Question 3 of 5
What happens to borrowed elements when you Synchronize with Central with "Relinquish all elements" checked?
Question 4 of 5
Why is editing the central model file directly considered dangerous?
Question 5 of 5
You need to edit a duct, but another user owns the "Mechanical" workset. What is the recommended action?