01 / 21

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.

Autodesk Revit

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 Model
The single source of truth stored on a shared network or BIM 360 cloud.
Local Copy
Your personal working copy, created from central, where you make day-to-day edits.
Worksets
Logical partitions (e.g., "Structure", "MEP") that organize who edits what.

Central vs Local Models

Central Model (Server / Cloud) Local Copy A Architect Local Copy B Structural Eng. Local Copy C MEP Designer SWC SWC SWC SWC = Synchronize with Central

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.

1
Keeps the team aligned: Everyone sees the latest walls, grids, and annotations.
2
Catches conflicts early: Revit flags overlapping edits at sync time, not weeks later.
3
Creates restore points: Each SWC writes a version to central that can be rolled back.
4
Releases element ownership: Borrowed elements are freed so others can edit them.

The Sync Lifecycle

1. Save Local 2. Pull from Central 3. Resolve Conflicts 4. Push to Central Ctrl+S Saves your edits to the local file Reload Latest Downloads others' changes to your copy Conflict Dialog Pick yours or theirs per element Publish Your changes become visible All four steps happen inside a single "Synchronize with Central" command

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.

User A Wall-042 User B Borrowed Blocked ✕ SWC Releases

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.

Grant
The owner relinquishes the element. You receive immediate edit access.
Deny
The owner keeps the element. You must wait until they sync or relinquish.
Auto-Grant
If the owner is offline or idle, Revit may auto-grant after a timeout.

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

1
Save your local file (Ctrl+S) to ensure all in-progress edits are captured.
2
Go to Collaborate tab and click Synchronize with Central, or type the keyboard shortcut SS.
3
Review the SWC dialog: choose which worksets to sync, add an optional comment describing your changes.
4
Check "Relinquish" boxes to release borrowed elements and worksets you no longer need.
5
Click OK. Revit pulls others' changes, flags any conflicts, then pushes your changes to central.
6
Resolve conflicts if prompted: choose to keep your version or accept the other user's version for each element.

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.

Conflict Resolution Dialog Wall-042 Moved 2m east by User B Yours Theirs Grid Line C Renamed to C.1 by User A Yours Theirs Keep Mine Keep Theirs

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:

1
Revit pulls updates from central: three new columns added by the structural engineer.
2
No conflicts detected because your walls and their columns don't overlap.
3
Your partition walls are published to central. The structural engineer now sees them on their next reload.

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.

1
You click Synchronize with Central. Revit detects that Wall-042 was modified by both users.
2
The conflict dialog appears: "Wall-042: Your version vs. User B's version."
3
You contact your colleague, agree to keep their version (north shift), and plan to apply the east shift afterward.
4
You select "Theirs," click OK, then manually reapply your east movement to the updated wall position.

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:

1
You try to edit the duct. Revit displays: "Element is owned by [MEP Designer]."
2
You click "Place Request" to send an editing request notification.
3
The MEP designer receives the request, finishes their edit, and grants permission or syncs (releasing borrows).
4
You receive access, add the fire damper, then Synchronize with Central to publish your change.

Common Mistakes

✕ Editing the Central File Directly
Never open and edit the central model itself. Always work from a local copy. Direct edits can corrupt the file.
✕ Syncing Too Rarely
Waiting until end-of-day to sync creates massive conflict lists. Sync every 30-60 minutes for smoother merges.
✕ Ignoring Relinquish Options
Forgetting to check "Relinquish all elements and worksets" blocks teammates from editing those elements.

More Pitfalls to Avoid

✕ Blindly Choosing "Mine"
Always review what the other person changed before overwriting. You may discard critical coordination work.
✕ Skipping Sync Comments
Without descriptive comments, the sync history becomes useless for tracking what changed and when.
✕ Working Offline Too Long
If you lose network access, save locally, but sync as soon as connection is restored to avoid divergence.

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?