The Pre-Issue CAD QA Checklist: Catch Drawing Errors Before They Ship

Every CAD manager knows the feeling. The set went out yesterday, and this morning the contractor emails to ask why sheet A-301 has a dimension style nobody recognizes, why the title block on three sheets still says "PRELIMINARY," and why a layer called "Layer1" is plotting at full black. None of it changes the building. All of it costs you time, credibility, and in the worst cases an RFI or a change order. A short, disciplined QA pass before issue, driven by a repeatable cad qa checklist, would have caught the lot.

This post gives you a copy-and-paste cad qa checklist you can run before any drawing set leaves the office. It is organized by category so you can scan it quickly, hand it to a junior drafter, or pin it next to your monitor. The goal is not perfection on every line. The goal is to catch the handful of errors that consistently embarrass firms and trigger rework: stray layers, rogue styles, inconsistent title blocks, hard-coded overrides, broken xrefs, and the wrong plot settings.

We will walk through the checklist itself, then look at how to automate the boring, repetitive parts so the review takes minutes instead of an afternoon. If you run standardization on incoming files too, pair this with our guide on AutoCAD layer management best practices for the upstream half of the problem.

Why a Pre-Issue QA Step Matters

The cost of shipping a set with errors is rarely the error itself. It is the downstream chain it sets off. A wrong layer color is trivial in isolation, but if it means a fire-rated wall plots the same weight as a furniture line, the reviewer flags it, the sheet comes back, someone reopens the file, fixes it, re-plots, re-checks, and re-issues. Multiply that by a dozen small misses across a 40-sheet set and you have lost a day. Worse misses, like an outdated revision in the title block or a missing xref that drops half a plan, can ship to the field and become an RFI or a claim.

There is also a trust cost that does not show up on a timesheet. When a consultant or client receives a set that is visibly inconsistent, they start checking your work more closely on everything, which slows every future exchange. Clean, consistent sets buy you the benefit of the doubt.

So why does "we'll catch it in review" fail so often? Because an unwritten review depends on whoever is doing it remembering every category, every time, under deadline pressure. Human attention is selective. The reviewer who is worried about dimensions will scan for dimensions and skim past the title block. The one rushing to make the courier will check the sheets that changed and assume the rest are fine. A written checklist removes that variability. It turns "look it over" into a fixed sequence of yes or no questions, and it makes the review auditable: you can see what was checked and by whom. A checklist is also how you get consistency across reviewers, so the QA pass does not depend on which person happens to be free that afternoon.

The CAD QA Checklist

Here is the core of this post: a scannable, category-by-category drawing qa checklist. Copy it into your firm's wiki, your issue template, or a printed sheet. Each item is a quick yes or no. If any answer is no, fix it before issue.

1. Layers

The single most common source of drawing inconsistency. Check the layer list against your standard before anything else.

• All layer names follow the firm standard (AIA, ISO 13567, or your custom scheme). No Layer1, 0-copy, or imported-from-elsewhere names.
• No stray or orphan layers left over from blocks, pasted content, or old design iterations.
• No empty layers that should have been purged (run PURGE, then confirm intentional empties remain).
• Layer colors match the standard, so plotted lineweights come out as intended.
• Lineweights are correct per layer and consistent across sheets.
• Nothing is left on layer 0 that should live on a named layer. Layer 0 is for block definitions, not drawing content.
• Frozen, locked, and no-plot states are deliberate, not accidental.

2. Dimension and Text Styles

Rogue styles are the errors reviewers spot instantly because they break visual consistency.

• One standard set of dimension styles is in use. No Standard, Copy of..., or one-off styles created mid-project.
• One standard set of text styles is in use, with no rogue styles imported from other files.
• Text heights are correct for each scale and match the firm standard.
• Dimension text heights and arrow styles are consistent across every sheet.
• All referenced fonts (SHX and TrueType) are present, so text does not substitute or shift on another machine.
• No dimension overrides that silently change a single dimension's appearance away from its style.

3. Title Blocks

The most missed category, because the fields look fine sheet by sheet but disagree across the set. The field set must agree on every sheet.

• Project name is identical on every sheet (watch for typos and abbreviation drift).
• Client name is identical and current on every sheet.
• Dates are correct and consistent (issue date, not the date you opened the file).
• Drawn-by, checked-by, and approved-by fields are filled and correct.
• Issue status is the same on every sheet (no PRELIMINARY or FOR REVIEW left behind on a few).
• Sheet numbering is sequential, has no gaps or duplicates, and the "Sheet X of Y" total matches the actual sheet count.
• Revision numbers and revision dates agree with the revision history block.

