Timezones and scheduled publishing
How Acrosite interprets the timezone you choose when scheduling, why it removes ambiguity for your team and audience, and what to watch for around clock changes.
When you schedule content, you choose a date, a time, and a Timezone. The timezone is what makes the schedule unambiguous — it tells Acrosite exactly which moment you mean. This page explains how timezones work in scheduled publishing.
Who this is for
Owners, Admins, and Managers, who schedule content across teams and audiences in different places.
Why a timezone is required
"Publish at 9:00" is ambiguous — nine in the morning where? By choosing a Schedule Date and Time together with a Timezone, you remove that ambiguity. Acrosite runs the publish at the chosen time in the chosen timezone, so everyone — your team and your audience — knows exactly when it will go out. See Schedule content.
Choosing the right timezone
- Schedule in your audience's timezone if you want content to appear at a particular local time for readers.
- Schedule in your team's timezone if internal timing matters more.
- Be consistent across a project so your scheduled times are easy to reason about.
Clock changes and edge cases
After the scheduled time
At the scheduled moment, Acrosite runs the same publish pipeline as an immediate publish — readiness checks, commit, and deployment trigger. See What happens when you publish. The outcome is recorded in your logs.
Changing a scheduled time
To move a scheduled publish, cancel its schedule and set a new date, time, and timezone. Cancelling before it runs is safe — nothing has been committed yet.