Content approval process for AI blog posts: roles, steps and a template

Why AI blog posts need an approval process

An AI draft looks finished. That is the risk: it reads well, so people are tempted to wave it through. Google is clear about what should happen first: "It is critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing" (Google Search Central: generative AI content (external link)). The same page gives the reason: "generative AI outputs may contain inaccuracies (also known as hallucinations)."

The review is not only about the body text. Google adds that it "also applies to metadata like <title> elements, meta description elements, structured data, and alternate texts for images, which can appear in Search results" (same source (external link)). And on effort, Google's guidance on helpful content says that "using generative AI to produce large amounts of text without manual oversight or curation represents little to no effort" (Google: creating helpful content (external link)).

So an approval process is not bureaucracy. It is the step that turns an AI draft into a post your company can stand behind. What Google says about AI content in general is covered in our guide Does Google penalize AI content?.

The four roles in a content approval process

Think in roles, not in job titles. One person can hold several roles, but each role should have exactly one owner per post.

• Writer (or editor of the AI draft): writes the brief, creates the AI draft, edits it, adds examples and sources, and fixes what the reviewers find.
• Subject expert: checks that the content is correct. In a law firm that is a lawyer, in a trade business the master craftsman, in software the product owner.
• Approver: makes the final yes or no. Checks that the post fits the brand, the goal and the company's standards, and that nothing risky slipped through.
• Publisher: puts the approved version online, checks the live page and schedules it.

The most common gap is the subject expert. If nobody owns the facts, everybody assumes someone else checked them.

The content approval process step by step

1. Brief. The writer notes the topic, the reader, the main keyword, the goal of the post, the sources to use and the subject expert's name. One paragraph is enough. Without a brief, reviewers judge the post against their own idea of it.
2. AI draft. The draft is created from the brief, ideally with your brand voice settings or a style guide.
3. Writer's edit. The writer removes filler, checks the structure against the brief, adds a real example from your work and links the sources. A draft should not reach a reviewer until the writer would sign it.
4. Expert review. The subject expert checks facts, numbers, names, prices and claims. Comments go into the document, not into a chat thread that gets lost.
5. Revision. The writer works in the comments and marks each one as done or explains why not.
6. Final approval. The approver reads the whole post, including title, meta description and image alt text, and approves or sends it back with a reason.
7. Publishing. The publisher schedules or publishes the approved version, then opens the live page once: links, images, formatting, author name.
8. Record. Note who approved which version and when. If a question about the post comes up months later, you can answer it.

What each reviewer checks

Each reviewer has a different job. If everyone checks everything, the post gets five opinions on commas and nobody checks the facts.

How many review rounds?

Two rounds are enough for most blog posts: one expert round and one final approval. Plan for a third only when the topic is sensitive, for example legal, medical or financial content, or when a client approves.

If a post needs a fourth round, the problem is usually earlier in the process: a vague brief, a writer who passed on an unedited draft, or reviewers who change the direction late. Fix the brief or the checklist instead of adding rounds.

A simple rule helps: a reviewer may send a post back once with all their comments. A second send-back needs a reason that was not visible in the first round.

Turnaround times: agree on them in advance

There is no standard time for a review. What matters is that everyone knows what is expected. Our advice:

• Set a deadline per round that fits your team, for example two working days, and write it into the brief.
• Agree on what happens when the deadline passes: a reminder, a deputy, or the post moves to the next slot in the plan.
• Plan the publishing date backwards from the review time, not the other way round.
• Keep posts small enough that one review fits into a normal working day.

RACI table for content approval

RACI stands for responsible (does the work), accountable (owns the result and decides), consulted (gives input) and informed (is kept up to date). Copy this table and replace the roles with names.

Rule of thumb: exactly one A per row. If a row has two As, two people will wait for each other.

One-page approval template

Copy this into your document, ticket or project tool and fill it in for every post.

Post title:
Main keyword:
Reader and goal of the post:
Planned publishing date:

Writer:                 Date handed over:
Subject expert:         Review deadline:
Approver:               Approval deadline:
Publisher:

Sources used (links):
1.
2.

Writer check
[ ] Follows the brief
[ ] Own example or experience added
[ ] Every fact has a source
[ ] Title and meta description match the text
[ ] Image alt texts describe the image

Expert check
[ ] Facts, numbers, dates and prices correct
[ ] Nothing outdated or promised that we do not offer
Comments:
Signed off by / date:

Final approval
[ ] Brand voice and goal fit
[ ] Author named correctly
[ ] Expert sign-off present
Decision: approved / back to writer (reason):
Approved by / date / version:

Publishing
[ ] Live page checked (links, images, formatting)
Published by / date / URL:

Common mistakes in content approval

• The approval bottleneck. One person approves everything and is often away. Name a deputy with the same right, and keep the approver's checklist short so approval does not take hours.
• Nobody owns the facts. The writer trusts the AI, the approver trusts the writer. Put one name next to "fact check" in every brief.
• Approving without reading. Approval becomes a click. The approver should read the whole post, including the title and meta description, before saying yes.
• Feedback in five channels. Comments in chat, e-mail and calls get lost. Keep all comments on the post itself.
• Late changes of direction. A reviewer rewrites the angle in round two. That belongs in the brief.
• Approving an old version. The approved text and the published text differ. Record which version was approved.

Small team, larger team or agency

Small team (1-2 people). One person often writes, approves and publishes. That works if you separate the steps in time: write today, review tomorrow with fresh eyes, using the checklist. For topics outside your own knowledge, ask one expert, for example a colleague or a partner, to check the facts only.

Larger team. Split the roles as in the RACI table. Use rights so that authors cannot publish without approval. Route posts to the matching subject expert per topic instead of sending everything to one person.

Agency with client approval. Add the client as the final approver, or as a consulted expert with the agency keeping final approval, and agree which of the two in the contract or kickoff. Send the client a finished post, not a raw AI draft, and ask for comments in one round with a deadline. Our page for agencies shows how client blogs can be run in one place.

To fit approval into an automated publishing plan, see our guide on how to automate blog posts.

How Blog Automation supports the approval process

In Blog Automation, the setting "Always send AI posts to review first" is on by default and marked as recommended. Posts move through draft, in review, approved, scheduled and published, and only approved posts can be scheduled or published automatically. A reviewer approves or sends a post "Back to author". In the Pro plan, roles and rights decide who may write, approve and publish. An activity log records who did what and when, and an e-mail tells the approver when a post is waiting. More on the approval workflow.

Frequently asked questions