Last updated: October 2026

Workflow & Analytics

Content Approval Workflow: Steps, Roles and a Free Template

Five steps to get content from draft to published with a clear owner at every stage, plus a template you can copy today.

Everything you need to master this in 2026.

Why it matters

Approvals protect quality, but a slow process kills velocity. A good workflow makes every decision explicit, short and recorded, so content moves quickly without anything going out unreviewed.

Actionable framework

Name the roles

One creator, one reviewer and one approver per account or client. The approver is a single person with a named backup, so a decision never waits on a group chat.

Define the stages

Draft, in review, changes requested, approved, scheduled, published, with rejected as the exit. Make one rule absolute: nothing is scheduled until its status is approved.

Set deadlines and escalation

Give reviewers and approvers 24 to 48 hours, cap review at two rounds, and decide in advance who steps in when someone is out. An unapproved post should miss its slot rather than go out unreviewed.

Review against a checklist

Voice, facts, links, media, platform fit, compliance and call to action. A fixed checklist makes feedback specific and keeps reviews short.

Record the decision and audit weekly

Log who decided, when, and why for every change request or rejection. Once a week, look at rejection reasons and time to decision, then remove the approval step that adds the least.

What a content approval workflow is

A content approval workflow is the set of rules that decides what happens to a piece of content between "someone wrote it" and "it is live". It answers five questions: who drafts, who reviews, who has the final say, how a change is requested, and what is allowed to be scheduled. If any of those answers lives only in someone's head, you have a habit, not a workflow.

The purpose is not to add steps. It is to make each decision explicit, short and recorded, so content moves quickly without anything going out unreviewed. A good workflow is one the team forgets about because it keeps working. A bad one is the reason a calendar goes empty in the week the approver is on holiday.

This guide covers the general process, whatever tool you use: stages, who does what, suggested turnaround times, message templates, a checklist you can print, and the ways workflows usually fail. If your question is specifically about getting clients to sign off on posts, that has its own page: the social media approval workflow, and the agency version lives on Bolta for agencies.

The six stages, and what each one is for

Not every team needs all six, and small teams often merge two of them. What matters is that each stage has one owner, a clear way in, and a clear way out. Start with this version and remove what you do not need.

1. Brief

Owner: Strategist or account lead

Decide what the post is for before anyone writes it: the audience, the single point, the call to action and the platform. Most late rejections are really brief problems, where the draft answered a question nobody asked.

Comes in: A slot on the calendar and a topic or goal.
Goes out: A one to three line brief the creator can write from without a meeting.

Watch for: Skipping this stage for routine posts is fine. Skipping it for campaign posts is how you get five drafts that all miss the same point.

2. Draft

Owner: Creator

Produce the post, with media attached and the link in place, in the format the platform needs. The creator self-checks against the checklist before submitting, so reviewers do not spend their time on typos.

Comes in: An approved brief.
Goes out: A complete post, not a rough idea: copy, media, link, alt text and proposed publish time.

Watch for: Half-finished drafts sent for review train reviewers to skim. Send it only when you would be comfortable seeing it published as is.

3. Internal review

Owner: Editor or second pair of eyes

Catch what the creator cannot see: voice drift, factual slips, broken links, wrong tags, an off-brand image. This is the stage that protects the client from your mistakes, so it comes before the client sees anything.

Comes in: A complete draft that passed the creator's self-check.
Goes out: Either 'passes to approver' or 'changes requested' with specific, checkable comments.

Watch for: Comments like 'make it punchier' send the creator guessing. Ask for a change a person can verify as done.

4. Approval

Owner: Approver (one named person, plus a backup)

A single yes or no on whether this goes out under the brand's name. For agencies this is usually the client; for in-house teams it is the brand or marketing lead; for solo creators it is you, on purpose, after a gap.

Comes in: A post that passed internal review, shown in the form it will publish.
Goes out: Approved, changes requested, or rejected, with a reason.

Watch for: If approval can be given by 'whoever sees it first', nobody owns the decision. Name the person.

5. Schedule

Owner: Publisher or scheduler

Put the approved version in the queue at its slot. The publisher does not edit content. If the copy needs to change, it goes back a stage.

Comes in: Approved status on the exact version being scheduled.
Goes out: Scheduled for a specific account, date and time.

Watch for: The common leak is an edit after approval. Treat any change to copy, media or link as a new version that needs a fresh yes.

6. Publish and review

Owner: Scheduler, then account lead

