Ownership & Borrowing — Use ownership/borrowing concepts to...

SECTION 1

Historical Context & Motivation

Before Building Information Modeling software existed, architectural collaboration relied on a surprisingly physical system: large-format paper drawings pinned to a wall, each bearing the initials of the drafter currently responsible for that sheet. If two people needed to revise the same drawing, one literally had to wait for the other to put the sheet back. The concept of ownership—the exclusive right to modify a design element—has always been central to collaborative design, even when it was enforced by nothing more sophisticated than a pencil-cup sign-out sheet.

As CAD tools digitized drafting in the 1980s and 1990s, teams discovered that simultaneous editing of the same file could corrupt geometry, overwrite annotations, or silently duplicate elements—problems collectively known as collisions. Early networked CAD packages addressed this with simple file-locking: if one designer had a DWG open, everyone else was locked out entirely. The approach was safe but brutally inefficient for large teams, especially in architecture studios where interior designers, structural consultants, and MEP engineers all needed concurrent access to a single building model.

1982

AutoCAD Launch

Autodesk releases AutoCAD, introducing digital drafting. Collaboration is limited to sequential file sharing—only one user edits a file at a time.

1997

External References (XREFs)

AutoCAD popularizes the XREF system, letting designers overlay others' drawings without modifying the original. This was an early form of borrowing: read-only access to shared content.

2004

Revit Introduces Worksharing

Autodesk Revit formalizes the concept of Worksets—partitions of a single BIM model that can be owned by individual team members, enabling true concurrent editing.

2012

Cloud Worksharing via BIM 360

Autodesk launches cloud-based collaboration, extending ownership and borrowing concepts beyond the local network to geographically distributed teams.

2020s

Real-Time Co-Authoring

Modern platforms refine element-level ownership, allowing multiple designers to edit different rooms of the same building simultaneously without collision.

The fundamental question that these decades of development address is deceptively simple: How can multiple designers modify a shared building model at the same time without overwriting, duplicating, or corrupting each other's work? Revit's answer draws on the twin concepts of ownership and borrowing—an elegant system that Visual Arts students will recognize as analogous to the studio etiquette of shared creative spaces, but enforced by software rather than social norms.

SECTION 2

Core Principles & Definitions

Revit's collaboration model rests on a small set of interlocking ideas. Understanding these principles is essential before you ever click "Enable Worksharing" in a live project. Think of them as the rules of engagement for a multi-person design studio operating inside a single digital file.

Central Model

The single authoritative copy of the Revit project, stored on a server or in the cloud. Every team member's work ultimately synchronizes back to this file. No one edits it directly.

Local Copy

Each collaborator works in a personal copy of the Central Model on their own machine. Edits happen locally first, then are published to the Central Model through a process called Synchronize with Central.

Worksets

Named groups of model elements (e.g., "Interior Walls," "Furniture," "Structure") that can be assigned an owner. A workset is the primary unit of ownership in Revit.

Ownership (Exclusive Edit Rights)

When you own a workset or element, you alone can modify it. Others can view it, but their local copies treat the element as read-only until you relinquish ownership.

Borrowing (Temporary Edit Permission)

If someone else owns a workset but you need to modify a single element within it, you can request to borrow that element. Borrowing grants temporary, element-level edit rights without transferring workset ownership.

✦ KEY TAKEAWAY

Think of ownership and borrowing like a shared painting studio. Each artist has their own easel (workset) and nobody touches another person's canvas without asking. If you need to add a detail to someone else's painting—say, a background element that crosses canvases—you ask permission to borrow that area temporarily. You make your mark, hand it back, and the original artist retains overall responsibility. This protocol prevents two people from painting contradictory things in the same spot, which in Revit terms means no element collisions, no data corruption, no lost work.

SECTION 3

Visual Explanation — The Ownership & Borrowing Flow

This diagram shows three designers (A, B, C) each working on a local copy of the Central Model. Each owns a different workset (Interior Walls, Furniture, Structure). Designer B successfully borrows an element from A's workset with permission, while Designer C is blocked from editing A's walls because no borrow request was made—the collision is prevented.

