Guide

Scheduling

A content job generates on a repeating schedule without anyone present. It is the difference between a tool you remember to use and a publishing routine that keeps running while you do something else.

Not switched on yet

Scheduling is not available in your workspace yet. Until it is, generate each piece when you want it — everything below describes how jobs will work once they are switched on.

What a job holds

Part	What it decides
Name	How you recognise it in the list. Name it for its output, not its cadence.
Brand voice and format	Fixed for the job — every run uses them. One job produces one kind of thing. See Voices.
Topics	The queue of things to write about. Covered below.
Cadence and time zone	When it runs, in a time zone you set per job.
Destination	Optionally, one place to deliver each finished piece to automatically.

Cadence

Cadence	Behaviour
`Manual`	Never runs on its own. The job exists as a saved configuration you trigger by hand.
`Daily`	Once a day, at a time you choose.
`Weekly`	On chosen days of the week.
`Monthly`	On a chosen day of the month.
`Cron`	An expression, for a pattern the others cannot express. Only reach for it if you already know the syntax.

The time zone is part of the schedule

A job set to nine in the morning runs at nine in the time zone stored on the job, not the time zone of whoever is looking at it. Set it to the audience's zone rather than your own — the point of a schedule is that nobody is watching.

A manual job can be run immediately at any time, and so can a scheduled one. Running by hand does not disturb the schedule.

Topics

A job holds an ordered list of topics and spends one per run. What happens when it reaches the end is the job's topic policy, and it is the setting most worth understanding:

Policy	When the list runs out
`Queue`	The job stops and pauses itself. Nothing is invented and nothing is repeated — you decide what comes next.
`Cycle`	It starts again from the top. Suitable for recurring subjects that genuinely bear revisiting.
`Top up`	BrandKind proposes further topics in keeping with the existing ones and carries on.
`Evergreen`	There is no list. One standing brief is used on every run, producing a fresh take each time.

A job that runs dry pauses itself and says so

On the queue policy, an empty topic list pauses the job with the reason recorded — it shows as needing topics rather than quietly stopping. Add topics and re-activate it. This is deliberate: silently doing nothing is the worst possible behaviour for a schedule.

Automatic delivery

A job can name one destination, and every piece it produces is sent there without anyone opening it. This is the fully unattended path: schedule, generate, publish.

Nobody reads it first

Automatic delivery means content reaches your live site without human review. Use it only once you trust the voice — run the job into your library for a few weeks first, read what it produces, and turn delivery on afterwards.

Watching a job

Each job shows when it last ran, how that went, and when it is next due. For the detail — what was written, how long it took, why a run failed — open History, where scheduled runs are marked as such so you can separate them from what people did by hand.

Nothing notifies you when a run fails. Scheduled work is worth checking on: a job that has been failing quietly for a fortnight looks identical to one nobody has needed.

Pausing and stopping

A job is active or paused. Pausing stops future runs and keeps everything else — topics, cadence, history — so you can resume without rebuilding it. Deleting a job leaves the pieces it already produced untouched.

Cost

Scheduled runs consume credits exactly as manual ones do, and they do it while nobody is watching. A daily job is roughly thirty runs a month; multiply before you create it. See Billing and credits.

Using schedules well

Start weekly, not daily. Weekly gives you time to read what it produced before the next one arrives.
One job per kind of output. A job that alternates between a newsletter and a press release is really two jobs wearing one name.
Queue the topics you actually want. The topic list is where the thinking goes; automation multiplies whatever you put in it.
Review monthly. Check the failures, read a sample, and prune the jobs nobody reads.