Confirm the post went out as approved, then record what happened. Once a week, read the rejection reasons and time to decision, and remove the stage that is adding delay without catching problems.

Comes in: A scheduled post reaching its time.
Goes out: Published, plus a line in the weekly audit if anything was rejected or late.

Watch for: A workflow nobody audits only gets slower. Look at it weekly for a month, then monthly.

Pick a path for your team

The same six stages compress or expand with the size of the team and the cost of a mistake. These four setups cover most cases.

Solo creator

Draft, wait, self-review against the checklist, schedule.

You hold every role, so the main control is time. Write today, review tomorrow. The checklist does the job a second person would do.

Small in-house team (2 to 5)

Draft, peer review, lead approves, schedule.

One reviewer and one approver is enough. Name the backup so a vacation does not stop the calendar.

Agency with clients

Draft, internal review, client approval, schedule.

Two distinct stages: your team catches its own mistakes first, then the client decides. Keep the client's step as short as possible: what to look at, what they can do, by when.

Regulated or high-risk

Draft, editor, compliance gate on flagged posts, approver, schedule.

Add compliance as a gate triggered by rules (claims, health, finance, legal), not as a step on every post. Keep a record of who approved what.

One more rule applies to all of them: tier the process by risk. A holiday greeting does not need the path a product launch needs. If every post gets the full treatment, reviewers learn to approve without reading, which is worse than having no review at all.

Roles matrix: who drafts, reviews, approves

This is general best practice, not a description of any one product. The principle behind it is separation: the person who wrote a post should not be the only person who checks it, and the person who schedules should not be the person who can change it.

Role	Drafts	Reviews	Approves	Schedules	Notes
Creator	Yes	Self-check only	No	No	Owns the first draft and the revisions. Does not approve their own work on a client account.
Editor	Occasionally	Yes	No	No	Checks voice, facts and format. Should not also be the person who wrote the draft.
Approver	No	Final look	Yes	No	One named person per account, with a backup. Holds the final yes.
Legal or compliance	No	Only flagged posts	Gate, not owner	No	Brought in by rule (claims, regulated topics, giveaways), not for every post.
Scheduler	No	Checks time, account, link	No	Yes	Schedules approved versions only. Cannot change the copy.
Solo creator	Yes	Yes, after a gap	Yes	Yes	Holds every role, so build in a delay: write today, review tomorrow, with the checklist open.

Three details are worth deciding up front. First, the approver is a person, not a group. Several people can review, but one person says yes, because a group decision tends to arrive after the slot has passed. Second, the backup approver has the same authority as the approver while covering. A backup who can only forward the message is not a backup. Third, compliance or legal review is a gate triggered by a rule, such as health claims, financial statements or contest rules, not a step every post passes through.

For a solo creator the matrix collapses into one person, and the thing you replace is the second pair of eyes. A gap of even a few hours between writing and reviewing catches a surprising share of errors, and the checklist below stands in for the reviewer.

Turnaround targets (suggestions)

These are starting points, not rules or industry benchmarks. Set yours from how quickly your own content has to move. A news-driven account may need hours; a monthly thought-leadership calendar can afford days.

Stage	Suggested target	Why
Brief to first draft	1 business day for a single post, 3 for a campaign set	Long enough to write well, short enough that the brief is still fresh.
Internal review	Same business day, or within 24 hours	Internal reviewers are on the same team, so there is no good reason for this to sit.
Approver decision	24 to 48 hours	Fast enough to keep a weekly calendar moving, with room for a busy day.
Revision after changes requested	Within 24 hours	Comments lose context quickly. The creator should still remember what the post was for.
Maximum review rounds	2, then a short call	A third round of comments almost always means the brief or the roles are unclear.
Lead time before publish	Approved at least 24 hours before the slot	Leaves time for one fix without a scramble.

Targets only work with a consequence attached. Write down what happens when one is missed: a reminder at the halfway point, then the backup approver at the deadline, then the post misses its slot. That last step matters most. If an unapproved post goes out anyway because the slot arrived, the approval stage is decorative.

Measure two numbers once a week: time from submission to decision, and how many posts needed more than one round. If the first is long, the problem is usually the approver's load or an unclear deadline. If the second is high, the problem is usually the brief.

Stage templates you can copy

Most delay in an approval process comes from missing information at a handoff: the reviewer does not know the deadline, the approver does not know what a good answer looks like. These five short messages fix that. Paste them into whatever you use.

Brief

Account lead to creator

