The Drawing Set Revision Problem: How I Stopped Contractors From Building Off the Wrong PDF

An architect's system for tracking drawing revisions in Google Sheets — so contractors and consultants always pull the current sheet, not last month's.

Six weeks into a mixed-use build, our GC called to ask why the elevator shaft dimensions in his set didn't match what the steel sub had. Turned out he was building off Rev C, which we'd superseded with Rev E two revisions ago — and somewhere between an email thread, a shared Dropbox folder, and a printed set sitting in his truck, the update never landed. That's not a communication failure you can blame on any one person. That's a system that had no single place saying "this is the current sheet, full stop."

Why architecture firms bleed hours on revision confusion

Every set of drawings has multiple lives. SD gets revised after the owner meeting. DD gets revised after the structural engineer pushes back on a beam depth. CD gets revised after permit comments, then again after value engineering, then again mid-construction because the client wants a different door swing. Each revision touches a subset of sheets, not the whole set — so you end up with A-101 at Rev F while A-201 is still at Rev D, and nobody outside your office actually knows that without asking.

Meanwhile you've got three consultants — structural, MEP, civil — each running their own revision cadence on their own drawings, which you're supposed to coordinate into a single issued set. If your only record of "who has what" lives in email subject lines and file names like A101_v3_FINAL_final2.pdf, you are one attachment mix-up away from a very expensive framing mistake.

Build a drawing register, not a folder structure

A folder structure tells you where a file lives. It doesn't tell you which file is current, who received it, or when it was superseded. What you actually need is a drawing register — one row per sheet number, tracking its current revision, issue date, who it went to, and a link to the actual PDF or DWG. This is the single source of truth your GC, your consultants, and your own project architect all check before touching a drawing.

• Sheet number and title (A-101, S-201, M-301, etc.)
• Current revision letter/number
• Issue date of that revision
• Issued for what (permit, bid, construction, client review)
• Who it was transmitted to, and how (email, plan room, printed set)
• The live file itself, attached directly to the row — not a link that rots when someone reorganizes the Drive

That last point is the one that actually prevents the wrong-PDF problem. A link to "the project folder" degrades the moment someone renames a subfolder or moves last year's CDs into an archive. This is where I stopped fighting Drive links and started dragging the actual current sheet PDF straight into the cell next to its row — FileFox does this inside Sheets, so the file travels with the row instead of living somewhere the row merely points to. When Rev E replaces Rev D, I drop the new PDF in, and the old one either gets archived in a separate tab or stays attached to a superseded-row I never delete.

The transmittal log: proof of who got what, when

Your drawing register tells you what's current. A separate transmittal log tells you what actually went out the door and to whom — which is what you pull up when a contractor claims they never got the update. I keep this as its own tab: date, recipient, sheets included, revision numbers, and method of transmission. It takes thirty seconds to log after you hit send, and it's saved me twice from a change-order dispute where the sub insisted they were never notified.

That formula sits in the transmittal log and pulls the current revision straight from the register when you type a sheet number — so you can't accidentally log a transmittal against a revision that's already been superseded. Small thing, but it's caught my own typos more than once.

Where a real project management template gets you most of the way there

There's no template built specifically for architectural drawing sets — nothing in the wild is going to hand you a pre-built sheet-number column with CSI divisions baked in. But you don't need to build the bones from scratch either.

For the bigger picture — phasing, milestones, who owes what by when across SD/DD/CD — a general project timeline template does the job better than anything purpose-built I've found, mostly because architecture project phases map cleanly onto generic milestone tracking.

If you're doing interiors or tenant improvement work alongside base building, the interior design project template is closer to your actual workflow than anything labeled 'construction' — it's built around client files, mood boards, and room-by-room tracking, which maps surprisingly well onto a TI drawing set organized by space.

Naming still matters, even with a register

A drawing register doesn't excuse sloppy file names — it just gives you a place to catch the sloppiness before it leaves your office. I still name files with sheet number, revision, and date (A-101_RevE_2026-03-14.pdf), because the moment that file gets forwarded outside the register — dropped into an email, printed, texted to a super — the filename is the only context it carries. If your naming is inconsistent, fix that first; the register is only as trustworthy as what feeds it.

What this doesn't fix

A spreadsheet register won't replace formal drawing management software on a large multi-consultant federal project — if you're required to run a BIM 360 or Procore document control workflow contractually, use it, and treat your Sheets register as your internal cross-check, not the system of record. This setup is built for small-to-mid firms running their own transmittals without a dedicated document controller, which is most of us.

Frequently Asked Questions

How do I track drawing revisions in Google Sheets?

Build a register with one row per sheet number, columns for current revision letter, issue date, and issue purpose, and attach the live PDF directly to the row so it updates in place. Keep a separate transmittal log recording who received which revision and when, so you have proof if a contractor claims they never got an update.

Can I build an architecture portfolio in Google Sheets instead of InDesign?

You can use a spreadsheet to organize and track your project images, final renders, and source files behind the scenes, but for the actual portfolio document you'll still want InDesign or a similar layout tool — Sheets isn't built for page design. What it's good for is making sure you can actually find the final, approved render when it's time to build the portfolio.

What should go in an architecture drawing transmittal log?

Date sent, recipient name and firm, sheet numbers included, the revision letter or number for each sheet, the purpose of issue (permit, bid, construction), and the method of transmission. This is your record if there's ever a dispute about who had which version of a drawing.

How do architects coordinate revisions across multiple consultants?

Each consultant's drawings get their own row in the shared register, tracked by their own revision sequence, but issued together as a coordinated set with a single issue date. The architect typically owns the master register and confirms all consultant sheets are current before compiling and transmitting the full issued set.

What's the difference between a drawing register and a transmittal log?

The register tells you what's current right now — the latest revision of every sheet. The transmittal log is a historical record of what actually went out the door, to whom, and when. You need both: the register for daily reference, the log for accountability when something goes sideways.