Before you start
- A chosen calendar slot. The brief fills a slot that already exists in the editorial calendar, with a pillar and a rough date attached. If the slot has not been chosen, the content pillars and calendar guide comes first, because a brief written without a pillar tends to drift into whatever the writer finds interesting.
- Audience research to draw on. Interview notes, support tickets, sales-call themes, search and community data: whatever the audience research for content guide produced. The brief does not do the research; it selects from it.
- The content goals and KPIs. The content goals and KPIs guide sets out what content is expected to do at each stage. The brief borrows one goal from that list rather than inventing a new one.
- Someone to review the brief. A second reader catches assumptions the author cannot see. In a team of one, that can be the subject expert who will later review the draft.
- About an hour. The first brief takes longer; once the template is familiar, most briefs take well under that.
The brief, step by step
Each step produces one line or one short block of the template at the end of the page. Write them in order, because each narrows the next: the goal limits the audience, the audience and stage limit the question, the question limits the angle, and so on down to the review criteria. A brief written out of order tends to start from a format or a title the briefer already likes and work backwards to justify it, which is how pieces end up with a goal invented to fit the draft.
State the goal and the measure
Begin with what the piece is for in business terms, not content terms. "Publish a guide" is an activity; "help evaluators understand how our approach differs so more of them request a demo" is a goal. Pick one goal from the content strategy and write the single KPIA metric tied directly to an objective. that will show whether the piece did its job: qualified sign-ups from the page, newsletter subscriptions, assisted conversions, or simply reading depth for an awareness piece. One goal per piece. A brief with two goals produces a draft that half-serves both, and the writer cannot tell which to favour when they conflict. If the slot in the calendar came with a goal already, confirm it still holds; if it came without one, this step is where the piece earns its place or gets cut.
Name the audience and their stage
Describe one reader, not a market. Who they are, what they already know, what they are trying to do this week and what is in their way. Then place them at a stage: are they becoming aware that the problem exists, comparing ways to solve it, or deciding between specific options? Stage changes everything downstream, from how much context the opening needs to what the call to actionThe prompt that tells a reader the one action to take next, such as a button or link. can reasonably ask. Pull the description from the audience research rather than from memory, and quote the reader's own words where you have them, because the writer will use those words in headings and openings. A brief that says "marketing managers" has described nobody; one that says "a marketing manager who has just been asked to justify content spend to a finance director for the first time" has told the writer exactly who to picture.
Write the one question the piece answers
Put the question in the reader's own words, as they would type it or ask a colleague. A piece that answers one question well beats a piece that touches on five, and the question is the test every later decision is checked against: does this section help answer it, does this example illustrate it, does this call to action follow from it? Resist compound questions. "How do I measure content and which tools should I use?" is two pieces. Write the question, then write the one-sentence answer underneath it, because if the answer cannot be stated in a sentence the question is still too broad. For search-led pieces, this is also where the target query and what its results page rewards are recorded; the SEO content brief guide covers that layer and this tutorial leaves it there.
Choose the angle and make the promise
The angle is the reason this piece, from this organisation, deserves to exist when plenty already answer the question. It might be first-hand experience the team genuinely has, a method nobody else has written down, data the organisation holds, a contrarian position the evidence supports, or simply a clearer explanation for a reader others have skipped. Google's helpful content guidance asks whether content offers original information, insight or analysis rather than summarising what others have said, and whether it shows the experience and expertise summarised as E-E-A-TExperience, Expertise, Authoritativeness, Trust.; the angle is where that is decided. Then write the promise: one sentence that tells the reader what they will be able to do after reading. The promise becomes the opening of the piece and the measure of whether the draft delivered. If no honest angle exists, say so now and give the slot to a piece that has one.
List the sources and the proof required
Decide what the piece must prove and where the proof will come from before anyone writes a word. List the facts, figures, quotes, screenshots or worked examples the argument needs, and against each one note the source: a named expert on the team to interview, a public document, the organisation's own data, a customer who has agreed to be quoted. Mark which claims are known and which still need research, and set a rule for the writer: nothing is asserted that cannot be sourced, and anything that cannot be sourced is either rewritten as a labelled opinion or dropped. This step is the one most often skipped and the one that most often sends a draft back, because a writer who discovers at draft stage that the central claim has no evidence has to rebuild the piece around whatever they can find. Where the proof is a named expert, the subject-matter expert interview tutorial shows how to prepare the questions, run the call and draft from the transcript.
Build the outline
Turn the question and the angle into a list of section headings in reading order, each with one line on what the section must contain. Lead with the answer or the promise, not with background; the writing for the web guide explains why readers on screens need the point first. An outline in inverted pyramid order, from conclusion to support to background carries that decision into the draft. Then order the sections by the reader's need: what they must understand before anything else makes sense, then the method, then the proof, then the edge cases and objections, then what to do next. Note where a table, a worked example, a diagram or a checklist would do the job better than prose. The outline is a contract, not a cage: the writer may propose changes, but the brief should say which sections are fixed and which are suggestions, so the editor can tell a deliberate improvement from drift.
Set the format and the length
Decide the content type the outline calls for: a guide, a tutorial with numbered steps, a comparison, a template with instructions, a short explainer, a video script, an email issue. Format follows the question and the reader's stage, not habit; a reader comparing options wants a comparison, and a reader with a task wants steps. When the format is a video for a YouTube channel, the tutorial on writing a YouTube video brief adds the fields only video needs, from the title and thumbnail written together to the opening, chapters and next step. Then set a length as a range rather than a target, derived from what the outline needs to cover properly rather than from a rule of thumb, and say what should be cut first if the draft runs long. Note any production requirements the writer should know up front: images or screenshots to capture, a designer's involvement, a subject expert's review slot, a legal check, accessibility requirements such as alternative text and descriptive link wording, and the house style guide if one exists.
Decide the calls to action
Write what the reader should do after reading and where in the piece each prompt sits. The call to action must match the stage from the audience step: an awareness piece earns a subscription or a related read, a consideration piece earns a template download or a comparison, a decision-stage piece earns a demo or a purchase. Asking a first-time reader to book a sales call is the most common mismatch and the reason many pieces convert nobody. Specify the primary action, one secondary action at most, the wording the brief wants, and the destination each one leads to. Add the internal links the piece must carry to related guides, the pillar page and the product or service page where relevant, because links are part of the piece's job for both readers and search (SEOImproving visibility in unpaid search results.), and they are easier to plan than to retrofit.
Add the distribution notes
A piece that is planned for distribution is written differently from one that is merely published. Note which channels will carry it, and what each needs from the draft: a summary paragraph for the newsletter, a quotable line for social posts, a question for a community thread, a short-video idea, or an excerpt a partner can run. Say whether the piece is the source asset for a set of repurposed formats, in which case the writer should produce the standalone sections and pull-quotes repurposing needs. Record who owns each channel and when it goes out relative to publication. None of this is the writer's responsibility to execute, but a writer who knows the newsletter needs a hundred-word summary writes a better opening, and a writer who knows the piece will be cut into short videos structures the sections so each stands alone.
Hand off with review criteria
Finish with the criteria a reviewer will apply, written as questions that can be answered yes or no: does the opening deliver the promise, is every claim in the proof list sourced, does the structure follow the outline or explain its deviations, is the call to action the one specified, does a named expert agree with the substance, can a reader scan it. Name the reviewer for each criterion, the date the draft is due, and the date the review is due, because unreviewed drafts are where most calendars slip. Then walk the writer through the brief rather than sending it cold, and let them push back: the questions a writer asks at hand-off are the rewrites avoided later. Store the brief with the published piece so the next refresh starts from what was intended rather than from what was published. When the first draft will come from an AI tool, the same brief becomes the prompt, and prompt patterns for marketing shows how its audience, proof list and review criteria carry over.
Brief template
The template is the steps above laid out as a form. Most teams keep it as a shared document with one copy per piece; the fields that matter most are the question, the angle, the proof list and the review criteria, and those are the ones a reviewer should read first. Everything else can be short. A brief that fills every field with a paragraph is harder to use than one that fills the important fields precisely and leaves the rest to a line.
| Field | What goes here | Written in step |
|---|---|---|
| Goal and KPI | One business goal and the single measure that shows success | Goal and measure |
| Reader and stage | One reader described specifically; awareness, consideration or decision | Audience and stage |
| The question | In the reader's words, with the one-sentence answer beneath it | The question |
| Angle and promise | Why this piece from this organisation; what the reader can do afterwards | Angle and promise |
| Proof required | Claims to support, source for each, which still need research | Sources and proof |
| Outline | Section headings in order, one line each, fixed versus suggested | Outline |
| Format and length | Content type, length range, what to cut first, production needs | Format and length |
| Calls to action | Primary and secondary action, wording, destination, required links | Calls to action |
| Distribution notes | Channels, what each needs from the draft, owners, timing | Distribution notes |
| Review criteria and dates | Yes-or-no questions, reviewer per criterion, draft and review dates | Hand-off |
A brief for a payroll guide
A payroll software company has a calendar slot under its "first hire" pillar. The brief sets the goal as trial sign-ups from the page, with a target of 25 a month after three months. The reader is a founder about to pay a first employee, at the consideration stage, whose own words from support tickets are "I don't know what I'm supposed to deduct". The question is "What do I have to do to run payroll for my first employee?" and the angle is a checklist the support team already uses internally that no competitor has published. The proof list names four claims: the registration steps, the deductions involved, the filing deadlines and the penalties for missing them, each sourced to the official tax authority pages, plus a quote from the head of support. The outline has seven sections, the format is a tutorial of 1,800 to 2,200 words with a downloadable checklist, the primary call to action is the trial and the secondary is the checklist download, and the distribution notes ask for a 120-word newsletter summary and three standalone sections for short videos. Review criteria name the head of support for accuracy and the editor for structure, with the draft due in 10 days.
To save starting each brief from scratch, the content brief template gives you the sections described here in a ready-to-copy format that writers and editors can share.
If pieces still take weeks to reach publication once briefs are in place, the diagnosis for slow content production traces where drafts wait and separates review, planning and workflow causes.
Verify it worked
Hand the finished brief to someone who has not met the team, then check it against the steps.
- That reader can say who the piece is for, which question it answers and what the reader should do next.
- The brief names one goal and the single KPI that will show whether the piece worked.
- The question is in the reader's own words, with a one-sentence answer beneath it.
- Every claim in the proof list has a source or is marked as needing research.
- The review criteria are yes-or-no questions, each with a named reviewer and a date.
If it goes wrong
- The writer keeps asking what the piece is for. The goal or the reader is vague, or there are two of them. Cut to one of each.
- The answer will not fit in one sentence. The question is too broad or compound, so split it into two briefs.
- A central claim has no source. The proof list was skipped, so rewrite the claim as a labelled opinion or drop it.
- The piece reads like a sales page and converts nobody. The call to action came from the wrong stage, so match it to the reader's stage.
- The draft summarises what others have said. The angle is missing, so return to that step, or give the slot to a piece with an honest angle.
Next steps
- Read the SEO content brief guide once the general brief passes review, if search is a channel for the piece.
- Read the writing for the web guide before drafting, so the opening carries the promise and the point comes first.
- Revisit the audience research for content guide when the reader description rests on memory rather than quoted words.
Common mistakes
- Briefing a topic instead of a question. "Write about content measurement" produces a survey; "how do I show which content led to leads?" produces a piece someone needs. The question step exists to force that choice.
- Two goals, two audiences or two questions. Each doubling halves the piece. Split it into two briefs and two slots.
- Skipping the proof list. The writer discovers at draft stage that the central claim has no source, and the piece is rebuilt around whatever can be found.
- Writing the brief as a draft. A brief that contains the opening paragraph and half the argument leaves the writer transcribing rather than thinking, and the piece inherits the briefer's blind spots.
- A call to action from the wrong stage. Asking an awareness reader to book a call converts almost nobody and makes the piece read as a sales page.
- No review criteria or dates. Reviews that have no deadline happen last, and drafts wait for them; the calendar slips a week at a time.
- Losing the brief after publication. Refreshes then start from the published page, with no record of what it was meant to do; the production hub treats the brief as part of the asset, filed with it.
