AI content workflow: From brief to publish-ready, reviewed every time.

ConvOps runs your content work as governed AI agent workflows. Briefs become drafts. Drafts face automated reviews, and findings loop back until they pass. A gate holds publishing until it is approved. Put it on a schedule and it runs every morning, remembering what yesterday taught it.

claude cowork · two reviews side by side · runs on a schedule

example · Claude Coworkconnected
Write next week's post on onboarding checklists.
task created · Blog Post workflow attached
Recalling our voice rules first, then the research.
approval · waiting for you
Both reviews are green. Ready to publish when you are.
Publish it.
published · sources attached
ConvOps · task · exampleBlog Post
task

Post: onboarding checklists

step 1 of 6
brief recall draft two reviews approve approvalpublish
in short

What is an AI content workflow with human review?

A ConvOps workflow your AI agents run from brief to publish-ready: research, drafts, automated reviews, then a gate that holds publishing until it is approved.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

key facts · october 2026

  • A gate holds the step until an explicit approval is given, recorded with the account that gave it.
  • Automated reviews send findings back to the draft, and the loop repeats until the reviews pass.
  • ConvOps does not publish to a CMS. The agent publishes through the tools its environment provides.
  • A brand or legal report bound as required in enforce mode keeps the step open until the report is filed.
  • Schedules run daily, on weekdays, weekly or monthly, each in its own time zone, and a program shows when they stop firing.
  • Before drafting, the agent recalls the voice rules and past rulings the team stored.

best for

  • Content teams publishing every week across several channels
  • Brands with a legal or compliance read before anything goes out
  • Teams that want the same brief and review on every piece

not for

  • A single post you will write once by hand
  • Teams that want AI text published with no review at all

updated

the problem

Fast content. Nobody knows what shipped.

AI drafts in seconds. Then the voice, the facts and the review depend on who was in the chat.

“Who approved that post?”

It went live with a wrong number in the headline. Nobody remembers signing it off.

“Where did that decision go?”

The team agreed on no jargon in March. Every new chat writes jargon again.

“What happens when someone leaves?”

Your editor knew the voice. Now the AI and the new hire are guessing.

watch it work

One article, brief to published.

A real post, run through the Blog Post workflow from Claude Cowork. Then put on a schedule.

01you, in Cowork

Ask for the post.

You ask for next week's post in plain words. ConvOps creates the task and attaches the Blog Post workflow, with its reviews and its approval.

example
example · Claude Coworkconnected to ConvOps
Write next week's post on onboarding checklists. Readers are ops leads.
task created · Blog Post workflow attached
Brief captured. Recalling our voice rules before I draft.
02the AI

It recalls the voice.

Before drafting, the AI asks shared memory: the reader, the voice rules, the rulings from past reviews. Run 40 writes with what run 1 had to be told.

example
example · ConvOps · recallbefore acting

askblog post voice and audience

memoryReaders are ops leads, not developers. No jargon.
memoryHeadlines under 60 characters. Ruled in the March review.
routeBrand voice guide: docs/brand/voice.md
03the AI · research and draft

Sources first, then words.

Sources are gathered and pinned before the draft starts. Every claim in the draft points back to one of them.

example
example · onboarding-checklists.mddraft 1

Onboarding checklists people actually finish

for ops leads · outline with sources

source 1Why most checklists stall after day one
source 2One owner per step, named up front
source 3Steps small enough to finish in one sitting
3 sources pinnedvoice rules applied
04two reviews

Two reviews. One red.

SEO and engagement review the draft side by side. A finding sends it back to the draft until both are green. A hard red files a bug instead of shipping.

example
example · SEO reviewfinding
  • Keyword in the title
  • Headline under 60 characters
  • Internal links
example · Engagement reviewpass
  • Answers the reader early
  • Concrete examples
  • One clear next step
headline too long · back to the draft
05you approve

You release it.

Keep the approval gate and the pipeline drafts on its own but ships only once an explicit approval is given. Remove it when the double green is enough.

example
waiting for approval

Publish "Onboarding checklists people finish"?

SEO green · engagement green · 3 sources

Send backPublish
approvedPublish step unlockedThe sources travel with the post.
06the schedule

Tomorrow it runs itself.

Put the workflow on a schedule. Each morning a new task fires with the whole process attached. You stop starting it and keep governing it at the gate.

