Brief to publish: a content workflow that holds

A content workflow that holds under calendar pressure defines its decision points before production starts. Who approves the brief? What does the review cover? Who signs off before publish? Teams that answer those questions in advance move pieces through the pipeline without stopping at each stage. Teams that don't make those calls on every piece — which is how calendar pressure becomes quality compromise.

The brief: the decision that makes every other decision faster

A brief that specifies the specific claim, the primary audience, and the voice register eliminates the most common review feedback: the draft isn't arguing anything specific, or it doesn't sound like the brand. When the brief is approved before production starts, the review pass covers execution — did the draft deliver on the brief? — not direction.

A review that's relitigating direction is a review that's filling the gap the brief left. Once the brief is written, it should be signed off before any drafting begins — not adjusted during the production session.

Brief approval is the highest-value checkpoint in the workflow. Build it in explicitly: the brief gets reviewed and approved before production starts. The person who writes the draft and the person who reviews it should agree on what the piece is supposed to argue before the first word is written.

The production session: what AI handles and what it doesn't

With a sharp brief in place, the production session is execution: translating the specific claim into a draft that argues it. AI drafts the structure and builds the piece section by section. What AI doesn't supply is the brief's content — the claim, the voice register, the link targets. Those come from the person who knows the content program.

The production session should be bounded: one session per piece, brief in hand, with a clear done-condition. A session that starts without a brief or without a clear done-condition tends to run long and produce something that needs structural revision.

Copper Sun's modules hold the brand voice, the current messaging framework, and the relevant project context so the production brief doesn't have to recreate the starting conditions from scratch. The session starts with consistent context regardless of who's running it. See how it works.

The review pass: what to check, in what order, in how much time

The review pass has one job: verify that the draft delivered what the brief specified. Not revise the brief. Not apply new strategic direction that wasn't in the brief. Verify execution against what was already approved.

A useful review structure covers three checks: does the draft make the specific claim from the brief, is the voice consistent with the brand, and are the required internal links present? Argument comes first. Voice and links follow. The sequence matters because structural problems require more revision time than voice drift.

Time-boxing the review pass helps. A first-pass review that runs longer than 30 minutes for a 1,500-word piece is usually finding problems the brief should have prevented. If revision cycles are long, look upstream — the brief probably isn't sharp enough to produce a draft that doesn't need structural work.

Approval and publish: who signs off and when

Approval is a handoff, not a second full review. By the time a piece reaches approval, it's been reviewed against the brief and revisions are complete. The approval step confirms the piece is ready to publish — not another editorial pass.

Who signs off matters. For a solo or two-person team, approval and publish may be the same person and the same step. For a larger team, one person approves. The rest review. Establishing that before calendar pressure sets in prevents approval from becoming another full review cycle.

A production schedule coordinates the steps. Brief approved Monday. Production Tuesday. Review Wednesday. Approval and publish Thursday. When each step has a time box, the workflow is a system rather than a series of one-off negotiations.

What to document when the workflow works

When a content workflow produces good pieces on schedule, the instinct is to move on. The instinct should be to write down what made it work: what the brief looked like, what the review checklist covered, what done meant for this format.

Documentation isn't bureaucracy — it's what makes the workflow repeatable when a contributor is new, when a format changes, or when the team is under pressure. A brief template that's written down gets used consistently. A review checklist that's written down gets applied without the lead present.

For the broader content operations context: content operations and AI workflow. For the editorial calendar that runs the production schedule: running an editorial calendar when the team uses AI. For quality consistency across contributors: managing content quality when everyone uses AI. For briefing AI effectively: how to brief an AI.

Frequently Asked Questions

What does a content production workflow include?

A content production workflow covers four stages. The brief defines the specific claim and the voice register before drafting begins. Production executes against the approved brief. Review checks whether execution matched the brief — claim made, voice consistent, links in place. Approval confirms the piece is ready to publish.

How do I create a content publishing process?

Start with the brief. Write down what every brief for this content type should include: the specific claim, the primary audience, and the voice register. Then define what the review covers and who conducts it. Then define who approves and when. Document each decision as you make it. A publishing process built from actual production experience is more durable than one designed in the abstract.

How do I document a content workflow?

Document the decisions that have to be made at each stage, not just the steps. Who approves the brief? What does the review checklist cover? What does done mean for this format? Those decisions, written down and tested against a few production cycles, are the workflow documentation worth having. Steps without decisions are a checklist that still requires judgment on every piece.

What are the steps from idea to published content?

Content moves from approved brief through production and review to publish. The brief specifies what to argue and for whom. Production executes it. Review checks whether the draft delivered. Each stage has a defined output that becomes the next stage's input — the approved brief enters production, the draft enters review, the final piece publishes. What would otherwise be per-piece judgment calls are captured in the brief template and the review checklist.