Scheduling across time zones without getting it wrong

When scheduling posts across time zones, most mistakes are about whose time, not time itself: the writer's, the reader's or the server's.

A scheduled post that goes out at the wrong hour is rarely a bug in the scheduler. It is almost always an unstated assumption about which clock the time referred to.

There are three clocks involved in any scheduled post, and confusing any two of them produces the same symptom.

The three clocks

The writer's clock is the one on the laptop of whoever set the time. It moves when they travel and it is the one they are thinking in when they type "09:00".

The audience's clock is the one that actually matters. It is where the readers are, which may be nowhere near where the writer is, and it may be several places at once.

The server's clock is where the scheduler runs. It is usually UTC, and it is the only one of the three that never changes.

Most scheduling errors come from a tool that stores the writer's time as though it were the server's, or displays the server's as though it were the writer's.

Pick the audience's time zone and state it

The fix is not clever arithmetic. It is deciding, once, whose time zone the schedule is expressed in, and then making that visible everywhere a time appears.

In LinkPro Social this is a setting on the organization. Every time you see or enter is in that zone, and the conversion to and from the server's clock happens underneath. It means a team spread across several countries all read the same calendar the same way, which is the actual problem worth solving.

Why not just use each person's local time

Because then the calendar means something different depending on who is looking at it, and a conversation about "the Tuesday morning post" stops being possible. A shared schedule needs a shared frame of reference more than it needs personal convenience.

Daylight saving is the part that breaks

The clocks that change twice a year are where scheduling quietly goes wrong, and it is worth understanding the specific failure.

If a post is scheduled as "09:00 local" it will land at 09:00 both before and after the change, which is usually what was wanted. If it was converted to UTC once at the time of scheduling and stored as an absolute instant, it will shift by an hour when the local clock changes — and nobody will notice until somebody asks why the morning post arrived at eight.

Storing the absolute instant is correct for something that must happen at a precise moment. Storing the local intent is correct for a publishing schedule. They are different problems and the difference only shows up twice a year.

Practical advice for scheduling across time zones

A few things that avoid most of the trouble:

  • Decide the audience time zone deliberately rather than inheriting whoever set the account up.
  • Say the zone out loud in any conversation about scheduling. "09:00" is ambiguous; "09:00 Cairo" is not.
  • Be suspicious of any schedule that looks right in one view and wrong in another. That is the signature of two clocks disagreeing.
  • Check the calendar after a daylight saving change rather than assuming it survived.

The simpler question underneath

Once the mechanics are right, the interesting question returns: when are the people you are writing for actually reading?

That is not answerable from a table of best times. It is answerable from your own reporting, over a few weeks, on your own audience — which is a slower answer and the only one worth acting on.