In the world of architecture and engineering, there is perhaps no greater source of anxiety than the phrase, "I think I'm looking at the wrong version of the drawing."

We have all seen it: files named Drawing_A101_Final.dwg, Drawing_A101_Final_v2.dwg, and the dreaded Drawing_A101_FINAL_FOR_CONSTRUCTION_ACTUALLY_FINAL.dwg. This "version chaos" isn't just a nuisance-it is a massive liability. When a contractor builds from an outdated revision, the result is expensive rework, wasted materials, and eroded profit margins. In fact, industry research from InspectMind shows that 5–15% of construction project costs are lost to rework, with over half of those errors caused by poor project data and miscommunication.

To stop this cycle, you need a rigorous Drawing Revision Control system. While many firms use SharePoint, network drives, or platforms like Aconex, the software itself isn't the solution-the process is.

Here is a step-by-step guide to setting up a professional revision control workflow aligned with ISO 19650 standards.

The Foundation: The "State" of Information

Before setting up folders or naming files, you must define the state of your drawings. Following the ISO 19650 framework, a Common Data Environment (CDE) divides information into four distinct containers based on its maturity and trustworthiness:

Work in Progress (WIP): Where the drawing is actively being created. Access is restricted to the immediate authoring team. This is considered "untrusted" information.
Shared: Information that has been checked and approved for coordination with other disciplines (e.g., the Architect shares a floor plan with the Structural Engineer to ensure no clashes).
Published: The "Single Source of Truth." These are the official, client-approved deliverables used for construction and formal procurement.
Archived: A historical record of every version, transmittal, and milestone, maintained for legal and audit purposes.

Step 1: Establish a Standardized Naming Convention

You cannot control revisions if your files are named haphazardly. A standardized naming convention allows anyone-and any system-to identify a file without having to open it. As noted by Bimicon, such a convention is mandatory to achieve higher BIM maturity levels where data is exchanged seamlessly between disciplines.

Avoid generic names. Instead, use a delimited string that identifies the project, the originator, the zone, and the type.

Example Format: ProjectCode-Originator-Volume-Level-Type-Role-Number

Bad: FloorPlan_v2.dwg
Good: PRJ01-ARC-ZZ-01-DR-A-0001.dwg

The Golden Rule: Keep the filename identical across revisions. Do not append "_v2" to the filename. Instead, handle the versioning via metadata or a dedicated revision column. This prevents broken links in CAD/BIM software and eliminates the clutter of multiple "Final" files.

Step 2: Structure Your Environment for Governance

If you are using SharePoint, avoid the temptation to create a "dumping ground" of deep, nested folders. Deep hierarchies are where order goes to die; they lead to broken file paths and OneDrive sync errors. More importantly, uncontrolled hierarchies lead to "folder sprawl," where users create their own local folders with nonsense names because they can't find what they need.

Instead, aim for a shallow, disciplined structure. While ISO 19650 states are traditionally managed via folders, the modern, scalable approach is to use metadata-driven architecture to optimize document retrieval and automate filename compliance.

By applying tags to your files, you can instantly query the status of any deliverable (e.g., "Show me all 'Published' structural drawings") without digging through a maze of directories. If you do use folders, keep them broad and high-level:

Library 1: WIP (Restricted access by discipline)
Library 2: Shared (Read-only for most; managed by a Lead Coordinator)
Library 3: Published (The only place contractors should look for construction sets)

Step 3: Implement a Formal QA/QC Workflow

A drawing should never move from WIP to Shared or Published without passing through a digital "gate." Many firms fail here by simply moving a file from one folder to another without verification.

A robust CDE requires standardized statuses and formal approval procedures:

Author: Completes the drawing and marks it "Ready for Review."
Reviewer: Checks for technical accuracy, coordination clashes, and ISO compliance.
Approver: Provides the final sign-off on the revision.
Action: Only after approval is the file moved to the "Shared" or "Published" area, and the revision number is officially incremented (e.g., P01 → P02).

Step 4: Manage the "Issue" Register

Simply having the latest file available is not enough; you must be able to prove who received it and when.

Maintain an Issue Register (or Transmittal Log). This log acts as your audit trail and should track:

The drawing number and specific revision.
The exact date of issue.
The intended recipient.
The purpose of the issue (e.g., "For Information," "For Approval," or "For Construction").

Step 5: Stabilize the CAD/BIM Workflow

For firms heavily reliant on Revit or AutoCAD, file paths are the backbone of your production. To prevent system instability and broken links:

Limit Syncing: Avoid syncing massive, entire project libraries to every local machine via OneDrive, as this can cause significant performance lag.
Control Library Size: Break large projects into multiple document libraries to maintain SharePoint performance.
Avoid Manual Renaming: As mentioned in Step 1, never rename a file to indicate a new version. Renaming a file often causes software like Civil 3D to lose Xref links, leading to hours of manual repair. Rely on the platform's built-in version history and metadata to track changes.

Common Pitfalls to Avoid

The "Folder Rabbit Hole": Creating endless subfolders. Use metadata (tags) to categorize drawings by discipline, zone, or status instead.
Broken Permissions: Granting "Full Control" to everyone to "make things easier." Use structured groups (e.g., "Architects-WIP," "Contractor-Published") to ensure users only see the information relevant to their role.
Manual Tracking: Relying on a disconnected spreadsheet that only one person updates. If your Issue Register isn't linked to your file environment, it will eventually become inaccurate and useless.

Scaling Your Revision Control

For small, low-complexity projects, a manual folder-and-log system might suffice. However, as your projects grow in scale and complexity, the administrative overhead of managing these processes manually becomes a bottleneck.

This is where a dedicated CDE framework becomes essential. By transforming a standard SharePoint setup into a structured CDE, you can automate the movement of files between WIP and Published states, enforce naming conventions via metadata, and create real-time dashboards that show exactly which drawings are pending approval.

The goal is to move from a system based on trust ("I hope this is the right version") to a system based on governance ("I know this is the right version because the system says so").

Ready to stop the version chaos? Learn how to transform your SharePoint into a professional Engineering CDE.

Loading...