AutoCAD Drawing Cleanup Checklist for Structural Engineers

Cleanup is the unglamorous half of steel CAD. A drawing can show the right rafter size and still be a bad file: unused layers from an architectural xref, a missing SHX, a raster of a scanned sketch, an exploded title, markup on a plottable layer, and a circular xref that only fails on the contractor's machine. Issue PDFs hide some of that. The next person who opens the DWG does not. Structural engineers need a cleanup checklist that is short enough to run on every issue, not a museum of every AutoCAD command.

This checklist is ordered the way failures actually show up: save a copy, audit, xrefs, layers, styles, blocks, leftover markup, geometry junk, then plot. It pairs with AutoCAD Layer Standards for Structural Steel Drawings and Using AutoCAD Blocks to Improve Structural Drawing Consistency. Across many files, the same steps become AutoCAD Batch Processing Ideas for Engineering Teams. LISP can run some of them; see StruTools LISP Programs. It cannot decide that a missing grid bubble is acceptable.

Cleanup is also file management. If you clean a working copy and then overwrite the issued snapshot, you have no before. If you never clean because 'the PDF looks fine', the next issue inherits every leftover. Keep issued DWGs in the tree described in CAD File Management Practices for Structural Engineering Projects. When the sheet cites MBS reactions, cleanup must not delete the design-note layer by accident; see Coordinating MBS Results with CAD and PEB Approval Drawings.

Always clean a copy

PURGE and OVERKILL cannot be fully undone by optimism. The issued folder should still hold the pre-clean file until the plot is accepted.

• Save-as or copy with a -clean suffix if you must keep both in working.
• Do not clean directly inside a locked issued snapshot; copy out, clean, re-issue.
• If batch cleanup is used, it reads a list of working files, not the archive.

Xrefs, images, and fonts before pretty layers

A drawing that looks clean on your PC and fails elsewhere is not clean. It is local.

Report missing xrefs, unloaded xrefs, and images with absolute paths to a personal desktop. Relative paths or a project support folder survive handoff. Missing fonts should be replaced with the office set, not ignored because the title still 'looks close'. Etransmit or an equivalent pack is part of cleanup when the file leaves the office; that is also a CAD file management event.

Layers: unofficial names and markup leaks

Cleanup is when unofficial layers get renamed or removed, and when working markup is frozen.

• List layers not in the steel standard.
• Freeze or no-plot the working markup layer before the check plot.
• Do not purge a layer that still holds a required analysis note.
• VISRETAIN: know whether xref layer overrides are intentional.

Blocks, explode leftovers, and styles

If the title is exploded, cleanup should fail the drawing, not 'fix' it by leaving it exploded.

Count inserts of GRIDBUB and the title block. Zero on a sheet that should have them is a defect. Unused definitions can be purged. Annotative styles and dimstyles from another office should not ride along into the next job. Reset to the steel template styles where the office standard says so.

OVERKILL and geometry junk — with a fence

Overlapping lines make plots heavy and hatch fail. Blind OVERKILL can delete a line that was a member edge.

• Run on a copy.
• Exclude blocks if your version and office rule say so.
• Do not run across xrefs you do not own.
• Plot before and after on a typical elevation if you are not sure.

The check plot is part of cleanup

A file that audits clean and plots the markup layer is not clean. Plot with the issue page setup.

Look at the PDF: revision letter, frozen clouds, readable members, no architectural garbage from an xref. If you use LISP to freeze markups, this is when you find out the layer name drifted. Batch publish comes after one sheet proves the setup; see AutoCAD Batch Processing Ideas for Engineering Teams.

Per-issue cleanup sequence

Same order every time so people do not skip the dull front.

1. Copy the drawing or the set.
2. AUDIT; recover if the file is damaged.
3. Fix xref and image paths; note missing fonts.
4. Apply layer standard; freeze working markup.
5. PURGE unused; confirm title and grid blocks still exist.
6. Optional OVERKILL on the copy only.
7. Plot a typical sheet with the issue page setup and read the PDF.
8. Only then batch the rest or move files toward issued.

Engineering tips

• Cleanup that cannot be listed in eight steps will not be run.
• Keep a 'known good' steel template as the style source rather than scavenging styles from a contractor DWG.
• If a raster is required, clip it and put it on a named layer. Giant unclipped scans are a defect.
• Do not bind xrefs as a cleanup shortcut unless the transmittal standard requires a bound file.
• Log drawings that failed audit. They should not enter a batch plot list.

Common mistakes

Purging, then discovering the title block is gone

You purged the unused definition after exploding the insert. Restore from the library; do not draft a new title by lines.

Cleaning only model space

Layouts hold viewports, titles, and leftover viewports on no-plot layers. Cleanup includes paper space.

Calling a DWG clean because the PDF looks fine

The next user still has to open the file. Paths, fonts, and xrefs are the test.

Structural AutoCAD cleanup checklist

Tick on every drawing that will be issued or packed.

• A copy exists; issued snapshot is not the experiment.
• AUDIT completed without ignored errors.
• Xrefs and images resolve from project paths.
• Fonts are office fonts, not mystery SHX from a home PC.
• Unofficial layers reviewed.
• Working markup frozen or no-plot.
• Title and grid blocks still present (not exploded).
• PURGE done on the copy after the above.
• Check plot with issue page setup reviewed as a PDF.
• File name matches the numbering system for this issue.

Frequently asked questions

Should we OVERKILL every drawing?

Only if the office has tested it on typical steel elevations and excluded blocks as needed. It is optional in this checklist for a reason.

Can LISP run this whole list?

It can run freeze, purge, and plot. Xref path policy and 'did we explode the title' still need a person. Use StruTools LISP Programs for the mechanical parts.

Is WBLOCK a cleanup method?

Writing out selected objects can strip junk, and it can also strip required unseen objects. Treat it as a last resort with a plot comparison.

When is a file too messy to clean?

When xrefs are circular, fonts are unknown, and the title is exploded beyond recovery. Start a new sheet from the template and xref the salvageable model, rather than spending a day on archaeology.

Clean files are part of the engineering issue

A steel drawing that plots once on your machine is not issued. A steel drawing that audits, resolves xrefs, freezes markup, keeps its blocks, and plots from a named page setup is ready to enter the set.

If you are doing this to twenty files, continue with AutoCAD Batch Processing Ideas for Engineering Teams. If files keep disappearing into personal folders, continue with CAD File Management Practices for Structural Engineering Projects.