Your CAD files live on one person's laptop

The single-point-of-failure problem in small architecture and engineering firms, and what to do about it

The laptop problem

In a firm of five to thirty people, the CAD files for a given project tend to live on the machine of whoever started that project. Sarah drew the initial site plan on her workstation, so the DWG files are on Sarah's hard drive. When someone else needs a file, they ask Sarah. If Sarah is at her desk, she copies it to the shared drive or emails it over. If Sarah is on holiday, at a site visit, or home sick, the file is effectively inaccessible until she returns.

This is a common arrangement in small-to-mid architecture and engineering practices. It develops organically. Nobody decides that critical project files should depend on one person's availability. It happens because working from a local drive is fast, shared drives are slow or unreliable, and the friction of uploading files to a central location after every save is just high enough that people skip it.

The result is a fragile system where project continuity depends on the physical presence of specific individuals. This fragility is invisible most of the time. It only surfaces when someone is unexpectedly unavailable, and by then the problem is urgent.

Why shared drives do not solve this

Many firms have a shared network drive or a NAS box in the office. In theory, this is where all project files should live. In practice, the shared drive is often slow, particularly for large CAD files. Opening a 50 MB DWG file from a network drive over a congested local network can take noticeably longer than opening it from a local SSD. That delay, even if it is only a few seconds per file open, is enough to push people toward keeping working copies on their own machines.

Once someone copies a file to their local drive to work on it, two copies exist. The local copy gets edited throughout the day. The shared drive copy grows stale. At the end of the day, the person may or may not remember to copy the updated file back. If they do, they may overwrite a version that someone else updated in the meantime. If they do not, the shared drive holds yesterday's file and the current version sits on a laptop that goes home at 5:30.

This is not a question of discipline or training. People in small firms are busy. They are juggling multiple projects, client calls, site visits, and deadlines. Remembering to upload files at the end of every work session is a manual step in a workflow already full of manual steps. The ones who remember most of the time still forget occasionally, and "occasionally" is often enough to create version confusion.

Cloud storage services like Google Drive and Dropbox improve on the NAS box by synchronising files automatically. But they introduce their own problems with large CAD files. Sync conflicts are common when two people edit files in the same folder. Dropbox's sync engine sometimes struggles with the file-locking behaviour of AutoCAD, leading to duplicated files with "(conflicted copy)" in the filename. Google Drive's desktop client, File Stream, can be slow to recognise changes to large binary files. And both services consume local storage for synced files unless you carefully configure selective sync, which most people in a busy practice do not do.

The departure problem

The laptop problem becomes acute when someone leaves the firm. An employee who resigns takes their institutional knowledge with them, but they also leave behind a hard drive full of project files that may or may not have been copied to the shared drive. The IT handover process, if there is one, involves someone sitting at the departing employee's desk, trying to figure out which folders contain current project files, which are old versions, and which are personal files that should be deleted.

In firms without dedicated IT staff, this handover is often done by the office manager or a senior architect who has other priorities. Files get copied in bulk to an external drive or a folder on the server labelled "John's files - to sort." That folder sits there for months or years, and when someone needs a file from one of John's old projects, they dig through an unsorted archive hoping the filename gives enough clues.

This problem compounds over time. Every departure leaves another folder of unsorted files. Every new employee starts fresh on their own machine. The firm's collective project archive becomes increasingly fragmented, spread across active machines, old hard drives, backup drives in desk drawers, and cloud storage accounts that may or may not still be accessible.

The remote work complication

The shift toward hybrid and remote work has made the laptop problem worse. When everyone worked in the same office, you could at least walk over to someone's desk and ask them to copy a file. With team members working from home two or three days a week, the file on Sarah's workstation is inaccessible unless Sarah is in the office, unless the firm has set up a VPN or remote desktop solution.

VPNs and remote desktop tools work, but they add latency and complexity. Connecting to the office network from home, navigating to someone else's machine, and copying a file over a VPN connection is slow and error-prone. Many small firms set up a VPN during the pandemic and have been tolerating its limitations since, without ever investing in a proper long-term solution.

The fundamental issue is that files tied to physical machines become anchored to physical locations. A firm that wants its team to work flexibly needs its files to be location-independent.

What centralisation looks like in practice

Solving the laptop problem requires moving the canonical copy of every project file to a location that is accessible to the whole team, regardless of who started the project or which machine they use. This sounds simple. The difficulty is doing it without making people's daily work slower or more complicated.

Fabric's cloud drive addresses this by storing files in the cloud and streaming them on demand. Files appear in the user's file browser as though they were local, but they occupy no space on the local hard drive. When someone opens a file, Fabric streams the data needed. When they close it, no local copy lingers. The canonical version lives in the cloud, accessible to everyone on the team, from any device.

This approach eliminates the two-copy problem. There is no local working copy that diverges from the central copy. There is one copy, in the cloud, and everyone accesses it directly. When Sarah saves a change, the file is updated for everyone. There is no upload step to remember, no sync delay to wait for, and no conflicted copies to reconcile.

The storage question

CAD files are large, and architects and engineers accumulate a lot of them. A single project might generate hundreds of DWG files, plus associated XREFs, plot files, PDFs, and supporting documents. Over the course of a year, a small firm can easily produce tens of gigabytes of project data.

Local hard drives fill up. This is especially true for laptops, which tend to have smaller SSDs than desktop workstations. An architect with a 256 GB or 512 GB laptop SSD can run out of space within a year if they are keeping multiple project files locally. The usual response is to delete old projects or move them to an external drive, which just shifts the accessibility problem to a different location.

