Most offices have CAD standards. Fewer have standards that are still being followed by the end of a busy project. The difference is rarely the document itself, it is whether the standard was practical and enforceable under deadline pressure.
Why standards break down
They break for predictable reasons: they are too elaborate to follow when someone is working late, they were never built into the template so following them requires extra effort, nobody checks, or an outside consultant sends files that do not comply and the exception becomes the norm.
A standard that requires discipline to follow will be abandoned. A standard baked into the template gets followed automatically.
Put it in the template, not the document
Every rule that can be enforced by setup should be. Layers preloaded with correct colours and line types, text and dimension styles defined and named clearly, title blocks with attributes rather than editable text, sheet setups and plot styles ready. If a drafter has to create a layer manually, the naming will drift.
Keep the naming logical and short
Layer names should be predictable enough that someone can guess correctly. Whether you use a national convention or your own, consistency matters more than the specific system. Long elaborate names get abbreviated under pressure, which is how you end up with four variants of the same layer.
Write down the decisions people actually argue about
Most standards documents cover the obvious and omit the contentious. Be explicit about the things that vary between drafters:
- Dimensioning conventions: from grid or from face, and how strings are structured
- What is drawn at each scale and what is referenced to a detail
- How revisions are clouded and tracked
- File naming and version handling
- How external references are attached and paths managed
- Which drawings carry which notes, and where standard notes live
Check at the right moments
Reviewing standards compliance at the end is too late. Check early on the first few sheets of a project, when correcting is cheap and the pattern gets set. A short review at ten percent complete saves a painful cleanup at ninety.
Handling incoming files
Decide in advance what happens when consultant files arrive non compliant: whether you convert them, quarantine them as references, or accept them as they are. Undecided, this is where standards quietly erode.
Keep it maintained
A standard nobody owns goes stale. Someone should be responsible for updating the template when a convention changes, and for making sure new starters and outside teams get the current version rather than whatever was on the server three years ago.
Short, embedded in the template, checked early, and owned by someone. That is what survives a deadline.