Which version of the drawings is current? Nobody knows.

The naming convention problem that costs architecture firms real money

Every architecture firm has a folder somewhere with a file called FINAL_v2_REVISED_ISSUED.dwg. Everyone who works in the industry has seen it. Everyone has a story about the time the wrong version went to the contractor.

The problem is old, well understood, and remarkably persistent. Drawing sets go through dozens of revisions over the life of a project. Each revision needs to be coordinated across disciplines, checked against specifications, and distributed to the right people at the right time. In theory, the file naming convention handles this. In practice, the naming convention is where things start to fall apart.

How drawings drift out of sync

A typical commercial project might produce hundreds of individual drawing sheets. Architectural, structural, mechanical, electrical, and plumbing disciplines each maintain their own sets. During design development and construction documentation, revisions come frequently, sometimes daily during intense coordination phases.

The standard approach is to keep everything on a shared network drive, organised into folders by discipline and phase. File names include revision numbers or dates. A project manager or document controller maintains a register. On paper, the system works.

In practice, several things go wrong at once. Someone downloads a set to work on it locally and forgets to upload the latest version. A consultant emails a revised sheet, and it gets saved to a desktop instead of the server. Two people edit the same file simultaneously, and one overwrites the other's changes. The revision register falls out of date because updating it is a manual step that gets skipped when deadlines are tight.

The result is a shared drive full of files where nobody can be entirely confident which version is the definitive one. People develop workarounds. They email colleagues to ask "is this the latest?" They add personal suffixes to file names. They keep their own local copies "just in case." Each workaround makes the underlying problem worse.

The cost of version confusion

When the wrong version of a drawing reaches a construction site, the consequences are tangible. A subcontractor builds to a superseded detail. The error might be caught during inspection, or it might not be caught until much later, when remediation is expensive and disruptive.

Even when errors are caught early, the rework costs money. A structural detail built to an old revision might need to be demolished and rebuilt. A mechanical rough-in based on a superseded layout might conflict with the architectural intent. These are the kinds of problems that generate RFIs, delay schedules, and erode the trust between project teams.

Liability is the other concern. When a dispute arises about which version was issued, the paper trail matters enormously. If the shared drive contains multiple copies of the same drawing at different revision stages, establishing which one was formally transmitted becomes an exercise in forensic file archaeology. Modification dates can be misleading. File names can be ambiguous. The revision register, if it was maintained at all, might not match what is on the server.

Professional indemnity insurers are keenly aware of these risks. Version confusion is a contributing factor in a significant number of claims against design professionals. The defence costs alone, setting aside any settlement, can be substantial.

Why shared drives struggle with version control

Network file servers were designed for general-purpose file storage. They do that job well enough. What they were not designed for is managing the lifecycle of documents that go through frequent, coordinated revisions across multiple contributors.

A shared drive has no built-in concept of a "current" version. It stores files. If you save a new version with a different name, both versions exist side by side, and the drive treats them as equals. If you save over the old file, the previous version may or may not be recoverable depending on backup schedules and IT policies.

Some firms address this by layering document management systems on top of the shared drive. These can help, but they add complexity. Staff need training. The system needs administration. And if the document management layer is optional rather than enforced, people will route around it when they are in a hurry, which is precisely when version discipline matters most.

More sophisticated firms use BIM management platforms with proper version control, check-in and check-out workflows, and audit trails. These tools exist and they work, but they are expensive, complex to set up, and require a level of IT infrastructure and ongoing support that many small and mid-sized practices cannot justify.

The gap in the market is between the shared drive (cheap, simple, insufficient) and the full enterprise document management system (capable, expensive, complex). Most firms of ten to fifty people fall into this gap.

A single source of truth

The most common failure mode in drawing version management is duplication. The moment a file exists in two places, those two copies can diverge. The longer they coexist, the more likely they are to diverge. Every copy is a potential source of confusion.

The simplest way to prevent this is to maintain one canonical copy of each file, accessible to everyone who needs it, from wherever they need it. This is the core idea behind Fabric's cloud drive (https://fabric.so/features/your-cloud). Files live in the cloud and are streamed on demand. There is one copy. When someone opens a file, they get the current version because there is only one version to get.

This does not solve every version control problem. Fabric is not a full version control system in the way that Git tracks every change to a codebase, and it does not replace the specialised BIM management platforms that large firms use for complex multi-disciplinary coordination. What it does is eliminate the most common and most damaging failure mode: the proliferation of copies across desktops, laptops, local drives, and email attachments that creates the version confusion in the first place.

Because the cloud drive streams files without consuming local storage, there is no incentive to download copies for offline access or to "work locally and upload later." The file is always accessed from its single location. The workflow that causes drift is removed, rather than managed through policy and discipline.

Finding the right drawing

Version confusion and findability are related problems. Even when you know the current version exists somewhere on the server, locating the specific sheet you need can be its own challenge. Folder structures in architecture firms tend to grow organically. Naming conventions vary between projects, between disciplines, and sometimes between individuals within the same team.

Fabric's semantic search (https://fabric.so/features/search) addresses this by letting you search by meaning rather than by file name. Instead of navigating through nested folders and remembering the exact naming convention, you can describe what you are looking for. A search for "ground floor reflected ceiling plan" or "stair detail section B" will surface relevant results based on the content and context of the files, not just their names.

