Fields are the right way to run a title block. I want to say that first, because the rest of this post is about the ways they go wrong, and I don't want anyone reading it as an argument against them. Every firm I know uses them. We use them extensively in SheetAgent for Civil 3D. Wire your sheet number, your sheet title and your custom properties to the Sheet Set Manager, and a renumber flows through forty title blocks without anyone opening a layout. That is how it should work.
The catch is that using fields requires attention and expertise, and on a real project not everyone touching the set has both.
What actually happens
Here is what I see, over and over, on sets with several engineers and drafters all collaborating in the same drawings.
Someone opens a sheet and the title block shows #####. That's a field that can't resolve at the moment, usually because the drawing wasn't opened through the sheet set, and it's harmless if you know what you're looking at. An inexperienced drafter or engineer doesn't. They see pound signs where a sheet number should be and they think it's a simple text edit. They double-click, type the number in, and save. The sheet looks fixed. What they actually did was replace the field with plain text, and that attribute will never follow the set again.
You can blame it on training or blame it on workload, and I've heard both, and at the end of the day the field gets disturbed either way. And there is no way to tell by looking at it. A typed number and a field look identical on the sheet.
So it sits there. The set renumbers, thirty-nine title blocks move, one doesn't, and nobody notices, because we get blind looking at the drawing. You've stared at that layout for weeks and your eye reads what it expects. The more people in the set, the more chances for a missed coordination like this, and every one of them is looking at their own drawing, not at the set.
It surfaces when someone finally looks at the whole thing at once, and most of the time that's QA/QC at the PDF print for review. Sheet numbers wrong. A sheet name or number missing. Found at the end, when the set was supposed to be done.
Then everyone tries to work out who did it, and the blame game never works. Six people were in those drawings over three weeks. It was one attribute. Nobody remembers. You just have to deal with it: open the sheet through the sheet set, reinsert the field, rewire it, check the ones around it, plot again. And it will happen again on the next revision, with a different sheet and a different pair of hands.
What we did about it
When we built SheetAgent, the question was never whether to use fields. It was how to take the expertise out of using them, so the set survives the person who doesn't understand them yet.
The program populates the fields for you. You select the fields in your title block once, sheet number, sheet name, whatever your block carries, and SheetAgent populates them in every layout. And if your title block carries a custom field, one that isn't native to the Sheet Set Manager, SheetAgent adds that custom field to the sheet set for you at sync. Creating custom properties in the sheet set by hand is exactly where inexperience shows, and it no longer has to be done by hand. Nobody opens a field dialog. An expert and a non-expert do the same thing: pick the attribute, and the tool fills it across the set. When the drawing is synced to the sheet set, any ##### that is still sitting there gets filled. That alone removes most of the manual work, and most of the confusion, because the pound signs that tempt someone into typing stop appearing in the first place.
It heals at update. If someone does type over a sheet name or a sheet number in a title block, the next time the set is updated, SheetAgent corrects it. Manual edits to title block fields are treated as accidents and repaired, unless the change was intentional. Intentional means one of two things: you changed the name, the number or any field in the Sheet Set Manager, the way you always have, or you changed it through the tool. Either of those is respected. A hand edit on a single layout is not, because on a real set that is almost never what anyone meant.
Intentional changes go through a button anyone can press. Users can still edit fields, nothing is locked away. But there is a simple button for changing sheet names and numbers that doesn't require training, just reading and pressing. Change it there and the change is intentional, the set knows it, and it flows to the title block, the labels, the key maps and the sheet set together. That is a second layer of safety for the sheet set: the correct path is easier than the wrong one, and the person who would have double-clicked the attribute now has somewhere obvious to go instead.
The sheet set itself has a backup. Sheet sets get corrupted. Anyone who has run a large project knows that, and it usually happens at the worst time. SheetAgent writes to the Sheet Set Manager and reads from it, and it keeps its own record of the set as it does. If something breaks on the sheet set side, one sync to the sheet set repairs it from that record and keeps the sheets in a working state. You are not rebuilding a set from memory the week of a submittal.
Underneath all of it is the thing I wrote about in the Project Control post: the tile is the truth. Each sheet knows what it covers and what number it is, and the sheet set is wired on top of that rather than being the only thing holding the numbers together. Two layers instead of one. When something upstream gets disturbed, the sheet still knows what it is.
Why this matters
None of this removes fields, and none of it asks the drafter to become an expert in them. It fills them for you, and then it moves the catch. Instead of finding the typed-over number at QA/QC at the PDF print, with the set supposedly finished and the blame game about to start, it gets found and fixed at the next update, by the tool, without anyone needing to know it happened.
That's the whole approach. Fields need attention and expertise. The set shouldn't depend on everyone having them.
What's next
That's the third of the things the first post promised. The alignment moves and the match lines drift. The scope moves and the set renumbers. A field gets disturbed and the title block stops following. Every one of them is a place where the set was trusted to hold still and didn't. Next, the last one, and the part almost nobody automates well: the key plans and the project-wide picture, one tiling that every discipline and every file inherits.
If you've ever found the wrong sheet number at the PDF print and known there was no point asking who typed it, you already know why this one needed writing.
See it on your own project at setline.ai, or read how title blocks are set up and how numbering and the sheet set stay in step in the documentation.