Schedule content
Schedule saved content to publish at a future date and time in a chosen timezone, change the time with Change Schedule, or publish it immediately.
Choose Schedule to publish a saved content version at a future date and time. Review is optional on every plan.
Who this is for
Owners, Admins, Managers and Editors can schedule. Other roles retain their existing writing and review permissions.
Schedule a publish
- Save your latest edits with Save Draft.
- Choose Schedule in the editor bar of a Draft, Needs Changes, In Review or Approved item.
- Set Schedule Date And Time and Timezone.
- If review is pending, explicitly choose Supersede Pending Review. Its comments, history and shared snapshot are retained; no approval is recorded.
- Choose Schedule in the scheduling panel.
The item becomes Scheduled with a pending job bound to that saved version. Reviewer setup is not required for direct scheduling. Blocking readiness issues, billing limits and publishing pauses still apply.
Nothing is committed before the job runs. The publishing worker checks the saved version and project readiness again when the job is due. Worker activation is an operational prerequisite; a queued job alone is not evidence that a provider ran it.
Change or cancel a schedule
To pick a new time, set New Date And Time and Timezone in the Scheduled Publish panel and choose Change Schedule. The same saved version stays scheduled; only the time moves. It works until the job starts running.
To stop the publish instead, choose Cancel Schedule before the job runs. A directly scheduled Draft returns to Draft; a Needs Changes item returns to Needs Changes; an Approved item returns to Approved. A superseded review remains in history and the content returns to Draft. Cancellation never fabricates approval or reopens a superseded review.
Publish now instead
Choose Publish Now to run immediately. Cancel an active schedule first.
What happens next
Check Publish Logs and Deployment Logs. Repository commit, deployment request and completed site build are separate outcomes. For manual deployment, Acrosite does not send an automatic deployment request.