THE SHORT ANSWER
A content brief gives writers a workable assignment: whose question the piece answers, which evidence exists and what makes a draft useful. Resolve essential decisions before drafting. Research questions may remain open, but label them clearly. The brief then becomes a practical foundation for the work rather than a collection of keywords and stakeholder wishes.
To see how this step fits into your content strategy, read the pillar guide B2B content marketing: From useful expertise to qualified demand.
Specify the reader and task
Describe a concrete situation and the question that brings readers to the piece. Add their existing knowledge and the decision it should prepare. “IT decision makers” alone is insufficient. Initial orientation differs from guidance for assessing an offer. State what deliberately falls outside scope. If stakeholders name conflicting goals, settle priorities before drafting. Otherwise the manuscript must resolve a disagreement that actually requires an editorial decision, and even good writing will be judged against incompatible expectations. Explore this further in the guide Running content reviews that produce decisions instead of preferences.
Outline the answer and reasoning
Express the provisional answer in a few sentences, leaving it open to correction through research. Sketch necessary sections as reader questions or practical steps. Each needs a function: explain, compare, apply or establish a limit. A rigid contents list is optional; coherent reasoning is essential. Mark mandatory elements and areas of writer discretion. This preserves independence without losing the agreed purpose or important requirements, and prevents a suggested outline from being mistaken for verified conclusions before research has started.
Hand over evidence and gaps
Link relevant primary sources, interview notes and approved examples with short usage notes. Explain which statement each source supports and its limitations. An unexplained link collection transfers every research decision back to the writer. Mark missing evidence and name contacts. Numbers require origin and context; unverified internal assertions remain research leads. Separate company positions from questions requiring independent examination so the article does not disguise a predetermined opinion as a research finding or conceal uncertainty behind an authoritative tone.
Write a hypothetical assignment
Suppose the planned article covers preparation for a software pilot. It addresses project leads who already selected an application and should help them draft an initial evaluation plan. Required sections cover hypothesis, test data, responsibilities and stopping criteria. The sample is explicitly hypothetical. Current technical prerequisites remain unresolved, with a product contact assigned to verify them. This example creates a workable assignment without dictating every sentence or hiding unfinished research behind an outline that merely looks complete to someone reviewing the brief quickly. Explore this further in the guide Editorial approvals with clear responsibilities and bounded review.
Define delivery and acceptance
State format, language, publication context and supporting assets. Explain tone and terminology through examples rather than abstract adjectives such as “modern.” Identify who checks facts, language and publication readiness. Make deadlines and dependencies visible. If an interview arrives late, establish whether timing or scope changes. Choose a few acceptance criteria, such as answering the main question, labeling assumptions and providing an applicable example. These criteria should guide draft feedback rather than leaving reviewers to collect personal preferences that were never part of the original assignment.
Test the brief through discussion
Before work begins, ask the writer to repeat the goal, central argument and open tasks. Resolve different interpretations now. When research changes the situation, update the brief transparently and decide the effect on scope and timing. Return to it during acceptance: does the piece accomplish its task, and are deviations justified? A useful brief supports professional judgment. It should not become an unchangeable obligation to follow an outline that the evidence has since shown to be incomplete or fundamentally mistaken.
INTERACTIVE / FROM READING TO ACTION
Three checkpoints for your implementation
Choose a checkpoint and track your reading progress. Checks are neither saved nor sent and do not score your business.
CHECKPOINT 01
Hand over evidence and gaps
Link relevant primary sources, interview notes and approved examples with short usage notes.
Explore in the article ↗CHECKPOINT 02
Write a hypothetical assignment
Suppose the planned article covers preparation for a software pilot.
Explore in the article ↗CHECKPOINT 03
Define delivery and acceptance
State format, language, publication context and supporting assets.
Explore in the article ↗Frequently asked questions
Should the brief fix the headline?
A working hypothesis helps; the final title must match the researched content.
How detailed should the outline be?
Detailed enough to clarify reasoning and required elements without blocking sound editorial choices.
What should be excluded?
Unprioritized wishes, unsupported claims presented as facts and material without relevance notes.
How can I put “Specify the reader and task” into practice?
Describe a concrete situation and the question that brings readers to the piece. Add their existing knowledge and the decision it should prepare. “IT decision makers” alone is insufficient.
What matters when working on “Outline the answer and reasoning”?
Express the provisional answer in a few sentences, leaving it open to correction through research. Sketch necessary sections as reader questions or practical steps. Each needs a function: explain, compare, apply or establish a limit.
