Most content pain traces back to the same root: the writer did not know what the post was for. Not the topic — the job. A brief fixes that, and a good one takes fifteen minutes to write and saves three rounds of edits. This is the template I use for every post on this site, including the ones I write myself — writing your own brief is how you avoid discovering your article’s purpose at paragraph forty.
The template
Eight fields. Anything longer than this does not get read, which makes it worse than nothing.
- Goal (one sentence). What should the reader do or decide after reading? Not “learn about caching” — “choose and install the right caching setup for their shared-hosting site.”
- Audience (one sentence with a constraint). “WordPress site owners on shared hosting who have never touched server settings.” The constraint is what shapes vocabulary and depth.
- Primary query + intent. The exact search phrase and what the searcher wants: a decision, a fix, or a how-to. The entire outline bends around intent — a “should I” query needs a decision framework like the one in my when-to-migrate guide, not a tutorial.
- Proof inventory. The first-hand material only we have: tests run, numbers, screenshots, mistakes made. If this field is thin, the post will be generic — and generic is the losing move per my 2026 strategy. Briefs with empty proof fields get rejected, not written.
- Outline (H2 level, 4-7 sections). Written by the brief author, not the writer, so the argument is locked before drafting starts.
- Internal links (4-6, specific). The exact URLs this post should link to and the anchor context. This is how clusters knit together; my Core Web Vitals guide links out precisely because briefs made it so.
- Format requirements. Target length range, FAQs (how many, which questions), images needed, and any CTA.
- Done means. The acceptance test: “reader can complete X,” or “answers the primary query within the first 200 words.” Vague done-conditions produce vague drafts.
The field everyone skips (and regrets)
Proof inventory is the field most briefs omit, and it is the one that determines whether the piece can compete. Any competent writer can produce correct-but-hollow text about running a migration; only someone who broke a checkout during one can write the section that wins the click. If you cannot fill field four, either you have the wrong writer or the wrong topic.
Using the brief with AI assistance
When production involves AI, the brief becomes even more important — it is the human intent AI works from. Field four becomes the “human writes these sections” marker, and the rest is fair game for drafting assistance, per the workflow in my AI workflow guide.
For solo writers: brief yourself anyway
The objection I hear: “I write alone, why do I need a brief?” Because the brief is not communication to another person — it is thinking made explicit before drafting. Writing my brief, I routinely discover the post’s real goal is narrower than I assumed, or that two planned posts are the same post. Fifteen minutes vs. a restructured draft at 1,800 words. If you are running everything solo, my one-person plan slots briefs into the weekly cycle so the overhead stays contained.
How long should a content brief be?
One page, roughly eight fields. Longer briefs do not get read. The eight fields: goal, audience, primary query and intent, proof inventory, outline, internal links, format requirements, and the done condition.
What is the most important field in a content brief?
Proof inventory. It lists the first-hand material only you have, and it determines whether the finished post can compete with generic coverage. Thin proof means the topic or writer is wrong.
Should solo writers bother with content briefs?
Yes. The brief is not communication, it is pre-drafting thinking. It regularly reveals that the planned post is narrower or more redundant than assumed, saving a costly restructure later.
How do internal links in a brief improve SEO?
Specifying exact target URLs and anchor context before drafting makes every post reinforce its topic cluster. Ad-hoc linking after writing produces scattered, weaker signals.
When should a brief be rejected instead of written?
When the proof inventory cannot be filled. No amount of good structure compensates for a post where nobody involved has real experience with the topic.
