Civil 3D sheet set automation

What sheet set automation covers

A sheet set is more than its layouts. Every sheet carries a viewport framed on one piece of the model, match lines to its neighbours, a key map showing where it sits in the project, a title block with its number, name and scale, and an entry in Sheet Set Manager. Producing a set by hand means building all of that for every sheet and keeping it consistent across the whole set.

Automation does that work from the model. In SheetAgent for Civil 3D, tiles placed in model space become layouts, one tile per sheet, each with its viewport, title block, match lines and key map already placed. The tile is the source; the sheet is built from it.

One-time creation or a set that stays current

Most of the effort on a civil set is not the first build. It is what happens afterwards: the alignment moves, the scope grows, the grading shifts, and sheets that were right last week no longer match the design.

A one-time tool creates sheets from the design as it stands. Civil 3D's own Plan Production works this way. It generates a first plan or plan and profile set from alignments, and each layout viewport captures a fixed window of the model when the sheet is created. A small shift inside that window still reads fine. Once a change moves the design outside it, there is no update path and the affected sheets are regenerated, along with the labels and references that went with them.

A set that stays current keeps the link between model and sheet. In SheetAgent for Civil 3D the tiles in model space drive the sheets. Move, resize or rotate a tile and press Update Sheets: the viewports, match lines and key maps follow, tiles that did not change are skipped, and Sync SSM brings the sheet set along. When the alignment moves under the tiles, Update Tiles moves them to it first. Nothing is rebuilt from scratch. In one firm's eight-week evaluation, 273 layouts were updated this way alongside 498 built.

How the sheets are generated

Single-viewport plan sheets are placed four ways. Array, path and free placement need no alignment, so grading, layout, utility and erosion control sheets are produced the same way as alignment sheets.

Mode	How the tiles are placed	Typical use
Array	Fills a closed boundary with a grid of tiles	Site, grading and layout plans
Path	Runs tiles along a polyline	Exhibits, corridors and studies
Alignment	Follows a Civil 3D alignment and its stationing	Roadway and utility plans
Free placement	Drops a single tile where you click	Single sheets exactly where you want them

Sheets with more than one viewport have three forms. Plan and Profile pairs a plan with its profile view along an alignment. Plan/Plan stacks two different tiles on one sheet, which suits narrow corridors such as utility runs. Plan Duplicate shows the same tile twice with different layer states, for existing against proposed.

Two more sheet types join the same set: PDF detail sheets, one layout per page of an existing details package, and key plans, an index or cover layout over drawings you already have. Layouts drafted by hand can be adopted rather than rebuilt, and are then updated and checked like the rest. For work spanning several drawings, Project Control holds one tiling that every discipline inherits.

What is placed on every sheet

Element	At build	When the design changes
Viewport	Located, sized and scaled from its tile	Follows the tile at Update Sheets
Match lines	Drawn where two sheets meet, labelled with the neighbouring sheet	Regenerated when the tiles, the alignment or the sheet numbers change
Key map	An overview viewport with the current sheet's tile hatched	Rebuilt at Update Sheets
North arrow and scale bar	Configured once on the template and placed on every sheet	The north arrow re-orients when a tile rotates; template edits reach every sheet
Title block fields	Sheet number, title, scale, page number and page count filled	Kept in sync; a renumber cascades to key maps, labels and the sheet set
Support viewports	Legends, keynotes and schedules repeated on every sheet	Redefine once on the template, then Update Sheets
Sheet Set Manager	One button creates the sheet set	Sync SSM applies additions, deletions and reordering

Sheet Set Manager, native and automated

Sheet Set Manager organises sheets once they exist. It lists them, holds their numbers and titles, and feeds the fields in their title blocks. Deciding where each viewport sits on the model, and moving it when the design changes, is outside it. That is the part automation adds.

SheetAgent for Civil 3D writes to Sheet Set Manager rather than replacing it. One button adds every layout to a sheet set. After an update, a renumber or a rename, Sync SSM shows what will be added, updated or removed, then matches the sheet set to the drawing. It writes the fields Sheet Set Manager knows natively and the ones it does not, such as the page number and count that read 1 of 30, and every sync rewrites them from the current sheet order. On a project split across several drawings, every drawing enrols in one sheet set.

Standards and checks before issue

Company layer standards come in through an Excel template downloaded from the Manager Portal. It asks only for the parts SheetAgent for Civil 3D generates: viewport and match line layer names, linetypes, colours and the key map hatch. Filling it in takes a few minutes, once, and your own layers are left alone.

Before a set issues, Health compares the sheets against the model and the template and lists what has drifted: a missing north arrow or scale bar, a viewport resized or rescaled by hand, an alignment that moved away from its tiles, a deleted layout, a reference that changed since the build, and layers that differ from the loaded standard. Each warning names the button that settles it. Health does not read the text in title block fields; it checks that the sheet number and name attributes exist and are configured. See what Health checks for the full list.

A worked example

A street improvement set along one alignment, with the client's title block, revised after the first submittal.

1. Set the title block. Set TB brings the client's title block in as an Xref, and the page setup is set once on that layout. Primary VP defines the viewport area once for every sheet.
2. Preview the tiles. Create Preview places tiles along the alignment at the scale you choose. Adjust any tile in model space before building.
3. Build. Build Sheets generates the layouts with viewports, match lines, key map, north arrow, scale bar and title block fields. The Sheet Set Manager button creates the sheet set.
4. The alignment is revised. Health raises a drift warning for that alignment. Update Tiles moves the tiles to the new geometry, and Update Sheets updates only the sheets that changed.
5. Coverage is checked. Gap Preview marks any coverage below your minimum. Add Tile fills it, and Update Sheets creates the new layout.
6. Issue. Sync SSM matches the sheet set, Health refreshes clean, and the set goes out.

The full sequence for revisions is in how to keep Civil 3D sheets updated after design changes.

Who it fits, and the limits

It fits firms where sheet production is the bottleneck between a finished design and a deliverable set, where designs change late, where sets mix grading, layout, utility and erosion control sheets rather than alignment sheets alone, and where projects arrive with a different title block each time.

• It needs Civil 3D 2025, 2026 or 2027 on Windows. It does not run in plain AutoCAD.
• Scale is chosen at preview. A sheet at a different scale is an added tile, not an update.
• Build is first-time only; after that the set is kept current with Update Sheets.
• Only what SheetAgent for Civil 3D created is maintained. Your own layers and per-sheet additions are left alone.

Questions