How to Commission Content So It Actually Gets Approved First Draft

Most content briefs fail before the writer ever opens a blank document.

The problem isn't the writer. It's that the brief itself contains hidden assumptions—about tone, structure, evidence standards, and what "done" actually means—that only become visible when the first draft lands and someone says "this isn't what we wanted." Then comes the revision cycle. Then another. The piece that should have taken two weeks takes six, and everyone involved feels like they've failed.

The real failure happened earlier, in the commission phase, when nobody articulated what success looked like in language precise enough to be actionable.

The thing everyone gets wrong: Treating briefs like job descriptions

Most editorial teams write briefs the way HR writes job specs—with a list of requirements and a hope that the right person will intuitively understand the gaps. "Write 1,200 words on content strategy trends. Target: marketing directors. Tone: authoritative but accessible."

This is a job description. It is not a brief.

A job description tells someone what to do. A brief tells someone what to think about before they do it. The difference matters enormously when you're paying for intellectual work.

When you hand a writer a requirements list, you're asking them to make dozens of micro-decisions in isolation: Which trends? How recent? How much space for each? Should we cite studies or use observation? Is "accessible" conversational or just jargon-light? Should the opening be a question, a statement, or a provocation?

Each decision is a fork in the road. The writer picks a path. You wanted a different one. Revision.

Why this matters more than you think

Every revision cycle costs time and money, yes. But it also costs something harder to measure: institutional knowledge about what your content actually is.

When your first drafts consistently need heavy revision, one of three things is happening. Either your writers aren't good (possible, but usually not the issue). Or your briefs are vague (almost always true). Or there's a mismatch between what your team thinks the content should be and what it actually needs to be (common, and fixable).

The third one is the dangerous one. It means your editorial operation isn't aligned on fundamentals. Different stakeholders have different mental models of the content. They're not communicating those models to writers. Writers are guessing. Drafts fail. Everyone blames the writer.

After this happens three or four times, you stop getting first-draft approvals not because your writers got worse, but because they learned to hedge. They write defensively. They include everything. They avoid strong positions. The content becomes safer and blander.

What actually changes when you brief properly

A precise brief does three things simultaneously: it constrains the writer's choices, it surfaces disagreement before writing starts, and it creates a shared reference point for evaluation.

Start by being specific about what you're not doing. "This is not a how-to guide. It's not a product comparison. It's not a trend forecast." Negative space is easier to agree on than positive space.

Then specify the argument. Not the topic—the argument. "The argument is that most teams misunderstand what content operations actually requires. The piece should show why that misunderstanding is costly, then reframe the problem." Now the writer knows what they're building toward.

Specify the evidence standard. "We're using observation and industry pattern-matching, not citing studies. If you need a statistic, it should be real and attributed." This prevents the writer from padding with invented numbers or spending hours hunting citations you never wanted.

Specify the structure. Not as a rigid outline, but as a skeleton: "Opening hook, three sections building the argument, closing that reframes the problem." This gives the writer a container without dictating every paragraph.

Specify the tone by example, not adjective. Don't say "authoritative but accessible." Show them a paragraph from a piece you loved. Say "like this."

When you do this, something shifts. Writers stop guessing. They write with confidence. Stakeholders see the draft and recognize it immediately—it's what they were imagining all along. Approval happens on first submission.

This isn't magic. It's just the difference between a brief and a wish.