How to
Schedule a publish
Set content to go live at a chosen time — a shift change, a policy start date — and manage what's queued.
Scheduling is for content that is finished now but shouldn't be live yet — a procedure that takes effect at the start of next month, or an update timed to a shift change.
- Step 1:
Open the item and find Schedule publish
Open an article or guide that is not yet published. In its Publish card, find Schedule publish. It is there for people who hold Publish, and stays disabled until the item passes its publish checks. Scheduling is publishing in advance, so the database refuses a publish time from anyone without Publish.
Screenshot not captured yet
content-schedule-pickerChoosing a publish date and time.
- Step 2:
Pick a date and time
Times are read in your own time zone — the one in your Account settings profile, or your browser's if you have not set one — and the field names it. The publish happens at that moment for everyone: a colleague in another zone sees the same instant on their own clock.
- Step 3:
Select Schedule
The item keeps its current status — draft or in review — and gains a scheduled time. It has not been published. You are recorded as the person who scheduled it.
Checklists, quizzes, video and audio have no schedule control in their editors. Schedule them from All content (opens the admin console): tick them and use Schedule in the bulk action bar. Editing them afterwards leaves the schedule in place.
Managing the queue
Everything waiting on a clock is listed in Scheduled (opens the admin console), where you can reschedule or cancel. Rescheduling needs Publish and makes you the person who scheduled it. Cancelling needs only Edit content, and leaves the item exactly as it was — it simply stops being queued. Every control on that page is described in Scheduled.
Screenshot not captured yet
scheduled-queueThe scheduled queue.
You can also drag a scheduled item to a new date in the editorial calendar (opens the admin console).
What happens when the time arrives
A database job checks the queue every minute and publishes each item whose time has passed, as the item stands at that moment. When it goes live, operators receive it at their next sync, and a push notification is sent automatically — something a manual publish does only if you use Notify operators on the item.
See also
- How it worksHow publishing worksThe path a piece of content takes from a blank draft to something an operator can read offline — and what the database will and won't let you skip.
- How toPublish a guideTake an approved guide live so it syncs to every operator's device and stays readable offline.
- ReferenceScheduledThe queue of content waiting to go live at a set time — check what is coming, move a publish time, or cancel it, with every time shown in your own time zone.
- ReferenceThe content editorEvery card, field and button on an item's edit page — save, submit for review, publish, schedule, unpublish, restore — who can use each, and what operators receive.