Octo for sheets in AutoCAD

A hundred sheets, the same rule. Without opening them one by one.

In construction, much of the documentation still goes out as DWG and PDF. AutoCAD accepts scripts and has a version with no graphical interface, the Core Console. Octo can write the scripts and batches that plot, publish and check the drawings, always for your team to review.

Request an assessment See what it does

No interfaceCore ConsoleAutoCAD without a graphical interface

Scripts.scrtext with commands in sequence

Command-line outputPDF, DWFand DWFx, from the command line

Sources7listed at the end of the page

What Octo does with the sheets.

Four possible deliverables. All of them run on a copy first and go through the team before issue.

Batch in the Core Console

It can build the AcCoreConsole.exe call with /i (drawing) and /s (script) to run the same routine on every file in a folder.

Deliverable: batch with the list of processed files

Plotting and publishing

It can write scripts with -PLOT, -PUBLISH (from a DSD file) and EXPORT to generate the sheets as PDF from the command line.

Deliverable: generated sheets and the publishing log

Standards check

It can propose scripts that check, in each drawing, the standards items your team defines, and list what deviates.

Deliverable: list of open issues per file

Custom commands

When a script isn't enough, it can write .NET commands, defined with the CommandMethod attribute; in the Core Console, the program sits in a trusted location.

Deliverable: command for the team to review and install

Eight arms, one issue.

The same Octo cycle, applied to this workstream. Each arm has a narrow role; the people who approve and sign are on your team.

Discovery
Identifies version and standard

AutoCAD version, layer standard, sheets and title blocks, and how sheets go out today.
Data
Lists drawings and outputs

Which files, which layouts, which plot settings. The list becomes the batch input.
Security
Works on a copy

The drawings belong to the client. Scripts that change files run on a copy first, until the team approves.
Architecture
Picks the path

A .scr script in the Core Console when no dialog is involved; AutoCAD with the /b switch when the script needs the full session; a .NET command when the logic calls for it.
Development
Writes the script

Uses the command-line versions, because commands that open a dialog box or a palette don't work in the Core Console.
Review
Checks on a few files

Runs first on a few known drawings and compares with sheets the team has already issued.
Release
Runs with your OK

Only with your approval, it runs the batch in the approved folder and leaves the log next to it.
Documentation
Records the rule

The script, plot settings and file list for each issue are recorded.

Octo does not sign sheets. Issuing them remains the responsibility of the licensed professional on your team.

Each task, its own path.

The criteria Octo uses to choose. The tool your team already uses remains the reference.

Task	Path	Note
Run the same routine on many drawings	`AcCoreConsole.exe /i drawing.dwg /s routine.scr`	No dialog boxes or palettes
Plot a sheet by script	`-PLOT`	To a plotter, a printer or a file
Publish a set of sheets	`-PUBLISH` with a DSD file	CSV log named after the DSD
Generate PDF or DWF	`EXPORT` from the command line	DWFx too
Logic the script doesn't cover	.NET command with `CommandMethod`	In the Core Console, in a trusted location

From request to routine.

Three steps. Each one only makes sense after the previous one has shown results on your team.

A proposal, not a promise

1 Today

On-demand issues

You describe the issue and Octo proposes the script and the batch.

PDF of every sheet in a folder
Publishing from a DSD
List of processed files

Benefit: the issue follows the same rule, without opening file by file

2 Next

Checking before issue

The company's standards items can be checked in each drawing before plotting.

List of open issues per file
Corrections made by the team
New round of checks

Benefit: fewer sheets sent back over a standards detail

3 Later

Company commands

What repeats on every project can become a custom command, installed by the team.

Reviewed .NET command
Installed in a trusted location
Version log

Benefit: the company standard lives in the software, not in people's memory

Confirmed by sources.

Every point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.

points with a published source, each with its reference alongside.

ConfirmedAutoCAD without an interface: AutoCAD Core Console is a version of AutoCAD with no graphical interface. The syntax is AcCoreConsole.exe [/i <dwg>] /s <script> [/product <product>] [/l <language>].Source: AutoCAD 2025, Core Console
ConfirmedNo dialogs in the Core Console: Commands that show a dialog box or a palette are not available in the Core Console. Custom programs loaded into it must be in a trusted location; ObjectARX programs for the Core Console are CRX files.Source: AutoCAD 2025, Core Console
ConfirmedScripts: Script files (SCR) automate repetitive tasks by running commands and options in a defined sequence. The /b switch runs a script when AutoCAD starts (b for batch processing).Source: AutoCAD 2026, customization; AutoCAD 2025, startup switches
ConfirmedPlotting and publishing by script: -PLOT plots from the command line to a plotter, a printer or a file. -PUBLISH publishes sheets under script control from a DSD file; in a script, BACKGROUNDPLOT is ignored, and the CSV log takes the DSD's name.Source: AutoCAD LT 2026, -PLOT; AutoCAD 2021, -PUBLISH
ConfirmedPDF from the command line: EXPORT creates a DWF, DWFx or PDF file from the command line.Source: AutoCAD LT 2023, EXPORT
Confirmed.NET commands: Custom .NET commands are defined with the CommandMethod attribute.Source: AutoCAD 2025, .NET developer's guide

What Octo does and what stays with you.

Octo prepares everything, but does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Surveys, calculates, organizes and produces the documents: spreadsheets, reports, drawing sheets and drafts.

Deliverable: material ready to check

Your team checks

The licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.

Step: review by the signer

Who signs

Octo does not sign. Designs, technical reports, ART/RRT (Brazil's professional responsibility records), accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the responsible engineer or architect, with an ART or RRT.

Sign-off: engineer or architect, with ART/RRT

Sources.

Autodesk documentation used in the research. Accessed on October 28, 2026.

AutoCAD: Core ConsoleSyntax, limits and trusted location
AutoCAD: script filesSCR with commands in sequence
AutoCAD: startup switchesThe /b switch
AutoCAD LT: -PLOTPlotting from the command line
AutoCAD: -PUBLISHPublishing by script, from a DSD
AutoCAD LT: EXPORTDWF, DWFx or PDF from the command line
AutoCAD .NET: CommandMethodDefining commands

Which issue still goes out one sheet at a time?

The assessment starts with an issue your team has already done, without touching the drawings. You get a proposal for what can be automated and decide with it in hand.

Request an assessment