A shared folder in the cloud solves access. It does not say which file is current, who may change it, or what a reviewer was looking at. The UK guidance on ISO 19650 that we read separates three things: the state a file is in, the revision it has reached, and what it may be used for. The maker help pages we read describe versions and locks. None of them describes a status field of that kind, and we did not read enough of any product’s documentation to say whether one exists.
We read each source on November 15, 2026. Software notes report each maker’s page that day, for the version it names. This is not legal or security advice.
What a common data environment is
ISO’s catalogue page for ISO 19650-1:2018 says the document gives recommendations for a framework to manage information, including exchanging, recording, versioning and organizing, for all actors. It says the document can be adapted to assets or projects of any scale and complexity. The page shows the 2018 edition as current, confirmed in 2024, and expected to be replaced by a draft revision. We did not read the sold standard. ISO 19650-1:2018
The UK framework that supports the series publishes free guidance. Its Guidance C describes the common data environment, or CDE, as a combination of technical solutions and process workflows. It says a CDE solution could be software or another form of tool, and that an organized hard-copy cabinet can also be one. It says many different technologies can be used within a single workflow. It calls it fundamental that workflows are developed first and solutions are then selected to support them. IMI Framework, Guidance C
The framework’s home page lists Guidance C as Edition 3, November 2022. IMI Framework Home These pages opened for us without signing in. The older site lists the earlier PDF editions as archived. UK BIM Framework, Resources
The guidance is written for those managing information for an appointing party (a client) or a lead appointed party, such as a project manager, designer or main contractor. A US office has these roles only if its contract sets them up. IMI Framework, Guidance C
States, revisions and status
Guidance C describes four states for a file or other information container: work in progress, shared, published and archive. In its email analogy, the archive keeps each step of the trail as it happens. According to the guidance, ISO 19650-1 recommends a revision code and a status code for each container, and ISO 19650-2 requires that the CDE can assign those and a classification code. The guidance says this extra metadata should not be part of the file’s unique ID. That applies where a contract adopts the standard. IMI Framework, Guidance C
The guidance gives two reasons for a status code. It tells the recipient what the file may be used for. It also shows where the file sits in the workflow. The guidance says this avoids separating states into folders or other dedicated areas, which it says can fragment the CDE workflow. In an example where folders stand in for a missing classification field, it says folder structures should complement the metadata, not duplicate it. Its checklist asks whether a documented workflow exists for how each type of file is developed, checked, shared, authorized, accepted, published and archived. IMI Framework, Guidance C
Our interpretation: three points from the guidance are useful to an office that is not working to ISO 19650.
- Revision is not status. A revision code says how far the content has moved. A status code says what the recipient may use it for. The guidance’s example is that a file under review should not be used for contractual purposes such as procuring materials, agreeing contract costs or constructing the works.
- Work in progress has its own revisions. The guidance recommends revision control while a file is being developed, so the author can go back to an earlier version. Shared revisions are numbered separately.
- Published means authorized and accepted. In the UK scheme, published information has been authorized by the lead appointed party and accepted by the appointing party, and carries a different revision prefix from preliminary work. Some files, such as models used only for coordination, may never reach it. IMI Framework, Guidance C
The status codes themselves come from a table in the UK National Annex to ISO 19650-2, revised in February 2021. Guidance C says the codes can be expanded but not replaced to suit a project, and that unsuitable codes can be left out, provided the project’s information standard documents the choice. We do not repeat the table. IMI Framework, Guidance C
The framework’s Guidance 2, Edition 9 of November 2022, explains what the 2021 annex changed. For status, it says two shared codes were removed, one shared code was added and another reworded, one published code was removed, and an older group of codes was deprecated. It says the purpose behind each published code should be set out in the project’s information standard. Its account of the changes does not mention revision codes. It also warns that where status and revision are added to a file name, changing them may break linked file references. IMI Framework, Guidance 2
The codes are a UK convention. A US contract may name a different scheme or none.
What the National CAD Standard covers
The National Institute of Building Sciences describes the United States National CAD Standard as a consensus standard for uniformly organizing and presenting facility drawing information. Version 7 consists of the American Institute of Architects’ CAD Layer Guidelines, the Construction Specifications Institute’s Uniform Drawing System, Modules 1 to 8, and the institute’s BIM Implementation and Plotting Guidelines. It is sold as an online document under single, site and enterprise licences, set by the number of employees with access. The page shows 2024 beside the Version 7 listing. NIBS, National CAD Standard
The standard’s own site speaks of voluntary adoption across the industry. It says the Drawing Set Organization module establishes set content and order, sheet identification and file naming for a set of construction drawings. NCS Version 7 Content Its question page gives the current version as Version 7, published in September 2025. Its answers say model file naming is addressed in Module 1 of the Uniform Drawing System and that model file names can include optional user-defined characters. Another answer says a supplemental drawing revising part of sheet A-102 would be identified as A-102-R1. The page marks that answer as specific to version 3.1. The model file answers carry no version mark. NCS, Frequently Asked Questions
We did not read the licensed standard. From the public pages, our reading is that it governs how drawing files and sheets are named and organized. We found nothing on those pages about a shared data environment, file states or status codes. An owner or agency may require it by contract; the contract decides.
What the makers’ help pages say
These notes report documentation, not tests. Each product does more than is listed.
Trimble Connect for Browser. The help page says the product tracks the revision history of uploaded files and lets a user view or download a particular revision. A new version must be uploaded under the same file name. Moving a file to another folder creates a new version, and so does renaming it. The page states no product version. Trimble Connect, File Version History A separate page describes check out and check in as revision control: a user checks out a file or folder to prevent others from changing it. While it is checked out, other project users can download and share it but cannot upload a new version, rename, move or delete it; a project administrator can rename, move and check it in. Both actions are recorded on the activity page. Trimble Connect, Check in and Check out
Bluebeam Studio. The Revu 21 help says only files that have been checked out of a Studio Project can be edited, and only one user can check out a file at a time. A file opened without check-out is read-only. Check In returns the file with its changes, and Revision History opens earlier versions. Bluebeam, Work with files in a Studio Project A support article for Revu 21 and Revu 20 says Studio Sessions, the shared markup space, do not maintain a revision history of files and support PDFs only. It describes a workflow in which a Project PDF is added to a Session, marked up, and written back to update the Project file, so the Project keeps the history. Bluebeam, Revision history for Studio Sessions
Vectorworks 2027. The help describes project sharing: one project file is stored on a cloud file service, a network share or the maker’s Project Sharing Server, and each user works in a local working file. A user checks out layers or objects, and no one else can change them until they are released. Users commit changes to the project file and refresh from it. The page says everyone sharing a project must use the same version of Vectorworks, and that the cloud storage method works best with small teams, to keep syncing delays down. The page does not discuss version history. Vectorworks 2027, Concept: Project sharing
Autodesk: one page on locking, from Civil 3D 2023. This is that release’s documentation. It said a drawing stored in Autodesk Docs was locked automatically when opened in Civil 3D 2023, and others could open it read-only until it was closed. It said locking was not automatic in Civil 3D 2020.1 or earlier, or in AutoCAD and AutoCAD-based products, where a user should lock the file by hand before editing. If two people edited an unlocked file and both uploaded, the document showed a Conflict status. Autodesk, Civil 3D 2023 Help We did not find the equivalent page for later releases, so check the help for the release you run.
Autodesk’s current help for its cloud files is titled Forma Data Management. We found no Autodesk page relating that name to Autodesk Docs. Its overview page says the Files tool can enforce a file naming standard on selected folders. It says project administrators can create smart controls that add or remove file versions depending on whether they meet defined attribute conditions. Autodesk, About Files The topic pages linked from it returned Page Not Found for us, so we read nothing on how it creates versions or locks files.
As we read these pages: Trimble Connect, Bluebeam Studio Projects and Civil 3D 2023 with Autodesk Docs lock a whole file (Trimble also a folder), and Vectorworks project sharing locks layers or objects. In Trimble Connect and Bluebeam, a version is created by an upload or a check-in, and in Trimble Connect also by a rename or a move. None of the pages describes a status field of the kind the UK guidance means. On markup, we read only the Bluebeam note that a Session keeps no revision history unless it is tied back to a Project file.
Access and backup, as NIST and CISA put it
NIST’s quick-start guide for small businesses lists actions to consider. They include restricting sensitive information to the employees who need it for their jobs, requiring multi-factor authentication on all accounts that offer it, and regularly backing up data and testing the backups. It asks whether access is removed when no longer needed. NIST SP 1300
NIST’s white paper for firms with no employees other than the owners was published on November 2, 2026. It lists enabling phishing-resistant multi-factor authentication, especially on email, sensitive file storage and business-critical cloud accounts. It lists using standard user accounts in place of administrator accounts whenever possible, and establishing a backup strategy with measures to protect and test backups. As a business grows, it says to remove access when an employee leaves or a third-party service agreement ends. NIST CSWP 50
CISA’s Cyber Essentials, a guide for leaders of small businesses and small agencies, lists multi-factor authentication for all users, starting with privileged, administrative and remote access users. It lists granting access and admin permissions on need-to-know and least privilege, and establishing regular automated backups. CISA, Cyber Essentials CISA’s page on multi-factor authentication says to opt in whenever it is available. CISA, More than a Password
An older US-CERT paper hosted by CISA states the 3-2-1 rule: keep three copies of any important file, on two different media types, with one copy offsite. It covers cloud storage as one backup option and advises weighing its risks for sensitive data. Its footer is dated 2012. CISA, Data Backup Options
Our interpretation: none of these sources discusses version history inside a collaboration tool, so they do not settle whether it counts as a backup. Whether a given service’s history or recycle bin meets the three-copy rule is a question for that service’s documentation and the office’s own risk decision.
A small-office scheme, as our own suggestion
This scheme is ours and untested. It follows the guidance’s states. A contract, an owner’s standard or a project information standard overrides it.
- Record the state of each file. Where the tool has a status field or the office keeps a register, record state there, as the UK guidance prefers. Where neither exists, folders for work in progress, shared and published are a fallback, and the guidance cautions that such folders can fragment the workflow. If folders are used, keep the working file in one place and put only issued copies, such as dated PDFs, in shared or published. Moving or renaming creates a new version in at least one product above, and the UK guidance warns that name changes can break linked file references. IMI Framework, Guidance 2
- Received files kept apart. Keep files from consultants and the client in their own area, by sender and date, unedited, and reference them from there. The UK guidance treats accepted information from an earlier stage as reference information for the next stage of work. IMI Framework, Guidance C
- A name that does not change. Our suggestion is a fixed set of fields, such as project number, originator, discipline, type and a sequence number. Where a contract or the National CAD Standard sets the names, use those instead.
- Revision and status outside the name where the tool has a metadata field or the office keeps a register. Otherwise keep a transmittal register that lists file, revision, status, date and recipient.
- One editor per file, or per checked-out part. Use the product’s check-out or lock, and check in the help for your release whether it locks automatically.
- Reviews on a copy with a known revision. Record which revision reviewers saw, and file the marked-up set with the issue. Keep superseded issues. Guidance C’s checklist suggests naming a PDF differently from its native drawing. IMI Framework, Guidance C
- Access and backup by the agencies’ guidance. We give no security advice of our own. The NIST and CISA documents above cover who should have access, multi-factor authentication, removing access when someone leaves, and tested backups. NIST SP 1300 CISA, Cyber Essentials
What we could not settle
- What ISO 19650-1 and 19650-2 require in their own words, and what the coming revision changes. They are sold documents.
- Whether the 2021 National Annex changed revision codes. The guidance’s account of the changes does not mention them, and we did not read the annex.
- What the National CAD Standard Version 7 says on file naming and revisions in full, and whether the National BIM Standard addresses a shared data environment. We read public pages only.
- How Forma Data Management, as Autodesk’s current help names the cloud file product, handles versions, locks and reviews, and whether current releases of AutoCAD and Civil 3D lock cloud files automatically.
- How markup and review records compare across the products, and how long each keeps version history.
- How long project records must be kept. That depends on the contract, the licensing board and state law. Ask the board or counsel.
Field Method files in a shared project
Base Plan is a draft tool that makes a base plan, CAD linework and a to-scale 3D model for San Diego County parcels from public data. Its page says the DXF layer names follow the National CAD Standard format, and that the property-line layer name has not been checked against the standard’s text. It also says the tool has not yet been opened in a CAD program or checked against a survey. Give its downloads a fixed name and a date, and file them as reference information, not as a survey.
Sources
- ISO — ISO 19650-1:2018, Information management using building information modelling, Part 1: Concepts and principles (catalogue page)
- IMI Framework (BSI and nima) — ISO 19650 Guidance C: Facilitating the CDE (workflow and technical solutions)
- IMI Framework (BSI and nima) — IMI Framework Home
- UK BIM Framework (IMI Framework) — Resources
- IMI Framework (BSI and nima) — ISO 19650 Guidance 2: Delivery phase
- National Institute of Building Sciences — United States National CAD Standard (NCS)
- United States National CAD Standard — Version 7 Content
- United States National CAD Standard — Frequently Asked Questions
- Trimble — Trimble Connect for Browser: File Version History
- Trimble — Trimble Connect for Browser: Check in and Check out
- Bluebeam — Work with files in a Studio Project (Revu 21)
- Bluebeam — Create a revision history for Studio Sessions PDFs (Revu 21, Revu 20)
- Vectorworks — Vectorworks 2027 Help: Concept: Project sharing
- Autodesk — Civil 3D 2023 Help: About Locking Documents Stored in Autodesk Docs
- Autodesk — Data Management Help: About Files
- NIST — SP 1300, NIST Cybersecurity Framework 2.0: Small Business Quick-Start Guide (February 2024)
- NIST — CSWP 50, Small Business Cybersecurity: Non-Employer Firms (November 2, 2026)
- CISA — Cyber Essentials
- CISA — More than a Password (multifactor authentication)
- CISA (US-CERT) — Data Backup Options
Try a relevant tool
These tools support site review and design studies. Read each tool’s stated capabilities and limits before use.
Explore Base Plan