- Industry
- Banking
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Head of Content
- Code
- CON-09
It schedules ready content across the website, mobile app, email and social, around rate-change effective dates, product launches, results-day quiet periods and blackout dates, and resolves clashes by priority. It proposes the schedule and books or moves slots in the content calendar once approved.
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 booked slots per channel, the fixed event dates and each piece's review status..
- 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 Head of Content with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the content calendar: it books or moves the approved slots. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The publishing calendar rules: channel cadences, rate-change and product-launch dates, the quiet period before the bank's results, regulatory publication dates, review lead times and blackout dates.
Reads from
the content calendar: the booked slots per channel, the fixed event dates and each piece's review status.
Acts in
the content calendar: it books or moves the approved slots.
Hands back
A list with one entry per piece, each with piece_id, title, channel, publish_at (ISO date-time or null), status (booked, moved, unscheduled or held), reason and clash_with (piece_id or null).
Asks a person when
The schedule moves a piece tied to a rate change, launch or regulatory date, publishes a promotion in the results quiet period, leaves a high-priority piece unscheduled, or moves something due within 48 hours.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most pieces per channel per day | 2 | No channel carries more than this many pieces in a day. |
| Days of compliance review before publishing | 3 | A piece without compliance approval is scheduled no sooner than this. |
| Quiet period before results (days) | 14 | No product promotion publishes in this many days before the bank's results. |
| Dates nothing publishes | 2026-12-25, 2027-01-01 | Comma-separated dates. |
| Time zone | America/New_York | The time zone the schedule is set in. |
| May move pieces tied to fixed dates | Off | When off, pieces tied to a rate change, launch or regulatory date never move. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A piece about a rate change never publishes before the rate's effective date.
- No channel carries more than 2 pieces a day; clashes go to the higher priority.
- A piece without compliance approval is scheduled at least 3 days out.
- No product promotion publishes in the 14 days before results, and nothing on 2026-12-25, 2027-01-01.
- When off is false, pieces tied to fixed events never move.
- All times are in America/New_York.
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.