This is particularly useful for people outside the core design team, such as site managers, quantity surveyors, or client representatives, who need to find specific information but may not be familiar with the firm's internal folder structure or naming conventions. It is also useful during the later stages of a project when the volume of drawings is large and the folder structure has become dense.

Connections to existing tools

Most architecture firms already have files spread across multiple platforms. Project drawings might be on a local server, consultant drawings in Dropbox, client correspondence in Google Drive, and specifications on a SharePoint site. This fragmentation makes the version problem worse, because the same drawing might exist in different states across different platforms.

Fabric's connections feature (https://fabric.so/connections) allows you to bring files from Google Drive, Dropbox, and other cloud storage services into a single searchable space. Rather than replacing existing storage, it layers a unified view on top of it. This reduces the need to maintain parallel copies across platforms and makes it easier to locate the most recent version of any document.

Annotations and markup

During the review process, drawings accumulate comments, markups, and annotations from multiple reviewers. When these markups live in separate files, on printed copies, or in email threads, they become another source of version confusion. Which comments have been addressed? Which markup set corresponds to which revision?

Fabric's annotation tools (https://fabric.so/features/annotations) allow markup directly on files within the platform. Annotations stay attached to the file they belong to, so there is no ambiguity about which version a comment refers to. For firms that review drawings digitally rather than on printed sets, this keeps the conversation anchored to the document.

What this approach does and does not solve

It is worth being clear about the boundaries. Fabric provides a single source of truth for files and a way to find them by meaning. It reduces the risk of version drift caused by file duplication. It makes drawings easier to locate and review.

It does not provide the kind of granular, commit-level version history that software developers expect from Git. It does not manage the formal transmittal and distribution process that large projects require. It does not replace BIM coordination platforms like BIM 360 or Aconex for projects that need those capabilities.

For many small and mid-sized architecture firms, though, the core issue is simpler and more fundamental than version control tooling: too many copies of the same file in too many places, with no reliable way to know which one is current. That is the problem a cloud-based single source of truth addresses.

Organising files without the folder maze

Beyond version confusion, the way drawing sets are organised affects how quickly people can find what they need. Fabric's smart organisation features (https://fabric.so/features/smart-organization) help keep project files structured without requiring rigid folder hierarchies that become difficult to maintain as projects evolve. Combined with semantic search, this means that the organisational structure can be flexible without sacrificing findability.

Sharing with external parties

When drawings need to be shared with clients, consultants, or contractors, Fabric's publish feature (https://fabric.so/features/publish) allows you to create polished, shareable pages with link analytics. You can see who has accessed the shared content and when, which provides a basic audit trail for document distribution. This is a modest but useful improvement over emailing attachments, where you have no visibility into whether the recipient has opened the file or which version they are working from.

Frequently asked questions

Does Fabric replace BIM management software?

No. Fabric is a cloud drive with semantic search and file streaming. It is not a BIM tool, a CAD editor, or a replacement for specialised platforms like BIM 360 or Aconex. It addresses the file duplication and findability problems that sit upstream of those tools.

Can Fabric handle large CAD and BIM files?

Fabric's cloud drive streams files on demand without consuming local storage. This makes it suitable for storing and accessing large files, but the editing of those files still happens in the native application (AutoCAD, Revit, ArchiCAD, and so on).

Does Fabric track every change to a file like Git does?

No. Fabric maintains a single canonical copy of each file rather than a full commit history. Its value for version management lies in eliminating the multiple-copies problem, not in providing granular change tracking.

How does semantic search work for drawing files?

Fabric's semantic search (https://fabric.so/features/search) indexes files by meaning rather than just file name. You can search for concepts like "second floor electrical layout" and find relevant results even if the file name uses a different naming convention.

Can I connect Fabric to our existing cloud storage?

Yes. Fabric's connections feature (https://fabric.so/connections) supports Google Drive, Dropbox, and other cloud storage services, allowing you to bring files from multiple sources into a single searchable space.

Is Fabric suitable for formal document transmittals?

Fabric's publish feature (https://fabric.so/features/publish) provides shareable links with analytics, which is useful for informal distribution. For formal transmittal workflows with contractual significance, most firms will still need a dedicated transmittal system or process.

How much does it cost to set up Fabric for an architecture firm?

Fabric does not require the kind of IT infrastructure or administration that enterprise document management systems demand. You can get started at https://fabric.so and begin using the cloud drive and search features without a complex setup process.

Can multiple team members access the same files simultaneously?

Yes. Because files live in the cloud and are streamed on demand, any team member with access can view the current version of any file at any time. The single-copy model means everyone is always looking at the same file.

Does Fabric work on mobile devices for site visits?

Yes. Fabric's cloud drive is accessible from any device with an internet connection, including phones and tablets. Files are streamed rather than downloaded, so they do not consume local storage on the device.

What happens if our internet connection drops?

Fabric requires an internet connection to access files. It does not currently offer offline support. For site visits in areas with limited connectivity, this is a consideration worth planning for, though most urban and suburban sites have adequate cellular coverage.

Related pages

• https://fabric.so/features/your-cloud

• https://fabric.so/features/search

• https://fabric.so/features/smart-organization

• https://fabric.so/features/annotations

• https://fabric.so/features/publish

• https://fabric.so/connections

• https://fabric.so/features/ai-assistant