
A brief is a thinking tool, not a planning document. The distinction matters because it changes what you put in one. A planning document contains everything relevant to the project — timelines, resource links, publishing checklist, SEO keywords. A thinking tool contains only what you need to make a decision or execute a task. A brief that includes everything is a brief nobody reads.
The best brief for a YouTube video is about 200 words. The best brief for a 2,000-word newsletter essay is about 150. These numbers feel uncomfortably short to most people who've worked in content marketing, where briefs are routinely four pages and cover 23 variables. That level of detail is appropriate when briefing an external writer who knows nothing about your brand. It's inappropriate when briefing yourself, your editor, or a VA who's been working with you for six months.
The six elements that actually matter in a brief
Working title. One sentence that tells you what this piece is — not what you aspire it to become, but what it actually is right now. "Why YouTube's new monetisation rules hurt mid-tier creators most" is a working title. "YouTube monetisation 2025" is a topic, not a title.
The central claim. One sentence stating the argument or insight the piece makes. Not the topic — the take. "YouTube's new monetisation threshold affects creators with 50K–500K subscribers disproportionately because they're above monetisation entry requirements but below the point where alternative revenue streams compensate." That's a claim. "YouTube monetisation is changing" is an observation with no claim.
The intended reader. One sentence describing specifically who you're writing for. "A YouTube creator with 80K subscribers who has hit monetisation thresholds but isn't earning enough from ads to justify the effort" is an intended reader. "Content creators" is not.
The format. Is this a how-to guide, an opinion piece, a case study, an explainer, a list, or a personal narrative? Format shapes structure, length, and tone. Deciding format at the brief stage prevents a rewrite at the draft stage.
Three to five section headings. A draft outline, not a final structure. These exist to check that the central claim can actually be supported across an article's worth of content. If you can't generate five section headings, the claim might not have enough substance yet.
One specific example or source. Name one real thing: a company, a study, a specific event, a named person. This anchors the piece in reality and prevents the generic slide that happens when you're writing from memory without any concrete referent. "Nielsen's Q3 2024 Creator Economy Report" or "what happened to MKBHD's channel in September" are anchors. "According to experts" is not.
What to leave out
Target word count. This is a planning document detail, not a thinking document detail. Word count determines file size; it doesn't determine quality or structure. Optimise for covering the claim adequately, and let length follow from that.
SEO keywords list. Keyword research belongs in the research phase, not the brief. Adding a keyword list to a brief trains you and your collaborators to optimise for the keyword before the argument is developed — which is how you end up with keyword-stuffed content that makes no interesting claim.
Publication checklist. The brief is for thinking, not production management. Checklists belong in your content management system, not your thinking document.
Audience persona documents. These are reference materials, not working materials. If your brief requires someone to consult a separate persona document before they can interpret it, the brief is too abstract. The intended reader description in the brief should be self-contained.
How Deaku's briefing engine fits into this
Deaku generates briefs automatically when you enter a topic into the Idea Inbox and click "Brief." The output includes all six elements above: a working title, a central claim, an intended reader profile (based on your connected channel data), a format suggestion, five section headings, and a sourcing note for one relevant data point or example.
The generated brief is a first draft to edit, not a final document to accept. The working title usually needs sharpening. The section headings are often too generic and need to be made more specific to your take. The format suggestion is right about 70% of the time. The intended reader profile improves noticeably after the engine has processed several weeks of your actual published content.
The generation takes 20–50ms. The editing takes 3–5 minutes. The combined time for brief creation is roughly a quarter of writing one from scratch. That efficiency matters most on the ideas you're less certain about — AI generation makes it worth briefing an uncertain idea, which you might otherwise skip. Some of those uncertain ideas, once briefed, turn out to be the best pieces.
Briefs as a team alignment tool
When you're working with a collaborator — a VA, an editor, a co-creator — the brief serves a second function beyond thinking tool: it's a shared reference that both people have approved before work begins. A 200-word brief that both parties have agreed on eliminates an entire category of revision: the "this isn't what I meant" revision.
The most common source of rework in creator workflows is misaligned interpretation of a vague brief or no brief at all. A VA who starts research without a brief will often research the wrong angle. An editor who starts revisions without a brief will often optimise for the wrong reader. Twenty minutes of brief review before execution saves two hours of correction afterwards. The math is clear even if the habit takes discipline to build.
The brief review habit: two minutes before you start writing
Before you open a draft, read the brief. Out loud if you have to. Check that the central claim still feels true — ideas sometimes clarify (or deteriorate) between brief and execution. If the claim has shifted, update the brief before you write. It takes 90 seconds. It means you're writing toward a clear destination rather than discovering one mid-draft.
The brief is the contract you write with yourself before you start. The more specific it is, the less time you spend wandering during execution. That discipline — clear thinking before production — is the whole game.