Why Revisions Go Wrong in the First Place

Most lost work isn't lost to a crash. It's lost at ten to five on a Thursday, when two people open the same floor plan, one saves, and the other saves a minute later. The first person's morning of reworked stair cores disappears without so much as a warning dialog.

The pattern repeats in every office. Files live on a shared drive but get copied to a desktop for speed. A colleague sends a "quick update" as an attachment. Someone opens a model from a backup folder because the network was crawling. Each of those detours creates its own branch of the truth, and within a fortnight nobody can confidently say which file is current.

Revision control doesn't have to be bureaucratic. It needs three things: file names that carry information, one agreed place where the latest version lives, and a short record of who changed what and why.

Build a File Name That Tells the Story

A well-built file name answers four questions before you open anything: which project, which discipline or zone, which drawing or model, and which revision. Something along these lines works for almost every practice:

24118-MEC-Zone3-Drainage-Plan-R0123456789.dwg

• Project number — matches your job folder, fee proposal and purchase ledger.
• Discipline or zone — stops MEP and structural files colliding on large jobs.
• Description — short, hyphenated, no spaces, no waffle.
• Revision code — R01, R02, or letters where an issued stage needs marking.
• Date — in ISO format (YYYY-MM-DD) so files sort chronologically rather than clustering under month names.

Ban the words final, latest, new and actual. They are lies within a week, and they multiply. Numbers and dates don't lie, and they don't argue back.

Keep a Revision Register — It Can Be Small

A register is a single shared sheet, nothing more. One row per issued file, with columns for file name, revision code, date, author, a one-line description of the change, who it was issued to, and status — work in progress, issued, or superseded.

The column people skip is the description, and it's the one that saves the most time. "Adjusted grid line C to suit steel delivery" tells the next person far more than "updated". Twenty seconds of typing now saves an afternoon of phone calls in three months.

Where the register lives matters. If it sits three folders away from the drawings, nobody will open it. Keep it beside the CAD folder, pin it in the project channel, and treat it as part of the deliverable rather than an administrative afterthought.

Use Cloud Storage Properly, Not Just as a Dump

Cloud folders with version history are excellent, but only if you work directly inside them. The common mistake is to drag files to the desktop for speed, edit, then copy back up. That breaks the version chain and hands you two copies with no clear parent.

A few rules worth enforcing:

• Open and save files from the synced project folder, not a local copy.
• Let sync finish before closing the laptop — a half-synced file is an invitation to conflict.
• Never have two people editing the same file simultaneously, even on a syncing drive. You'll get duplicated files with someone's name bolted onto the end.
• Keep a nightly backup to a separate location, and once a month actually test restoring a file. An untested backup is a rumour.

Lock, Check Out, or Work on Copies Deliberately

Larger practices tend to run a common data environment with proper check-out and file locking. Smaller studios can get most of the benefit with a simple convention: a current folder that holds the live files and a working folder for experiments. When something is ready, it moves into current with a bumped revision code and a register entry.

Be careful with references. Renaming a host model or moving an xref will break every sheet that depends on it. Renaming should happen at revision boundaries, in one coordinated pass, and never halfway through a Tuesday afternoon.

Pick one approach and stick to it. Some teams bump the file name at each issue; others keep one file and track revisions in the title block and register. Both work. The hybrid where nobody agrees is the one that costs you a weekend.

Archive at Milestones and Hand Over Cleanly

At every fixed point — planning submission, tender, construction issue — freeze the set. Copy the whole folder to an archive location labelled with the stage and date, publish the PDFs, and file the register alongside them. That snapshot is what protects you when someone asks in eighteen months what was actually issued.

At the end of a job, hand over native files, published PDFs and the register in a folder structure that mirrors your working one. A future team will thank you, and so will your future self when the same client returns with an extension.

None of this is glamorous. It's habits, and habits take about a fortnight to settle. Start with naming and the register this week, add proper cloud discipline next, and bring in archiving at your next milestone. The first time it saves an afternoon's work, nobody will need convincing again.