example
every weekday · 07:00next fire · tomorrow 07:00fired
example · ConvOps · runsone task per fire
  • Post: first-week goalsdrafting
  • Post: handover noteswaiting for you
  • Post: onboarding checklistspublished
example
example · Claude Coworkconnected to ConvOps
Write next week's post on onboarding checklists. Readers are ops leads.
task created · Blog Post workflow attached
Brief captured. Recalling our voice rules before I draft.
the workflow

The Blog Post workflow, running.

From brief to published in six steps. Reviews run side by side, and you keep the last word.

workflow · Blog Postrunning · step 1 of 6
  1. 01

    Brief

    Topic, reader and angle, captured as structure, not a doc.

  2. 02

    Recall

    Voice rules and past rulings come back before a word is written.

  3. 03

    Research and draft

    Sources gathered first. The draft cites them.

  4. 04

    Two reviews at once

    SEO and engagement side by side. Findings send it back.

    decision
  5. 05

    You approve

    Keep this gate and nothing publishes until it is approved.

    needs approval
  6. 06

    Publish

    Ships with its sources attached.

what teams run it for

What content teams run on it

Labelled examples from different kinds of content work.

example · B2B marketing

A weekly article with an SEO report

An industrial supplier publishes one buying guide a week. An SEO report bound to the review step must be filed before the draft reaches the approval gate.

Required report and approval gate

example · global brandenterprise

One campaign in eight locales

A consumer brand runs one task per locale from the same workflow. Each local editor approves their market's copy at the gate, and the step history shows which account approved which locale.

One workflow, per-locale approvals

example · internal communicationsenterprise

The monthly staff digest

A hospital group's comms team runs the digest on a monthly schedule inside a program. If a month passes with no run, the program turns silent before anyone asks where the digest went.

Monthly schedule in a program

example · product marketingenterprise

Launch pages with a legal read

Launch copy for a new savings account waits at two gates: product marketing approves the message, and legal approves the claims. A rejection sends the draft back to the writing step.

Two approval gates with a rejection route

example · social

Three hooks for every post

The Social Post workflow writes a question hook, a story hook and a statistic hook. The editor picks one at the gate and the agent polishes it.

Social Post template

example · sales enablement

Case studies with a quote check

A custom report type records that every customer quote was confirmed with the customer. The case study reaches approval only after that report is filed.

Custom report type

example · video

Training scripts with a fact check

Scripts for a training channel pass a fact-check review that loops back to the draft until it is clean. There is no approval gate: the review is the bar, and the script moves on to the production team's queue.

Review loop, no approval gate

example · research

Sources gathered before the outline

A research step at the start of the workflow answers the piece's key question, with a source for each finding. It has no approval of its own; the writer reads it before the outline gate.

Research step, no approval

what it remembers

The voice lives in shared memory.

Every review makes the next draft better. Kept by the team, not by one editor.

Voice rules

Readers are ops leads. No jargon. Plain verbs. Recalled before every draft.

how we sound

Past rulings

Headlines under 60 characters. Decided once in review, applied to every draft after.

decided once

Where sources live

The research folder and the brand guide, so no draft starts with a search.

where it lives

Linked to each post

Every ruling points back to the post that produced it.

traceable

recurring work

Run it every week

A content calendar is recurring work. ConvOps runs it, shows when it stops, and counts what it costs.

Give each recurring piece a schedule: an article every Tuesday, a newsletter on the first weekday of the month, social posts every weekday. Each schedule has its own time zone and a preview of the next five runs. Group them into a program, and its verdict shows when a run is late, silent or failing.

Plan the one-off pieces on Plan, next to the scheduled ones. Spread finds the least-loaded days before each deadline and shows a preview before anything moves.

Define the numbers each article must report in Metrics, such as review rounds or findings per draft, and bind them at the review step that produces them. ConvOps also records the cost of every run by itself. Markers on the trend show each change to the workflow those metrics are bound to.

schedule firesTuesdays, in its time zone
recallvoice rules and rulings
draftsources first
reviewsfindings go back
brand reportreport required
editor approvesapproval
publishthrough the agent's tools
the difference