Post: [topic or working title]
Account and platform: [account], [platform]
Goal: [one outcome, such as sign-ups, replies or awareness of X]
Audience: [who this is for]
Key point: [one sentence]
Must include: [link, offer, hashtag, tag]
Must avoid: [claims, competitors, topics]
Draft due: [date]   Slot: [date and time]

Submit for review

Creator to editor

Ready for review: [post name]
Checked against the checklist: yes
Anything I am unsure about: [one line, or "nothing"]
Media: [attached, alt text added]
Link: [checked and loads]
Proposed slot: [date and time]
Please respond by: [date and time]

Request changes

Reviewer to creator

Decision: changes requested (round [1 or 2] of 2)
Must fix: [numbered list, each one something that can be checked as done]
Nice to have: [optional items, clearly separated]
Fine as it is: [what to keep, so it is not rewritten by accident]
Please send back by: [date and time]

Client or stakeholder approval request

Account lead to approver

Hi [name], the posts for [week or campaign] are ready for your decision.
What we need: approve, request changes, or reject each post.
Please decide by: [date and time]
After that time: [what happens, for example "the post will not go out and we will reschedule it"]
Anything you want changed, tell us which post and what to change. One round is usually enough.

Rejection note

Approver to team

Decision: rejected
Reason: [pick one: off-brand, factually wrong, wrong timing, wrong audience, legal concern, other]
Detail: [one or two sentences]
Next step: [rewrite, replace with a different topic, or drop it]

Content approval checklist

Pre-approval checklist

Post: ____________________ Account: ____________________ Slot: ____________ Reviewer: ____________

Voice and message

It sounds like this brand, not like a template.
It makes one point, and the first line says what it is.
The call to action is single and specific.
Nothing in it contradicts a recent post, offer or announcement.

Facts and claims

Names, titles, dates, prices and numbers are checked against a source.
Any claim about results, savings or comparisons can be backed up.
Quotes and statistics are attributed, and the permission to use them is on file.
Anything that needs a disclosure (sponsored, affiliate, giveaway rules) has one.

Links, media and platform fit

Every link loads, goes to the right page and carries the right tracking.
Images and video are the right size and have alt text or captions.
Tags and mentions point to the correct accounts.
Length, line breaks and hashtags suit the platform it publishes on.

Risk and timing

The post is safe to run next to today's news and the brand's other posts.
Nothing in it needs legal or compliance sign-off, or it has had it.
Account, date and time are correct for the audience's time zone.
The approver saw the version that will actually publish.

Decision: [ ] Approved [ ] Changes requested [ ] Rejected Name: ____________ Date: ____________

Use the checklist twice: the creator runs it before submitting, and the reviewer runs it again. Most items take seconds. The value is not in any single line but in the reviewer no longer relying on memory, which is what slips on a busy Friday. The Print button prints only the checklist.

Common failure modes and how to fix them

Approval workflows rarely fail dramatically. They fail by getting slower, vaguer and easier to bypass. These are the patterns we see most often, each with the smallest fix that tends to work.

The unnamed approver

What it looks like: Everyone assumes someone else approved it. Posts sit in review, or go out because nobody objected.

Fix: Name one approver and one backup per account. Write both names into the workflow.

Approval by silence

What it looks like: A post publishes because no one replied. Then the one person who would have objected objects.

Fix: Decide the default in advance. We suggest that no response means no publish, with a reminder before the deadline.

Edit after approval

What it looks like: The approved version and the published version are not the same. A small fix 'just before posting' becomes the thing that gets screenshotted.

Fix: Treat any change to copy, media or link as a new version that needs a new yes. Approval should refer to a specific version, not to the post in general.

Feedback in five places

What it looks like: A comment in chat, an email, a call and a spreadsheet cell all disagree. The creator guesses which one wins.

Fix: One place for feedback per post. If a comment arrives elsewhere, copy it to the post and say so.

Endless rounds

What it looks like: Each round fixes the last round's comments and adds new ones. The post is on version nine.

Fix: Cap rounds at two. Round two must list everything that is left. After that, a five minute call decides.

Everything gets the full process

What it looks like: A holiday greeting goes through the same three reviews as a product launch, so people start rubber-stamping.

Fix: Tier the workflow. Low-risk posts get one reviewer. Launches, claims and regulated topics get the full path.

Reviewing without context

What it looks like: The approver sees text in an email and is asked to imagine the image, the link preview and the platform.

Fix: Show the post as it will appear, with media and the proposed slot. Include the brief in the same view.