Fabric's cloud streaming model avoids this entirely. Because files are streamed rather than stored locally, the size of your file library has no relationship to the capacity of your hard drive. A firm with terabytes of project history can keep every file accessible without asking anyone to upgrade their laptop or manage external storage.

Sharing files outside the firm

The laptop problem also affects how firms share files with external collaborators. When a structural engineer needs the latest architectural DWG for coordination, someone in the architecture firm has to find the file, make sure it is the current version, and get it to the engineer. If the file lives on one person's laptop and that person is unavailable, the coordination meeting gets delayed.

Fabric's publish feature lets you create shareable links to files and folders. You can send a consultant a link to the relevant project folder, and they can access the files directly. Fabric's link analytics show whether the recipient has opened the link, which is useful for tracking whether consultants have picked up the latest drawings before a coordination deadline.

Finding old files

Six months into a project, someone needs a drawing from the early concept phase. The file was created by a team member who has since moved on to a different project, or possibly a different firm. The filename might be something like "Site Plan Option B rev2.dwg" or it might be "SP_02_20240315.dwg." Without asking the person who created it, finding the right file means scrolling through folders and opening files until the right one turns up.

Fabric's semantic search indexes files by content and meaning, so a search for "concept site plan with the angled building" can surface relevant files even when filenames are unhelpful. This is particularly valuable in firms where naming conventions are inconsistent, which is to say most firms.

Connecting existing storage

Migrating files to a new platform sounds like a large project, and for firms with years of accumulated files, it can feel daunting. Fabric connects to dozens of existing storage services, including Google Drive, Dropbox, and other common platforms. This means you can bring existing files into Fabric's workspace without copying everything manually or abandoning your current setup.

The connections feature lets you integrate gradually. Start with one active project and see how the workflow feels. Move more projects over as confidence builds. The existing files in your current storage remain accessible through Fabric's unified interface.

Notes on what Fabric is and is not

Fabric is a cloud workspace and file management platform. It handles storage, organisation, search, and sharing. It does not replace AutoCAD, Revit, or any other CAD authoring tool. You continue to do your design work in the software you already use. Fabric provides the layer around those tools that keeps files centralised, findable, and shareable.

Fabric does not currently support offline access. For site visits or travel without internet, you would need to plan ahead and download the files you expect to need. For day-to-day office and remote work with an internet connection, the cloud streaming model works well.

Fabric also offers an AI assistant that can help with tasks like summarising documents, answering questions about file contents, and organising materials. Annotations support timestamped notes on video and audio files and drawing on images, which can be useful for project documentation and review.

The smart organisation features help maintain a coherent folder structure as projects grow. For firms whose file organisation has evolved organically over years, this can bring some order to the archive.

Frequently asked questions

How does Fabric's cloud drive handle large AutoCAD files?

Fabric streams files on demand rather than syncing them to your local drive. When you open a DWG file, Fabric delivers the data your application needs. The file appears local to AutoCAD, but it does not consume permanent space on your hard drive. This works well for the large binary files common in CAD workflows.

Can multiple people access the same CAD file at the same time?

Fabric provides centralised cloud storage and makes files accessible to everyone on the team. File-level collaboration, such as multi-user editing of a DWG, depends on the capabilities of the CAD software itself. Fabric ensures that everyone is working from the same canonical file location rather than separate local copies.

What happens to files when an employee leaves the firm?

Because files are stored in Fabric's cloud rather than on individual machines, an employee's departure does not create a file accessibility gap. The files remain in the team's cloud workspace exactly where they were, accessible to everyone with the appropriate permissions.

Does Fabric work with files on an existing shared drive or NAS?

Fabric connects to dozens of cloud storage services. For files on a local NAS, you would upload them to Fabric's cloud drive or to a connected cloud service. Fabric does not directly mount local network drives, but the migration path is simple for most setups.

Can I access files from home or on site?

Yes. Fabric's cloud drive is accessible from any device with an internet connection, through the desktop app, mobile app, or web browser. This makes remote and hybrid work practical without VPN configurations or remote desktop tools.

Does Fabric require dedicated IT staff to set up?

No. Fabric is a cloud service that requires no server infrastructure, no network configuration, and no IT expertise to deploy. A firm principal or office manager can set it up and invite team members without technical assistance.

How does semantic search differ from regular file search?

Regular file search matches filenames and, in some cases, text content. Fabric's semantic search understands meaning, so searching for "foundation detail section" can find relevant files even if the filename is "SD-401_rev3.dwg." This is particularly useful when naming conventions vary across projects and team members.

Can I share files with external consultants who do not use Fabric?

Yes. Fabric's publish feature generates links that anyone can open in a browser without creating an account or installing software. You can share individual files or entire project folders with consultants, clients, and other external collaborators.

Is Fabric a replacement for AutoCAD or Revit?

No. Fabric is a file management and cloud storage platform. It organises, stores, and shares your files. You continue to use AutoCAD, Revit, and other design tools for your drawing and modelling work. Fabric provides the infrastructure layer that keeps those files centralised and accessible.

Does Fabric support offline access for site visits?

Fabric does not currently support offline access. For site visits without reliable internet, you would need to download the files you expect to need before going offline. For all connected work, whether in the office or working remotely, files are available on demand.

Related pages

• Cloud drive

• Semantic search

• AI assistant

• Connections

• Publish and share

• Smart organisation

• Annotations

• Architecture studios

• For consultants

• Desktop app