Prompting vs a pipeline.

  • A new chat for every post, the voice explained again
  • One reviewer, when someone has time
  • A wrong claim ships because nothing stopped it
  • Someone has to remember to start it
  • The voice recalled before every draft
  • Two reviews side by side, every time
  • Findings loop back. A hard red files a bug.
  • A schedule starts it every morning

Reviews side by side

The review step tells your AI session to start both reviewers at once. ConvOps holds the step; your session runs the two agents on the same draft.

The loop is a detour

Findings send the run into a fix sub-workflow that returns to the draft step. It repeats until the reviews pass.

Two schedule modes

A schedule runs every few minutes, hourly, daily, on weekdays, weekly, monthly or on a repeat rule, in its own time zone. Each fire either creates a fresh task or wakes the same task where its workflow stopped.

Rules reach the step

Policies like "every claim carries a source" arrive with the step the agent is on. Guidance at the moment it acts.

next to what you use

ConvOps next to what you already use

Keep the CMS and the writing tools. ConvOps holds the process the piece goes through.

ConvOps next to the content tools teams already weigh
ConvOpsAI inside the CMSA writing toolA chat prompt
ProcessBrief, research, draft, reviews and a gate, in orderOne edit at a timeA document and suggestionsWhatever the prompt asks for
Review before publishingA gate holds publishing until it is approvedPublish rights in the CMSComments in the documentNone
Brand and legal checksRequired reports, filed before the step moves onStyle settingsStyle rules and suggestionsInstructions in the prompt
Recurring calendarSchedules in a program with a health verdictScheduled publishingNoneStarted by hand
RecordEvery step, reason and approval on the taskRevision historyVersion historyThe chat history
start this week

Four moves to your first run.

Connect the AI tool your team already uses, install the workflows, and run one real piece of work through them.

  1. move 1

    Install the Content Studio pack: blog post, social post, newsletter, repurpose

  2. move 2

    Run one article attended: brief, research, draft, then the two reviews

  3. move 3

    Watch the fix loop send findings back to the draft until both reviews pass

  4. move 4

    Then add the schedule, and stop starting it yourself

install these

built on

The parts doing the work.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

questions

What teams ask.

What is the content use case in ConvOps?

In ConvOps, the content use case runs articles, social posts, newsletters and repurposed pieces as workflows your AI agents follow from brief to publish-ready. Research and drafting come first, automated reviews send findings back to the draft until it passes, and a gate holds publishing until it is approved. A schedule can start the same workflow every day or every week.

Where does a person review AI-written content in ConvOps?

Wherever you put a gate. In ConvOps, a gate holds the step until an explicit approval is given, recorded with the account that gave it. Most teams approve the outline and the final draft, and let research and the automated reviews run without a stop. Add a gate before legal sign-off and the run waits there; remove one and the reviews become the bar.

Can ConvOps run a content calendar on a schedule?

Yes. In ConvOps, a schedule starts a task at the cadence you set, such as daily, weekdays or weekly, in its own time zone, and you can preview the next five runs before saving. Group the schedules into a program and it shows a health verdict, so a calendar that stopped firing shows up as late or silent instead of going unnoticed.

Does ConvOps publish to our CMS?

No. ConvOps holds the workflow, the gates and the record, and posts nothing itself. The agent publishes through the tools its environment provides, such as a CMS connection, or hands you the final text to post. Either way the publish step comes after the gate, so the agent reaches it only once the piece has been approved.

How does ConvOps keep brand and legal checks from being skipped?

Bind them as reports. In ConvOps, a report type such as a brand check or a legal review can be bound to a step as required in enforce mode, and the step will not advance until that report is filed. Observe mode never blocks and records whether each step would have met it, and the simulator previews what a binding would do before you switch it on.

Which numbers show content quality over time in ConvOps?

The ones you define first. In ConvOps you define the metrics each article must report, such as review rounds or findings per draft, and bind them at the review step, where each value is recorded with who recorded it. ConvOps also records the cost, duration, tokens and outcome of every run by itself, and agents cannot write those. Markers on the trend show every workflow change, so you can see whether an edit helped.

Is a scheduled content workflow autonomous, or only a timer?

The schedule only starts it. In ConvOps, the run then recalls what earlier runs learned, researches, drafts, faces its reviews and stops at the gates you placed. Memory, reviews, gates and the record are what make it a governed workflow rather than a timer, and a program over the schedules tells you when the runs stop arriving.