Content creation workflow for agencies, step by step

A content creation workflow is the path a piece of content takes from the moment someone asks for it to the moment it's live and reported on: the steps, the order they run in, who does each one, and what counts as done.

When we read the top search results for "content creation workflow" on October 1, 2026, most were written for one company's marketing team, with one brand voice and one person who signs off. An agency runs the same steps for every client at once, and each client brings its own voice, its own approver and its own idea of done. That changes where the process breaks.

This guide covers the eight stages, who owns each one in a small agency, the client file every stage should read from, and a worked example that shows where the time actually goes. We make GoMimic, which covers two of the stages (client sign-off, and turning a published post into each client's other formats), so weigh what we say about it accordingly. Outside sources are linked where they're used and were checked on October 1, 2026.

The short version

• There are eight stages: take the request, write the brief, draft, edit and check, get the client's approval, publish, distribute and report.
• Give every stage one owner and a plain test for done, so a handoff is a status change rather than a meeting.
• Keep one file per client that every stage reads: how they sound, what they can't say, who approves and how many rounds are included.
• The work is usually quick and the waits are slow. Count the days a post sits untouched, not only the hours spent writing it.
• Publishing isn't the end. Put distribution and the report in the same process, or they happen only when someone remembers.

The eight stages

Each stage below says what happens, who usually owns it and how you know it's finished.

1. Take the request

Requests arrive by email, on a call, in a chat thread, or as a comment on last month's report. When each client's requests come in a different way, some get lost, and nobody notices until the client asks where the post is.

Pick one place per client where a request becomes real, usually a task in your project tool, and have the account manager move anything that arrives elsewhere into it.

Done when the request names the client, the topic, the date it's needed and the person who will approve it.

2. Write the brief

The brief tells the writer what to write and why. For a search-led post it usually holds the target keyword and the intent behind it, the angle, the reader, a few subtopics and the internal links to include.

Keep it short and in the same shape every time, so a writer who has never worked on this client can pick it up. What it shouldn't hold is everything about the client. How they sound and what they can't say belong in the client file, which the brief points to rather than repeats. Briefs that restate the voice each time drift apart, and the newest one wins by accident.

Done when the writer can start without asking a question.

3. Draft

The writer drafts against the brief and the client file. If your writers use an AI assistant for part of this, Google doesn't object to that in itself. Its guidance on AI content (updated December 10, 2025) asks you to "focus on accuracy, quality, and relevance", and warns that using such tools to turn out many pages that add nothing for readers can break its spam policy on scaled content abuse.

There's a second reason to keep a person in the draft, and it matters to anyone handing work to a client. In January 2025 the US Copyright Office concluded that copyright doesn't extend to material made purely by AI, or where a person had too little control over what the tool wrote (Copyright and Artificial Intelligence, Part 2). The same report says a person's own expression, and their creative selection, arrangement or changes, can still be protected, and that each case is decided on its facts. If your contract says the client owns what you deliver, ask your lawyer what that covers when a tool did some of the writing.

Done when the draft is complete and every fact and figure in it has a source noted beside it.

4. Edit and check

The editor reads the draft against the brief and the client file. A note like "this client never opens with a question, see their file" belongs in the edit. "I'd put it differently" usually doesn't, because it's the editor's taste rather than the client's.

Then the facts. Every number, quote and claim about another company should trace back to a source the editor has actually opened. Google's helpful content guidance suggests telling readers how a piece was made, so a line saying how a claim was checked helps the reader as well as the client.

Done when the editor would be comfortable with the client's most careful reader seeing it.

5. Get the client's approval

This is where a post tends to wait longest. A draft can sit with a client for a week without anyone disagreeing with it, simply because nobody has opened it.

Four things shorten the wait. Name one approver and a backup. Agree how many days they have. Agree how many rounds of changes are included. And make saying yes take as little effort as possible: a link they can open on a phone, not an attachment they have to download and mark up. Our guide to getting client sign-off has messages you can copy for each step, including what to send when a client goes quiet.

Done when the named approver has said yes, and the yes is somewhere other than one person's inbox.

6. Publish

This is usually the most settled stage. The post goes into the client's CMS with a checklist: the title tag and meta description, the URL, internal links, image alt text, the author and the category.

If your agency doesn't have publishing access, this stage is a handoff to the client's team, and it isn't finished until you've seen the post live.

Done when the post is live and someone has opened the live URL.

7. Distribute

One published post becomes the other pieces that client uses: a LinkedIn post, a newsletter section, an X thread, whatever their audience reads. Our content repurposing examples show what each kind of post can turn into.

This is the stage that's easiest to skip, because it has no natural owner. The writer has moved on to the next brief and the account manager is chasing an approval. If nobody owns it, it happens for the clients who ask and not for the ones who don't. Our guide to building a content distribution system goes through it in detail.

Done when every format the client uses has been written from the post, approved, and handed to whoever schedules it.

8. Report

The report shows the client what went live, where, what they approved, and how it performed. It's also the stage that justifies the retainer, so it shouldn't depend on someone rebuilding the month from chat threads.

Done when the client can see what went out without having to ask.

Who owns each stage

In a small agency, five roles can cover the eight stages. One person often holds two of them, which is fine as long as nobody edits their own draft: the editor's job is to catch what the writer can't see.

Notice how many stages land on the account manager. That's normal, and it's also why distribution and reporting slip first: they sit at the end of the busiest person's list.

The client file every stage reads

Every stage above refers back to one thing: what you know about this client. When that lives in one person's head, every holiday and every resignation puts it at risk. When it lives in five places, the places disagree.

Keep one file per client, and have every brief, draft and edit point to it. It should hold:

• How they sound, shown with a few of their own sentences rather than described with adjectives.
• Words they use and words they never use.
• What they can't say: claims their industry restricts, competitors they won't name, offers that have ended.
• Who approves, the backup, and how long they usually take.
• How many rounds of changes are included.
• Which formats and channels they use after a post goes live.
• Links to their best past posts, the ones they'd show a new writer.

The file goes stale unless something keeps it current. A simple rule helps: when a client makes the same change twice, it becomes a line in their file. If they delete "game-changing" from two drafts in a row, write it down, and the third draft won't need the edit.

A worked example: one post, thirteen days

Here is an invented agency to show where the time goes. Six people run content for ten clients. One of them is a dental practice that wants a post on choosing a family dentist. Counted in working days:

• Day 1. The request comes in on a call. The account manager logs it with the topic, the due date and the approver, the practice manager. 10 minutes.
• Day 2. The SEO lead writes the brief. 45 minutes.
• Days 3 and 4. The writer drafts it. 3 hours.
• Day 5. The editor edits and checks it, and the account manager sends it to the practice manager. 1 hour.
• Days 6 to 9. Nothing happens. The draft is with the client.
• Day 10. The practice manager asks for two changes. The writer makes them and it goes back. 30 minutes.
• Day 11. Waiting again.
• Day 12. Approved.
• Day 13. The account manager publishes it and checks the live page. 20 minutes.

That's under six hours of work spread across 13 working days. On five of those days nobody touched the post, because it was sitting with the client. Then the distribution pieces were written by hand three days after the post went live, because that stage had no owner.

Faster writing wouldn't have changed much here: drafting was two of the 13 days. What would have changed it is in the stages around the writing:

• An approver and a review window agreed when the client signed, and kept in the client file.
• An approval the practice manager could give from a link on her phone, instead of a document to download.
• Distribution as part of publishing, done the same day, with one named owner.

Mistakes to avoid

• Treating publish as the finish line. The post is live, but the pieces that bring readers to it haven't been written.
• Restating the voice in every brief. Write it once, in the client file, and point to it.
• Editing to taste. An edit should point to the brief, the client file or a fact. Otherwise it's a preference, and the client may not share it.
• Sending drafts as attachments. Two versions in two inboxes means nobody is sure which one was approved.
• Handoffs with no owner. Every gap between two stages is where a post waits. Name who moves it on.
• Measuring only how fast you write. Track how long posts wait with the client, too, and you'll see which clients need a different arrangement.

Running it for many clients

The stages don't change from one client to the next. The client file does. That's what lets a writer move between accounts without a long handover, and it's why a process that works for three clients can still work for fifteen.

A few habits help once the roster grows:

• One board, a column per stage, a card per post. Tag each card with its client. A glance shows where posts are piling up. If your agency looks like the example above, it will be the client approval column.
• Batch by stage. Write the week's briefs in one sitting and do the edits in another, so each person stays in one kind of work for a stretch.
• Flag posts that have waited too long. A post that has been with a client for longer than their agreed window gets a nudge that day, not at the end of the month.
• Keep the record per client. What was published, what was approved and when should be findable by client, so the monthly report is a lookup rather than a reconstruction.

Where GoMimic fits

We make GoMimic for two of these stages: distribution, and the client's sign-off on what comes out of it. It's client-aware content distribution software for small agencies, and it starts the moment a client's post is published.

You set up a client once. GoMimic learns how they write from their published posts, and a writing trait only counts once it shows up in three of them. It learns only from their real writing, never from its own drafts, and it gets more accurate every time you use it, per client. Paste a published post and get the formats you picked for that client back in under 60 seconds, in their voice. Or connect the client's blog feed, and new posts arrive as drafts on their own.

Your client approves content with one click. No login required. Every post, asset and approval stays on that client's record, so your team never has to rebuild a client's voice from scratch.

Where it falls short:

• It turns a published post, or a short brief, into that client's formats. It won't write the client's blog post.
• It isn't a project tool, so you still need a board for the first six stages.
• It doesn't schedule or post to social channels. Approved assets can go to Slack or Google Drive, or by webhook to Zapier and on to Buffer or whichever scheduler you use.
• The voice builds over several posts, so a new client's first drafts need more editing.

Flat agency pricing. Not per seat. Not per client. Pro covers up to seven clients and Agency covers unlimited clients. There's a 7-day trial with no card, and before that you can try it with a real client post, no account needed.

Follow GoMimic on LinkedIn