If a writer keeps sending back an article that is on topic but still not what you asked for, the assignment probably left too much open to interpretation. This guide is for marketing leads who need to brief writers for articles, whether those writers are freelancers, people on your team, or an AI-assisted workflow. By the end you'll have a content brief process you can run in eight steps, and a first draft that lands close to what you pictured.
You don't need a long document for this. A good brief is short, and it answers the questions a writer would otherwise have to guess at. Guessing is where most of the rework comes from, so the steps below are all about making the important decisions visible before anyone starts drafting. A writer brief template can remind you which fields to fill in, but a template only holds the questions, and you still have to answer them for each article.
1. State the job this article must do
Start by writing down why the article exists. Put the business purpose on one line and the reader's outcome on another. The business purpose might be to help a defined buyer understand a problem, to support a decision, or to walk someone through a task. The reader outcome says what they'll know, decide, or do after reading. Pick one primary purpose, because a brief with five goals gives the writer five ways to go wrong.
Add the format you want and the action you'd like the reader to take, if there is one. If the article should end with an invitation to start a trial or read another page, say so in the brief and say where it belongs. A writer can't work out the conversion goal from a keyword.
You'll know this step is done when someone who didn't create the assignment can explain why the article exists, who it helps, and what the reader should be able to do afterward.
Common mistake. Writing a goal like "get traffic" or a subject like "write about content briefs." Traffic is a channel result, and a subject is only a topic. Neither one tells the writer what value the article has to deliver.
2. Describe the reader's starting point
Next, name the person the article is for. "Everyone interested in the topic" doesn't help a writer pick a level of depth, so describe a real segment instead. Say what role they have, what they already know, what they've probably read or tried, and what problem they're trying to solve. If there's a misconception or an objection the article should deal with, put that in as well.
A good test is whether the writer can picture one specific reader and choose the right vocabulary, examples, and next step without making up a persona. If you have worked out buyer personas already, pull the relevant details in, but tell the writer what that persona needs from this particular article. A persona name on its own is just a label.
Here is a simple way to check yourself. Ask what this reader already knows, what they need to believe or understand by the end, and what they would do next. If you can answer all three in a couple of sentences, the writer can too.
Common mistake. Handing over a demographic label or a keyword and expecting that to stand in for the audience. A keyword shows what someone typed, not who they are or what your business wants them to understand.
3. Check intent, demand, and existing coverage
If search is part of the goal, choose one primary query and treat it as the article's north star. Then describe the likely search intent in plain words, such as whether the searcher wants a definition, a how-to, or a comparison. Secondary terms can sit alongside it as supporting ideas, so the writer knows which concepts matter without repeating them like a checklist.
Take a few minutes to look at what's already ranking for the query. You're looking at the kind of answer and the format people are being offered, and at any questions the article should cover because they help the reader. Competitor pages can show you patterns in structure and depth, but they're reference points, not something to copy.
Then look at your own site. Make sure you don't already have a page that covers the same ground, and note any related pages that could shape the assignment. Finish by writing one sentence on what this article will add beyond a summary of what already ranks.
This is a place where tooling can save you time. DeepSmith's Content Map organizes your pages by topic and funnel stage, maps competitor sites onto the same topics, and shows you the coverage gaps and the topics competitors cover that you don't. Opportunity Agents return ideas with the data point behind each one. Both help you choose what to assign, and the brief still has to say what the article is for.
You'll know this step is done when the brief names the main query, explains what the searcher wants, points to existing coverage, and says what this page contributes.
Common mistake. Keyword dumping. A list of terms gives the writer vocabulary without explaining why the reader searched or what the page should do for them. Keyword density isn't a target worth setting, so don't turn the query terms into one.
4. Choose an angle and set the boundaries
The angle is the part most briefs skip. It's the editorial decision that makes the topic useful to this audience on your site, and it isn't the same thing as the topic, the keyword, or the headline. Ask what this article will say or do that a generic piece on the same subject wouldn't, and write that down in one or two sentences.
Then draw the edges. Decide which reader questions are essential, which are secondary, and what the article will leave out. Naming the adjacent subjects you don't want covered keeps the writer from stretching the assignment into a different article, which is a very common way for a draft to come back "on topic" but not what you meant.
Do this before you build the outline. If you pick headings first, you tend to end up with an orderly structure that has no point of view.
You'll know this step is done when the writer can describe the page's main point in their own words and can name at least one direction the brief rules out.
Common mistake. Sending only a topic and hoping the writer finds the argument you had in mind. A related one is a brief whose objective says one thing and whose outline says another, so the writer has to pick which one to follow.
5. Map the reader's journey through the article
Now give the writer a working title and a recommended structure. Use H2 and H3 headings where they help, and add a line on what each major section needs to accomplish. For a how-to, put the actions in the order the reader would do them. Mention any examples, steps, or questions that have to be covered, and mark the sections that are optional. Moz has a useful walkthrough on writing an SEO content brief if you want a second view on structure.
You usually don't need a full heading-by-heading script. A skeleton outline is often enough, and it leaves an experienced writer room to use their judgment. A more detailed outline can make sense for a newer freelancer who needs a precise assignment. If the topic is question-driven, it also helps to build the structure around the questions readers ask so the headings match how people look for the answer.
Give a word-count range only when there's a real scope or publishing reason for one. Length is a planning aid, and it's one more thing to decide when you brief writers for articles. There's no universal word count that search engines prefer, and an arbitrary target mostly encourages padding.
You'll know this step is done when the section order follows the reader's task, every required heading has a clear job, and nothing is in the outline only because a keyword needed a home.
Common mistake. Going to either extreme. A bare list of headings leaves the writer guessing what to say under each one, and a script that prescribes every paragraph removes the judgment you hired them for.
6. Supply evidence, source material, and access to expertise
A writer can only be as accurate as the material you give them. Gather the approved internal facts, the research you want used, product or subject-matter context, examples, interview notes, and any sources you prefer. Say which claims need evidence and what kind of evidence counts. Separate verified facts from opinions and from open questions, and if an important fact isn't available, label it unknown instead of asking the writer to fill in the gap.
It also helps to decide what original value the piece can add. That might be first-hand experience, your own data, a useful example, or a more complete explanation than a basic summary would give. Google's guidance on people-first content asks the same kind of questions, such as whether a page offers original information, substantial coverage, and real expertise, and it warns against content that only summarizes what others have said. Those are good editorial questions to ask even though they don't promise a ranking. If your drafts tend to read as thin, a guide on how to add original insight to a draft shows what that looks like in practice.
Tell the writer who can answer subject-matter questions and when to stop and ask instead of guessing. Content Marketing Institute's 2025 B2B research reports that 81% of B2B marketers' teams used generative AI tools, up from 72% the year before, so there's a fair chance some of your drafts already involve an AI tool. If you're working with an AI-assisted writer, say plainly that company and product claims must not be invented, and that a person will check anything that needs editorial or market judgment.
You'll know this step is done when the brief tells the writer what evidence is available, what still has to be found or confirmed, and what to do when an answer is missing.
Common mistake. Asking for authority without giving access to anyone who has it. Another one is treating a polished draft as proof that its facts are right, since good prose can sit on top of a wrong claim.
7. Make voice, constraints, and logistics usable
Voice instructions fail when they're only adjectives. "Clear, helpful, and human" could describe almost anything, so pair each quality with an example of what it looks like in a real sentence. It's even better to include a short approved paragraph, or a before-and-after, so the writer can see the difference. If you haven't put your standards in writing yet, it's worth taking time to document your brand voice once so you can reuse it. HubSpot's piece on brand voice is a decent place to see examples of how teams describe theirs.
Then separate your hard requirements from your preferences. Hard requirements might be a section that has to appear, a claim that must be avoided, a product detail that has to stay exact, or a format rule. Preferences are the things a writer can reasonably decide for themselves. When everything is marked as required, the writer can't tell which items matter.
Add the practical parts too: any metadata or formatting you need, whether a visual is wanted, the deadline, who reviews the draft, and how the writer should raise a blocker. For a search-focused piece, give the primary query and the supporting concepts, and say whether things like question-style headings or a table would help this article. Don't hand over an unprioritized keyword list or ask for a density target.
This is another step where stored context can take weight off you. DeepSmith's Deep IQ holds your company positioning, products and claims, buyer personas, brand voice, visual guidance, and content types, so every article it produces starts from the same shared context. That keeps the voice and the product facts consistent, but it doesn't replace the angle, evidence, and scope for the specific piece, which you still have to decide.
You'll know this step is done when the writer can tell what's required from what's preferred, can find the context they need, and knows the deadline and who reviews the work.
Common mistake. A long list of SEO instructions. It can distract the writer from the reader and push them toward robotic writing, so keep the list to what actually changes the article.
8. Run a preflight check and agree on the finish line
Think of this as the last stage of your content brief process. Before you send the brief, read it as if you'd never heard the assignment explained out loud. Check that the audience is specific, the angle is clear, the outline follows the reader's task, the evidence is either on hand or marked as missing, and no two instructions contradict each other. Confirm the deadline, the reviewer, and the call to action if there is one. Then invite the writer to flag any big ambiguity before they begin, because a question now costs far less than a rewrite later.
Next, write acceptance criteria in terms of the assignment. These are the reader outcome, the required topics, the evidence and accuracy standard, the scope, the voice, and any hard format rules. When the draft arrives, you review it against those criteria and not against a feeling. If you change the direction after sending the brief, call it a change in assignment so it doesn't get treated as the writer missing the original instructions. A simple scoring rubric can make that review quicker and more even from one article to the next.
Once the draft is in, take a minute to record why revisions were needed. Sort them into missing brief information, execution errors, late changes, and personal preference. Over a few articles you'll see which gaps keep recurring, and fixing those is better than making every brief longer. You can also track a few simple team measures, such as how many revision rounds came from mismatched expectations, how long it took to get from brief to accepted draft, and whether the essentials showed up in the first draft. These are your own diagnostics and not industry benchmarks, and a good brief won't remove revisions entirely.
When you're ready to turn this into something repeatable, a content briefing system is the natural next move. If you want to look at the production side, the way to design a content production workflow covers how briefs fit into the larger pipeline. And on DeepSmith, Content Studio's Writer takes a planned idea and produces a researched, brand-grounded article with links, a cover image, and publish-ready metadata, which you then review and publish from Produced Content.
You'll know this step is done when a second person can read the brief and explain what a successful draft looks like, and the writer knows where to ask before making a consequential assumption.
Pro tip. Ask the writer to tell you, in a few sentences, who they think the reader is, what angle they're taking, and what counts as success. If their version differs from yours, fix the brief while the mismatch is still cheap to correct.
What to do next
Take one article you have coming up and run it through the eight steps before you assign it. Keep the brief to what the writer would otherwise have to guess, and at the end save a note on which parts you had to think hardest about, because those are the parts a vague brief would have left to chance.
If you'd like to see what producing articles from your own context looks like, you can start a free DeepSmith trial and run your first idea through the Writer.
