Content ops: the editorial calendar that survives contact

Every content team has two calendars. There's the one in the spreadsheet — colour-coded, ambitious, quietly fictional — and the one in everyone's head, which says "we publish when someone finishes something." The gap between them is where quality goes to die: rushed drafts, skipped edits, pieces published at 6pm on a Friday because the calendar said so, and a growing pile of "almost done" Google Docs nobody will ever open again.

The fix isn't a better spreadsheet. It's a system with honest capacity math, briefs that do the arguing upfront, and refresh loops that treat the archive as an asset. This is how we run our own journal, and how we set up client teams on growth engagements where content has to survive the departure of the agency that started it.

Start with capacity, not ambition

The single most common content-ops failure is a calendar divorced from arithmetic. Someone declares "two posts a week" because that sounds like a serious cadence, and three months later the well is dry and the last four posts were filler that actively damaged the brand.

Do the sums once, honestly:

Hours per piece, fully loaded. A good 1,500-word article is not "a day". It's research (2–4 hours), drafting (4–6), editing (2), art or diagrams (2), subject-matter review (1), and publish mechanics (1). Call it 12–16 hours of other people's jobs, which means calendar time is two to three weeks even when everyone is responsive.
Available hours per week. A team with one half-time writer and a borrowed engineer-reviewer has perhaps 25 editorial hours a week.
The answer. That's two strong pieces a month, not two a week.

A calendar built on real capacity has a magical property: it survives contact with reality. A calendar built on aspiration produces exactly one thing reliably — guilt. Publish monthly, forever, and you beat the team that published weekly for four months and vanished. Search engines and readers both reward clusters that compound, and compounding requires continuity, not intensity.

The pipeline: five states, four handoffs

We run every piece through five states, with a named owner per state. Anyone can see, at a glance, where work is stuck:

Idea — a one-line pitch in a shared backlog. Anyone on the team contributes; nobody is obligated. Ideas are free and should be.
Briefed — the idea has a one-page brief (below). Owner: the editor. This is the gate where most ideas die, by design.
Drafting — assigned to a writer with a due date derived from real capacity, not hope.
In review — subject-matter check and edit, in parallel, with a hard SLA.
Scheduled — final art, meta, internal links, and a publication date on the actual calendar.

Two rules make the pipeline work. WIP limits: at most two pieces in Drafting per writer, ever. A third assignment waits. Work-in-progress is where deadlines go to die, and WIP limits force the honest conversation early. Age limits: anything sitting in one state beyond its SLA (two weeks for drafting, five working days for review) gets flagged in the weekly stand-up — not to shame anyone, but because stuck work signals a bad brief or a capacity lie, and both are fixable only if visible.

The brief that prevents the rewrite

Nearly every painful rewrite we've ever witnessed traces back to a vague brief. "Write something about accessibility" produces a draft, three rounds of contradictory feedback, and a writer who quietly resigns inside. Our brief template is one page and non-negotiable:

The reader, specifically. Not "marketers" — "a performance marketer at a DTC brand who has been asked to 'do content' and has no writers." Everything follows from this.
The job the piece does. One sentence: "After reading, they can run a refresh audit on their archive this week." If you can't write this sentence, the idea isn't ready.
The argument. Three bullet points the piece commits to. Reviewers disagree with the brief, in writing, before a draft exists — not with the draft, in comments, after a week of work.
The evidence kit. The examples, data, screenshots and internal war stories the writer must include. This is where institutional knowledge gets harvested, and it's why our pieces sound like us rather than like the internet.
Search intent and the one query it must deserve. What's the searcher actually trying to do, and why is this the best answer on the web? "Why is this the best answer" is a brutal question that kills half of all briefs. Good. They died cheap.
Non-goals. What the piece will not cover. Content bloat is a brief problem.

Total time to write a good brief: 45 minutes. Total time it saves: four to eight hours of circular editing, every single time.

