Commissioning at Scale: How to Brief Writers Without Losing Consistency

The moment you move from managing one writer to managing ten, everything breaks. Not because the writers are worse—they're not. It breaks because the thing that held consistency together was you, sitting in every conversation, making the same judgment calls in real time. Scale removes you from that position. And most teams never recover.

The instinct is to solve this with documentation. More detailed briefs. Longer style guides. Stricter templates. The logic is sound: if you write down the rules precisely enough, consistency will follow. In practice, this creates a different problem. Writers stop thinking. They optimize for compliance instead of clarity. Your output becomes technically consistent and editorially dead.

The real issue isn't that you need better instructions. It's that you've confused consistency with uniformity, and you're trying to enforce the second when you actually need the first.

Consistency in editorial work means something specific: every piece reflects the same underlying judgment about what matters, what's true, and what's worth saying. It's not about word choice or tone markers or whether you use Oxford commas. Those are surface-level. A writer who understands your editorial philosophy can break your style guide and still sound like you. A writer who doesn't understand it will follow every rule and sound like someone else entirely.

The teams that scale without losing voice do something different. They commission around a principle, not a prescription.

Start by identifying the one thing that actually matters about how your brand thinks. Not your values statement—that's too abstract to be useful. Something more specific. Maybe it's that you refuse to use jargon as a substitute for explanation. Maybe it's that you always lead with what's changing, not what's staying the same. Maybe it's that you treat your reader as someone with limited time but genuine curiosity. This becomes your north star. Everything else—the tone, the structure, the depth—flows from this.

When you brief a writer, lead with this principle. Not as a rule. As context. "We're commissioning this because we think most coverage of this topic mistakes complexity for depth. We want to show that it's actually simple—and that matters." Now the writer knows what success looks like. They're not filling a template. They're solving a problem.

The second move is to commission in conversation, not in documents. A brief should be a dialogue. You ask the writer what they think the story is. You listen for whether they've understood the principle. You push back if they're heading toward the obvious take. This takes time upfront, but it compresses everything downstream. Revisions become minor. Fact-checking becomes faster. You're not rewriting—you're refining.

Third, build feedback loops that reinforce principle over prescription. When you give notes, connect them back to the underlying editorial judgment. "This paragraph feels like it's explaining the mechanism when we agreed the story was about why it matters to people" is different from "This is too technical." One teaches. The other just corrects.

The teams that maintain voice at scale also do something counterintuitive: they hire for judgment, not for experience. A writer who's worked at five publications has internalized five different editorial philosophies. They're slower to adopt yours. Someone earlier in their career, with strong critical thinking but no institutional baggage, learns your principle faster and applies it more consistently.

Finally, accept that some inconsistency is the price of scale. If you have ten writers, they will sound slightly different. That's not failure. That's diversity of thought within a coherent framework. The alternative—total uniformity—requires either total control or total mediocrity. You can't have both scale and voice and perfection. Pick two.

The teams winning at this have made a choice: they're optimizing for editorial consistency, not operational consistency. They've built systems that scale judgment, not just output. It's harder than writing a longer style guide. But it's the only way to grow without disappearing.