Skip to main content

How It Works · Last updated May 20, 2026

How the human review workflow works

Automating content production does not mean removing the human. This is how the review workflow keeps a person on the publish decision — without slowing the pipeline to a crawl.

Overview

AutoPublish can publish directly, but most teams that run client work, franchise content, or anything brand-sensitive want a human to sign off first. The review workflow is how that happens. The key idea: review is not writing. A draft reaching the review queue is already finished — structured, on-brand, with image and metadata, and already past the 14-signal quality gate. The reviewer's job is judgment and polish, which takes minutes, not the hours that producing an article from scratch costs. That is what makes a human-in-the-loop workflow sustainable even at a high publishing cadence.

Step by step

  1. 1

    Turn on review for a site or stream

    Set a connection or content stream to require review. Generated articles for it will enter the queue instead of publishing automatically. Review is optional and configurable per site.

  2. 2

    Articles are generated and gated

    Articles run the normal pipeline — SERP brief, generation, image, metadata, internal links — and are scored by the 14-signal quality gate before they reach the queue.

  3. 3

    Gated drafts enter the review queue

    Each finished, quality-gated article lands in the review queue in a pending state, with its 0–100 quality score visible so the reviewer knows where it stands before reading.

  4. 4

    A reviewer is assigned

    The article can be assigned to a specific reviewer — a teammate, a client contact, or a corporate brand owner — so the person accountable for the content is the one who signs off.

  5. 5

    The reviewer reads and edits in place

    Using the built-in editor, the reviewer revises the article directly — tightens prose, fixes a detail, adjusts the meta, swaps the image, or regenerates a section that needs work.

  6. 6

    Approve, or send back

    The reviewer approves the article for publishing, rejects it, or returns it for revision. A returned article can be edited or regenerated and resubmitted for another pass.

  7. 7

    Approved articles publish

    Once approved, the article publishes to the connected CMS on schedule. Only articles a human has read and signed off on ever go live.

Frequently asked questions

Is review mandatory?

No — it's optional and set per site or content stream. You can route client and brand-sensitive sites through review while letting your own blog publish directly. The quality gate, by contrast, always runs.

Doesn't reviewing every article cancel out the automation?

No, because review is editing a finished, quality-gated draft, not writing one — a few minutes per article. Automation removes the production work; review keeps the judgment. That combination is the point of the workflow.

Can a client approve content without an AutoPublish seat of their own?

Articles can be routed to the person accountable for them for sign-off. This is what makes the workflow suitable for agency client approval and franchise corporate sign-off — see the approval workflow feature for the formal governance layer.

What happens to a rejected article?

A rejected or returned article can be revised — edited in the queue or regenerated — and resubmitted for another review pass. It does not publish until a reviewer approves it.

Can I start with review on and turn it off later?

Yes, and many teams do exactly that — review everything at first, then move trusted streams to direct publishing once the output is consistently strong. The setting is yours to change per site at any time.

When AutoPublish is not the answer

We would rather you know now than sign up and churn. AutoPublish is not the right tool if any of these describe you:

  • You need a few deeply original thought-leadership pieces — that is a job for a specialist writer with real lived experience, not a volume tool.
  • You will not review AI output at all. The 14-signal quality gate is a safety net, not a replacement for editorial judgment.
  • You want to publish thin content fast to game search. The quality gate is built specifically to stop that — you would be fighting your own tool.
  • Your content needs licensed expertise — medical, legal, or financial advice — without a qualified expert reviewing it before publish.
  • You need original news reporting or investigative journalism, which depends on primary sourcing AutoPublish does not do.
Read the full honest comparison — vs hiring writers, vs generic AI, and when not to use AI content

Related pages

See it on your own site

Free tier with 3 credits. No credit card. Connect a CMS and run the whole process end to end in under 10 minutes.