A content calendar full of things that are 'nearly done'
The plan says two articles a month. In practice, one draft has been sitting with the technical director since the start of the quarter, another needs images, a third is approved but nobody has put it into WordPress. The marketing manager spends more time chasing than writing.
When a piece does get published, it has usually been through four versions in email attachments, with comments on the wrong one.
Case studies and service pages are worse. They need input from the person who did the work, a check from sales, sometimes sign-off from a director, and each of those people treats the request as the least urgent thing on their list. The piece is not blocked by any one person. It is blocked by the gaps between them.
Where the time actually goes
Writing is often the fastest part. The slow parts are the handoffs between people who have other jobs.
- Subject experts are asked to write or review in their spare time, which does not exist.
- Briefs are vague, so first drafts miss the point and need rewriting.
- Reviews happen by email attachment, so version control is guesswork.
- Nobody can see which piece is waiting on whom.
- Publishing needs formatting, images, meta descriptions and internal links, which is fiddly work that gets put off.
What slow content costs
Topics go stale before they are published. The expertise inside your business never reaches the website, so competitors with thinner knowledge but faster publishing rank above you. The marketing person becomes a project chaser, and experts learn to dread requests from marketing.
| Stage | Usual delay | What removes it |
|---|---|---|
| Expert input | Waiting for them to write | A short recorded interview instead |
| First draft | Vague brief, wrong angle | Structured brief from the interview |
| Review | Attachments and lost comments | One shared draft with a named reviewer |
| Publishing | Formatting and uploads | Push to CMS with fields filled |
The pipeline we build
- A content board (Airtable, Notion, Trello or a small app) where each piece has a stage, an owner and a due date, visible to everyone.
- Expert capture by short call or voice note, transcribed automatically, so the expert talks rather than writes.
- A draft produced from the transcript and brief by a model such as Anthropic Claude or OpenAI, written to your house style, clearly marked as a draft for a person to rework.
- Review routing: the piece goes to the right reviewer, reminders follow if it sits too long, and comments stay on one document.
- Pre-publish checks for missing meta descriptions, broken links, image alt text and heading structure.
- Publishing to WordPress, Webflow or your headless CMS through its API, with the fields filled from the draft, as a draft post for a final visual check.
The writer is still the writer. The pipeline removes the chasing and copying around them.
We keep the model's role narrow on purpose. It turns a rambling transcript into an ordered draft and fills in structural fields, which is the tedious bit. Facts, opinions and claims come from your expert and are checked by your reviewer, because a confident draft with a wrong detail in it is worse than no draft at all.
What the team notices
The expert gives a short interview instead of dreading a writing task. The marketer edits a draft that already contains the right material. Everyone can see where each piece is. When the reviewer is slow, the system reminds them, not the marketer. Finished pieces arrive in the CMS ready for a last look rather than as a Word document to be rebuilt.
Managers get something they rarely have: a view of how long each stage takes, so if reviews are always the slow step, that becomes a conversation about who reviews rather than a vague sense that content is slow.
Is this your content process?
- Pieces sit waiting for an expert for weeks.
- Drafts go back and forth as email attachments.
- Approved content waits to be uploaded.
- Nobody can say at a glance what stage each piece is at.
- The marketing lead spends more time chasing than creating.