Deadlines
Dates Without Zones Are Not Dates
A date or time written without a zone is an instruction to guess, and the guess is wrong in the expensive direction more often than chance would suggest.
Who is working when, for the people on this page
Us, stating the deadline
A Friday deadline means the end of our Friday
The client reading it, Dubai
There is no working Friday in their week at all
two parties · four days of the seven are working days for all of them · Mon, Tue, Wed, Thu
The phrase that started this was 'by Friday'. It felt complete to the person who wrote it, which is the whole of the difficulty.
To keep remote-work decisions transparent, teams can the official site and discuss the resulting patterns together instead of treating activity as a private managerial score.
A useful independent source for this part of the workflow is KPMG.
Four timestamps from one week, and what each turned out to mean
A submission portal closing “at midnight on the 14th”
You: Thu 23:59 · Them: Thu 17:59 — The portal ran on a clock six hours behind ours and nothing said so
A payment deadline given as “the 20th”
You: Fri 17:00 · Them: Fri 09:00 — The paying bank's cut-off was 09:00 local, which is the real deadline
A tender clarification window “closing 5pm Wednesday”
You: Wed 17:00 · Them: Wed 10:00 — Their 5pm, not ours, and seven hours earlier here
An auction-style price validity “until 09:00 tomorrow”
You: Mon 09:00 · Them: Mon 02:00 — Sent from a country seven hours ahead, so it had already expired on arrival
four phrases · every one read as two different instants · the widest gap between the two readings is 8 hours
In all four the real deadline was earlier than it looked from here, which is the direction that costs something. The cases where the omitted zone runs the other way are just as common and leave no trace at all, because nothing goes wrong when you are early. One team’s own job.
A time written without a zone is not a time. It is a time in some place, and the place is whichever one the writer was sitting in.
This is well known and almost universally ignored, including by organisations whose entire business is deadlines.
Why the errors run one way
If the omitted zone is behind yours, you compute a deadline later than the real one and miss it. If it is ahead, you compute one earlier than the real one and submit early, which costs nothing and is never noticed.
So the whole class of error is silent in one direction and expensive in the other, and nobody accumulates evidence that it is a problem until something is late.
The four shapes
Portals and systems. A submission portal, a procurement system, an auction, a booking site. The clock is usually the server's, which is often neither party's. Worst case, the displayed countdown is local and the stated deadline is not.
Banks and payment rails. The deadline that matters is the cut-off of the institution doing the work, not the date on the invoice. A payment instructed at ten in the morning and one instructed at two in the afternoon can leave on different days.
Carriers and ports. Cut-offs are always local to the facility, and the facility is frequently not in the same place as the person telling you about it.
Ordinary email. "5pm Wednesday" from somebody whose signature block does not say where they are.
How to write one that cannot be misread
The useful form in running prose is a time, a zone and a date:
14:00 UTC, Friday 13 March
The useful form for anything machine-read is the full ISO form, which carries the offset and sorts correctly:
2026-03-13T14:00:00Z
UTC is the right default for anything crossing more than two borders, because it is nobody's local time and therefore belongs to neither party. Where one party's local time is obviously the operative one — a port cut-off, a court filing, an office closing — name that place explicitly rather than converting it, because the conversion is the thing that will be wrong.
Do not convert on somebody else's behalf
A common and well-meant mistake is to convert a deadline into the recipient's time before sending it.
It usually helps. It occasionally produces a confident, wrong number, and a wrong number stated in the recipient's own time zone is far more dangerous than a correct one in a foreign zone, because it will not be checked.
The safer habit is to give the authoritative form and, if a conversion is useful, to give it alongside and marked as a convenience.
Cut-off is 09:00 on the 20th, Singapore time — which should be 02:00 here, but the Singapore time is the one that binds.
Daylight saving is where the careful get caught
Most of the remaining errors live here, and they are made by people who are otherwise precise.
Offsets change twice a year and not on the same dates in every country, so for two to three weeks each spring and autumn the gap between two places is an hour different from what everybody has internalised. A recurring call drifts. A deadline computed in March on March's offset is wrong if it falls in April.
Writing a zone name rather than an offset avoids most of this: "Europe/Berlin" or "Berlin time" is correct all year, while "UTC+1" is correct for part of it. UTC itself does not shift at all, which is the main reason to prefer it.
The one-line check
Before sending anything with a deadline in it, read the deadline back and ask whether somebody in another country could compute it from the message alone, without knowing where you are.
If the answer is no, the message contains a guess and the guess has been delegated to the person with the least information.
The places this is already solved
Several industries settled this long ago and their conventions are worth borrowing rather than reinventing.
Aviation and shipping run on UTC throughout, and every time in an operational message carries it. Financial messaging formats carry explicit value dates and cut-offs. Software logging conventions converged on timestamps with offsets because the alternative made incidents impossible to reconstruct.
In each case the convention was adopted after an expensive period of not having one, and in each case the cost was not a single dramatic failure but a steady accumulation of small reconstructions: what happened first, who was told when, whether the thing arrived before the cut-off.
Ordinary commercial correspondence has not been through that, which is why it is still written in local time with no zone and why nobody finds it strange.