Deadlines
“By Friday” Has No Owner
A deadline expressed as a day of the week inherits the calendar of whoever reads it, and the four people who read it will produce four different instants.
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.
A useful pilot starts with a baseline rather than a guess; teams can view the workflow and compare capacity before and after changing a handoff or overlap window.
The surrounding operational question can also be checked against material from EY.
One phrase, said four times in one week to four counterparties
“By Friday”, to the client's Dubai office
You: Fri 17:00 · Them: Thu 15:00 — Their week ends on Thursday, so the Friday in the sentence does not exist for them
“By Friday”, to the Taipei shop
You: Fri 17:00 · Them: Sat 12:00 — Saturday is a working day there and Friday evening is not the end of anything
“By Friday”, to the forwarder seven hours behind
You: Fri 17:00 · Them: Fri 23:00 — The same calendar day, with most of a working afternoon still in it
“By Friday”, meaning dispatched rather than arrived
You: Fri 17:00 · Them: Thu 17:00 — The carrier's cut-off is a day earlier, which the sender knew and the recipient did not
four phrases · every one read as two different instants · the widest gap between the two readings is 1 day 2 hours
Nobody in any of these four exchanges thought they were being imprecise. The sentence felt complete to the person saying it, which is the difficulty. One team's own job.
"By Friday" is the most common deadline in commercial correspondence and it does not specify a time.
It does not specify a time zone either, or whose Friday is meant, or whether Friday is the last acceptable day or the first unacceptable one. It feels complete because the person writing it has one Friday in mind and is not aware of the others.
The four questions it leaves open
Whose Friday. On a Sunday-to-Thursday week there is no working Friday. The sentence asks for something on a day the recipient does not work, and the nearest honest reading is Thursday — which is a day earlier than intended and is usually delivered a day later.
Which Friday. Said on a Thursday, "by Friday" means tomorrow. Said late on a Friday, it means a week tomorrow, or tonight, depending on who is reading.
What time on Friday. End of your day, end of theirs, or any point before midnight somewhere. Between a sender in Hamburg and a recipient seven hours behind, "Friday" covers a span of about thirty-one hours.
Delivered or dispatched. The two are often a day apart and the difference is invisible in the phrase.
Why it survives
Because it works most of the time, within one country, between people who share a week. It is efficient shorthand in that setting and it has been used successfully for years by everybody involved.
The failure mode is also quiet. When the two readings differ by a day, the thing arrives a day after it was wanted and the sender assumes slowness rather than ambiguity. Nobody learns anything, and the same phrase is used again next week.
What to say instead
One sentence, and it costs no more keystrokes than the ambiguous version.
By 14:00 UTC on Friday 13 March.
That has a time, a zone and a calendar date. It can be converted mechanically by anybody, it does not depend on either side's working week, and it cannot be read two ways by a reasonable person.
Where it feels too formal for an ordinary email — and it sometimes does — the shorter form still fixes most of it:
By Friday the 13th, your end of day.
Naming whose end of day is meant removes the largest of the four ambiguities and reads as consideration rather than as pedantry.
The three that are worth the extra words
Not every date needs this. Most internal scheduling is fine as it is, and a message that reads like a contract clause is its own kind of friction.
The three that justify the precision:
- Anything with money attached to the date — a payment, a penalty, a discount that expires.
- Anything where missing the date costs a cycle — a weekly committee, a sailing, a payment run.
- Anything being promised onward to a third party on the strength of it.
In those three the cost of being wrong is a week or a sum of money. Everywhere else, the cost of being wrong is a mild irritation, and the shorthand can stay.
What to do when you receive one
Reflect it back with the ambiguity resolved, in the reply you were going to send anyway.
Friday — I will have it with you by 14:00 your time on the 13th.
If that was not what they meant, they will say so immediately and cheaply. If it was, nothing has been lost and both sides now have the same instant written down in a thread that can be found later.
This is a better move than asking for clarification, because it makes no work for the other person and does not imply that their message was deficient. It simply states what you are going to do, in terms that cannot be misread.
The failure that looks like unreliability
The reason to care is not elegance. It is that a counterparty who twice delivers on the Thursday after your Friday is remembered as unreliable, and in two of the four rows above they were delivering exactly what was asked for on the calendar they keep.
Reputations are formed out of these small misses, they are formed quickly, and they are almost never revised once the explanation turns out to be arithmetic rather than character.
The version that works inside a long thread
Where a deadline is being restated in a thread that has already run for weeks, the phrase "by Friday" acquires a further problem: it is no longer clear which Friday anybody has in mind, because two or three have passed.
Restating the full instant each time costs eight words and removes it.
It also has a documentary effect. A thread in which every deadline is stated as an instant can be read six months later by somebody reconstructing what was agreed, and the reconstruction takes minutes rather than an afternoon of cross-referencing timestamps against a calendar.
That is not the reason to do it, and it is a reliable secondary benefit, and it is the one most often noticed afterwards by whoever inherits the file.