How to Manage Structural Steel Approval Drawing Revisions Efficiently

Revision control is how a team agrees which PDF is real. Without it, the shop has Rev B, the reviewer commented on Rev A, and the detailer is already drawing Rev D in a file called final_final. Steel will follow whichever file reached the nesting software.

This article describes a simple letter-and-cloud system, how to describe changes, and how to issue partial packages without losing the plot. It sits beside drawing numbering and comment response.

If your generator reprints the whole set every time a note changes, you still need a human revision description. Automation does not excuse “Rev C — updated.”

One letter, one story

Each issue that leaves the office gets a revision letter (or number, if that is your standard) and a description that a stranger can understand: “Rev C — moved brace at grid D to clear door 102.” “Updated” is not a description. The title block table should match the transmittal.

Cloud what changed, not what you looked at

Clouds are for deltas. Clouding the whole plan because you “reviewed it” trains people to ignore clouds. Remove old clouds on the next issue unless your standard keeps a history view — and if you keep history, say so on the notes sheet.

Partial issues

You can issue three sheets of a forty-sheet set. The transmittal must list those three, their letters, and state that other sheets remain at the previous letter. The drawing index should show mixed revisions without implying the old sheets were rechecked if they were not.

File names and graveyards

Issued files should include the drawing number and revision. Keep superseded PDFs in a superseded folder, not next to the live set with similar names. See CAD file management.

When a revision is really a new document

A sketch emailed to site is a document. Number it. Otherwise you have created an uncontrolled drawing that contradicts the stamped set. Either revise the sheet or issue a numbered sketch that the next revision will absorb.

A practical workflow

1. Decide which sheets actually changed.
2. Cloud the delta; update the title-block table.
3. Write a human revision description.
4. Update the index for mixed letters.
5. Transmit the list of sheets, not “the set.”
6. Move superseded files out of the live folder.

Engineering tips

• Never reuse a letter for a different change.
• If two changes ship on the same day, they can share a letter if they share a transmittal.
• Back-check related sheets even when only one was clouded.

Common mistakes

Revving every sheet because the plot stamp changed

That hides real deltas. Change the plot stamp without pretending it is an engineering revision if nothing else changed — or document it clearly as administrative.

Editing the issued PDF in place

Always a new file. Overwriting destroys the record of what was approved.

Describing revisions only in email

Emails vanish. Title blocks remain.

Checklist

• Changed sheets identified
• Clouds match the delta
• Title-block table filled
• Index shows mixed revisions honestly
• Transmittal lists sheets and letters
• Superseded files moved
• Related BOM/CNC updated if needed

Frequently asked questions

Letters or numbers?

Either is fine. Pick one per office and do not mix them on a job.

Do clouds stay forever?

Usually they come off at the next issue after they have been seen. Follow your office standard and say it on the notes sheet.

What if the reviewer comments on an old revision?

Say so in the response, map the comment to the current sheet, and fix the distribution list.

Can the generator assign revision letters?

It can increment them. A person still writes the description and chooses which sheets deserve a bump.

Where this leaves the work

A revision system is successful when anyone can answer “what is current?” in one minute. If that answer needs a meeting, the system has already failed.

Next, set the numbering rules in how to organize drawing numbers and revisions.