UAE · ENBook a demo
IT CompanyContentDecision-maker

Content Calendar Agent

Schedules content across channels.

Content Calendar AgentContent Planning
Industry
IT Company
Department
Content
Team
Content Planning
Kind
Decision-maker
Approver
Content Operations Lead
Code
CON-09

It schedules ready content across the blog, newsletter, social and partner channels around SaaS release dates, client case-study embargoes, events and conference talks, and resolves clashes by priority. It proposes the schedule and books or moves the slots on the content calendar, never ahead of the release it describes.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the project management tool: the content calendar, the product release calendar and the review status of each piece..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Content Operations Lead with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the project management tool: it books or moves the slots on the content calendar. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The publishing calendar rules: channel cadence, the product release calendar, client embargo terms, event dates, review lead times and blackout dates.

Reads from

the project management tool: the content calendar, the product release calendar and the review status of each piece.

Acts in

the project management tool: it books or moves the slots on the content calendar.

Hands back

A list of slots, each with ref, title, channel, publish_at (ISO 8601), reason, moved_from (or null) and conflicts (a list or empty).

Asks a person when

A fixed date moves, a release slips and dependent content must move, or a piece is scheduled against a client embargo.

ApproverContent Operations Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Most pieces per channel per day2No channel carries more than this on one day.
Publish after the release by at least (hours)2Content about a release goes out no sooner than this after the release is live.
Review lead time (days)3A piece is scheduled no sooner than this many working days after it entered review.
Blackout dates2026-12-24, 2026-12-25, 2026-12-31, 2027-01-01Comma-separated dates when nothing is published.
May move fixed datesOffWhen off, embargo, release and event dates are never moved.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Publish content about a release at least 2 hours after the release is confirmed live, never before.
  • Never publish a client case study before its embargo lifts.
  • Keep each channel to 2 pieces per day and avoid 2026-12-24, 2026-12-25, 2026-12-31, 2027-01-01.
  • Schedule a piece no sooner than 3 working days after it entered review.
  • Move a fixed date only when off is true, and then only with the Content Operations Lead.
  • Resolve clashes by priority: launch, then campaign, then evergreen.

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.

Content Calendar Agent · IT Company | Basinwright Industries