Content workflow: what it is and how to design one for several clients

What is a content workflow

A content workflow is the set of steps a piece of content follows from idea to published and measured, with one person responsible for each step. For a video or social agency, the piece might be a short film, a carousel or a caption, and the steps are the ones your team already runs: brief, create, edit, review, client approval, schedule, publish.

It is made of stages, owners and the rules for moving between them. That separates it from a process, which can describe how a single task is done, and from a plain to-do list, which records tasks but not where a piece stands. A workflow answers two questions at any moment: where is this piece, and who has to act next?

It also differs from a content management system. A CMS stores and publishes content. The workflow is the agreement about who does what before anything reaches it, and it works the same whether the files sit in a CMS, a shared drive or a social scheduler.

The seven parts of a workflow

Seven parts cover it. When a workflow fails, one of them is usually missing or assumed.

Keep stages to the states that change who does the work. A status that changes neither the owner nor the next action can go. Several people can contribute to a stage, but one decides when it is done.

The handoff is where most of the value sits. The exit rule of one stage is the entry rule of the next, and both are written down once. The Kanban Guide asks for the same thing in its definition of workflow: explicit policies for how work items move through each state. "Edit complete, with a version number and a caption draft" is a rule. "Feels ready" is not.

The stages from idea to measurement

For agency client work, the stages below cover most pieces. Rename them to the words your team uses.

Most agency work needs all eight, because the client approval and the shared calendar are what separate it from in-house publishing. A solo creator with no client can merge brief and creation, and drop approval.

Task-based and status-based workflows

A task-based workflow moves through a list of jobs: write the brief, shoot, cut, check the caption. A status-based workflow moves the piece itself through named states, and each state tells you who owns it and what happens next.

For agency client work, use status-based stages for every client and keep task checklists inside the stages that need them, such as a caption check at review. The stages carry the handoff rules above, and the checklists stop small jobs being forgotten.

How an agency workflow differs from an in-house one

An in-house team has one brand, one set of approvers and one calendar. An agency has several of each, and the workflow has to keep them apart.

A client sign-off stage sits outside your team

In-house, approval usually means a manager down the corridor. In an agency, one stage belongs to someone who does not work for you. They may reply in a day or a week, and they judge the work against a brief they wrote months ago. Give that stage its own entry rule, exit rule and deadline, and decide in advance what silence means. How to run client review rounds without losing feedback covers the mechanics.

Brand rules belong to the client

Each client has its own tone, banned phrases, logo use, music licences and platform habits. Store them per client and name the stage that checks them, usually review or just before scheduling. Otherwise one client's rules get applied to another client's post.

One calendar answers for every client

An agency calendar has to show who has capacity, which client is waiting on you and which publish dates collide. Clients compete for the same editors and the same review slots, so separate calendars per client look organised until two of them need the same editor on the same Thursday. Building one content calendar that survives several clients sets out a layout that holds up.

Where workflows usually fail

• Too many stages. Fourteen stages look thorough and are rarely followed. People skip the ones that feel pointless, and the record then says a piece passed "Internal QA" when nobody looked. Start with the fewest stages that separate different owners, and add one only after a real mistake slipped between two existing ones.
• One word, two meanings. "In review" can mean the editor wants a look or that the client now holds the file. Define each stage by its exit condition in one sentence, then ask two people to explain it back. If the answers differ, the stage is not defined yet.
• Feedback stored in chat. Chat is a good place to discuss notes and a poor place to keep them. Decide where feedback is recorded at the review stage, and make that the only place it counts.

Write it down before you buy anything

A page or a sheet is enough. For each stage, write one row.

Then test it on live work. Walk three pieces, ideally across two clients, through the stages. Wherever you cannot name the owner or the condition that makes a stage done, the document is not finished. Run it for a full cycle, such as a month or one retainer period, before you judge it. Early changes usually fix a misunderstanding rather than a flaw in the design.

What software has to do for a content team

A board where cards drag between columns is not enough, because a document with the same stages does the same job. Software earns its place when it enforces the rules you wrote. Test a tool against four things:

• Files and versions stay with the stage. If the approved version goes out, the tool has to know which file that is.
• Feedback attaches to a version. A note on v2 must not look like a note on v3.
• Invalid states are refused. A piece should not be marked approved without a version, or scheduled without a channel and a time. A spreadsheet cannot enforce that.
• Clients stay separate but share one calendar. Permissions and brand rules per client, with every client's dates and every editor's load in one view.

Name the tool by what it is, not by brand. A shared calendar covers scheduling, a project board tracks tasks, a review tool holds versions and feedback, and a CMS publishes to a site. The question is whether one record ties them together or you reconcile four.

By team size, a solo editor with two or three clients can run on a sheet and a shared folder. A team of three to ten usually feels the strain at review and approval, so choose for versions and client sign-off first. Beyond that, calendar capacity across clients matters most.

With one client, a short list of stages and a clear owner, a shared folder may be all you need. Money and capacity sums often stay in a sheet even after the workflow moves, and when a spreadsheet stops working for video explains which parts outgrow one.

Questions people ask about content workflows