Cloud Coordination Models: Read-Only References for Revit
Edition: 25 September 2026 · Category: BIM News
This is an archived English edition. The briefing below preserves the original written briefing’s reporting and analysis, with paragraph headings added for reading. Words such as “today”, “planned” and “upcoming” refer to the edition date, not the website publication date. Product status, prices and deadlines should be checked again before a new decision.
The edition’s main signal: on September 24, Autodesk published a detailed workflow for Cloud Coordination Models. Revit can link a lightweight, read-only coordination package published from Forma Data Management. This allows a team to see issued geometry and changes from other disciplines without taking ownership of their authoring model. The coordination reference, however, is not a replacement for the designer’s native model, a formal transmittal or project approval.
Controlled read-only packages
A published package can be linked into Revit as a read-only coordination background. One team publishes a named package to Forma Data Management, and another discipline links it into Revit as a Cloud Coordination Model. The reference supports navigation, measurement, clearance checks and alignment. It does not grant permission to edit another company’s elements, and it does not load its families, templates or authoring methods. The BIM execution plan should define who may publish a coordination package, how it is named, which model version it represents and who confirms that it is suitable for coordination.
The important process change is that recipients can coordinate against the same package issued for shared work rather than an uncertain local copy. Read-only access prevents accidental editing, but it does not prevent selection of the wrong source. Recipients therefore need the package author, creation time, revision, intended use and connection to a transmittal record.
Publication views determine scope
Selected 3D views can determine the information included in the handover. When a Revit package is published, selected 3D views may define its scope. An element can therefore be correct in the authoring model yet absent from the coordination reference because of visibility settings, phase, discipline, filter, workset or section box. Teams should use dedicated publication views, lock their settings and compare the expected object set with the published result. Critical categories should have a separate zero-tolerance completeness check.
Multi-format and version boundaries
The reference is lightweight, multi-format and does not require a model upgrade. Autodesk lists Revit, IFC, Navisworks, DWG and other supported sources. Coordination geometry is optimised for fast display, and a package from another Revit release can be linked without upgrading its native model. Exact support depends on the Revit release in use. This is useful for an organisation supporting several Revit versions, but versionless does not mean identical semantics or features. The supported-version matrix should test visibility, categories, properties, coordinates and change comparison separately.
For a multi-version Revit policy, this can separate file upgrade from coordination access. A pilot must still prove that users of every supported release see the expected object set and can perform their assigned review.
Property-level change comparison
Changes can be inspected at property level, not only through colour highlights. The Revit 2027 Changes Details palette can compare values for a selected element between two cloud coordination model versions. Differences are grouped as analytical, construction, dimensional, identity and IFC-related changes. Changed elements are highlighted visually, while Show in Canvas locates them in the active view. A BIM manager should define which property changes trigger an issue, design review, quantity recalculation or withdrawal of previously issued construction information. Treating every change as equally important would create noise and obscure critical decisions.
Issues and verified model correction
An issue can be created from the coordination context, but resolving the issue does not modify the model automatically. Revit 2027 includes Forma Issues integration, while Autodesk points users of earlier Revit releases to a separate add-in. A new package version can be reviewed before the next coordination cycle. The issue preserves location and context, but it does not prove that the authoring model was corrected, checked and republished. The recommended chain is change, issue, responsible model author, new native version, new package, repeated verification and only then closure.
When native Revit links are required
A Cloud Coordination Model does not replace a conventional Revit link in every situation. Autodesk recommends it as a read-only background for clearance checks, alignment and coordination. A normal Revit host link remains necessary when teams must schedule, tag, document or otherwise work with another discipline’s native elements, provided contracts permit that depth of access. The link type should be selected according to the information-use purpose, not only a smaller file size or faster loading.
Shared information and approval rules
The workflow supports the ISO 19650 Shared principle, but the platform does not replace governance. Autodesk associates this workflow primarily with the shared information state. Forma Data Management is a common data environment with document control, reviews, transmittals, issues and permission management. A named coordination package is not automatically a contractual Published deliverable. Its status depends on project rules, approval, suitability code, revision and transmittal record. Package metadata and the BIM execution plan should clearly distinguish WIP, Shared, Published and Archive states and specify the permitted use of each reference.
Analysis and practical implications
Today’s analysis. A lightweight coordination reference is a managed information product, not merely a smaller model.
The recommended chain is native discipline model, controlled publication view, named Shared package, read-only reference in Revit, change review, issue, native correction, new package and approval.
The greatest opportunity is to coordinate several disciplines against the same issued artefact without distributing editable models, families, templates or proprietary authoring methods. A lightweight reference can reduce local copies, accidental upgrades and ambiguous email attachments. It also allows the author to see the latest shared context inside Revit rather than in a separate viewing window.
The main risks are these. The wrong named package or version is linked. The publication view hides a critical element. Read-only is mistaken for approved. Different source formats expose different geometry or properties. Change comparison identifies a difference without explaining its engineering importance. An issue is closed before the corrected model is republished. An older Revit release lacks equivalent capabilities. The coordination reference is used for quantities or documentation even though native elements are required. The common data environment state, transmittal and contractual issue remain disconnected.
Recommended pilot.
Pilot step 1
select one architectural and structural model pair and two Revit versions supported by the organisation.
Pilot step 2
create dedicated publication views with controlled phases, filters, worksets and section boxes.
Pilot step 3
define rules for package name, revision, information state, suitability and owner.
Pilot step 4
compare the published object set with a pre-approved list of categories and elements.
Pilot step 5
test Revit, IFC and DWG sources for coordinates, categories, dimensions and key properties.
Pilot step 6
introduce known geometry, identity and IFC-property changes and observe how different Revit releases display them.
Pilot step 7
turn one detected change into a Forma Issue and trace it to a native correction and new publication.
Pilot step 8
require a new package version and repeated verification before the issue can be closed.
Pilot step 9
identify use cases where a cloud coordination model is prohibited and a native Revit link is mandatory.
Pilot step 10
measure loading time, missing objects, misinterpreted changes, issue-closure time and the reduction in local copies.
The practical consequence for a BIM manager is clear. The team must govern not only the file but also the publication recipe. That recipe includes the source model issue, selected view, visibility rules, package name, intended use, permissions and the Revit versions used by recipients. If any component is unrecorded, the reference may be lightweight and fast but still unreliable.
Acceptance criteria should contain four forms of evidence. First, completeness evidence showing that the expected object set was published. Second, location evidence showing that coordinates and levels did not move. Third, semantic evidence confirming that critical categories and properties remain available. Fourth, process evidence showing that the package has the information state and a transmittal record. Only then does faster coordination become a controlled quality improvement rather than another layer of uncertainty.
For teaching, use a laboratory exercise in which students compare the same discipline model as a native Revit link and as a Cloud Coordination Model. They must identify what can only be seen, what can be checked, what cannot be documented and how the selected publication view changes the delivered information. Assessment should focus on the traceability of source, version, scope and intended use rather than visual similarity on screen.
Today’s final signal: a lighter coordination reference is valuable only when the project team can prove its source, scope, version, information state, intended use and connection to the change in the authoring model.
Original edition sources
These direct links were cited in the original scheduled brief. The scheduled message was retrieved in full on 25 October 2026; this recovery is not a claim of a fresh product test or new source validation.
- https://www.autodesk.com/blogs/aec/2026/09/24/a-lighter-way-to-coordinate-models-in-revit/ - https://help.autodesk.com/cloudhelp/2027/ENU/Revit-WhatsNew/files/GUID-B9284B64-E145-41D6-9242-9B243F262B2F.htm - https://help.autodesk.com/view/DOCS/ENU/?guid=About_Autodesk_Docs
Archive media note: This article follows the original written source package. The available public recording title does not establish an exact match, so no player is embedded. Original date-matched imagery has not been recovered.
