Every painful blog revision loop traces back to the same missing object: a brief. The owner asked for “a post about our service,” the writer delivered a post about the service, and the two discovered in round three that they meant different posts — different readers, different promises, different proof. A content brief is the one-page document that prevents that discovery. Written before a word of the draft, it fixes the audience, the promise, the proof, the structure, and the links, so the first draft lands within one round of right instead of three rounds of wrong.
This article provides the template and the reasoning per field. It slots into the rest of the publishing workflow: the brief feeds the managed blog calendar for a small business site, the draft it produces goes through the blog post refresh check before publishing, and the whole loop sits inside the review discipline described in AI blog writing for WordPress with human review. If someone else does the writing for you — as with done-for-you blog posts for a small business — the brief is not optional polish; it is the contract that makes delegation possible at all.
Why One Page Beats Five
Briefs fail in two directions: too thin (“write something about X”) gives the writer nothing to aim at, and too thick (a five-page strategy deck) gives the writer no room to think. The one-page constraint is the whole trick, because it forces decisions. If the audience cannot fit in two sentences, it is not decided yet; if the promise cannot fit in one, the post does not have one. A brief is also a commitment device for the owner: anything left vague in the brief will be decided later, by the writer, under deadline pressure, and the owner will then pay for the revision. The one-pager discipline from product teams applies exactly here — compress until every remaining word earns its place, and what survives is the actual brief. Treat the page limit as a feature: it converts “we should think about the blog” into a decision, in writing, before money or hours are spent.
The Audience Field
The first field names the single reader the post is for — not a demographic spread, a person. “A homeowner in our service area who suspects their problem and has not yet called anyone” beats “homeowners aged 30-60.” The sharper the person, the easier every later decision: the examples pick themselves, the jargon level sets itself, and the call to action writes itself. If your business serves two genuinely different readers, that is two posts with two briefs, not one post hedging between them. Add one sentence on the reader’s current situation and one on their fear, because posts that name the fear out loud are the ones that get read to the end. A useful test: before any other field, complete “this post is for the reader who…” aloud. If the sentence stalls, the brief stalls; go talk to a real customer before writing anything else.
A second test worth applying: read the audience sentence to a colleague and ask who would not want to read the post. If the answer is “nobody,” the audience is still too broad — a post for everyone is a post for no one, and the broad version always shows up later as a draft with no edge. The colleague does not need to know your market; the confused look is the measurement.
The Promise And The Proof
The promise is what the reader walks away able to do — one sentence, concrete, checkable. “Understand our service” is not a promise; “know the three questions to ask before hiring anyone for this job, including us” is. The proof is what makes the promise believable: a number from your own jobs, a named case, a before-and-after, a documented process. Every claim in the draft will lean on something, and the brief names that something in advance, which is what separates a post with evidence from a post with adjectives. Decide the proof before the draft because proof discovered during writing usually turns out to need a customer call, a photo hunt, or a permission request — each of which can stall a draft for a week. If the honest answer is “we have no proof for this post,” that is valuable news at brief time, when you can either change the post’s claim or go collect the proof, instead of at draft time, when the choice is publish fluff or start over.
Structure And Links
The structure section is a list of the post’s sections in order — five to eight items, each named by its job, not its topic. “Open with the symptom the reader already recognizes,” “the three questions in order,” “what our process looks like,” “when not to hire anyone.” This is not scripting the prose; it is fixing the skeleton so the writer’s energy goes into the muscle. The links field names the internal posts the new one must connect to and the one or two external references it should lean on, because links decided at brief time become natural inline references, while links retrofitted after the draft read like decoration. Check both against the live site before the brief is final — a link field pointing at a renamed post is a draft defect waiting to ship. Together, structure and links are where the brief protects the site’s existing content investment: the new post should strengthen the old ones, not strand beside them.
The Brief Template At A Glance
| Field | What goes in it | Test |
|---|---|---|
| Audience | One named reader, their situation, their fear | “This post is for…” completes without stalling |
| Promise | One concrete, checkable outcome | Reader could verify it after one read |
| Proof | The numbers, cases, or processes that make it believable | Every claim has something to lean on |
| Structure | Five to eight sections named by job | Skeleton complete, prose left to the writer |
| Links | Internal connections and one or two external references | All targets checked live before drafting |
Five fields, one page, one decision per field — the template is deliberately smaller than the anxiety it removes. Fill it once and the next forty briefs take fifteen minutes each.
What The Brief Does Not Do
Two boundaries keep the brief healthy. It does not script the prose: a brief that dictates sentences produces paraphrase, not writing, and you hired a writer for the second thing. And it does not replace review: the draft still passes the blog post refresh check before publishing, the tone still gets checked against the brand, and factual claims still get verified by a human as described in AI blog writing for WordPress with human review — the brief makes review faster because there is a written standard to review against, not because review became unnecessary. Inside the workflow, the brief is the handoff point where strategy becomes assignment: the calendar says when, the brief says what and why, the writer says how. Keep those lanes clean and a small business blog stops being a monthly scramble and becomes a system — one that survives vacations, staff changes, and the month nobody feels inspired, because the decisions were already written down.