Ask five content leads how their team gets an article from idea to published and you will get five different answers. One runs everything through a single managing editor. Another has a board with columns that writers pull work from. A third has three reviewers looking at the same draft at once because legal, product and brand all need a say.
None of them is wrong. They are just different shapes of the same thing: a way of deciding who touches a piece of content, in what order, and what has to be true before it moves on.
Most advice on this topic stops at a generic list of stages. That is useful, but it does not show you what a working process actually looks like inside a real team, or why a team chose that shape over another. The editorial workflow examples below do. Each one is a pattern you can recognise, copy, or combine, with notes on who it suits and where it tends to crack.
If you are still getting your head around the basics, start with what an editorial workflow is and why it matters, then come back here to pick a model.
How to Read These Examples
Every example below is described in the same way, so you can compare them side by side:
- The flow: the stages a piece moves through.
- Who it suits: the team size, content type and pace it fits best.
- Why it works: the problem this shape solves.
- Where it cracks: the failure you should watch for.
These are organisational models, not templates for a specific type of company. If you want ready-made stage lists for a startup blog, a SaaS marketing team, an agency or an enterprise, the editorial workflow template guide covers those. This article is about the structure underneath: how the work is routed and who holds it at each point.
1. The Linear Relay
The flow: Idea, brief, draft, edit, approve, publish. One stage at a time, one owner at a time, like a baton being passed.
Who it suits: Small teams of two to six people publishing a few pieces a week, where the same editor reviews almost everything.
Why it works: It is easy to understand and easy to explain to a new freelancer. At any moment, exactly one person is responsible for a piece. There is no debate about whose turn it is, because the baton is either in your hand or it is not.
Where it cracks: Every handoff is a place for work to wait. When the editor is on holiday, nothing moves. As volume grows, the relay turns into a queue in front of one person, and the team starts quietly skipping stages to keep up.
The fix is usually not to abandon the relay but to give every stage a backup owner and a rough time limit. A relay with a deputy editor and a "two working days in review" expectation can carry a team much further than people expect.
2. The Kanban Pull Board
The flow: A board with columns such as Ideas, Ready to Write, Writing, In Review, Ready to Publish and Published. Writers and editors pull the next card when they have capacity, instead of having work pushed onto them.
Who it suits: Teams with a steady stream of evergreen or SEO content and several writers working in parallel.
Why it works: The board makes the whole pipeline visible in one glance. You can see that six pieces are piling up in review while nothing is ready to write, and that tells you where to put attention this week. Pull-based work also reduces the "I was assigned four things on Monday and finished none of them" problem.
Where it cracks: Boards fill up. Without a limit on how many cards can sit in each column, "In Review" becomes a parking lot. Cards also lose context when the brief, the draft and the feedback all live somewhere else.
Teams that make this model work set a work-in-progress limit for each column (for example, no more than five pieces in review at once) and keep the brief and comments attached to the card itself.
3. The Newsroom Desk
The flow: Pitch, assigning editor accepts or rejects, assignment with deadline, draft, desk edit, copy edit, publish. A central desk controls what gets commissioned and in what order.
Who it suits: Digital publications, editorial brands and content teams that publish daily or react to news and trends.
Why it works: Decisions about what to cover sit with one accountable person or a small group. That protects the publication's standards and its schedule at the same time. Writers know exactly who to pitch to and who to ask about a deadline.
Where it cracks: The desk becomes a bottleneck when it also tries to do every edit. It can also become a black box for writers: pitches go in and nobody hears back.
Strong desks separate commissioning from editing, so the assigning editor decides what gets made and other editors handle the line work. They also give every pitch a visible status so contributors are not left guessing.
4. The Topic Pod
The flow: The team splits into small pods, each owning a topic cluster or product area. Each pod has its own writer, editor and subject expert and runs its own short relay from brief to publish.
Who it suits: Mid-sized and larger teams covering several distinct subjects, such as a SaaS company with separate product lines or a publication with clear sections.
Why it works: Pods build depth. The same people keep working on the same subject, so briefs get sharper, reviews get faster and internal linking inside a topic cluster becomes natural. It also spreads review load so one central editor is not reading everything.
Where it cracks: Pods drift apart. One pod's "ready for review" means something different from another's, and the brand voice starts to vary between sections. Shared assets such as design and SEO can get pulled in several directions at once.
Teams running pods usually keep a thin layer of shared rules on top: one definition of done for each stage, one style guide, and a regular cross-pod review of what was published.
5. The Hub and Spoke Contributor Model
The flow: A central editor or small core team (the hub) briefs and edits work from many outside contributors (the spokes): freelancers, subject matter experts, customers or guest authors. Brief, contributor draft, hub edit, expert check, approve, publish.
Who it suits: Teams that rely on expertise they do not have in-house, such as B2B companies writing technical content or publications with a large freelance network.
Why it works: The hub protects quality and consistency while the spokes bring knowledge and volume. A small core team can publish far more than it could write itself.
Where it cracks: Contributor drafts vary wildly. Without a strong brief, the hub spends its week rewriting. Experts also tend to be slow reviewers, because reviewing is not their real job.
The best version of this model invests heavily in the brief: audience, angle, structure, examples to include and a clear word count. It also asks experts for something narrow ("check these three claims") instead of "have a look when you can."
6. The Parallel Review Workflow
The flow: Draft, editorial review, then legal, compliance, product and brand reviews running at the same time instead of one after another, followed by a single consolidated approval and publish.
Who it suits: Regulated industries, enterprise teams and any content where several departments genuinely need to sign off: finance, healthcare, security, or product launch content.
Why it works: Sequential reviews multiply waiting time. If four reviewers each take three days in a row, a piece waits close to two weeks. Running them in parallel collapses that into the time of the slowest reviewer, and it surfaces conflicting feedback in one round instead of four.
Where it cracks: Reviewers contradict each other and nobody has the authority to decide. The writer ends up stuck between legal asking for a caveat and brand asking for a shorter sentence.
Parallel review only works with a named final approver who resolves conflicts, and a clear scope for each reviewer. The content approval workflow guide goes deeper into setting up approvers and sign-off rules for this kind of team.
7. The Tiered Fast Lane
The flow: Every piece is sorted at the brief stage into a lane. Low-risk content (a minor update, a social cut, a refresh of an existing article) takes a short path: draft, edit, publish. High-stakes content (a new pillar page, anything with legal claims, a launch) takes the full path with specialist reviews and approval.
Who it suits: Almost any team past the early stage, especially those combining new content with ongoing updates and refreshes.
Why it works: Most workflows fail because they treat every piece the same. A typo fix should not wait in the same queue as a product launch. A tiered model protects reviewers' time for the work that actually needs it and keeps routine publishing moving.
Where it cracks: Everything slowly drifts into the full lane, because nobody wants to be the person who skipped a review. Or the opposite happens, and risky pieces get waved through the fast lane under deadline pressure.
The tiers need written criteria that anyone can apply, such as "makes a claim about pricing, security or legal terms" or "new page versus update to an existing one," and the person writing the brief chooses the lane. Once the criteria are stable, routing each lane to the right reviewers is a good candidate for editorial workflow automation, so nobody has to remember who reviews what.
Comparing the Seven Models
Here is the short version of when each editorial workflow example fits:
- Linear relay: small team, one editor, modest volume.
- Kanban pull board: several writers, steady evergreen or SEO pipeline.
- Newsroom desk: high frequency, strong central editorial judgment.
- Topic pod: several distinct subjects, mid-sized or larger team.
- Hub and spoke: outside contributors and subject experts doing the writing.
- Parallel review: multiple departments must sign off.
- Tiered fast lane: a mix of routine updates and high-stakes pieces.
Most Teams Combine Two or Three Models
In practice, the cleanest processes are hybrids. A SaaS content team might run a kanban board for its blog, a tiered lane system to keep refreshes moving, and parallel review only for launch content. A publication might use a newsroom desk for commissioning and topic pods for the actual production.
The question is not "which example is right for us?" but "where does our work actually get stuck, and which pattern removes that friction?" A team whose problem is visibility needs a board. A team whose problem is slow sign-off needs parallel review or tiers. A team whose problem is weak drafts needs stronger briefs and the hub and spoke discipline, whatever its structure looks like.
Whatever you choose, write it down. A model that only lives in the managing editor's head is not a workflow. If you are setting up the process for the first time, the guide on how to build an editorial workflow for a growing publication walks through roles, stages and approvals step by step.
How to Choose Your Starting Model
If you are deciding where to begin, work through these questions in order:
- How many people touch a typical piece? Two or three suggests a relay. Five or more suggests a board or pods.
- Who does the writing? In-house writers fit a board or pods. Mostly outside contributors fit hub and spoke.
- How many sign-offs are truly required? One editor is a relay or board. Several departments means parallel review.
- How varied is your content? If updates and launches share one queue, add tiers.
- Where did your last three delayed articles get stuck? Design the model around that stage first.
Then run it for a month before adding anything. Most teams overbuild in the first week and spend the next quarter removing steps nobody follows.
Making the Model Visible
Whichever shape you pick, the same thing decides whether it survives: can everyone see where each piece is and who holds it right now? Once a team relies on a spreadsheet, a doc folder and a chat channel at the same time, every model above starts to fail in the same way.
That is where the way you manage the workflow day to day matters as much as the model. Status, owners, deadlines and feedback need to sit in one place. Narranta was built for exactly this: one workspace where each article moves through your own stages, with its owner, reviewers and comments attached, so the model you designed on paper is the one your team actually runs.
Frequently Asked Questions
What is an example of an editorial workflow?
A simple example is a linear relay: idea, brief, draft, edit, approval and publish, with one named owner at each stage. Larger teams often use a kanban board, a newsroom desk, topic pods or parallel reviews instead, depending on volume and how many people need to sign off.
Which editorial workflow model is best for a small team?
For most teams under six people, a linear relay or a simple kanban board is enough. Add a backup owner for each stage and a rough time limit for reviews before you add any new stages.
What is the difference between an editorial workflow example and a template?
An example shows how a team routes work and who holds it at each point. A template is a reusable list of stages and owners you copy into your own process. Examples help you choose the shape; templates help you fill it in.
Can a team use more than one workflow model?
Yes, and most mature teams do. A common combination is a board for everyday content, a fast lane for updates and refreshes, and a parallel review path for launch or regulated content.
How do I know my current workflow model is not working?
Look at where your last few delayed pieces got stuck. If they waited in front of one person, the model is too centralised. If nobody knew who owned them, the model lacks clear handoffs. If they waited for several reviewers in a row, move those reviews into parallel.
Choosing the Shape That Fits Your Team
The seven editorial workflow examples here are not a ladder you need to climb. A relay is not a beginner's version of a pod. Each solves a specific problem, and the right one is the one that removes the friction your team feels most often.
Pick the model that matches how your team works today, write it down, and make it visible. If you want a single place to run it, with stages, owners and reviews built in, you can set up your team's workspace in Narranta and map your chosen model in an afternoon.