The diagram above captures the essential topology of Revit's collaboration system. Notice that no designer directly touches the Central Model; all edits happen in local copies, and the Synchronize with Central operation is the only channel through which changes flow back to the authoritative file. This architecture means that if two designers attempt to modify the same element without one of them holding ownership or a borrow grant, Revit can detect the conflict at synchronization time and prevent the collision before any data is lost. The green dashed path—Designer B's borrow request to Designer A—represents the controlled exception: a temporary, element-scoped permission that lets collaboration happen across workset boundaries without surrendering the safety guarantees of the ownership model.

SECTION 4

How Ownership & Borrowing Work in Practice

The Lifecycle of an Element Edit

When you click on a wall, a door, or a piece of furniture in your local copy and begin editing, Revit silently checks the element's ownership status against the Central Model. The outcome of that check determines everything that happens next, and it follows a precise decision tree that Visual Arts students can think of as a kind of access-control choreography—every step exists to ensure that exactly one person can modify an element at any given moment.

The decision tree illustrates every path an edit attempt can take. If you own the element, you proceed immediately. If the element is unowned, Revit auto-borrows it for you. If someone else owns it, a borrow request is issued; if denied, the edit is blocked to prevent collision.

Three Ownership States

At any moment, every element in the Revit model exists in one of three states. The first is owned by you, meaning you have exclusive edit rights, either because you own the entire workset the element belongs to or because you explicitly claimed the element. The second is owned by someone else, in which case you can view the element in your local copy but cannot modify it without requesting a borrow. The third is unowned, meaning no user has claimed the element; in this case, the first person to begin editing it automatically borrows it, and Revit records this claim in the Central Model so that subsequent users are locked out until the borrower synchronizes or relinquishes.

💡 Relinquishing vs. Synchronizing

Ownership and borrow claims persist until you take action. Synchronize with Central publishes your edits and, by default, relinquishes borrowed elements (but not workset ownership). You can also manually Relinquish All Mine from the Collaborate tab to release claims without syncing your edits, which is useful when you realize you don't actually need to modify an element you accidentally claimed.

SECTION 5

Workset Organization & Collision Scenarios

Organizing Worksets Effectively

The way you partition a model into worksets directly affects how smoothly ownership and borrowing operate. A poorly organized workset structure is like a poorly planned shared studio: if every shelf, drawer, and table is jumbled together under one label, it becomes impossible to grant fine-grained access. Conversely, if worksets are too granular—one workset per door, for instance—the administrative overhead of ownership claims overwhelms the design process. The most common strategy in architectural practice is to organize worksets by building system (Structure, Interior, Envelope, MEP) or by spatial zone (North Wing, South Wing, Atrium), depending on how the design team is organized.

Common workset organization strategies and their collision profiles

Workset Strategy	When to Use	Collision Risk
By Building System	Teams organized by discipline (architect, structural, MEP)	Low—each discipline owns its own systems
By Spatial Zone	Large buildings where multiple architects handle different wings	Medium—zone boundaries may have shared elements
By Design Phase	Projects with overlapping schematic/DD/CD phases	High—phase boundaries shift, causing ownership ambiguity
Minimal (Default Only)	Very small teams (2–3 people) on simple projects	High—relies entirely on element-level borrowing

Common Collision Scenarios

Even with a well-designed workset structure, collisions can still arise if team members misunderstand the ownership model. The most frequent scenario occurs when two designers attempt to edit the same unowned element nearly simultaneously—Revit resolves this by granting ownership to whichever synchronization request reaches the Central Model first, but the second designer receives a conflict warning and must choose whether to keep their own edits, accept the other person's changes, or merge manually. A subtler collision involves hosted elements—a door hosted by a wall, for instance. If Designer A owns the wall and Designer B borrows the door to change its swing direction, but A simultaneously moves the wall, the door's position changes as a side effect. Revit handles this through its parametric engine, but the visual result may surprise both designers, which is why communication protocols are just as important as software safeguards.

Race Condition: Two users edit the same unowned element before either syncs. First to sync wins; second receives a conflict dialog.
Host-Dependent Collision: A hosted element (door, window) is borrowed while the host (wall) is modified by its owner. Both edits succeed, but the combined result may be unintended.
Workset Hoarding: A team member takes ownership of a workset and forgets to relinquish it, blocking all others from editing those elements for the entire session.
Stale Local Copy: A designer works offline too long without syncing, then encounters numerous conflicts when reconnecting because the Central Model has evolved significantly.

SECTION 6

