The CAD Standards Document: The One File That Makes Outsourcing Work

When a firm tells us outsourcing "didn't work" for them, we ask one question: did you send them your CAD standards?

The answer is almost always some version of "they should have figured it out from our old drawings."

That's the problem. Not the drafter, not the time zone, not the price. If the only place your standards live is in the heads of your people and in the habits buried inside old DWGs, then every new person, employee or outside team, will guess. And every guess turns into a redline you have to make yourself.

A CAD standards document fixes that. It's not glamorous. It's probably the highest-ROI document your firm will ever write.

Why your old drawings are not a standard

"Just match the last project" sounds reasonable until you open the last project:

• Three different text styles, because three people touched it over two years.
• Layers named ROAD, C-ROAD, road new and Layer1, all holding road linework.
• A title block that was edited in place instead of updated in the template.
• Dimensions at two different scales because someone copied a detail from another job.

Old drawings show what happened. A standard says what should happen. Anyone learning from your old drawings is learning your inconsistencies along with your style.

What a CAD standards document must include

Keep it short enough that people actually read it: 8 to 15 pages is plenty for a small firm. These are the sections that do the real work:

1. File setup and naming

• Template file (.dwt): the one file every new drawing starts from. Link to it; don't describe it.
• File naming convention, e.g. [ProjectNo]_[Discipline]_[SheetType]_[Rev].dwg → 26-114_C_GRAD_R2.dwg.
• Units and coordinate system. For civil and geotech work in Florida: which State Plane zone (East, West or North), which datum, US survey feet or international feet. Getting this wrong doesn't look wrong. It just puts everything in the wrong place.
• Xref rules: relative or absolute paths, overlay or attach, where base files live.

2. Layers

This is the section that prevents the most rework. Define:

• Naming structure. Many firms adapt the U.S. National CAD Standard pattern (Discipline-Major-Minor, e.g. C-ROAD-CNTR). You don't need the whole NCS; you need a consistent pattern.
• A layer table: name, color, linetype, lineweight, plot/no-plot, and what goes on it.
• Forbidden practices: nothing on layer 0 except block definitions, no geometry on Defpoints, no color overrides by object.

Example table:

3. Text and dimension styles

• Text style names, fonts and heights at plot size (e.g. 0.08" general notes, 0.12" titles, 0.20" sheet titles).
• Annotative or not: pick one. Mixing annotative and non-annotative text in the same set is one of the most common sources of "why is this text tiny on sheet 4?"
• Dimension style names per scale, arrowheads, precision (feet-and-inches vs. decimal feet).

4. Blocks and symbols

• Where the block library lives.
• Standard blocks with names: north arrow, boring symbol, section cut, detail callout, revision cloud and delta.
• Attribute definitions for blocks that carry data (boring ID, depth, elevation).

5. Sheet setup and plotting

• Sheet sizes you use (22×34 / 24×36) and the title block for each.
• Viewport rules: locked, scale set, no geometry drawn in paper space except title-block content.
• Plot style (CTB/STB): attach the actual file.
• PDF output settings: resolution, layers on/off, combined vs. individual sheets.

6. Quality control checklist

The section most firms skip, and the one that matters most when someone outside your office is drawing. A one-page checklist that every set passes before it leaves:

• All objects on standard layers (no layer 0, no non-standard names)
• PURGE and AUDIT run, no errors
• Xrefs resolved, no broken paths
• Title block complete: project number, date, revision, sheet number of total
• Revision clouds and deltas match the revision table
• Spelling check run on all layouts
• Scale bar and north arrow present on every plan sheet
• PDF reviewed at 100%, not just at "fit to screen"

7. Delivery and revisions

• What you deliver: DWG, PDF, both? eTransmit packages?
• Revision naming and how redlines are sent back (marked-up PDF, Bluebeam session, email with numbered comments).
• Turnaround expectations for first submittal vs. resubmittals.

The test: could a stranger produce your drawing?

Here's how you know your standards document is good enough: give it to someone who has never seen your work, along with a markup, and look at what comes back.

If you have to fix layers, text sizes and the title block, the document isn't done. If you only have to review the engineering, it is.

That's the real point. A standards document turns drafting from a craft that lives in one person into a process that lives in your firm. It's what lets you bring on a new hire in days instead of months, hand off overflow to an outside team without fear, and survive the day your longtime drafter retires.

Common mistakes when writing standards

Writing a novel. A 60-page standards manual doesn't get read. If a rule doesn't prevent a real, recurring mistake, cut it.

Describing instead of linking. "Use our standard title block" is useless without the file. Every standard that has a file (template, plot style, block library) should link to the actual file in a known location.

Copying the full National CAD Standard. The NCS is a great reference, but small firms don't need all of it. Borrow its naming logic and keep only the layers you actually use.

Never updating it. Standards drift. Assign one person to own the document, and review it twice a year or whenever the same redline shows up three times.

Keeping it secret from outside help. Some firms write good standards and then don't send them to freelancers or outside teams "because they should already know." Your standards are the cheapest training material you'll ever produce. Share them.

Don't start from zero

You don't need to write this from scratch over a month. Here's a one-week plan:

1. Day 1: Pick your three best recent drawing sets. These become your reference.
2. Day 2: Export the layer list from your template (LAYER → right-click → select all → copy, or use a LISP routine) and clean it into the table above.
3. Day 3: Document text/dim styles and the title block. Fix the template while you're at it.
4. Day 4: Write the QC checklist from the last ten redlines you had to make. Your past corrections are your checklist.
5. Day 5: Hand it to someone who hasn't drawn for you and run the stranger test.

Where we come in

Every project we take on at Kronos GMT starts with your standards. If you don't have them written down yet, we'll build the document with you from your existing drawings as part of onboarding. We use it, you keep it, and the next person you hire inherits it too.

That's what we mean by a system that works no matter who's drawing.