Deadlines
Delivered On Time and Recorded As Late
The most expensive outcome in this subject is not lateness but a false record of lateness, which is created quietly and is almost never corrected.
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.
When different working weeks make capacity hard to read, teams can read the practical guide before deciding whether a delay came from workload, handoffs, or a calendar mismatch.
For broader context beyond this collection, see the resources published by SHRM.
Four occasions where both sides believed the other had slipped
A drawing asked for “by Thursday”
You: Thu 17:00 · Them: Thu 09:00 — They sent it at 09:00 their time, which was the previous evening here, and it was filed unread
A sample promised “Monday”
You: Mon 12:00 · Them: Mon 04:00 — Dispatched on their Monday morning; our Monday had not started
A report due “end of the month”
You: Tue 18:00 · Them: Wed 01:00 — Their last day of the month ran six hours past ours
An approval needed “before the call”
You: Wed 14:00 · Them: Wed 15:00 — Sent an hour after our call and an hour before theirs
four phrases · every one read as two different instants · the widest gap between the two readings is 8 hours
In all four the supplier met the date on the calendar they were working to, and in all four somebody here recorded a missed deadline. Two of the four went into a supplier review. One team's own job.
The worst outcome here is not a missed date. It is a date that was met and recorded as missed.
That happens quietly, it happens on both sides at once, and it is almost never corrected, because by the time anybody looks the file says what it says.
How the record gets made
Somebody asks for a thing by Thursday. The supplier sends it on Thursday morning their time, which is Wednesday evening here. It arrives outside working hours and sits unopened until Friday, because Thursday here was spent on something else.
The person chasing on Friday morning sees no reply in their thread, notes that the Thursday date was missed, and says so — politely, in a line that goes into a project log or a supplier scorecard.
Three weeks later, nobody remembers the detail. The log says the drawing was late.
The symmetrical version
The same thing happens in the other direction and is harder to see, because it is a conclusion about you.
A counterparty eight hours ahead asks for something on Tuesday. It is sent at four on Tuesday afternoon here, which is midnight there, so from their side nothing arrived on Tuesday at all. Their internal note records a slip.
You will never hear about it. It accumulates.
The three places this does damage
Supplier scorecards. Once a late mark is in a quarterly review it is treated as data. Nobody re-derives the timestamps, and the supplier is often not told which specific occasions are being counted, so they cannot contest them.
Price. A supplier believed to be unreliable is held at arm's length, given shorter payment terms, double-ordered against and eventually replaced, all of which costs money for a reason that is not true.
The relationship itself. The second false mark produces a defensive counterparty, and a defensive counterparty stops volunteering the one thing you most need from them, which is early warning when something really is going to slip.
The check that prevents it
Before recording anything as late, look at the timestamp in the sender's time zone.
That is the whole of it. Most mail clients will show it. If the thing arrived at 06:14 local and the sender is seven hours ahead, it left their desk at 13:14 on the previous day, which was comfortably inside the deadline as they understood it.
| What the log says | What to look at before writing it |
|---|---|
| No reply by the deadline | Whether it arrived outside your hours and was not opened |
| Delivered a day late | The send timestamp in their zone |
| Repeatedly slow | Whether every instance was sent near their day's end |
| Missed the call | Whose working day the call sat in |
The habit that makes it unnecessary
Acknowledge receipt with the time.
Received 08:40 my time on the 14th, thanks — which I make 15:40 your 13th, so comfortably inside.
That line takes fifteen seconds, it puts the resolved fact in the thread where any later argument will look for it, and it tells the other party that their timestamps are being read correctly. The second effect is larger than it sounds: a supplier who knows their dates are being counted on their own calendar behaves differently from one who suspects they are not.
Correcting one that is already in the record
Worth doing, and worth doing in writing rather than in a conversation.
A one-line correction in the same place the original mark lives — naming the date, the timestamp and the zone — is received as diligence by anybody sensible, and it is the only thing that stops the mark being quoted a year later by somebody who was not there.
The alternative, which is to let it stand because it is only one mark and arguing looks petty, is how a counterparty who has never missed a date acquires a reputation for missing them.
Asking before concluding
Where a date does look to have been missed and the timestamps are ambiguous, one line resolves it and costs nothing.
I had this down as due on the 14th and it reached me on the 15th my time — was there something at your end, or am I reading the dates wrongly?
The second clause is what makes it work. It offers the possibility that the error is yours, which is often true, and it makes the answer easy to give honestly.
What it avoids is the alternative, which is to say nothing and record it. A counterparty who is never told about a mark against them cannot correct it, cannot explain it, and cannot change whatever caused it — and the third of those is the one that actually matters, because a supplier who learns that their Thursday evening sends arrive too late will start sending on Thursday mornings.