Shop Drawing Revision Control: Clouds, Logs, Naming, and File Versions

Shop drawing revision control is the set of habits that put everyone on the current version of a drawing. Revision clouds mark what changed, a revision log records every issue, consistent file names sort correctly, and superseded sheets leave circulation the day a new revision is released.

This guide covers each habit in turn, including numbering, logs, and file naming. Every revision travels through the wider shop drawing submission workflow, so weak control at any point can put an old sheet in front of the shop or the field.

Key Takeaways

  • Revision control gives the shop and the field exactly one current version of each sheet.
  • Four habits carry it: revision clouds, a revision log, consistent file names, and pulling superseded sheets.
  • Cloud only the changes in the latest revision, and tag each cloud with the revision number.
  • Log who issued each revision, when, to whom, and why.
  • File names should sort by sheet and revision without opening the file.
  • A monthly audit of the field set against the log catches stale copies before they get built.
Architectural floor plan with redline markups highlighting construction revisions, design changes, and updated specifications

What Shop Drawing Revision Control Covers

Shop drawing revision control is the discipline of tracking every change to a drawing so the right version reaches the right people. It is also called drawing version control, and it covers the drawing file, the printed copies, the log, and the distribution route.

The stakes are practical. A fabricator who cuts material from a superseded sheet produces parts that do not fit, and the remake lands on the schedule at the worst moment. The drawing can be perfectly drafted and still cause the loss if the wrong version is the one in the shop.

Revision and resubmittal are related but different. A revision is a new version of a drawing. A resubmittal sends a revised drawing back through review. Every resubmittal contains a revision, but a drafter may revise several times internally before anything is submitted.

Why Shop Drawing Revisions Multiply

Shop drawings change more often than most people expect, and the sources are predictable. Many revisions begin as construction redlines from a reviewer or the field, and others come from elsewhere:

  • Reviewer comments from the contractor, architect, or engineer.
  • Field conditions that differ from the drawings.
  • Coordination changes when another trade moves its work.
  • Design changes issued through addenda or supplemental instructions.
  • Internal corrections found during the drafter’s own check.

Each source can create a revision at a different time, which is why a single set date is not enough to describe what is current. Individual sheets move independently, and the control system has to track them one by one.

Revision Numbering: Letters, Numbers, and Status

There is no single universal scheme, so the first rule is to pick one and write it down. A common pattern uses letters for revisions issued for review and numbers once a drawing is released for construction. Others use numbers throughout. Either works if everyone on the project reads it the same way.

Three rules apply to any scheme. Never reuse a revision number, even for a revision that was withdrawn. Advance the number every time the drawing changes, including small changes. And show the revision in the title block, so the sheet itself says which version it is.

Status deserves its own label. A drawing marked preliminary, issued for review, or released for fabrication tells the reader what they can do with it, and it prevents a draft from being treated as approved.

Revision Clouds and Delta Tags

A revision cloud is a cloud-shaped outline drawn around a change so reviewers and installers can find it fast. Paired with a delta tag, a small triangle holding the revision number, it tells the reader what changed and in which revision.

A few rules keep clouds useful:

  • Cloud the full area that changed, not just a single point.
  • Place a delta tag with the revision number beside each cloud.
  • Clear earlier clouds when a new revision is issued, so only the newest changes stand out.
  • Describe each change in the revision block on the sheet.

Clouds are an aid, not a guarantee. A change that was made but never clouded is invisible to a reviewer who relies on clouds alone, which is why the log carries the full record.

The Revision Log: What to Record

The revision log is the single place that says which version is current. Teams that keep it as a living record, updated at the moment a revision is issued, can answer questions in seconds. Teams that update it afterward spend those seconds hunting through email.

FieldWhat to RecordWhy It Matters
Revision and dateRevision number and the date it was issuedShows which version is current
DescriptionA short statement of what changedLets reviewers find changes quickly
Source of changeReviewer comment, field condition, or design changeExplains why the revision exists
Sheets affectedEvery sheet touched by the changePrevents partial updates
Issued by and toWho released it and who received itProves who holds which version
ReceiptConfirmation that recipients acknowledged itCloses the loop on distribution

Shop drawing revision logs also protect the project in a dispute. When someone asks what was requested, what was delivered, and when, the log and the marked-up set together answer all three.

Construction File Naming and Folder Structure

Good construction file naming lets anyone find the current drawing without opening anything. The name should carry the project, the sheet, the revision, and the date, in a fixed order so files sort correctly. A pattern might look like PRJ245_M-201_RevC_2026-10-19.dwg.

Words such as final, latest, or new fail after the second revision, so they stay out of file names. Folders matter as much as names. A simple structure keeps working files, issued files, and superseded files in separate places:

  • Working: drafts in progress, editable by the drafting team only.
  • Issued: the current released version of each sheet.
  • Superseded: earlier versions, archived and read-only.

Moving a file to the archive on the day it is replaced is what stops it from circulating.

Issuing a Revision and Pulling Superseded Sheets

Issuing a revision follows a sequence, and skipping a step is how stale copies survive.

  1. Update the drawing and cloud each change with a delta tag.
  2. Advance the revision number, date, and description in the title block.
  3. Record the revision in the log.
  4. Issue the sheet through one controlled route with a transmittal.
  5. Withdraw superseded copies, printed and digital.
  6. Confirm receipt and record it.

Name one person as the owner of the live set on each project. That person verifies that printed sheets in the field match the log, and a monthly audit makes the check routine instead of a reaction to a mistake.

Controlling Printed and Digital Sets Together