Worked Example — Managing a Multi-Designer Renovation

Imagine a college gallery renovation project where three Visual Arts students are collaborating in Revit. Alex handles the structural shell, Brynn manages the interior layout, and Casey is responsible for the lighting and ceiling design. Let's walk through how ownership and borrowing keep their work collision-free.

Gallery Renovation — Avoiding Collisions

Step 1 — Enable Worksharing & Create WorksetsAlex opens the project and enables Worksharing via the Collaborate tab. Three worksets are created: "Structure" (assigned to Alex), "Interior Layout" (assigned to Brynn), and "Lighting & Ceiling" (assigned to Casey). The file is saved as the Central Model on the shared server.

Central Model established; three worksets with clear ownership.

Step 2 — Create Local CopiesEach student creates a local copy by opening the Central Model and saving a local version to their own machine. Revit automatically manages the link between each local copy and the Central Model.

Three local copies, each connected to the Central Model.

Step 3 — Concurrent Editing Without ConflictAlex modifies the structural columns in their local copy while Brynn simultaneously places partition walls and exhibition panels. Because these elements belong to different worksets owned by different users, there is zero risk of collision. Each user freely edits their own domain.

Parallel editing proceeds smoothly—no ownership conflicts.

Step 4 — Borrowing Across WorksetsCasey needs to attach a ceiling-mounted light track to one of Brynn's partition walls. The wall belongs to the "Interior Layout" workset, which Brynn owns. When Casey selects the wall to host the light track, Revit issues a borrow request. If Brynn's editing permissions are set to allow borrowing (the default), the request is granted automatically. Casey can now place the light track on Brynn's wall without Brynn needing to pause their work.

Borrow granted: Casey edits one element in Brynn's workset temporarily.

Step 5 — Synchronize & RelinquishAt the end of the session, all three students perform Synchronize with Central. Alex's structural changes, Brynn's interior layout updates, and Casey's lighting additions are all merged into the Central Model. Casey's borrow on the partition wall is automatically relinquished during sync, returning full control to Brynn. The Central Model now contains everyone's work, with no collisions and no lost data.

All changes merged; borrows relinquished; Central Model updated cleanly.

SECTION 7

Strengths, Limitations & Comparisons

The ownership-and-borrowing system in Revit is not the only model for collaborative design, and it comes with both significant strengths and real-world limitations. Understanding these trade-offs will help you make informed decisions about project setup and team communication.

Strengths and limitations of Revit's ownership & borrowing system

Aspect	Strengths	Limitations
Data Integrity	Guarantees that no element is modified by two users simultaneously, eliminating corruption and silent overwrites.	Overly cautious—an element locked by a user who stepped away for lunch is inaccessible to the entire team until they return.
Granularity	Operates at both the workset level (coarse) and the individual element level (fine), offering flexibility.	Element-level borrowing is implicit and can surprise users who don't realize they've claimed something.
Concurrency	Multiple users can edit different parts of the same model at the same time—vastly faster than sequential file locking.	Requires frequent Sync with Central; infrequent syncing leads to stale copies and painful conflict resolution.
Scalability	Works on both local networks and cloud platforms (BIM 360 / Autodesk Construction Cloud), supporting distributed teams.	Network latency can delay borrow requests and synchronization, especially for large models over slow connections.
Learning Curve	Concept is intuitive once understood—'own it or borrow it' maps to everyday social norms.	New users often forget to relinquish elements, inadvertently blocking teammates.

✦ KEY TAKEAWAY

Ownership and borrowing in Revit function much like a version control system in software development—Git, for example, uses branches and merge requests to prevent code collisions in the same way Revit uses worksets and borrow permissions to prevent model collisions. The underlying principle is identical: isolate concurrent edits, then merge them through a controlled process. Recognizing this parallel can deepen your understanding of any collaborative digital workflow, whether you're building an architectural model, editing a film, or co-authoring a design document.

SECTION 8

Connection to Advanced Collaboration & BIM Coordination

Ownership and borrowing within a single Revit file is just the first layer of coordination. In professional practice, building projects involve multiple linked Revit models—one each for architecture, structure, and MEP—along with clash detection tools that extend the collision-avoidance concept beyond a single file. Understanding how these layers relate to the foundational ownership model will prepare you for advanced BIM coordination workflows.

