Whether your writer is a person or a model, the quality of what comes out is decided almost entirely by what goes in. A weak brief cannot produce a strong page, no matter how good the writer is. At scale this becomes the highest leverage point in the whole operation: improve the brief and you improve every page it touches, all at once. Briefing the writer agent well is the difference between a factory that produces authority and one that produces filler.
It is the input discipline that makes the rest of building a content factory work.
The brief is a contract, not a suggestion
We treat the brief as a contract the page must fulfil. It is not a loose prompt to inspire the writer, it is a specification that defines what a correct page looks like. If the brief is complete, the draft is checkable against it. If the brief is vague, there is nothing to check against and quality becomes a matter of opinion, which does not scale.
The rule is simple and absolute: no brief, no build. A page does not enter the writing stage until its brief is complete. This feels slow the first time and saves enormous rework forever after, because a good brief stops the most common failure at scale, which is producing a fluent, well written page that answers the wrong question.
What a complete brief contains
Every brief carries the same core fields, because consistency in the input is what produces consistency in the output.
- One keyword. The single primary term the page targets. One keyword to one page, never two pages chasing the same term and never one page hedging across three.
- One intent. What the searcher actually wants: a definition, a how to, a comparison, a decision. The whole page serves that one intent.
- One reader. Who this is for, named concretely. A first time venue owner and a seasoned operator need different depth and different language.
- The answer shape. What the forty to sixty word opening answer must cover, so the page wins the snippet.
- Required links. The pillar to link up to, the siblings to link across to, and a group page where natural. Specifying these in the brief is how we avoid orphan pages and link dumps.
- The proof point. The named framework or directional figure the page should stand on, drawn from real, defensible ground.
- The house rules. The voice fingerprint and the hard rules, including no hyphen used as a dash and no em dash, carried in full.
That last block is why briefing and prompting overlap so heavily. The brief inherits from system prompts that hold quality, so the writer never has to guess the rules. The standing rules live in the prompt, the page specific instructions live in the brief, and together they fully constrain the output.
Research belongs in the brief, not the draft
The worst time to discover you lack the facts is halfway through writing. A complete brief includes the verified research the page will be built on, gathered and checked first. This is the principle behind research before writing: separate finding the truth from phrasing it well, because doing both at once is where errors creep in. The writer's job is then to express verified material in our voice, not to invent or half remember it.
This separation also protects accuracy. When research is done up front and recorded, the fact check at the gate is verifying against a known source rather than trying to reconstruct where a claim came from. It makes the whole chain auditable.
Specific beats long
A common mistake is to think a better brief is a longer brief. It is not. A brief padded with generic guidance the writer already knows just buries the parts that matter. The best briefs are short and sharp: the specific keyword, the specific intent, the specific links, the specific proof. Everything generic lives in the standing prompt, so the brief only carries what is unique to this page. Specificity is what makes a brief useful. Volume just makes it ignored.
Briefs make output reviewable
A precise brief does not only improve the draft, it makes the review meaningful. When the gate can hold the page against a concrete contract, the question stops being "is this good" and becomes "does this meet the brief". That is a far more reliable check, and it is one a second person or a system can perform consistently. The brief is what turns subjective editing into objective verification, which is the only kind of review that survives at a thousand pages.
Different page types need different brief templates
One brief template cannot serve every kind of page. A glossary definition, a deep pillar, a how to and a case study each answer a different shape of question, and forcing them through identical instructions produces pages that are technically complete and quietly wrong for the job. So we keep a small family of brief templates, one per content type, all inheriting the same standing rules but differing in what they ask the writer to deliver.
A pillar brief, for example, demands breadth: the subtopics it must cover, the siblings it must link down to, the proof point it must anchor. A glossary brief demands the opposite, a tight definition and a single clean example, with strict limits on length so it does not bloat into a mini pillar. A case study brief leans on a real, careful narrative and forbids inventing numbers. The fields are mostly shared, but the emphasis shifts, and that shift is what makes each page fit its slot in the cluster.
Keeping the family small matters as much as having it. Five templates that everyone knows beat fifteen that nobody can remember. We resist the urge to spawn a new template for every minor variation, because the value of templates is consistency, and consistency dies when there are too many of them to hold in mind. A few well chosen shapes cover almost everything a knowledge library needs.
Improving the brief improves everything
Because every page flows from a brief, the brief template is the highest leverage document in the operation. When we notice a recurring weakness across drafts, a flat opening, a missing link pattern, a weak proof, we almost never fix it page by page. We fix the brief template, and the next hundred pages improve at the source. This is the same compounding logic we apply across the group in our building thesis: invest in the system that produces the work, not just the work.
For how briefing sits beside pipeline management, voice and quality control, the content operations pillar ties the inputs to the outputs. Get the brief right and most of the battle for quality is already won before anyone writes a word.
The KHG Brief Contract: every writer brief names one keyword, one intent, one reader and the required links and proof before a single word is written. No brief, no build.
Common questions
What makes a brief good?
Specificity, not length. One keyword, one intent, one named reader, the required links and the proof point, with all generic guidance left in the standing prompt. A short, precise brief beats a long, padded one.
Should research happen before or during writing?
Before. Gather and verify the facts in the brief, then let the writer express them in voice. Doing research and drafting at once is where errors and unsupported claims creep in.