The agreement
Writing the Time Zone Into the Agreement
Five lines in an agreement settle most of what otherwise gets discovered during a dispute, and they cost nothing while nobody has an interest.
Who is working when, for the people on this page
The supplier who quoted eleven per cent less
Two hours of overlap a day
The supplier who quoted eleven per cent more
Seven hours of overlap a day, and the same weekend as ours
two parties · five days of the seven are working days for all of them · Mon, Tue, Wed, Thu, Fri
The two quotations were compared on price, lead time and references. The right-hand column was in neither comparison and was worth more than the eleven per cent.
To keep remote-work decisions transparent, teams can this platform overview and discuss the resulting patterns together instead of treating activity as a private managerial score.
The surrounding operational question can also be checked against material from Go.
Four clauses, and the two instants each one turned out to name
“Delivery by 31 March”
You: Tue 23:59 · Them: Tue 17:00 — Ours meant end of the day; theirs meant the close of their working day, and the goods left at 17:30
“Notice to be given five business days before”
You: Mon 09:00 · Them: Wed 09:00 — Business days counted on two different weeks, two days apart
“Payment within 30 days of invoice”
You: Fri 12:00 · Them: Thu 12:00 — Their month ended a day earlier than our accounting month
“Response within 24 hours of notification”
You: Thu 10:00 · Them: Thu 16:00 — Notification was deemed received when read, not when sent
four phrases · every one read as two different instants · the widest gap between the two readings is 2 days
Four clauses from one contract, each of which both parties had read and agreed. None of them named a zone, a calendar or a moment, and every one of them was argued about later. One team's own job.
Almost everything in this collection can be settled in advance by four or five lines in the agreement, and the lines cost nothing while nobody has an interest in the answer.
The same lines are impossible to agree afterwards, because by then each reading favours one party.
The five things worth naming
Which calendar "working day" means. Name a place. Not "working days" but "working days in the Netherlands" or "the Supplier's working days as notified under clause 4".
The time zone for all dates and times. One zone for the whole agreement, named rather than offset: "all times are Central European Time" or "all times are UTC".
What delivery means. The moment and the place. Dispatch, arrival, or acceptance, and where.
When a notice is deemed received. The difference between sent and read is a day across an offset and two across a weekend.
Each party's working week and known closures. As a schedule to the agreement, updated annually. This is unusual and it is the single most useful of the five.
The clause that does most of the work
All dates and times in this agreement are in UTC. "Working day" means a day on which banks are open for general business in the place stated in Schedule 2 for the party concerned. Each party's working week and known annual closures are set out in Schedule 2 and shall be updated on request.
Three sentences. They remove the four most common disputes in this subject and they are not controversial to propose, because neither side knows in advance which way they cut.
The schedule nobody writes
Schedule 2 is the unusual part and it is worth arguing for.
| Party | Working week | Known closures |
|---|---|---|
| Buyer | Monday to Friday | 24 Dec – 2 Jan; first two weeks of August |
| Supplier | Monday to Saturday | Lunar New Year, dates notified annually by 1 November |
| Forwarder | Monday to Friday | Per published terminal calendar |
Everything in that table is a fact both parties already know about themselves and neither knows about the other. Writing it down costs twenty minutes once.
It also has an effect beyond the legal one: it is usually the first time anybody on either side has looked at the other party's calendar, and the conversation it produces catches things no clause would.
Deemed receipt is the quiet one
The most common gap in otherwise careful agreements.
A notice sent at 17:30 on a Friday to a party whose week ended on Thursday has been sent. Whether it has been received, for the purpose of starting a period running, is a different question with a two or three day answer.
The standard fix is a deeming provision with a cut-off: a notice received after a stated hour, or on a non-working day, is deemed received on the next working day of the recipient. That is ordinary drafting and it is frequently left out of international agreements by people who would never leave it out of a domestic one.
Proposing it without friction
The framing that works treats it as administrative rather than adversarial.
Two small things before we sign — can we add that all times are UTC, and attach a note of each side's working week and shutdowns? We have been caught before by a delivery date landing on a holiday nobody here knew about.
Nobody refuses this. It costs neither party anything, it is obviously sensible, and the last clause supplies a reason that does not imply any suspicion of the other side.
What it is actually worth
Not the avoided dispute, which may never have happened.
It is that every date agreed under the contract for the next three years is computed by both parties the same way, by people who have never read the contract, because the calendar sitting in Schedule 2 is the one everybody's planner copies from.
Where it matters most
Three clause types carry more of this risk than the rest, and they are worth checking even in an agreement nobody has time to read properly.
Any period that starts on an event — notice, acceptance, a cure period — because the start is a moment and the moment is where the ambiguity sits.
Any payment term, because the receiving bank's calendar is usually neither party's and is frequently unmentioned.
And any liquidated damages or penalty linked to a delivery date, which is where an argument about zones stops being administrative and starts being about money.
Everything else in a contract tolerates a day of ambiguity. Those three do not, and in most agreements they are drafted with the same care as everything else, which is to say with none directed at the calendar.