A clean digital repository does not help if an outdated printed sheet is still pinned up in the field office. Revision control has to cover both forms. When a revision is issued, the printed sheets it replaces should be collected or marked superseded, and the replacement should be handed to a named person, not left on a shared table.

Digital sets need their own guardrails. Limit who can write to the issued folder, make the archive read-only, and keep the log pointing at the file that is actually current. A reader should be able to open the log, find the current revision, and reach that exact file in two steps.

CAD Standards That Make Revision Control Easier

Consistent drawings are easier to control. Shared construction CAD standards give every sheet the same title block, revision table, and layer structure, so a reviewer always knows where to look for the revision and what it says.

A dedicated layer for revision clouds and tags is a small habit with a large payoff. Clouds can be turned on for a review set and off for a clean issue, and earlier clouds can be cleared without touching the linework.

Common Revision Control Failures

Most failures are handling problems, not drafting problems:

  • The shop builds from an email attachment instead of the issued file.
  • A change is made but never clouded or logged.
  • A revision number is reused or skipped.
  • The log is updated last, or not at all.
  • Two people edit different copies of the same drawing at once.

Each of these has the same fix: one controlled route for issuing drawings, and a log that is updated at the moment of release.

A Worked Example: A Piping Package Through Three Revisions

Consider a mechanical piping package. The following is illustrative, and real events vary. Revision A goes to review and returns with comments. Revision B incorporates them. A field conflict then forces Revision C, which reroutes one run.

Revision C is issued to the shop, but a foreman forwards an older email with Revision B attached, and a crew cuts pipe from it. The log shows Revision C went to the shop on a specific date, which makes the mistake easy to trace but does not undo it.

A superseded stamp on the Revision B file, a single distribution route, and a receipt confirmation from the shop would likely have caught the problem before any pipe was cut.

Shop drawing VA updating AutoCAD construction drawings and coordinating design revisions from a home office

Where Dedicated Drafting Support Fits

Revision control fails when the person responsible is overloaded. Clouds get skipped, the log lags, and files pile up in the wrong folders. Virtual Construction Assistants (VCA) places remote shop drawing and AutoCAD technicians with construction teams, so revisions are drafted, clouded, and logged as they happen. Once placed, the technician works directly with the client team on workload and priorities.

For teams that want a dedicated resource on this work, VCA’s drawing revision support is one place to start. The right setup depends on trade mix and revision volume.

Things to Know

  • Write down the numbering scheme at kickoff so everyone reads it the same way.
  • Never reuse a revision number, even for a withdrawn revision.
  • Update the log at the moment of release, not afterward.
  • Keep working, issued, and superseded files in separate folders.
  • Issue drawings through one controlled route, with a transmittal.
  • Audit the field set against the log monthly.

Frequently Asked Questions

What is shop drawing revision control?

It is the practice of tracking every change to a shop drawing so everyone works from the current version.

It combines revision clouds, a revision log, consistent file naming, and controlled distribution. The goal is that the shop and the field never build from a superseded sheet.

What is a revision cloud on a drawing?

A revision cloud is a cloud-shaped outline around changes, so reviewers and installers can see what differs in the latest revision.

It is usually paired with a delta tag showing the revision number. Earlier clouds are normally cleared when the next revision is issued, so only the newest changes stand out.

What should a shop drawing revision log include?

It should record the revision number, date, description, sheets affected, who issued it, and who received it.

Adding the reason for the change, such as a reviewer comment or a field condition, makes the log far more useful in a dispute. The log is the single place that says which revision is current.

How should construction drawing files be named?

Use a consistent pattern with project code, sheet number, revision, and date so files sort correctly without being opened.

Avoid words such as final or latest, which stop meaning anything after the second revision. Move superseded files to a separate archive folder instead of leaving them beside the current set.

What is the difference between a revision and a resubmittal?

A revision is a new version of a drawing, while a resubmittal sends a revised drawing back through review.

Not every revision is resubmitted. A drafter may revise internally several times before a package goes out, and each internal revision still needs its own number so the log stays accurate.

Keeping Everyone on the Current Sheet

Revision control is not paperwork for its own sake. It is the system that keeps a fabricator from cutting material from the wrong version. Clouds, a live log, sortable file names, and a clean archive each remove one way for an old sheet to survive.

If your team has to start somewhere, start with the log and the archive folder. Those two habits catch more problems per hour of effort than anything else on the list.

Founder & CEO, Virtual Construction Assistants | CEO, Lipsky Construction

Third-generation builder with 20+ years in construction operations. AGC NYS Board of Directors; testified before the U.S. House of Representatives.

ON THIS PAGE

Which tasks could your team delegate?

Explore how virtual assistants help general contractors, trade contractors, and specialty firms prepare estimates, coordinate schedules, and manage bookkeeping.

Black Friday
Black Friday Deal 2026

First Month Free

A dedicated VA matched to your workflow, free for your entire first month.

Offer Closes In
134Days
00Hrs
00Min
00Sec

Black Friday Deal 2026

Up to
4 Weeks Free

Sign by Dec 5 and get 4 weeks free.
Sign by Dec 6–31 and get 2 weeks free.

Offer Closes In
00
Days
00
Hrs
00
Min
00
Sec

Black Friday · Limited Time Offer

Black Friday
· Limited Time Offer

GET UP TO 4 WEEKS OF VA
SUPPORT, FREE

New clients and existing clients adding a VA can claim up to 4 weeks free. Sign by December 5 to get 4 weeks. Sign by December 6–31 to get 2 weeks. 

Free 15-minute intro call · No obligation

VCA horizontal Logo
Welcome to Virtual Construction Assistants
What brings you here today?

Find skilled construction VAs to support your business.

Apply to work with leading construction companies.