Most content programmes don’t fail on writing quality. They fail because nobody knows what to write next, briefs are a sentence long, approvals stall, and three months later the plan is a spreadsheet nobody has opened. This service builds the system that stops that happening.
Content programmes rarely fail on writing quality. They fail because nobody knows what is next and the approvals stall.
What a content pipeline is
The process that takes a topic from idea to published page, with each step defined and each handover written down. What gets written, who briefs it, what the brief contains, who writes it, who checks the facts, who approves it, and what happens to it after publication.
It’s unglamorous and it’s the difference between a content programme that runs and one that stops in month three.
Who it’s for
This suits businesses producing content regularly:
- teams with more than one writer, internal or freelance
- businesses where content sits waiting for approval
- anyone whose content quality varies depending on who wrote it
- marketing teams inheriting a programme with no documentation
The problems it usually solves
Nobody knows what’s next. Without a maintained plan, topic selection happens in a meeting each month and drifts toward whatever someone thought of recently.
Briefs that are a title and a word count. A writer given that produces a generic article, and it isn’t their fault. A brief has to carry the search, the angle, the sources, the internal links and what the piece must not say.
The approval queue is the real bottleneck. On one client programme I worked on, well over a hundred finished pieces were waiting for sign-off. Commissioning more writing wouldn’t have helped anything. The constraint was approval, and the plan had to be sequenced around content dependencies rather than around production capacity.
Quality varies by writer. Without a written standard, every writer applies their own, and the site reads like it was written by six people because it was.
Published and forgotten. No refresh cycle, so the library ages quietly and declines all at once.
What’s included
- A topic plan built from search demand, commercial value and what you already have
- A brief template, with a worked example for each content type you produce
- Written standards: voice, structure, sourcing, linking and what’s banned
- A workflow with each step and owner defined, including approvals
- A tracker showing what’s planned, written, waiting and live
- A fact-checking standard, including what counts as an acceptable source
- A refresh cycle, so published content gets revisited rather than abandoned
- Handover and training, so your team runs it
What goes in a brief
| Section | What it carries |
|---|---|
| The search | The question, the intent behind it, and the demand |
| The angle | What this piece says that the ranking pages don’t |
| Required points | What must be covered for the piece to be complete |
| Sources | Primary sources to use, and what not to cite |
| Internal links | Which pages to link to, and why |
| Voice notes | Anything specific to this piece |
| Exclusions | Claims not to make, competitors not to name, figures needing confirmation |
The exclusions row is the one most briefs miss, and it saves the most rework.
Sequencing around the real constraint
A content plan should be ordered by dependency, not by ambition. If a hub page has to exist before the pages beneath it make sense, the hub comes first. If approvals are the bottleneck, the plan sequences around what can actually get through rather than around how fast writing can be produced.
Building a plan that ignores the actual constraint produces a document that looks impressive and doesn’t survive contact with the month.
What you get
- A maintained topic plan, in priority order
- Brief templates with worked examples
- A written content standard
- A tracker your team keeps current
- A documented workflow, including who approves what
Limitations
A pipeline can’t create capacity. If there’s no one to write and no budget for writers, a better process makes that clearer rather than solving it. It also depends on someone owning it, and the tracker going stale is the most common failure.
What this won’t solve
A process doesn’t make weak content strong. It makes good content repeatable and stops the obvious failures, and the expertise still has to come from somewhere.
Talk to the person doing the work
There is no account manager here and no team to be handed to. If you get in touch, it is me who reads it, me who looks at your site, and me who does the work if we go ahead.
Get in touch, or start with a free assessment.
Engagement and price
There are no list prices here, and that is deliberate. What a piece of work costs depends on the state of the site, how much of it there is and what you actually need, none of which I know before looking at it.
So it starts with a free analysis. I look at your site, your Search Console and who you are really competing with, then come back with what I would do first and what it would cost to do. No obligation attached, and if the honest answer is that you do not need me yet, I will say so.
How the work gets done
Topic plans are built through the strategy planner, with existing content assessed through content quality scoring and performance from the crawl and data integrations. This service sits under content, and pairs with blog and article writing and content refreshes.
FAQ
What should a content brief contain?
The search and the intent behind it, the angle that makes this piece different from what ranks, the points it must cover, the sources to use, the internal links, and the things not to say. That last part saves the most rework and is the part most briefs leave out.
We already have a content plan. Why isn’t it working?
Usually because it’s ordered by ambition rather than by dependency, or because it ignores the real bottleneck. If finished pieces are sitting waiting for approval, producing more writing won’t help, and the plan needs sequencing around what can actually get through.
Can you run the pipeline as well as build it?
Yes, though the aim is usually to hand it over so your team owns it. Which makes more sense depends on whether you have someone with the time to maintain the plan and the tracker, since those going stale is the most common way this fails.
How do you keep quality consistent across writers?
A written standard covering voice, structure, sourcing and linking, plus briefs detailed enough that a writer isn’t guessing. Without both, every writer applies their own judgement, and a site with six writers reads like it was written by six people.
Get a system that survives a busy month
Get in touch, or start with a free assessment, which includes a look at your current content operation.