- Industry
- Oil & Gas
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Head of Corporate Communications
- Code
- CON-09
It schedules ready content across channels around the disclosure calendar, the quiet period before results and production reports, project milestones and any HSE incident, 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: booked slots, the disclosure calendar and quiet periods in the window..
- 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 Corporate Communications 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 calendar rules: the disclosure calendar and quiet periods, channel cadence, review lead times for legal and HSE, and what pauses after an incident.
Reads from
the content calendar: booked slots, the disclosure calendar and quiet periods in the window.
Acts in
the content calendar: it books or moves the slots for the pieces in the schedule.
Hands back
A list of slots, each with piece_id, channel, publish_at, reason and moved_from (or null), plus a list of pieces not scheduled with why.
Asks a person when
The schedule moves a piece tied to a disclosure, puts anything in a quiet period, touches a site with an open incident, or drops a high-priority piece.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most pieces per channel per day | 2 | No channel gets more than this in a day. |
| Quiet period before results (days) | 14 | No investor or operational performance piece goes out in these days before results. |
| Pause promotion after an incident | On | Promotional and celebratory pieces about the affected site stop while an incident is open. |
| Review lead time (days) | 5 | Pieces need legal and HSE review this many days before the slot. |
| Blackout dates | 2026-12-24, 2026-12-25, 2026-12-31, 2027-01-01 | Comma-separated YYYY-MM-DD. |
| Time zone | UTC | The time zone slots are booked in. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Schedule no investor or performance piece in the 14 days before results, and nothing market-sensitive before its disclosure.
- When on is on and an incident is open, pull promotional pieces about that site and hold any piece about it for the Head of Corporate Communications.
- Book no more than 2 pieces per channel per day and nothing on 2026-12-24, 2026-12-25, 2026-12-31, 2027-01-01.
- Leave 5 days of review before each slot.
- Resolve clashes by priority, then by tie to a fixed date, and book in UTC.
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.