Deadlines
The Clock That Starts When They Open It
A twenty-four hour response promise is about working time, and how many calendar days that occupies depends entirely on when the request was sent.
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 find the product details and compare capacity before and after changing a handoff or overlap window.
For broader context beyond this collection, see the resources published by Git.
Five requests sent with a twenty-four hour expectation attached
Sent 17:30 on a Thursday to an office seven hours behind
4 / 2Two of the four days were not working days on their side: the request reached their desk on Friday morning and their weekend began that evening. Twenty-four hours of their working time, spread over four days of ours
Sent 09:00 on a Tuesday to the same office
2 / 2Both days of this wait were working days on their side. The only one of the five that behaved as expected
Sent 16:00 on a Thursday to a Sunday-to-Thursday office
4 / 1Three of the four days were not working days on their side: their week ended two hours after it arrived. Read on their Sunday and answered the same morning
Sent on a Friday to a six-day shop
2 / 2Both days of this wait were working days on their side. Faster than the sender expected, and nobody noticed
Sent at 11:00 on the day before a national holiday
6 / 2Four of the six days were not working days on their side: a two-day holiday nobody here had looked up. The twenty-four working hours were spent promptly inside a six-day window
five waits · 18 calendar days · 9 of them working days on the other side
What varied here was not the amount of work. Every one of these was answered in the first hour the other side had available; what differed by a factor of three was how many of our calendar days passed before that hour existed. One team's own job.
A twenty-four hour response commitment is a commitment about somebody's working hours. The calendar time it occupies depends on when the request arrives relative to their week, and that varies by a factor of three or more.
Both sides usually understand this and neither says it, so the promise gets planned against as though it were a calendar promise.
The arithmetic
A request arriving at the start of somebody's working day is answered that day. The same request arriving two hours before they finish is answered the next day. The same request arriving two hours before their weekend is answered after it.
Nobody has been slower in the third case. The work took the same hour; it simply had to wait for an hour to exist.
The send time is the lever
This is the part that is within your control and is usually left to chance.
Of the five rows above, the one that behaved as expected was the one sent at nine in the morning into a working day that still had most of itself left. The one that cost four days was sent at half past five in the evening, which is when people clear their desks.
End-of-day sending is a strong habit and it is close to the worst possible time for anything crossing a border westward, because it lands at the far end of their day as well.
What a sensible commitment looks like
If you are the one making the promise, make it in the unit you can keep.
| Form | What it commits to | When it is honest |
|---|---|---|
| Within 24 hours | A calendar day | Only if you work every day |
| Within one working day | A day on your calendar | Usually; say whose |
| By 17:00 the next working day | An instant | Best, and requires knowing your own cut-off |
| Same day if received before 11:00 | An instant, with a condition | The most useful form for a service desk |
The last row is worth noting. Putting a cut-off into the commitment lets the other party decide whether to hurry, and it converts a vague promise into something both sides can plan against.
The clock that starts on receipt
Where a commitment is contractual, the question of when the clock starts is worth settling, because there are three plausible answers and they differ by a day.
- When the request was sent.
- When it arrived.
- When it was first available to be read during their working hours.
The third is the one most service agreements actually mean and the first is the one most customers assume. An agreement that does not say which produces an argument at exactly the moment when nobody wants one.
The silence in the middle
The practical damage of all this is not the duration. It is that the person waiting cannot tell the difference between a request being worked on and a request not having been seen.
A twenty-four hour promise that will be met on their Sunday feels, from Thursday evening here, exactly like being ignored. The chase that follows arrives into the same closed office, and the escalation after that arrives to somebody who is also not there.
One line sent on receipt — "got it, you will have this on Sunday our time" — removes the whole sequence. It costs the sender twenty seconds and it is the single highest-value message in this part of the subject.
What to ask for instead of speed
When something is genuinely needed quickly across a large offset, the useful request is not "can you do this in twenty-four hours".
It is "what is the latest I can get this to you for it to come back by Wednesday". That question has a factual answer, the person on the other end can give it without promising anything they cannot deliver, and it hands you the one thing you can act on, which is your own send time.
Where the promise comes from
Most twenty-four hour commitments were written by somebody who has never had to meet one across a border.
They appear in service descriptions, in proposals and in the parts of contracts nobody negotiates, and they are written in the unit that sounds reassuring rather than in the unit the work is done in. The person who wrote it was describing an intention, and the intention is usually met.
The practical consequence is that arguing about whether the commitment was met is almost always the wrong conversation. The commitment was met. The customer waited four days.
What resolves it is rewriting the commitment in a unit both sides can check, which costs nothing to either party and removes a recurring argument that neither of them can win.