Image
Workflow
Marketing

Content production pipelines that ship on schedule

A piece slips because its stage, its owner and the claim that still needs a source are written down nowhere anyone can look. An agent holds all three, drafts with each claim’s source shown, queues a social post only after a named person approves it, and leaves the newsletter send to a person.

The short answer

Short answer

You keep content and social posts on schedule by holding a stage, an owner and a due date for every piece, and letting an agent draft against them with sources shown.

A named reviewer approves each piece. A social post is queued only after a person approves it, and the newsletter waits as a draft until a person sends it.

Today

Why did the piece due on the fourteenth never go out?

Nobody decided to let it slip. It sits in no stage anybody can name, the person who was going to review it never agreed to, and the one claim in the third paragraph that needs a source is what actually stopped it, except nobody wrote that down either. None of those three states is recorded anywhere a person can look.

Social posts slip the same way, only faster. The post was drafted, somebody meant to approve it, and the slot on the calendar came and went while it sat in a shared document.

Who is this for?

A marketing or content lead who owns a publishing calendar and reviews what goes out, and who also answers for the social channels and the newsletter. It suits a team that already writes briefs and has rules for voice and sourcing. Where those rules live only in one editor's head, writing them down comes first.

What changes when every piece has a stage, an owner and a date?

Part of the jobCalendar in a spreadsheetWith an agent holding the pipeline
A stalled pieceDiscovered on the due dateNamed, with its stage and owner, as soon as it stalls
The reviewer's jobReconstruct where each claim came fromRead the draft with each claim's source beside it
An unsourced claimSoftened until it passesStopped and routed to whoever can source it
A social postPasted into a scheduler by whoever remembersQueued at its approved time after its approval is recorded
The newsletterAssembled the night before from whatever is to handAssembled from approved pieces and saved as a draft for a person to send
The approvalA thumbs-up in a chat threadRecorded against the exact version approved

How it works, step by step

A date needs something to be measured against. This workflow holds the stage, the owner and the due date for every piece, and assembles the draft so a reviewer can check it without reconstructing it.

01

Hold the calendar

It keeps the calendar of pieces and posts, with the stage each one is in, the person who owns it, and the date it is due.
02

Build the draft with its sources

It assembles the draft from the brief and the sources and templates you authorize, with the source of each claim shown beside the claim. Google Search Central's guidance on people-first content asks whether content presents information in a way that makes you want to trust it, such as clear sourcing.
03

Check it against your written rules

It reads the draft against the rules you already own: voice, lexicon, and the claims you have said need sourcing. For a social post it also checks that every image carries a description. The W3C Web Accessibility Initiative's images tutorial states that images must have text alternatives that describe the information or function represented by them.
04

Name what is stuck

It surfaces what is stalled, what has no owner and which claim nobody has sourced, and routes the unsourced claim to a person without softening it.
05

Human gate: a named reviewer approves each piece and each post

Nothing leaves the pipeline without its named reviewer. A long-form piece stops at the approved draft, and a person publishes it. A social post is approved one at a time, with its wording, image, channel and time, and an edit after approval sends it back for approval again. A newsletter issue is approved as a whole, and a person sends it. The approval gates page explains why each of those sign-offs carries one name.
06

Queue approved posts and prepare the newsletter

Only after that approval does the agent place a post in your scheduling queue, on the channel and at the time the reviewer approved. Until it goes out, anyone with access can pull it, and pulling it is recorded. For the newsletter, it assembles the issue in your template from pieces already approved, checks every link and the unsubscribe line your template carries, and saves it in your email tool as a draft for the list you named. A person sends a test, reads it and sends it.
07

Record the approval

It keeps what was approved, by whom, and against which version, so an approval is a trail and not a memory.
08

Report against the date

It states where each piece and post stands against its date, naming the stage it is sitting in.

Stays a person's

What stays a person's?

Long-form publishing

The agent stops at the approved draft. A person publishes it.

Every social approval. Each post, its channel and its time are approved by a named person before it is queued.

The newsletter send. The agent saves a draft and stops. It adds and removes no subscribers.

Replies and conversations

It answers no comments and sends no direct messages.

Paid promotion. Paying to promote a post, or running ads, is outside the workflow.

Strategy and judgment

Positioning, creative direction and the marketing ops seat itself stay with the people who own them.

The fallback. The brief, the sources and the drafts are yours, so a person can run the review by hand whenever it is needed.

Where this fits

Workflow / Automate a Workflow

Tier 1, Automate a Workflow is the offer for this: one process, from the brief to an approved draft or a queued post, and the record of who approved it. Decisions about truth, brand voice and release belong to people. Before you start, run the readiness checklist against your calendar and your rules. Moving up to the marketing ops manager as an AI Employee could come later, and nothing here promises it. The rest of the marketing workflows are in the use case library.

How does a social post move from draft to scheduled?

StageWhat the agent doesWhat a person does
DraftWrites the post from an approved piece or briefSets the brief and the channels
CheckReads it against voice, sourcing and image descriptionsOwns the written rules it checks against
ApprovePresents wording, image, channel and time togetherApproves, edits or rejects the post
QueuePlaces the approved version at the approved timeCan pull it until it goes out
After it goes outRecords what went out and whenHandles every reply and comment
Tier 1 / Prove
How It Works

Questions, answered

No. A long-form piece stops at the approved draft and a person publishes it. A social post is queued only after a named person approves that exact post, its channel and its time. The gate is closed by default, and the review can be done by hand at any point without the agent.
AI Opportunity Audit · Content pipeline

See which stage your last piece stopped in

Bring the pieces that slipped last quarter and see which stage each one stopped in.