CAD File Management Practices for Structural Engineering Projects

CAD file management is the reason last week's elevation is still findable when a change order arrives. It is also the reason a contractor opens the right DWG instead of a similarly named trial. Structural projects produce many files: model xrefs, sheet DWGs, PDFs, transmittal packs, and sometimes analysis extracts that CAD must cite. If those objects live in one unsorted folder, AutoCAD Batch Processing Ideas for Engineering Teams will publish the wrong set, and AutoCAD Drawing Cleanup Checklist for Structural Engineers will clean the wrong copy.

This guide is the CAD twin of How Engineering Teams Can Organize MBS Files and Project Outputs. Analysis and CAD should share issue language even if they do not share directories. Drawing numbers should follow the office system, including approval drawing numbering when the set is an approval package. Names, xrefs, and transmittals are the three practical controls. Cloud sync is not, by itself, a control—it is a transport that can overwrite a freeze if you let it.

Automation still needs this tree. LISP loads from an office path; it should not hunt a desktop. Title attributes extract into transmittals only if the issued DWGs are the ones in the list. StruTools LISP Programs will not rescue a project that issues from Working. The StruTools MBS Approval Package will not invent a numbering system you never applied. File management is the floor; the tools stand on it every time.

Name files like the sheet index already does

If the transmittal says S-201 and the file is called elev-final3.dwg, you do not have management. You have archaeology.

• Project code, sheet number, and issue letter in the file name.
• The same sheet number as approval drawing numbering when that system applies.
• No 'final', 'latest', or person names in issued file names.
• PDF names match DWG names so batch publish output is recognizable.

Xrefs need owners and relative paths

A grid xref with an absolute path to one user's Documents folder will fail on issue day at the contractor.

Keep shared grids and typical details in Xrefs with relative paths from the project root. Assign an owner so two people do not edit the grid at once. Do not bind as everyday practice. Binding is a transmittal variant, produced from issued files, as noted in the batch-processing article. Incoming architectural xrefs stay in Incoming until someone maps layers; they do not land directly in Issued.

Working versus issued is the same idea as MBS

Editable CAD and frozen CAD must not be the same files. The analysis side already learned this; CAD should copy the pattern.

When an issue is signed, copy the DWGs and PDFs into Issued-letter and protect them. Further edits happen in Working toward the next letter. That matches How Engineering Teams Can Organize MBS Files and Project Outputs so a transmittal can cite 'drawings issue C, analysis issue C' without a scavenger hunt.

Transmittals are first-class files

The pack you sent is part of the project record. If it is only an email attachment, you will not be able to say what the contractor had.

• Store the transmittal PDF and the packed DWGs in Transmittals, named with the issue letter.
• List missing sheets in the transmittal rather than hoping nobody notices.
• Incoming marked-up PDFs go to Incoming, then to Working as a next-issue task, not as silent overwrites of Issued.

Link CAD management to cleanup and batch

A tidy tree with dirty files is still a bad issue. A clean file in the wrong folder is still a lost issue.

Run AutoCAD Drawing Cleanup Checklist for Structural Engineers on Working copies before they copy into Issued. Run publish batches from the index of Issued, not from Working. Layer and block standards (AutoCAD Layer Standards for Structural Steel Drawings, Using AutoCAD Blocks to Improve Structural Drawing Consistency) live in the template, which itself should be versioned outside any one job.

Permissions, backups, and personal copies

Personal copies are how unofficial tables and unofficial elevations start. They also bypass backup of the project tree.

• Issued is read-only after freeze, or writable only by a controller.
• Backups include Issued and Transmittals, not only Working.
• Personal sandboxes are allowed; they are not the issue path.
• Office LISP and block libraries live outside the job tree so jobs do not each grow a private standard.

Opening CAD folders on a new structural job

Do this before the first grid is drawn, while the numbering system is still empty and easy to obey.

1. Create Working, Xrefs, Issued, Transmittals, and Incoming using the project code.
2. Agree sheet numbers with the approval numbering system and analysis issue letters.
3. Place the steel template and confirm the office LISP and block paths load.
4. Set relative xref paths from the project root.
5. Issue A copies Working into Issued-A after cleanup and a check plot.
6. Send a named transmittal pack from Issued-A, stored in Transmittals.

Engineering tips

• Put the current issue letter in a one-line pointer at the project root.
• Never store the only copy of a typical-detail xref inside a sheet DWG's backup folder.
• If two buildings share a site, split trees by building before the first xref.
• Match PDF output folders to issue letters so batch publish cannot mix A and B.
• When architecture issues a new background, park it in Incoming and bump CAD issue only after a coordination pass.

Common mistakes

Email as the CAD archive

Attachments duplicate names and lose xrefs. Transmittals folders exist so you can reopen what was sent.

One folder called DWG

Working, xrefs, and issued files will mix. Batch jobs will pick the wrong one.

Editing files inside Issued because it was quicker

That is the next issue. Copy to Working, change, cleanup, re-issue as the next letter.

CAD file-management checklist

If this fails, stop batch plotting until it passes.

• Working and Issued are different folders.
• File names include project, sheet, and issue letter.
• Sheet numbers match the approval numbering system where it applies.
• Xrefs use relative project paths.
• Incoming files are quarantined until mapped.
• Transmittal packs are stored, not only emailed.
• Issued is protected from casual overwrite.
• Cleanup happens before copy-to-issued.
• Office LISP and block libraries are not stored only inside the job.

Frequently asked questions

Should CAD and MBS share one project folder?

They can share a project root with sibling trees (03-Analysis, 04-CAD). They should not dump solver scratch files next to sheet DWGs.

How do we handle client-required names that break our pattern?

Keep an internal name that matches the index, and a transmittal mapping if the client demands different filenames. Do not abandon the index.

Is cloud storage acceptable for Issued?

Yes if you can freeze copies and control writes. Real-time overwrite of a snapshot is not an issue system.

Where do Lisp programs live?

In an office support path, such as the one used by StruTools LISP Programs, not copied into every job where they will drift.

If you cannot find the issued DWG, you did not issue it

CAD file management for structural work is a shallow tree, honest names, relative xrefs, and transmittals you can reopen. It is the same idea as MBS filing, spoken in DWG. Without it, layer standards and LISP are decorations on a junk drawer.

Keep drawings healthy with AutoCAD Drawing Cleanup Checklist for Structural Engineers, keep numbers aligned with approval drawing numbering, and keep analysis packages aligned with How Engineering Teams Can Organize MBS Files and Project Outputs.