- Industry
- Procure AI
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Content Operations Lead
- Code
- CON-09
It schedules ready content across the website, newsletter, client portal and social channels, balancing cadence, service launch dates, regulatory deadlines, client fiscal year-ends and review lead times, and resolves clashes by priority. It proposes the schedule and books or moves the slots in the content calendar.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the content calendar: the slots already booked per channel in the window, with each piece's status, ready date and embargo..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Content Operations Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the content calendar: it books or moves the slots for the pieces in the schedule. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The publishing playbook: channel cadences and best times for procurement and finance audiences, blackout periods (client quarter-end close, year-end), the service launch calendar and the review lead times per format.
Reads from
the content calendar: the slots already booked per channel in the window, with each piece's status, ready date and embargo.
Acts in
the content calendar: it books or moves the slots for the pieces in the schedule.
Hands back
A list with one entry per piece and channel, each with piece_id, title, channel, publish_at (YYYY-MM-DDTHH:MM in the set timezone, or null), status (scheduled, moved or unscheduled) and reason.
Asks a person when
The schedule moves a piece tied to a service launch, regulation date or webinar while off is false, a high-priority piece is left unscheduled, or a reschedule moves something due within 48 hours.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most pieces per channel per day | 1 | No channel gets more pieces than this on one day. |
| Review lead time (working days) | 3 | A piece publishes no sooner than this many working days after its ready date. |
| Blackout dates | 2026-12-24, 2026-12-25, 2026-12-31, 2027-01-01 | Comma-separated dates, as YYYY-MM-DD, on which nothing is scheduled. |
| Keep the client portal quiet at quarter-end (days) | 3 | No client portal or newsletter piece goes out in the last this-many working days of a calendar quarter, when clients' finance and AP teams are closing. |
| Timezone for publish times | America/New_York | The timezone the schedule's publish times are given in. |
| May move launch-tied pieces | Off | When off, moving a piece tied to a launch, regulation date or webinar needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Never schedule a piece before its embargo lifts or sooner than 3 working days after its ready date.
- Schedule no more than 1 pieces per channel per day, and never on 2026-12-24, 2026-12-25, 2026-12-31, 2027-01-01.
- Keep client portal and newsletter pieces out of the last 3 working days of each quarter.
- Give publish times in America/New_York, at each channel's best time from the playbook.
- Pieces tied to a fixed date keep it; when off is false, moving one needs the Content Operations Lead.
- On a clash the higher-priority piece keeps the slot; a piece on a regulation that takes effect soonest goes first among equals.
- A piece that fits nowhere in the window is left unscheduled with the reason.
See the Content Calendar Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.