Review with roles, not audiences

Review collapses when everyone reviews everything. Split it:

The subject-matter check (30 minutes, one expert): is anything wrong, missing, or dangerous? Comments limited to facts. Taste is not invited.
The edit (one editor, full pass): structure, voice, length, honesty. The editor is accountable for the published piece sounding like the brand.

That's it. Two reviewers. The CEO gets the piece when it's live, like everyone else — if leadership needs veto rights, they exercise them at the brief stage where vetoing is cheap. Teams that let stakeholders discover content at the draft stage are running a consensus machine, not an editorial operation, and the output always reads like the committee it came from.

The refresh loop: your archive is the product

New pieces get the attention; old pieces get the traffic. A post published two years ago often outranks and out-earns everything you shipped this quarter — until the screenshots go stale, a stat ages out, and it quietly slides down the results page taking your pipeline with it.

So the calendar has a third lane alongside new work and promotion: refresh. The mechanics:

Every piece gets a review-by date at publication — 12 months for evergreen process pieces, 6 months for anything touching tools, platforms or regulations.
Quarterly, pull the twenty pages with the most non-brand organic traffic and the twenty with the steepest year-over-year decline. That's your refresh queue, ordered by money at stake.
A refresh is scoped like new work but costs a third of it: verify claims, update examples, tighten the intro, improve internal links to your newer work, and only republish the date if the substance genuinely changed.

Teams running a refresh loop routinely get more growth from 200 old pages than from their next 20 new ones. It's also the honest way to honour the reader who bookmarked you.

Cadence is a promise, so promise small

The calendar itself, once the system exists, is almost boring: one strong piece every two weeks, one refresh per week, one promotional beat per piece across lifecycle email and social, everything visible in one board, reviewed for twenty minutes each week. Boring is the point. Ambition belongs in the quality of the work, not the fantasy of the schedule.

If this sounds like how we run client work generally — small batches, visible pipeline, honesty about capacity — it is. It's the same approach, applied to words.

Key takeaways

Build the calendar from capacity math: fully-loaded hours per piece ÷ honest weekly hours. Two great pieces a month beats the heroic schedule that collapses.
Five pipeline states, named owners, WIP limits, and age limits that surface stuck work.
The one-page brief — reader, job, argument, evidence kit, intent, non-goals — is where disagreements should happen, because that's where they're cheap.
Review with exactly two roles: subject-matter check and edit. Stakeholders weigh in at the brief.
The refresh loop is the highest-ROI lane in the whole system; date every piece at publication.
Cadence is a promise to the reader. Promise small, keep it forever.

FAQ

What tooling do we need? A board with five columns and a calendar view. Linear, Notion, a spreadsheet, index cards — genuinely doesn't matter. What matters is that status is visible to everyone without asking, and that SLAs are written next to the states. Tool migrations are the most popular way to avoid doing content ops.

How do we handle content from leadership or other teams? Thank them, and route it through the same pipeline with the same brief and edit. The pipeline isn't bureaucracy — it's the mechanism that makes "we publish good things" independent of who had the idea. The editor's job is to make everyone sound like the brand at its best, including the founder.

We're a team of one. Does any of this apply? Especially then. Capacity math stops you over-promising; the brief stops you rewriting your own drafts in circles; the review-by dates stop your archive rotting while you chase the new. Shrink the SLAs, keep the states.

How do we know if a piece worked? Decide at the brief stage: a piece either serves discovery (rankings, non-brand traffic), trust (reply rates, demo-call mentions, sales enablement use), or both. Judge discovery pieces at 90 days, trust pieces by what humans say to you. A piece judged on the wrong axis looks like a failure while quietly doing its job.

What do we do with pieces that will never rank? If they serve sales or onboarding, keep and link them generously — not everything needs to rank. If they serve nobody and embarrass you, prune them; redirect what's worth saving. A smaller, better archive beats a larger, indexed museum of 2019.