Deadlines
Stating a Deadline So It Cannot Be Read Two Ways
A deadline that cannot be misread has four components, and most working sentences supply one or two of them.
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.
International teams need more than a time-zone converter, so managers can the feature summary to connect calendar assumptions with the work completed around them.
The surrounding operational question can also be checked against material from MIT Sloan Management Review.
The same requirement, written four ways, and what each produced
“Need this back by Friday”
You: Fri 17:00 · Them: Thu 15:00 — Read on the recipient's week, which ends on Thursday
“Need this back by Friday 13th”
You: Fri 17:00 · Them: Fri 23:00 — The day was now unambiguous and the hour was not
“By end of day Friday 13th, your time”
You: Fri 17:00 · Them: Fri 22:00 — Correct and still three hours adrift, because their day ends later than ours
three phrases · every one read as two different instants · the widest gap between the two readings is 1 day 2 hours
Four versions of one sentence, written over four weeks to the same counterparty. Each revision removed one ambiguity and exposed the next. Only the fourth stopped producing surprises, and it is the one line here with nothing to draw, because the two readings of it are the same instant. One team's own job.
A deadline that cannot be read two ways contains four things: a date, a time, a zone, and a statement of what has to have happened by then.
Most working sentences supply one or two. Adding the others costs about nine words.
The four components
The date. A calendar date, not a day of the week. "Friday" needs a week to resolve it; "Friday 13 March" does not.
The time. An hour, not an edge of a working day. "End of day" names a boundary that moves between parties and sometimes between people in the same office.
The zone. Named explicitly. UTC where more than two parties are involved, or a named place where one party's local time is the operative one.
The event. What has to have happened: sent, received, approved, cleared, standing in the yard. This is the component most often left out entirely and it is the one with the largest spread.
The worked example
By 14:00 UTC on Friday 13 March, I need the signed drawing in my inbox — not sent, received.
Twenty-one words. It has all four components, it can be converted by anybody, and the last clause removes the single most common dispute in this area, which is whether a thing dispatched on time but arriving late was late.
When to use the full form
Not everywhere. A message that reads like a clause of a contract makes ordinary correspondence heavier and signals a formality that most working relationships do not need.
The cases that earn it:
- Money turns on the date — a payment, a penalty, an expiring price.
- Missing it costs a cycle rather than a day — a committee, a sailing, a payment run, a weekly batch.
- The date is being promised onward to somebody else.
- It has already gone wrong once with this counterparty.
The fourth is worth taking seriously. One miss is ambiguity; the second miss with the same phrasing is a choice.
The form for a chain of dates
Where several things have to happen in sequence, a list with owners does more than a paragraph.
| By when | What | Who |
|---|---|---|
| 14:00 UTC Tue 10 March | Drawing issued to the shop | Us |
| 14:00 UTC Fri 13 March | Signed drawing received back | Client |
| 09:00 local Mon 16 March | Material released to the floor | Shop |
| 17:00 local Thu 19 March | Collection booked with the carrier | Forwarder |
Each row has an instant, an event and an owner. Anybody reading it can see which of the four dates their own work sits behind, which is the thing a prose paragraph reliably fails to convey.
Do not bury the date
A deadline in the fourth paragraph of a long message is a deadline that will be missed by somebody reading quickly on a phone.
Put it in the first two lines, or in the subject, or both. This is not a style preference; the recipient is frequently reading in a second language, between other things, at the wrong end of their day, and the scanning behaviour that results is well documented and entirely reasonable.
What to do when you cannot be precise
Say so, and give the shape of the uncertainty instead of a false point.
I do not have a firm date yet. What I can say is that it will not be before the 10th and that I will know the real date by the 6th.
Two facts, both reliable, and the recipient can plan against them. This is almost always better received than a precise date that is a guess, and it preserves something that a wrong precise date spends: the assumption that your dates mean something.
Repeating it at the end
A long message that opened with a deadline should close with it.
This is not redundancy in the way it looks. The recipient reads the first paragraph, works through the content, forms a view about what has to be done, and then stops reading. The closing line is where they look to confirm what they now have to do, and if the date is not there they will act on their recollection of it.
To summarise: signed drawing to me by 14:00 UTC on Friday 13 March. Everything else above can follow next week.
Two lines, and they also do a second job: anybody forwarding the message internally forwards something whose requirement is visible without reading the whole thing, which is how most such messages actually travel.