editorial-qa

# Editorial QA

A senior editor's playbook for pre-publish content QA. The discipline that catches problems BEFORE content ships, not after.

Most content QA is broken in one of two directions. The thin version is "did I read it once and is the spelling OK," which catches typos but misses brief drift, voice inconsistency, hallucinated facts, AI tells, and structural problems that reach readers as "this is fine but not memorable." The thick version is a 47-item checklist that nobody completes honestly because it is process theater: checkboxes nobody actually believes catch problems.

This skill is the discipline of catch-problems QA. Each check earns its keep by catching a specific class of failure that would reach readers if missed. Checks that do not catch anything get cut. Checks the production volume cannot sustain get redesigned (sampling instead of full audit, automated instead of manual). The QA framework is what is left when you remove the theater.

The skill covers three production shapes: single editorial pieces (one at a time, full QA), AI-generated drafts (with the AI-content audit that did not exist as prominently 2 years ago), and programmatic SEO sets at scale (sampling discipline, threshold gating). Each needs its own QA shape; the underlying methodology composes across all three.

When to use this skill: building a content QA process from scratch, auditing an existing QA process that ships sloppy work or burns out the team, designing QA gates for an AI-assisted workflow, or building sampling discipline for programmatic SEO sets.

---

## What this skill is for

This skill spans pre-publish quality control. It plugs in at the END of every other content skill's output. The six-skill content suite distinction:

- `content-strategy` is program scope: what to produce.
- `pillar-content-architecture` is hub scope: how the topical hub fits together.
- `content-brief-authoring` is per-piece scope: briefs each piece.
- `content-and-copy` is execution scope: writes each piece.
- `programmatic-seo` is scaled scope: generates many pages from data.
- This skill is gate scope: verifies before publish.

Every skill above produces a draft. This skill is what gets drafts to publishable. It is the gate where quality is actually enforced.

The audience: editorial leads, content directors, in-house content QA, agencies with production lines, content ops managers, anyone running a writer (human or AI) and accountable for what ships. The voice is senior editor to junior editor or content marketer. Specific, opinionated, honest about where QA earns its keep versus where it becomes process theater.

---

## Catch-problems QA vs checkbox QA

The keystone distinction. Two failure modes plus the discipline.

**Thin QA (typo-checking dressed as quality control).** "I read it once, it is fine." Catches obvious mistakes; misses brief drift, voice inconsistency, hallucinated facts, structural problems, AI tells. Output: shipped content that is "fine but not memorable." Cost: invisible until a brand misstep, a hallucinated statistic, or a competitor's content compounds and the thin set falls behind.

**Thick QA (47-item checklist nobody completes honestly).** Every conceivable check listed; no triage. Reviewers either skim and check boxes (theater) or burn out under the cognitive load. Output: shipped content slightly more polished than thin QA produces, but the team's review velocity collapses. Cost: throughput drops; reviewers leave; the checklist atrophies into a few checks that actually run.

**Catch-problems QA (the discipline).** Each check earns its keep by catching a specific class of failure that would reach readers if missed. Checks that do not catch anything get cut. Production volume drives sampling versus full-audit decisions. Reviewers are accountable for what they caught, not for box-completion.

The litmus test. If the team can name the last 3 problems each QA check caught, the check earns its keep. If a check has not caught anything in 6 months, it is theater. Cut it; reallocate the attention to checks that catch real problems.

---

## Brief adherence check

Did the writer execute the brief? The check is straightforward when the brief is well-authored (see `content-brief-authoring`).

The brief-adherence checks:

- **Target keyword and cluster.** Present in title, first paragraph, headings.
- **Search intent and SERP format.** Piece matches the dominant SERP format (article when SERP wants article, listicle when SERP wants listicle).
- **Target audience.** Piece reads as written FOR the named audience, not for a generic reader.
- **Heading structure.** Piece follows the H2 / H3 outline in the brief, or has a documented reason for deviation.
- **Required entities.** Every entity flagged in the brief appears in the piece.
- **Internal links.** Outbound links specified in the brief are present with the right anchor text.
- **Anti-patterns.** Piece avoids the off-limits language and structures named in the brief.
- **Success criteria acknowledged.** Piece is shaped to MEASURE against the success criteria.

The brief-adherence check is the cheapest, fastest, highest-value QA gate. It runs first in the QA sequence because catching a brief-adherence failure early saves the editor from spending time on voice and structure on a piece that will need to restart.

If briefs are vague, this check is impossible. Fix briefs first; the QA process cannot enforce a contract that does not exist.

Detail in [`references/brief-adherence-checklist.md`](references/brief-adherence-checklist.md).

---

## Voice consistency check

Does the piece sound like the brand?

- **Vocabulary.** Brand-specific terms used correctly; off-brand terms absent.
- **Sentence rhythm.** Matches brand voice (short and punchy versus measured and layered versus colloquial).
- **Stance.** The piece takes positions consistent with brand POV.
- **Register.** Formal or casual matches the surface (blog versus whitepaper versus help doc)