Synchronizing with Central — Synchronize with central and resolve common conflicts (conceptual)

Historical Context & Motivation

Before the emergence of Building Information Modeling, architectural collaboration relied on a patchwork of redlined paper drawings, manually circulated file copies, and verbal coordination among team members—a process that was slow, error-prone, and fundamentally unable to scale to the complexity of modern design projects. As firms grew and projects became larger, the need for a single source of truth—a unified digital model that every team member could contribute to simultaneously—became urgent. Autodesk's introduction of worksharing in Revit addressed this need by allowing multiple users to work on a shared central model through individual local copies, with a synchronization mechanism that merges everyone's work back together.

The central question that the synchronization workflow answers is deceptively simple: how can a dozen designers edit the same three-dimensional model at the same time without overwriting each other's work? The answer involves a careful choreography of element ownership, conflict detection, and resolution strategies—concepts that every collaborative Revit user must understand before pressing the Synchronize with Central button.

Core Principles & Definitions

Revit's worksharing architecture rests on a clearly defined hierarchy of files and ownership rules. The central model is the authoritative version of the project; it resides on a shared network location or cloud server and is never edited directly. Instead, each team member creates a local copy on their own machine, works within that copy, and periodically synchronizes changes back to central. The model is subdivided into worksets—named partitions of elements—that help organize ownership and visibility. Understanding these concepts and their interplay is essential before examining the mechanics of synchronization itself.

Visual Explanation — The Synchronization Cycle

Notice that the central model never appears open on anyone's screen for direct editing. Each designer's interaction is mediated through their local copy, which functions as both a workspace and a staging area. When you synchronize, Revit performs a two-phase transaction: first it uploads your local changes to central, then it downloads all the changes that other team members have published since your last sync. This bidirectional exchange is what keeps every local copy in agreement with the evolving project state. If Revit detects that two people have changed the same element, it raises a conflict and asks you to resolve it before the sync can complete.

How Synchronization Works — The Mechanism in Detail

The Two-Phase Sync Transaction

When you invoke Synchronize with Central (keyboard shortcut SS in many configurations), Revit executes a structured sequence. In Phase 1 — Upload, the application packages every element you have modified, created, or deleted since your last synchronization and transmits those changes to the central model. In Phase 2 — Download, Revit retrieves all changes published by other users and integrates them into your local copy. Between these two phases, the software checks for conflicts—situations where your edits and another user's edits touch the same element or dependent elements.

Element Ownership and Borrowing

Revit tracks ownership at the individual element level, not just at the workset level. When you select and modify an element, Revit quietly makes a borrow request behind the scenes. If the element is not currently owned by anyone, the borrow is granted immediately and recorded in central. If another user already owns that element—because they have unsynchronized edits to it—Revit can either place your request in a queue (if your user settings dictate) or notify you that the element is unavailable. This fine-grained ownership system is the first line of defense against conflicts: by preventing two users from editing the same element simultaneously whenever possible, Revit reduces the likelihood that conflicting changes will accumulate.

What Happens During a Conflict

Despite the borrowing mechanism, conflicts still arise. The most common scenario occurs when two users edit dependent elements—for instance, one user moves a wall while another user has placed a door in that wall. Neither user directly edited the same element, yet the changes are logically incompatible. When Revit detects such a situation during synchronization, it presents a conflict resolution dialog that lists every conflicting change and asks you to choose: keep your version, accept the other user's version, or (in some cases) attempt to merge both. The decision should be informed by project priorities, design intent, and communication with your team—not made hastily.

Common Conflict Types and Resolution Strategies

Conflicts in Revit worksharing are not all created equal. Understanding the taxonomy of conflicts allows you to anticipate problems, structure your worksets intelligently, and resolve issues quickly when they arise. The diagram below categorizes the most frequent conflict types encountered in collaborative Visual Arts and architecture projects.

Worked Example — Resolving a Dependency Conflict

Imagine a scenario common in studio-based Visual Arts programs: you and a classmate are collaborating on a gallery renovation project in Revit. You are responsible for the interior partition layout, while your classmate is placing door families in those partitions. A dependency conflict arises when you move a partition wall after your classmate has already placed a door in it. The following walkthrough demonstrates how this conflict appears and how to resolve it.

Best Practices vs. Common Pitfalls

Experienced Revit users develop habits that minimize conflict frequency and maximize team efficiency. The table below contrasts best practices with the most common mistakes that Visual Arts students encounter when first working in collaborative Revit environments.

Connection to Advanced Collaboration — Cloud Worksharing and Beyond

The conceptual framework of Synchronize with Central remains consistent whether you are working with a traditional file-server-based central model or with Autodesk's cloud-based collaboration platforms. However, the cloud introduces several enhancements that extend the paradigm you have learned. Understanding these connections will prepare you for professional practice, where cloud-based BIM collaboration is increasingly the standard.

As you progress into advanced coursework and professional internships, you will encounter projects that layer additional coordination tools on top of the basic SWC workflow—tools like Navisworks clash detection, Dynamo scripting for automated checks, and model audit protocols. All of these advanced techniques build upon the foundational understanding of element ownership, synchronization, and conflict resolution that you are developing now. The conceptual model remains the same; the toolset simply becomes more powerful.

Practice Problems

Lesson Summary