How to Build an AI Content Approval Workflow That Holds at Volume
An AI content approval workflow is the set of gates a machine-written draft has to pass before it publishes under a brand's name. A workflow that holds has five of them: grounding before generation, machine screening, tiered human review, a recorded sign-off, and a publish lock that nothing bypasses. The order matters more than the tooling.
Most teams already have an approval process. It was designed for a world where a person wrote every draft, and it breaks in a specific way when the drafts arrive twenty at a time.
Why the old workflow fails once AI writes the drafts
The traditional workflow is request, draft, review, publish. It works because drafting is slow. A writer produces three pieces a day, a reviewer reads three pieces a day, and the review step is a real read.
Put a generator in the draft slot and the maths flips. Sixty drafts land on the same reviewer. The reviewer does what anyone would do: skims. Skimming catches typos and tone. It does not catch the sentence that quietly promises an outcome the brand can't back, or the statistic that appeared from nowhere with a confident decimal point.
Volume doesn't make review harder in proportion. It makes review different in kind, because the reviewer's attention is now the scarcest resource in the pipeline and the old workflow spends it on the wrong things.
So the workflow has to change shape, not just speed. Here is the shape.
The five gates
Gate 1: Grounding, before a word is written
Nothing gets generated from a bare prompt. The generator reads the brand's own materials first: the brand guide, the approved claims, the product pages, past posts that survived review. If a draft can only say what the brand has already said or documented, most of the review burden disappears before review starts.
This gate is invisible in the workflow diagram, which is why teams skip it. Then they discover that every downstream gate is doing the grounding's job by hand. We covered the mechanics in Ground Your AI in Your Brand.
Gate 2: Machine screening, before a human reads
Every draft is checked, automatically, against the brand's rules: restricted terms, banned topics, claims with no source, superlatives, comparisons to competitors, anything the brand's lawyer has ever winced at. Each hit produces a flag with its reason, not just a highlight.
The point of this gate is to change what the human looks at. A reviewer who opens a draft and sees "two flags: 'guaranteed' is a restricted term; the 40% figure has no source in the knowledge base" is doing judgment. A reviewer who opens a clean draft with no flags is doing a sanity read, and can approve it in one click with a clear conscience.
Machines are good at consistency and bad at judgment. Humans are the reverse. Gate 2 is where you put the consistent part.
Gate 3: Tiered human review
Not every piece needs the same reviewer. A social post that passed screening clean needs a brand operator's glance. A piece with a flag needs someone with authority to overrule the rule, or to fix the copy. A piece for a regulated brand, or one that names a customer, needs whoever owns that risk.
Write the tiers down. Three is usually enough:
- Clean drafts. Any approver for that brand. One click.
- Flagged drafts. The brand's owner, or the person who wrote the rule that fired. They either edit the copy or record why the flag doesn't apply.
- Escalations. Legal, compliance, or the client. Triggered by specific rule families, not by reviewer mood.
The failure mode here is routing everything to the most senior person "to be safe". That person becomes the bottleneck, the queue grows, and within a month they're skimming. Tiering exists to protect their attention for the pieces that need it.
Gate 4: A recorded sign-off
Approval is an event with a name and a timestamp, attached to the exact version of the draft that was approved. If the copy changes after sign-off, the sign-off is void and the piece goes back to Gate 3.
This sounds bureaucratic until the first time a client asks "who approved this?" and the answer lives in a Slack thread that's been archived. An email chain has no structure, no version, and no reliable timestamp. A workflow that can't produce the record on demand doesn't have an approval step. It has a suggestion step.
What the record should contain is its own subject; see What an AI Marketing Audit Trail Should Record.
Gate 5: A publish lock
The scheduler, the connector, whatever actually sends the piece to LinkedIn or the email tool, refuses anything that isn't in the approved state. Not "warns". Refuses.
This is the gate that makes the other four real. If there's a path from draft to published that doesn't cross Gate 4, someone will use it on a Friday afternoon, with good intentions, and the workflow is now decorative.
How to set it up, step by step
Step 1: Write the rules down per brand. Restricted terms, banned topics, the claims that need a source, the channels the brand has approved. If you run several brands, each gets its own list. A rule that's right for a fitness brand is wrong for a law firm. This is usually a two-hour conversation with whoever has been catching these problems by hand.
Step 2: Decide the tiers and name the approvers. For each brand: who can approve clean drafts, who handles flags, who gets escalations. Names, not roles. "The marketing team" cannot click approve.
Step 3: Put screening in front of review. Whatever tool you use, the reviewer should open the draft and see the verdict first. If your tool shows the draft and hides the checks, or runs no checks at all, the reviewer is back to skimming.
Step 4: Make the approved state the only thing that publishes. Test this by trying to publish an unapproved draft. If you can, fix it before you do anything else.
Step 5: Export the record and read it. After the first week, pull the log for one brand and check that you can answer, for any published piece: what was generated, what was flagged, who approved, when. If any of those is a shrug, the record isn't complete.
Common mistakes
- Approving the brief instead of the piece. Concept approval is useful, but it doesn't cover the words that were actually generated. Both, in sequence.
- Letting the reviewer see drafts without the screening verdict. This is the single most common way an "AI workflow" turns into proofreading at production speed.
- One approver for all brands. Voice bleed and mis-routed flags follow within weeks. The person who owns Brand A's rules should approve Brand A.
- Treating edits after approval as harmless. A fixed typo is harmless. A "small wording change" that reintroduces a restricted term is not, and the workflow can't tell the difference. Re-approve.
- No record because "we trust each other." Trust isn't the issue. Memory is. Six weeks later nobody remembers who signed off, and the client's compliance reviewer isn't asking about trust.
Frequently asked questions
Does every AI-generated piece need human approval?
Yes, if it publishes under a brand's name. The volume argument cuts the other way: the more pieces you generate, the more important it is that a person is accountable for each one that ships. The trick is making approval cheap for clean drafts (one click, with the screening verdict visible) so that human attention goes to the pieces that need it.
Can the approval step be automated for low-risk content?
The screening can be, and should be. The approval shouldn't. "Low risk" is a judgment, and the pieces that cause trouble are the ones someone judged low-risk. What you can automate is the routing: a clean draft goes to the fastest tier, not to nobody.
What if the client wants to approve every piece themselves?
Give them a way to do it that produces a record: a link that shows the piece as it will appear, with the screening verdict, and one button. Not an email. We wrote up how that works in Client Content Approval Without the Email Chain.
Where this leads
The teams getting real leverage from AI content haven't removed the human from the loop. They've moved the human to the right place in it: after the machine has done the consistent, boring checks, and before anything can publish.
That's the workflow Azimuth runs for every brand in a workspace. Grounding first, screening with reasons, tiered approval, a signature on the record, and a publish step that refuses anything without one. The details of what we do and don't do with your data are on the Trust Center.