Ask any engineer what a layout is and you will hear the same answer: a viewport on paper space that shows what is in model space. It is correct, and it misses the point.
For a new engineer I explain it as a question instead. What do you want to show on the paper, at what scale, and at what rotation if any, so that it is clear for you and clear for the reviewer. Answer that and you have a layout. Answer it badly and you have work to redo, because that view dictates the callouts and the plan labeling that come after it: where the leaders land, which label fits, what has to be moved because it sits on top of something else.
So what we want is something visually clear and presentable. That is not a matter of taste. If we cannot read it, then we cannot submit it for review or for construction. Layouts are the engineer's representation of their hard work and design, and they are judged as that. SheetAgent for Civil 3D is built around that idea: generate the sheets fast, keep them readable, and leave the judgment with the engineer.
A set has no order. It grows.
There is no defined order to producing a set. Sometimes we start from layout, sometimes with grading, and at the end of the day the set grows as we put more information into it.
Cover and notes are usually the easiest, and they come early for that reason rather than because they are sheet one. We create one or two views of the project and the project location, and we put the notes in with blank information as fillers. Then, as time passes and the design and the specs firm up, those notes get revised.
A set that grows is a set that is edited, and the sheets placed first are the ones revised last. A tool that only builds a set solves the smaller half of the problem. SheetAgent is built for the larger half: keeping the set right while it changes.
Rectangular or alignment-based? The geometry decides, not the discipline
Each layout is a type of work, and the work comes in two shapes. Either it sits in an area, which wants a rectangle, or it follows a line, which wants an alignment. Layout and grading can be either: a regular rectangular viewport, or alignment based. The discipline does not decide it; the geometry does.
Each project is unique, and most of them mix the two.
On a college campus we might have both: layouts and grading as rectangular viewports, then the utilities as plan over plan, and plan and profile. On a roadway, it is all alignment based. On a subdivision, another mix again. The uses are massive and each project needs a different configuration.
That is why SheetAgent places sheets four ways instead of one. A grid fills a boundary. A path follows a polyline. An alignment follows the stationing. Free placement drops a tile where you click, which is what an exhibit or a one-off addition needs.
Two viewports on one sheet cover the rest. Plan over plan puts two or more consecutive tiles on the same sheet, which is what a utility run or a thin roadway corridor needs, because one viewport per sheet leaves most of the sheet empty and stretches the set over far more sheets than it deserves. Plan and profile puts the plan above its profile along the alignment. The same tile twice, each viewport with its own layer state, gives you existing against proposed on one sheet.
Legends, key maps and sections: the variation is the point
Configuration is not a nice-to-have on top of a template. It is the job.
Some projects have one legend. Some have a legend and keynotes. Some need one key map; some need two, one per area and one for the overall project. Some have sections, where each layout page needs its twin section or detail viewport. And sometimes each sheet needs a slightly different configuration from its neighbors: a viewport trimmed here, one edited there, as the user wants.
There are three different things sitting around the main view, and the difference between them matters:
A support viewport carries content that repeats on every sheet. The legend, the keynotes, a schedule. You draw its rectangle once on the template, place it once in model space, and it appears on every sheet from then on.
A key map is the small overview on each sheet showing where that sheet sits in the project, with the current sheet's area hatched. Each key map keeps its own hatch control, so a second key map is genuinely a second one, not a copy. On a multi-drawing project you choose once whether the key maps show each discipline's own zone or the whole project layout, and every discipline follows.
A secondary viewport is one tile per sheet, so each sheet shows something different: the twin section, a detail, a hand-drawn profile. This is what carries sections. It is placed per sheet, and each tile can be moved, rotated or stretched into position on its own.
Then the details package. A standard details PDF becomes one layout per page, viewports pointed at the pages, numbered in sequence with the rest of the set rather than living beside it.
Match lines, sheet numbers and the sheet index: what holds the set together
Between the sheets are the match lines: drawn where two sheets meet, each labeled with the neighboring sheet, so a reader can walk the set. Along the bottom of every sheet are the title block fields, the sheet number and the sheet name, and behind those is the sheet set.
The sheet index table on the cover is a Civil 3D feature. You right-click the sheet set and insert the sheet list table. What decides whether that table is right is the sheet set behind it: every layout enrolled, numbers and titles current, numbering running straight through a project split across several files. That part is worth getting right once, because the cover is read first and corrected last.
The first pass of QA belongs to the machine
When a set comes back for checking, this is what gets looked at, in roughly this order. Missing sheet names and sheet numbers. Missing north arrow or scale bar. Did the design alignment change, and is the layout still showing the correct background. Are the layers consistent. Key map hatches and legends, all in the same place on every sheet. The viewport titles, plan or plan and profile. Are the match lines there.
Most of that can be checked by the software before a person looks at it, which is what the Health panel is: a standing audit that compares the sheets against the model and the template and lists what has drifted. It catches the missing north arrow or scale bar per sheet, the alignment that moved away from its tiles, the viewport somebody resized by hand, the reference that changed since the build, the deleted layout, the layers that differ from the company standard, and the legend or key map label that moved on the template but never reached the sheets. Each warning names the button that settles it.
Two things on that checklist are not audited. The plot style table comes with the page setup from the template, so it is set once for the whole set rather than checked sheet by sheet. And the viewport titles are set when the sheets are made and synced by the label tools, not verified afterwards. Field values are the same story: the software checks that the sheet number and sheet name attributes are there, and then keeps them right by rebuilding them from the sheet set rather than by auditing what they say.
So the first pass belongs to the machine and the second pass belongs to the engineer. What the second pass is for is the thing no checker can do: reading the sheet as a reviewer will read it. That is the standard, and it has not changed. If it cannot be read, it cannot be submitted.
All of it stays yours: what SheetAgent never overwrites
Control means the user can edit anything at any time.
Move the match lines. Turn them off entirely if that is what your standard wants, and whatever you draw yourself is left alone. Move a label that conflicts with text, and it stays where you put it. Rotate a tile and the sheet follows it, viewport, north arrow and match lines together. Decide whether to update at all, and when. Edit the hatch on a key map, rotate its twist, add a second one. Put the legend and the viewports where you want them on the template, which is your canvas: what sits there is what every sheet inherits.
The line underneath all of it is simple. Only what the software created is maintained by it. Your layers and everything you drew are untouched, and where it adds something after the fact it adds what is missing and leaves the rest alone. Where a change has a judgment in it, you are asked rather than told: which side wins when a viewport was edited by hand, whether to keep a moved match line or revert it, whether to apply a retile now.
SheetAgent automates and simplifies layout creation. It never replaces the engineer's judgment and choices.
Because in the end every layout in a set is the same three things: an area, a scale, and a border. That is why they can be generated and maintained instead of drawn one at a time. And it is why generating them takes nothing away from the engineer, whose work they represent.
Frequently asked questions
What is a layout in Civil 3D?
A layout is a paper space sheet with a viewport that shows part of model space at a chosen scale and rotation. It sets what the reviewer sees, and it dictates the callouts and labels that follow.
When should a sheet be rectangular, and when should it follow an alignment?
Use a rectangular viewport when the work sits in an area, such as site grading. Follow an alignment when the work runs along a line, such as a roadway or utility run. Most projects mix both.
What is the difference between plan over plan and plan and profile sheets?
Plan over plan puts two or more consecutive tiles on one sheet, which suits thin corridors and utility runs. Plan and profile puts the plan above its profile along the alignment.
Does SheetAgent overwrite my manual edits?
Only what it maintains. At the next update SheetAgent restores the title block fields and viewports it created, which is how a sheet name typed over by hand gets corrected. Your own layers and everything you drew stay untouched, and where a change involves judgment, such as a viewport edited by hand, SheetAgent asks before acting.
Can SheetAgent check a sheet set before review?
Yes. The Health panel compares the sheets against the model and the template and flags drift: missing north arrows or scale bars, alignments that moved, viewports resized by hand, changed references, deleted layouts and layers that differ from the company standard.
Want to see how SheetAgent handles each of these? The documentation covers plan sheets and the four placement modes, plan and profile sheets, key plans and key maps, match lines, sheet names, numbering and Sheet Set Manager, and what Health checks.