4. Object Overrides

Overrides defeat the entire point of a layer standard. A drawing where color and linetype are set per object cannot be controlled from the Layer Manager.

• Color is ByLayer on all drawing entities. No hard-coded color assignments.
• Linetype is ByLayer. No per-object linetype overrides.
• Lineweight is ByLayer (or ByBlock where intended for blocks).
• No object-level overrides that mask the true layer state. Use SETBYLAYER if you find any.

5. Naming and Standards Compliance

• The file name follows the firm convention (project code, sheet number, revision).
• The layer standard in the file is the current approved one, not a superseded version.
• Plot style assignment is correct (the right CTB or STB for this project).
• Block and xref names follow convention and do not collide with standard names.

6. Xrefs

Broken or wrongly attached references are how half a plan disappears or a base file shows up twice.

• All xref paths resolve. No "not found" or "unresolved" references in the External References palette.
• No missing references that leave gaps in the drawing.
• Each xref is attached or overlaid correctly per your nesting strategy (overlays do not nest, attachments do).
• Reference paths are relative where your office standard calls for it, so the set survives being moved.
• No unintended bound or exploded xrefs that should still be live references.

7. Plot and Output

The last gate. Everything upstream can be perfect and a wrong plot setting still produces a bad sheet.

• The correct plot style table (CTB or STB) is assigned in every layout.
• Plot scale is correct for each viewport and matches the scale noted on the sheet.
• Paper size and orientation match the title block and the intended output.
• Plot area is set to the layout (not Display or Window by accident).
• A test plot or PDF export looks correct: lineweights read, text is legible, nothing is clipped.

Run these seven categories in order and you will catch the large majority of issue-day errors. The next question is how to do it without spending half a day clicking through palettes.

How to Automate the Boring Parts of CAD QA

A manual checklist is a huge improvement over nothing, but several categories above are pure pattern matching: comparing the file against a known standard and listing the deltas. That is exactly the kind of work software should do, so the human reviewer can spend attention on judgment calls instead of counting layers. This is where a drawing quality control tool turns the manual pass into a repeatable, partly automated one.

MorphoCheck (the MORPHOCHECK command) scores a drawing across five categories: layers, dimension styles, text styles, object overrides, and naming. In one pass it surfaces the non-standard layers, the rogue styles, the hard-coded overrides, and the naming violations that map directly onto sections 1, 2, 4, and 5 of the checklist above. Instead of eyeballing the Layer Manager, you get a category-by-category score and a list of what is off, which is the cad standards compliance picture you would otherwise assemble by hand.

For the style category specifically, finding the drift is only half the job; you still have to fix it. MorphoStyle (the MORPHOSTYLE command) compares the file's dimension and text styles against your template, shows the differences, fixes the definitions, and reassigns the affected entities. That closes section 2 of the checklist in a controlled way rather than redefining styles by hand and hoping every dimension picks up the change.

Title blocks, section 3, are the category most resistant to a single-drawing scan, because the whole point is consistency across sheets. The Title Block Manager (the MORPHO_TITLE command) lines up every sheet's title block in a register: rows are sheets, columns are fields such as PROJECT_NAME, DRAWING_TITLE, SCALE, DRAWN_BY, ISSUE_STATUS, DATE, and SHEET_OF. It flags missing or mismatched values across sheets, so the one sheet still marked PRELIMINARY or the abbreviation that drifted on sheet 14 jumps out immediately. When you find problems, you fix them in bulk: Set Value across sheets, Fill Empty, Fill Series, Auto Number, Number X of Y, and Find and Replace. It works across multiple files with Add DWG and can read AutoCAD sheet sets with Add DST, so legacy and sub-consultant files get checked alongside everything else. It is deterministic, reads your existing title blocks with zero setup, and consumes no AI quota. Corrections are written only when you click Apply, and the change is reversible in AutoCAD.

If your firm uses AutoCAD's Sheet Set Manager, this is a complement, not a replacement. Sheet Set Manager is excellent for authoring a structured set: it auto-numbers sheets, links title block fields to sheet and set properties so you fill a value once and it propagates, and publishes the whole set with index tables. What it does not do is audit arbitrary, real-world drawings for existing inconsistencies, especially files that were never part of a configured sheet set or that use plain-text and attribute title blocks. The Title Block Manager is the audit and bulk-fix layer for exactly those cases, and it can even read your .dst sheet sets so SSM-managed sheets land in the same consistency check as everything else.