The bottleneck approver

What it looks like: One busy person holds forty posts. The calendar empties out every holiday week.

Fix: Batch approvals into one sitting a week, set a backup, and let low-risk categories skip the top approver.

A process nobody measures

What it looks like: People feel it is slow but cannot say where. Every fix is a guess.

Fix: Record who decided, when, and why for every change request or rejection. Review the log weekly and cut the stage that adds the least.

Running this workflow in Bolta

This guide works in any tool, including a spreadsheet and a shared inbox. If you want the workflow built into the place where you schedule, this is what Bolta does today. It only lists what is true of the product.

Two stages: internal review, then client

Posts can pass through internal review first and then go to the client, so your team catches its own mistakes before the client sees anything.

Clients sign in to decide

Client approval happens inside Bolta after the client signs in. There is no anonymous review link. A client can Approve, Request changes or Comment.

Approval is tied to the version sent

An approval applies to the version that was sent for review. If the post changes, the approval does not silently carry over.

Reminders after 2 and 5 days

If a client has not responded, Bolta sends reminders after 2 days and again after 5 days, so you are not writing the chasing emails yourself.

Reviewers do not use a paid seat

People who only review and approve do not take up a paid seat on your plan.

Required reviewers and per-brand assignment

You can mark a reviewer as required, and assign reviewers brand by brand, so each client's posts go to the right person.

Approve your own posts on every plan

Approving your own posts is available on every plan, including the free Starter plan. Explorer is $19 a month.

Mapped to the stages above: your team drafts and does internal review, the client or approver decides, and only approved posts are scheduled. For the client side in detail, including what a client sees and does, read the social media approval workflow page. For agency setups with several brands, see Bolta for agencies. Plans and prices are on the pricing page, and the content calendar guide covers the scheduling side.

Free content approval workflow template

Roles, stages, service levels, a review checklist, a post record and a weekly audit in one plain-text file. No sign-up. Copy it, download it, or share the link.

Prefer a direct file? bolta-content-approval-workflow-template.txt

Worked example: approving and rejecting in Bolta

This is how the five steps run in Bolta, where every draft an agent produces waits for a person before anything publishes.

Drafts arrive in one queue. Each draft lands in the Approve tab of the Hub with its platform, account, proposed slot and attached media, so the reviewer sees the context without opening anything else.
Approve. Approving sends the draft to its scheduled slot. Only approved drafts are scheduled.
Edit, then approve. If the copy is close, the reviewer rewrites it in place and approves their own version.
Reject. Rejecting stops the draft from going out, and the rejection is recorded against it so recurring problems show up in the weekly audit.
Unapproved means unpublished. A scheduled slot is only a proposal. If a draft has not been approved by its slot, it does not go out.

For the product side, see Bolta's social media approval workflow.

See the social media approval workflow in Bolta Try Bolta free

Or use our free tools in Public Apps to execute faster.

Frequently asked questions

What is a content approval workflow?

A content approval workflow is the defined path a piece of content takes from draft to published: who reviews it, what they check, who gives the final yes, how changes are requested, and when approved work is allowed to be scheduled.

What are the stages of a content approval process?

A typical process has six: brief, draft, internal review, approval, schedule, and publish with a weekly review. Small teams merge some of them. Agencies keep internal review and client approval as separate stages.

Who should approve content?

One named approver per account or client, with a backup. Reviewers can be several people, but the final decision should belong to one person so it never stalls waiting on a consensus.

How long should content approval take?

As a starting point, we suggest 24 to 48 hours for the approver, the same business day for internal review, and 24 hours for revisions. Treat these as targets to adjust, not rules. If your posts are time-sensitive, shorten them and plan for more lead time.

How many review rounds are reasonable?

Two. If a post still has open issues after a second round, move the conversation to a call or a decision from the approver rather than a longer comment thread.

What should happen if the approver does not respond?

Decide it before it happens. We suggest a reminder at the halfway point, escalation to the backup approver at the deadline, and no publishing without approval. A missed slot costs less than an unreviewed post.

Does every post need the full approval process?

No. Tier it. Routine, low-risk posts can go through one reviewer. Launches, claims, regulated topics and anything involving a person or a number should take the full path. A single process for everything leads to rubber-stamping.

Does a client need to log in to approve in Bolta?

Yes. Clients sign in to review. They can approve a post, request changes, or leave a comment. There is no anonymous link. For the client-facing side, see the social media approval workflow page.