Linked Revit Models or Shared Authoring: What Collaboration Are You Buying?

Identify the model that needs shared authorship

Facility, equipment and cabling information can change on different schedules. A facility contributor may revise a pathway interface while an equipment contributor retains the same rack arrangement. The cabling team needs to see both contributions, decide how the change affects its own content and return an updated model. Several parties being involved does not yet explain whether they need to edit one model together.

Ask where the proposed edits belong. If each party maintains its own source model and sends references to the cabling author, the collaboration problem is exchanging and incorporating separate contributions. If two cabling specialists need to develop different portions of the same cabling model, the problem includes shared authorship within that model. A project can need both arrangements.

Autodesk's Revit 2026 collaboration documentation distinguishes these mechanisms explicitly. Linking supports working in the context of several models; worksharing supports several users working on one model. This article applies that distinction to the modeling work a buyer commissions. Collaboration status does not establish geometry accuracy, technical design acceptance or authorization for physical work.

References: [A1]

Linked models retain separate contributions

In a linked arrangement, the cabling project is the host and the facility or equipment projects supply linked context. Autodesk describes linking separate project files and architectural, structural and MEP models. The host lets an author work with those contributions in view without treating them as one shared source model.

Placement matters because the context must relate to the cabling content. Revit supports reference positioning, including shared-coordinate workflows, and linked elements can serve as references for dimensions and alignment. The parties must agree the applicable project reference; merely seeing several models together does not establish that their positioning is appropriate for the intended comparison.

There is also a continuing file relationship. Autodesk distinguishes relative paths, which locate a linked file relative to a working directory, from absolute paths to a disk or network location. A recipient receiving the cabling host needs the agreed dependencies or access arrangement, rather than an assumption that the author's reference locations will also work for the recipient.

For the documented linked-file workflow, Revit updates a changed source link when the project opens; links can also be reloaded while it remains open. That updates the referenced context. The buyer still needs a cabling response to the change: which authored objects require revision, which remain applicable and what the next recipient should receive. A refreshed facility reference alone does not establish that this dependent work was performed.

References: [A1][A2][A6][A7]

Worksharing coordinates authors within one model

Worksharing addresses a different boundary. Autodesk describes a central project model shared by team members who make design changes in local copies. The project can be subdivided into worksets. Those are subdivisions of the workshared project, rather than a new set of independently authored source-model files.

The distinction between local work and shared state matters to the purchase. Autodesk documents saving locally separately from synchronizing with central. Synchronization sends the local changes to the central model and brings changes from other contributors into the local model. Reload Latest can bring in central changes without sending the user's own changes to central. A statement that someone saved their work therefore leaves open whether that work has reached the shared model.

At buyer level, the proposed arrangement should identify who contributes cabling content to that shared project, which parts they maintain and who prepares the recipient's model issue. Having several people on the team or sending them copies of a native file does not describe that arrangement. The shared project, contribution mechanism and delivery responsibility must be explicit.

The environment is part of the choice. Revit 2026's overview distinguishes local-area-network worksharing from Revit Server and Revit Cloud Worksharing. Do not assume that a description of central and local files establishes the proposed remote environment, access or supported participation. Confirm the actual arrangement with the parties who will provide and use it.

References: [A1][A3][A4]

A shared cabling model can still have links

Linking and worksharing are compatible parts of a collaboration arrangement. Several cabling authors can contribute to one workshared project while that project references separately maintained facility, equipment and building-services models. Shared authorship of the cabling project does not make its authors responsible for editing every referenced source.

Autodesk supplies a concrete dependency here. In a worksharing-enabled model, links reside in worksets. Reloading an updated linked file requires the containing workset to be editable. Its guidance assigns link tracking to a team member and describes synchronizing after the update so that the team receives the updated link. It also documents a per-user option for leaving a link unloaded without unloading it for other users.

For the buyer, this means incoming-reference coordination remains identifiable work even when the cabling model is shared. Name the person who incorporates the relevant source issue and communicates the affected cabling task. One person's current view does not establish that every contributor is seeing the same reference state. Ask which linked source issue underlies the delivered cabling response, rather than treating membership in a shared project as the answer.