Put together, the automated pass looks like this:

Xrefs and plot settings (sections 6 and 7) still want a human eye, but the bulk of the tedious comparison work is handled, which is what makes the QA pass fast enough to actually run every time.

Make It a Standing Process, Not a Heroic Effort

A checklist that lives in someone's head is not a process. To make pre-issue QA stick, give it three things.

First, make it a standing document. The checklist above should live somewhere everyone can reach it: a wiki page, the issue-folder template, a pinned PDF. When it is written down, it survives staff changes and does not depend on the most experienced person being in the office.

Second, give it an owner. Someone signs off that the QA pass ran before the set goes out. That is not about blame; it is about making sure the step does not silently get skipped under deadline. On a small team it is the CAD manager. On a larger one it can rotate, as long as it is always assigned.

Third, define when to run it. The honest answer is at least twice: a lighter pass when a milestone is in sight, and the full pass immediately before issue, after the last edits and before the PDF or plot goes out. Running it too early means you re-run it anyway after late changes. Running it only at the very end with no earlier look means you discover a structural problem (a layer standard mismatch, a missing xref strategy) when there is no time to fix it properly. A quick mid-stream check plus a thorough pre-issue check is the balance most firms settle on.

Tie the automated tools into that cadence. The fastest version is to run MorphoCheck and the Title Block Manager as the first move of the pre-issue pass, let them produce the list of deltas, fix what they surface (using MorphoStyle for the style drift), then spend your human attention on xrefs and a test plot. The manual checklist becomes the safety net behind a partly automated first pass, not the whole job.

Frequently Asked Questions

How long should pre-issue QA take?

For a typical set, the full pass should take well under an hour once you have a written checklist and automate the repetitive categories. The manual-only version of this review on a 40-sheet set can eat an afternoon, which is precisely why firms skip it under pressure. When MorphoCheck handles the layer, override, and naming scan, MorphoStyle handles style drift, and the Title Block Manager handles cross-sheet consistency, the human time drops to reviewing flagged items plus checking xrefs and running a test plot. The point of automation here is to make the QA pass cheap enough that it always happens.

Which parts of the checklist can be automated?

The pattern-matching categories. Layer standard compliance, dimension and text style consistency, object overrides, and naming all come down to comparing the file against a known standard, which MorphoCheck scores and MorphoStyle remediates for styles. Title block consistency across sheets, the hardest category to do by eye, is exactly what the Title Block Manager's register is built for. What stays manual is judgment: confirming xref attach and overlay choices are correct for your nesting strategy, and running a test plot to confirm the output reads the way you intend. For the upstream layer work that feeds all of this, see our layer management best practices.

What is the single most missed item?

Title block consistency across sheets. Individual sheets almost always look correct in isolation, so a sheet-by-sheet review passes them, but the set as a whole disagrees: one sheet still says FOR REVIEW, the project name is abbreviated differently on a handful, the "Sheet X of Y" total is wrong because a sheet was added late, or a revision date never propagated. Because the error only appears when you compare sheets side by side, it survives a normal review and ships. A per-sheet register that lines up every field in columns is the reliable way to catch it, which is why this is the category we most strongly recommend automating.

Do these tools change my drawings without asking?

No. MorphoStyle and the Title Block Manager show you the differences first and only apply changes when you choose to. In the Title Block Manager specifically, corrections are written only when you click Apply, and the change is reversible in AutoCAD. The tools are deterministic, so the same drawing produces the same findings every time, which is what you want from a QA step.

Conclusion

Issuing a drawing set with errors is expensive in ways that never appear on the original estimate: rework, RFIs, change orders, and the slow erosion of trust that makes every future exchange more friction-filled. A disciplined pre-issue QA pass prevents most of it, and it does not have to be heroic. Run the seven-category checklist above, automate the repetitive comparisons with MorphoCheck, MorphoStyle, and the Title Block Manager, and assign someone to own the step so it actually happens before the set goes out. The firms that ship clean sets are not more careful by nature. They have a written checklist and tools that do the boring parts, so being careful is the path of least resistance.

Bookmark this checklist, give the automation a try on your next set, and make the pre-issue pass a habit rather than an afterthought.

Stop shipping drawing sets with avoidable errors. Run a standards-driven QA pass in minutes. Start your free trial and Download MorphoCAD.

MorphoCAD is an AutoCAD plugin that brings CAD standardization to your drafting workflow. Learn more at morphocad.com.