Single-file ownership vs. multi-model BIM coordination

Feature	Single-File Ownership & Borrowing	Multi-Model BIM Coordination
Scope	Elements within one Revit project file	Elements across multiple linked Revit files and even non-Revit models (IFC, Navisworks)
Collision Prevention	Enforced by ownership locks—prevents same-element editing	Detected by clash detection software (Navisworks, BIM 360 Model Coordination) after the fact
Resolution	Conflict dialog at sync time; automatic or user-chosen	Clash reports assigned to team members via issue-tracking workflows
Communication	Built into the software; borrow requests are automatic	Requires explicit coordination meetings, BCF (BIM Collaboration Format) exchanges, and documented protocols

As you advance in your BIM skills, you'll encounter tools like Navisworks and Autodesk Construction Cloud that perform automated clash detection—scanning combined models for physical intersections, such as a duct passing through a structural beam. These tools complement the ownership-and-borrowing system by catching inter-disciplinary collisions that no single-file workflow can prevent. The conceptual foundation, however, remains the same: define clear boundaries of responsibility, control who can modify what, and reconcile changes through structured processes.

🔮 Looking Ahead

Cloud-based platforms are increasingly moving toward real-time co-authoring, where ownership is managed at the sub-element level and conflicts are resolved instantaneously. For Visual Arts students entering interdisciplinary design fields, fluency in these collaboration paradigms—from Revit's worksets to cloud-based real-time editing—is becoming as essential as fluency in the design tools themselves.

SECTION 9

Practice Problems

PROBLEM 1 — CONCEPTUAL

In Revit's worksharing model, what is the fundamental difference between ownership and borrowing? Why does Revit need both concepts rather than relying on just one?

PROBLEM 2 — BASIC CALCULATION

A project has 4 worksets and 6 team members. If worksets are assigned so that each workset has exactly one owner, how many team members lack workset-level ownership? For those team members without ownership, describe the mechanism they must use to edit elements in the model.

PROBLEM 3 — INTERMEDIATE

Designer A owns the "Exterior Shell" workset and is redesigning the main entrance facade. Designer B, who owns the "Interior Layout" workset, needs to modify the interior side of the entrance wall to add a reception desk that attaches to it. Describe the step-by-step process by which Designer B can safely make this edit without causing a collision. What happens if both designers try to modify the same wall element at the same time?

PROBLEM 4 — APPLIED

You are leading a student team of five designing a campus art gallery in Revit. The building has three floors, and your team includes an exterior envelope designer, a structural consultant, two interior designers (one per floor for the upper floors), and yourself handling the ground-floor gallery. Propose a workset structure that minimizes collision risk. Justify each workset, explain who owns it, and identify the two most likely borrowing scenarios that will arise during the project.

PROBLEM 5 — CRITICAL THINKING

Revit's ownership-and-borrowing model prevents most edit collisions, but it does not prevent all forms of design conflict. For instance, two designers might each make valid, non-colliding edits to adjacent elements that are geometrically incompatible when viewed together (e.g., a structural beam lowered to a height that intersects a duct placed by the MEP engineer in a linked model). Discuss the conceptual limits of ownership-and-borrowing as a collision-avoidance strategy. What additional coordination mechanisms would you recommend, and how do they complement—rather than replace—the ownership model?

SUMMARY

Lesson Summary

Revit's collaboration model is built on the principle that a Central Model serves as the single authoritative file, while each team member works in a local copy. The model is partitioned into worksets—named groups of elements that can be assigned to an owner. Ownership grants exclusive, persistent editing rights over a workset's elements, ensuring that no two users can simultaneously modify the same element. When a designer needs to edit a single element in someone else's workset, the borrowing mechanism provides temporary, element-level permission—fine-grained enough to allow cross-boundary collaboration without relinquishing the safety of the ownership model.

This system prevents data collisions—the overwriting, duplication, or corruption of model elements—by enforcing a simple invariant: at most one user can modify any given element at any given time. The Synchronize with Central operation merges local edits into the Central Model and automatically relinquishes borrowed elements. Thoughtful workset organization—by building system, spatial zone, or discipline—minimizes the need for borrowing and reduces collision risk. For collisions that ownership cannot prevent, such as spatial conflicts across linked models, clash detection tools and structured coordination meetings provide the next layer of protection.