References: [A5]

Follow one facility change through two arrangements

Consider a fictional planning comparison with three upstream source models retained by three different contributors: facility F/1, equipment E/1 and building services M/1. A separate cabling model C/1 links all three. The facility contributor issues F/2 with a changed entry interface. E/1 and M/1 remain unchanged. These are invented model and issue labels; no actual files, software session or successful exchange is represented.

Under a linked-reference offer, one cabling author receives the intended F/2 issue through the agreed exchange. The author incorporates that reference into C and assesses the affected cabling content. For this example, stipulate that one modeled cabling approach needs revision. The required return is a revised cabling issue C/2, identifying F/2, E/1 and M/1 as its reference basis, together with the agreed files or access needed by its recipient. Delivering F/2 alone supplies the upstream change but leaves the cabling response outstanding.

Under a shared-authoring offer, stipulate that two nominated cabling contributors work on the same C project. The assigned contributor incorporates F/2 under the project's link and worksharing arrangement. The affected cabling approach is revised, the necessary contributions reach the shared model, and the designated issuer prepares C/2 for the recipient. These are the example's required tasks, rather than reported completed actions. Saving one contributor's local revision alone would leave the shared-model return unestablished.

Both arrangements therefore start with one changed upstream model and two unchanged upstream models. Both require one cabling-model response and one defined recipient delivery. Two cabling contributors do not create two separate cabling deliverables in this scenario. Shared authorship changes how contributions to C are coordinated; it does not eliminate the F/2 exchange or the recipient's need for an identifiable output.

The choice follows the continuing workload. If one author can maintain C and the other contributors only maintain F, E and M, a planned linked-reference reissue can address the stated need. If several specialists must continue authoring C, the shared arrangement addresses an additional collaboration requirement. An offer listing only periodic reference files leaves that requirement unanswered. Conversely, buying shared participation adds little to a recipient whose entire task is reviewing an occasional issued snapshot. Neither arrangement supplies a price or turnaround advantage without an actual scope and delivery plan.

Define the working arrangement and the delivered issue

Compare proposals by following a change through the proposed work. For separate contributions, identify how the cabling author receives a new source issue, incorporates its context, resolves the affected cabling task and returns the next output. Agree whether the purchase covers one coordination delivery or continuing updates, and what event calls for another issue. Frequent upstream changes can create substantial reissue work even when only one person authors the cabling model.

For shared authoring, identify the model in which participation is required and the contributors whose work belongs there. Confirm the actual Revit version, local, server or cloud arrangement, access responsibilities and nominated model issuer. The proposal should distinguish participation in that working environment from delivery of a model copy for review or onward use. A recipient who must continue authoring needs a different arrangement from one who only receives C/2.

Then define the output independently of the working method. State which cabling issue the recipient receives, the linked-source basis it uses, the dependencies that accompany it and the task the recipient must be able to perform. A central model can continue changing after a recipient issue is prepared. Describe the delivered snapshot and its intended use rather than promising that every later working change is automatically part of it.

A useful review asks the intended recipient to confirm the agreed outcome: access to the identified context and cabling issue for a reference delivery, or the agreed contribution and return workflow for continued authorship. Treat an unavailable reference, a missing cabling response and an inability to participate as different gaps. They require different corrections.

References: [A2][A4][A6]

Bring the collaboration need to the planning inquiry

Use Leviathan's Physical Infrastructure Planning & CAD service to discuss the physical planning outputs: layouts, routing coordination, point-to-point schedules and agreed documentation. Describe which parties retain the source models, which model needs multiple authors, how changes are expected to arrive and what the next recipient needs to do. That gives the scope conversation a concrete collaboration requirement.

The actual authoring tools, production resources, supported outputs, permissions and any hosting responsibility require engagement-specific confirmation before a Revit or worksharing commitment. The service page remains the place to establish the planning engagement; this comparison establishes no managed BIM or cloud-hosting offer.

Use the project inquiry below to outline the arrangement and the requested update work. A short description of the intended model relationships is enough to begin; keep restricted project files and credentials out of the initial inquiry.