If you have ever compared a content brief's H2 outline against the published article, you have probably seen this: the headings are not the same. A section got dropped. Two got merged. A new one appeared. The article is still on-topic, the writing is still fine, but the structure does not match the brief.
This is the single most common form of brief drift, and it is almost always blamed on the writer being undisciplined. It is not. The H2 outline is the section of the brief structurally most likely to be ignored, and the reasons are predictable.
Headings without word counts are categories, not constraints
A brief that lists H2s as titles only - "What is X," "Why it matters," "How to do it" - has given the writer category labels, not constraints. Within a section labeled "Why it matters," the writer can produce 80 words or 800 and either looks like they hit the brief.
So the writer optimizes for what they care about: rhythm. They balance section lengths by feel. The section they like gets longer. The section they do not get shorter. The brief had no answer to "how long should this be," so the writer's instincts answered it.
Word counts per heading are the fix, and they have to be tight enough to matter. "150-200 words" constrains. "200-500 words" does not.
Headings without a stated purpose get reinterpreted
"What is X" is a category. Without a one-line purpose - "definitional grounding for readers who do not know the term" - the writer is going to reinterpret it. They might use the section to argue why X is important, or to compare X to Y, or to set up the rest of the article. All are reasonable. None match what the brief actually meant.
A heading with a stated purpose is a contract. A heading without one is a Rorschach test. Two writers reading the same outline will produce structurally different drafts, and neither of them is being lazy.
Outline-by-headings ignores the article's center of gravity
Every article has a center of gravity - the section that does most of the load-bearing work. In a how-to, it is the steps. In a comparison, it is the side-by-side. In a definitional explainer, it is the definition plus implications.
A brief that lists eight equal-weight H2s has not told the writer where the article's center of gravity is. So the writer picks one on instinct. Sometimes they pick the section closest to their own expertise. Sometimes they pick the section they have a strong opinion about. Sometimes they spread the load evenly across all eight, which produces a thin-everywhere article.
Word counts per heading also solve this. If "How to do X" is 700-900 words and every other section is 150-300, the writer knows where the article actually lives.
The brief shows H2s, not the order they will be read in
Writers do not read briefs in section order. They scan for the headings table because it is the most concrete thing on the page. The intro framework, the source URLs, the CTA, the no-list - all of those get read later, after the writer already has a mental model of the article from the H2s alone.
So if the H2 outline carries the constraints but not the purpose statements or word counts, the writer's mental model gets locked in around an under-specified structure. When they hit the source URLs and CTA paragraph in the brief, they are working backward to fit them into the structure they have already committed to.
The fix is to put the H2s last in the constraints page, after the intro framework, source URLs, and CTA. The writer reads the constraints in order, then sees the headings as the final assembly instructions. The mental model forms with all the constraints already in mind.
Photo by cottonbro studio on Pexels
The outline is treated as fixed, but it should not always be
This one is the inverse of the first four. Briefs sometimes specify the H2 structure so rigidly that the writer cannot fix obvious problems. If the brief says "Section 4 must be 'Mistakes to avoid'" and the article actually has nothing useful to say in that section, the writer either fills it with filler or fights with the brief.
A surviving brief is explicit about which headings are negotiable and which are not. "Section 4 must address common pitfalls; you can rename or restructure if a better frame appears" is a constraint with room. "Mistakes to avoid - exact heading" is a constraint without room. Both are valid. Mixing them up creates friction.
Google's helpful content guidelines push toward structure that serves the reader, not structure that satisfies the brief. A brief that locks down headings in places where reader intent has shifted is going to produce articles that read as ranking-driven rather than reader-driven. The Schema.org Article specification is a useful background read if you want the structured-data side of why heading hierarchy matters as a signal.
What a working H2 outline looks like in the brief
A working H2 outline in the brief has three columns: heading title, target word count range, purpose in one phrase. It is positioned last in the constraints page, after intro framework, sources, and CTA. Headings that must stay exactly as written are flagged with a "fixed" annotation; the rest are negotiable.
Here is the same outline in working form:
| Heading | Words | Purpose | Flexibility |
|---|---|---|---|
| What is X | 200-250 | Definitional grounding | Title flexible |
| Why it matters now | 250-300 | Stakes for the reader | Title flexible |
| How to do X step by step | 700-900 | The actual guide | Fixed heading |
| Common pitfalls | 200-250 | Pitfalls and edge cases | Title flexible |
| Wrap and CTA | 150-200 | Drive to action | Fixed heading |
The writer reads that and has zero room to invent structure. They also have permission to rename three of the five headings if a better frame appears mid-draft. Both are necessary.
A free Content Brief Builder handles this format natively - the H2 outline ships with word count ranges and a purpose column on every brief it generates. The full longer piece on what survives the draft is on the EvvyTools blog and walks through the other four sections that drift along with the H2 outline.
How to audit the H2 outlines in your current briefs
Pull the last ten briefs your team produced. For each one, mark the H2 outline section. Then ask three questions:
- Are there word count ranges on each heading? If no, every heading is a category, not a constraint.
- Is there a one-line purpose statement on each heading? If no, two writers will reinterpret the heading differently.
- Is the article's center of gravity (the section that should carry the most weight) clearly the longest target range? If no, the writer will distribute weight on instinct, usually evenly.
If any of those three answers is "no" on more than half of the briefs, the outline format is the leverage point. Fix the template once. Subsequent briefs all inherit the fix.
Common pushback from writers
When you tighten the outline format, expect writers to push back at first. "Word counts per heading constrains my voice." They do not - the ranges are wide enough to leave room for paragraph rhythm, and they constrain only the section length, not the prose inside it.
"Purpose statements make me feel like I am filling in a worksheet." Not really - the purpose statement just tells the writer what the section is for, which the writer already had to figure out on their own before. The brief just supplies the answer.
The Wikipedia entry on content marketing is a good reference for the underlying principle: consistent structure across a content series compounds for topical authority, and the structure has to come from somewhere. If it does not come from the brief, the writer invents it, and consistency suffers.
The format the outline should ship in by default
Every brief generated by your team's tooling should default to: heading title, word count range, purpose statement in one phrase, and a flexibility flag (fixed or negotiable). Anything less is leaving the writer to invent constraints, which is when drift starts.
Briefs that ship in this format produce drafts that come back close enough to the intended structure that the editorial pass is a polish. Briefs that ship without it produce drafts that need restructuring, and the cost compounds across the content series.
The H2 outline does not have to be the section that drifts. It is the section that drifts because most briefs hand the writer category labels and call it an outline. Hand them constraints with purpose statements, and the structure holds.
Top comments (0)