A simple approval process for social media posts

Most small businesses don't have a formal approval process for social media. Someone writes a post, maybe shows it to the owner on their phone, and it goes out. That works until the day a post goes out with the wrong price, a typo in the headline, or an offer that ended last week.

An approval process doesn't have to be slow or bureaucratic. A good one takes minutes, catches the mistakes that matter, and means nobody has to wonder whether a post was checked. Here's a simple version you can set up this week.

Why bother with approvals?

• Mistakes are public and permanent. Screenshots last longer than deleted posts.
• Prices, dates and offers change. The person writing a post isn't always the person who knows what changed.
• Brand voice drifts. Without a second look, every person writes a little differently.
• Clients expect it. If you're an agency, a client who approved a post is a client who doesn't get surprised.
• It spreads the load. When there's a clear process, the owner doesn't have to personally check everything.

Step 1: Decide the roles

Keep it to three roles, even if one person holds two of them.

• Creator. Writes the post, chooses the image, picks the time.
• Reviewer (optional). Checks facts, spelling and tone. In a very small team, skip this.
• Approver. Has the final say. One approver per area is best: for example the owner for offers and prices, a manager for everyday posts.

Write these names down. "Whoever's around" is not an approver.

Step 2: Decide what needs approval

Not everything needs the same level of checking. A simple split:

• Always needs approval: posts that mention prices, offers, dates, competitions, partners, anything legal or medical, replies to complaints, and anything that spends money, such as boosted posts or ads.
• Approval by one person is enough: everyday posts, behind-the-scenes content, reposts of customer photos (with permission).
• Can go without approval: short, friendly replies to positive comments, if you've agreed the tone in advance.

Write this list down too. It saves a lot of "does this need checking?" messages.

Step 3: Use one checklist

Give approvers the same short checklist every time. For example:

1. Facts: Are the prices, dates, times, locations and names right?
2. Offer terms: If there's a deal, are the conditions clear and correct? Has it actually been agreed?
3. Spelling and grammar: Especially in the first line and any text on the image.
4. Links: Does every link work and go to the right page?
5. Brand voice: Does it sound like us?
6. Image rights: Do we own the photo, or have permission to use it? Are the people in it happy to be shown?
7. Network fit: Is the caption within the network's length limit? Does the image suit the format?
8. Tags and mentions: Are the right accounts tagged, and nobody tagged who shouldn't be?
9. Timing: Is this the right day and time? Is anything happening in the news that makes this post a bad idea today?

Nine questions sounds like a lot, but most take a second each.

Step 4: Set a response time

The most common reason approval processes fail is that posts sit waiting. Agree a time limit, for example approvals within one working day, and plan posts far enough ahead to allow for it. Time-sensitive posts (a flash offer, a same-day update) should be flagged as urgent so the approver knows.

Step 5: Limit the rounds

Endless back-and-forth wastes everyone's time. Agree that feedback should be specific ("change the price to 250, remove the second hashtag"), and aim for no more than two rounds. If a post needs a third round, it's usually faster to talk for two minutes.

Step 6: Keep everything in one place

Approvals spread across WhatsApp chats, emails and comments on shared documents get lost. Whatever tool you use, it should show:

• Everything waiting for approval, in one list.
• The exact post as it will appear, with its image, caption and time.
• Who approved it and when.

That last point matters more than it seems. When a question comes up later ("who agreed to this discount?"), a record saves an argument.

Step 7: Plan for emergencies

Sometimes a post needs to come down or go up fast: a weather closure, a sold-out event, a mistake someone spotted. Decide in advance who can act without the usual approval, and what they must do afterwards (for example, tell the owner and note what happened).

Approvals for agencies and their clients

If you manage social media for clients, add one more layer: the client's sign-off. Tips:

• Send clients a batch to review, such as a week's posts, rather than one at a time.
• Make it easy: a link where they can approve or ask for changes is better than an attachment.
• Agree what happens if the client doesn't respond by the deadline. Silence shouldn't count as a yes for offers or prices.

How Wirk handles this

In Wirk, approvals are built in rather than added on. Everything the AI prepares (posts, replies, ad campaigns and budget changes) waits in Approvals until a workspace admin approves it. Admins can change the text, the caption for each network and the time before approving, or reject it outright. Every decision is recorded in the audit log.

Agencies can send clients a review link where the client approves or asks for changes without needing an account, and the link expires or can be revoked. Admins can also approve from a chat app such as Slack or WhatsApp, which helps with that one-working-day response time.

Start small

You don't need all of this on day one. Start with three things: name your approver, write the "always needs approval" list, and put everything waiting in one place. Add the checklist and response time once the basics are working. Within a month, approvals will feel like a normal part of posting, and wrong-price posts will be a thing of the past.