QA/QC is a system you run, not a virtue you have. Three layers:

Layer 1 — Self-check (every deliverable, before anyone sees it)

  • Inputs: volumes, geometry, land use, code sections traced to source; source written in the file.
  • Units & magnitude: does every number pass a sniff test? (A 4,000 vph driveway is a typo, not a finding.)
  • Internal consistency: text ↔ tables ↔ figures ↔ appendix all agree; totals foot; AM/PM not swapped.
  • Standards: checked against the governing manual edition the agency uses, not the newest one.
  • Assumptions: every assumption logged in the project note with basis (the project note template has the table).
  • Files: naming convention, dated, prior versions archived, links/formulas not broken.
  • Print-or-PDF review — errors hide on screens.

Layer 2 — Domain checklists (open the one that applies)

Synchro QAQC Checklist · SPM Plan Review Checklist · Parking QA/QC (step 18 inside Workflow - Parking Study) · Quantities and Pay Items How-To · Redline Response Workflow (comment closure check)

Layer 3 — Senior review (make it easy to review you)

Send with: what it is, what you checked, what you’re unsure about (specifically), assumptions list, and where the source files live. A reviewer who trusts your Layer 1 gives you better work.

Personal red-flag list (grows from Lessons Learned System)