AutoCAD Batch Processing Ideas for Engineering Teams

One-drawing-at-a-time CAD is how issue night becomes midnight. Batch processing is the opposite idea: a named list of drawings, a named action, a log of failures. Publish to PDF, freeze markup layers, purge copies, run a scripted page setup, pack a transmittal. Those are good batch jobs. Recursing through a working folder and touching every DWG the search finds is not a good batch job. It is how last week's trial elevation overwrites this week's issued sheet.

This article stays on ideas and rules, not a vendor-script dump. AutoCAD already has publish, sheet sets, scripts, and etransmit-style packing. LISP can help per drawing; see AutoLISP for Structural Engineers: Practical Automation Examples and StruTools LISP Programs. Cleanup steps that you batch must be the same steps as AutoCAD Drawing Cleanup Checklist for Structural Engineers. File lists must come from CAD File Management Practices for Structural Engineering Projects, not from 'whatever is newest'.

The same discipline showed up on the analysis side: parse issued MBS reports, not trial folders (How Engineering Automation Can Process MBS Output Files). CAD batch work deserves the same freeze. If the list is the issued sheet index, batch it. If the list is a directory listing, stop. Approval package composition after the DWGs are clean is a different layer again—the StruTools MBS Approval Package—not a substitute for a plot log.

A batch job has a list, an action, and a log

If you cannot name those three, you do not have batch processing. You have a loop and a hope.

• List: sheet index or a curated file list for this issue letter.
• Action: one verb (publish, freeze, purge-on-copy, pack).
• Log: which files succeeded, which failed, and why.
• Stop rule: missing xref, missing page setup, or audit error fails the file rather than skipping it silently.

Publish and plot lists

The most valuable batch on a steel job is still the PDF issue. It is also the one that silently drops a layout when page setups are informal.

Use named page setups in the template. Publish from a sheet set or a list, to a folder named with the issue letter. Include a plot stamp or a title attribute for the issue so the PDF cannot pretend to be last week's. Failures belong in the log and on the transmittal as missing, not as 'we will send it later' without a note.

Scripted cleanup on copies

PURGE across a live issued folder is not bravery. Batch cleanup belongs on copies, then a plot comparison.

• Copy the list to a -clean working area.
• Run audit, freeze markup, purge.
• Do not OVERKILL in batch until it has been proven on a typical elevation.
• Replace the issued files only after PDFs match the office check.

Scripts versus LISP versus sheet sets

Pick the blunt tool that matches the action. Do not write a framework.

Sheet sets / publish

Best for plot lists and organizing layouts that already follow a numbering system.

Script files (.scr)

Best for a short command sequence on each file: open, layer freeze, plot, close.

LISP

Best when the action needs a test (does GRIDBUB exist?) rather than a blind command stream.

Packing transmittals in batches

Etransmit-style packing is batch work: gather DWGs, xrefs, fonts, and plot files for the issue. It is not a substitute for relative paths.

Pack the issued list only. Include the font set the office actually uses. Exclude trial folders and personal desktops. The pack name should use the same issue letter as approval drawing numbering if that is how the package is identified. A pack that contains Working and Issued mixed is a defective transmittal.

What never to batch

Some actions look automatable and will destroy a job in a minute.

• Redefine library blocks from a live project folder
• Bind all xrefs 'to make files simpler' without a standard that says to
• Scale entire models to 'fix units' across a directory
• Overwrite issued snapshots in place
• Run untested OVERKILL on the only copy

Standing up a publish batch for one PEB or steel issue

One issue letter, one list, one output folder.

1. Build the sheet list from the index, not from a folder dump.
2. Confirm page setups and markup freeze on one typical drawing.
3. Publish to a folder named with the issue letter.
4. Read the failure log; do not ignore skipped layouts.
5. Spot-check PDFs for revision letter and frozen clouds.
6. Pack the issued DWGs and xrefs as a separate transmittal job.

Engineering tips

• Name output PDFs with project, sheet, and issue. 'plot1.pdf' is not a record.
• Keep the script in the office folder with a version, same as LISP.
• If a drawing fails audit, take it off the batch list until cleanup passes.
• Do not batch from a cloud-sync folder that is still uploading.
• A batch that cannot produce a log is not ready for issue night.

Common mistakes

Directory recursion as a sheet list

Working, trial, and backup DWGs will enter the PDF set. Use an index.

No failure log

Silent skip of a layout is a missing construction sheet. Fail loudly.

Cleaning and plotting the same files in one unreviewed loop

Split the jobs. Cleanup on copies. Plot after a person accepts a sample.

Batch-job go-live checklist

If the list is not curated, the batch stays off issue night.

• File list matches the sheet index for this issue.
• Action is a single verb.
• Sample drawing succeeded.
• Failure log path exists and is read.
• Output folder named with the issue letter.
• Issued snapshots are not overwritten in place.
• Markup freeze is part of plot, not an optional extra.
• Transmittal pack is a separate, listed job.

Frequently asked questions

Is a sheet set required?

No, but you need some index. A sheet set is one good index. A checked spreadsheet of layouts can be another.

Can we batch-bind xrefs for contractors who will not keep paths?

Only as a stated transmittal variant, produced from issued files, not as everyday working practice.

Where do LISP programs fit in a batch?

As the per-drawing action inside the loop—freeze, attribute fill, checks—loaded from the office path such as StruTools LISP Programs.

How is this different from package automation?

Batch processing acts on DWGs. Package tools such as the StruTools MBS Approval Package act on the composed approval set after those DWGs are fit to issue.

Lists, not folder-wide hope

Batch processing earns its keep when the list is the issue, the action is named, and failures are logged. It becomes a liability when it touches whatever a directory search can see.

The list itself comes from file management. Continue with CAD File Management Practices for Structural Engineering Projects, and keep per-file health on AutoCAD Drawing Cleanup Checklist for Structural Engineers.