The content schedule

The content schedule is the Content tab of the Content Agent: every piece the agent has planned, is writing, or has published, shown as a list or a calendar. Each piece is a slot with two dates: a generate-by date (when the draft is written) and a Scheduled date (when it goes out). Generation starts as soon as a piece is planned, as long as generation budget is left; the scheduled date sits later on your calendar, so Review first mode usually has time to accept or decline before the slot, while Auto-publish skips that inbox when quality checks pass. To get there, click the Content tile in the left rail, which lands on the Content Agent, or hover the tile and choose Content Agent. The page opens on the Content tab; Activity and Settings sit next to it. On current plans, the Content Agent is a Business plan feature and is not available on white-label workspaces. On lower plans the page shows a demo calendar behind an upgrade overlay. If setup is incomplete, a setup wizard opens on its own, and a readiness banner above the schedule walks you through the recommended steps one at a time, such as connecting a CMS or adding Knowledge Base items. For what the agent is and how it decides, start with the Content Agent overview.

​

The slot lifecycle

A piece moves through these statuses, shown as badges on the schedule:

• Planned: scheduled by the planning agent, not yet written. The planner sets type, length, and tone when it books the slot, and a persona when it has one; persona is optional. Planned and Generating rows show dimmed with a dashed border in the list.
• Generating: the writer is producing the draft.
• Needs review: the draft is ready and waiting for your accept or decline. In Review first mode every piece stops here. In Auto-publish mode a piece stops here for one of two reasons: it failed a quality check, or it has required CMS fields the AI could not fill with confidence.
• Scheduled: cleared to publish at its slot time, by your accept or by Auto-publish after quality checks.
• Approved: used when a piece publishes immediately instead of waiting for its slot. This happens when the Publish timing setting is Immediately on approval rather than At scheduled slot.
• Publishing: a short lock while the CMS write is in flight. It is counted under the Scheduled tab.
• Published: live, or pushed to your CMS as a draft, depending on your Publish state setting (Publish live or Publish as draft). With no CMS connected, the piece is marked published for manual export instead.

Three statuses cover the exceptions:

• Delayed: generation failed after two attempts, or a planned piece was released for re-planning (its date fell outside the current usage period, a higher-priority idea displaced it when the budget was full, or it lost its linked prompt). The agent refunds the failed attempt and re-plans the topic; the piece shows a note such as “Postponed. It will be rescheduled automatically.” No action needed.
• Publish failed: the draft is ready, but the CMS write gave up. The piece shows the CMS error, the attempt count, and a hint. Deterministic CMS config errors fail immediately; transient errors retry with backoff, up to 5 attempts. The detail sheet offers the fix that matches the error, such as Set author or Fix CMS connection, plus Publish now, Decline and Delete. If the last write may already have landed, it tells you to check your CMS for a duplicate first.
• Suppressed: declined. It leaves the schedule, will not be generated or published, and the decline reason is stored on the piece. Declining is possible from Needs review, Scheduled, Approved and Publish failed, and always needs a reason.

A Failed status also exists for pieces whose generation could not start. These are hidden from the list, the calendar counts and the filter tabs, so you will rarely see one; the calendar legend still lists it.

​

Reading the schedule

The filter tabs above the schedule group statuses the way you triage them: All, Drafting (planned), Generating, Needs review, Scheduled (approved, scheduled and publishing), and Published, each with a live count. Two more tabs, Publish failed and Delayed, appear only while a piece is in that status, so an extra tab is itself a signal. Counts leave out suppressed and failed pieces. “Needs review” is the tab to check daily; the rest mostly run themselves. The List / Calendar toggle sits at the right end of that filter row. The list has the columns Status, Type, Title / Topic, Source, Scheduled and Published at; it sorts by Scheduled ascending by default, and you can sort by Scheduled or Published at, 25 rows per page. The list is best for triage. The calendar shows a month by default (week is available), with a dot per piece coloured by status and a legend above the grid; it is best for seeing cadence and gaps. Click a row or a dot to open the same detail sheet. The detail sheet, titled Content details, shows the status badge, the Scheduled and Generate-by times, Priority, Auto-publish, Type, Length, Tone and Persona, the agent’s Why this was prioritized explanation, and a full draft preview once it is generated. The footer actions depend on the status: a Needs review piece gets Open in editor, Decline and Accept; a Scheduled or Approved piece gets Open in editor, Decline and Publish now; a Published piece gets a link to the live page or CMS draft and Track performance. Publish now overrides the schedule, so the piece moves to today on the calendar. If you accept a piece whose scheduled date has already passed, the sheet asks whether to reschedule it to the next slot or publish it now. Tick rows in the list to act on several at once: Accept, Decline, Publish now and Delete each show how many of the selected pieces they apply to, and are disabled with an explanation when the selection does not fit (for example, Accept needs every selected piece to be in Needs review). Shift-click or Cmd/Ctrl-click selects a range. Viewers cannot use bulk actions.

​

How pieces get on the schedule

You don’t add pieces by hand. The planning agent pulls from your content gap backlog, ranks ideas by expected impact, and schedules as many as your budget share and calendar allow, spacing them across your publish windows, skipping blackout dates and respecting the max-per-day cap. The Source column in the list shows where each idea came from. The agent re-plans when new gap recommendations arrive, when your billing period resets or your allowance grows, and at least every few hours as a backstop. Each run’s reasoning appears in the Activity tab under “Planning activity”. Two things pace the schedule: your settings (Budget share, Max per day, Publish timing, Publish state, automation mode and publish windows) and your remaining generation budget. When the budget runs out, planned pieces wait and show a Waiting for budget badge, and the page shows a notice with the reset date: “Content Agent generation paused” when the Content Agent’s share is used (with an Adjust budget share button), or “Generation budget used” when the whole organization budget is used (with a View plans button). “Content Agent budget fully allocated” is informational: existing drafts continue and new recommendations wait for the reset. A paused schedule is a budget signal, not a bug.

​

What happens next

When a draft finishes generating, it lands in Needs review and you get an in-app notification; several drafts that pass the quality check in the same hour give one alert. In Auto-publish mode, pieces that pass the quality check skip review and queue for their slot without a notification. From there, the review flow takes over: see Reviewing, approving and declining drafts. After a piece publishes, the footer of its detail sheet shows a Track performance link into the Page Tracker.