Campaign time-zone checklist for distributed teams
Plan a campaign with named time zones, approval deadlines and release checks that remain clear across daylight-saving changes.
By the Postly Team
Before you start
Record the audience's location, campaign deadline and each destination's intended release time. An offset such as UTC−5 is not interchangeable with a named zone throughout the year.
Prepare and review the release
- Write the planned release as a date, local time and named zone in the brief. Distinguish a simultaneous global release from a local-morning release in each region.
- Review the schedule displayed in Postly and compare it with the brief. Check each location separately when a campaign contains several local times.
- Set approval deadlines before the earliest release. Leave enough time to correct rejected media or a missing destination without rushing the entire campaign.
- After publication, compare actual results with the planned release. Preserve the time zone in the campaign record so a later reviewer can interpret it.
Worked example
A webinar starts at 15:00 Europe/London. The team records that named zone and checks its equivalent for a New York audience on the actual event date. It does not reuse an old conversion from a month with different daylight-saving rules.
If something goes wrong
- Calendar looks an hour wrong: compare named zones and the actual event date.
- One region publishes early: inspect that destination's saved time rather than moving every post.
- Approval arrives late: reschedule the affected release and tell the campaign owner which destination changed.