The Reply That Is Not Late Yet

The calculation

Three facts, none of which takes long to establish: what time it was for them when the request arrived, which days they work, and whether anything closes them this week.

From those, the first hour in which somebody could have read it falls out. If that hour has not happened yet, the reply is not late and there is nothing to chase.

The right-hand column is the one worth internalising. A chase sent before it is not merely ineffective; it costs something.

What an early chase costs

It is read as impatience by somebody who has done nothing wrong, which makes the next exchange slightly worse.

It adds a message to the queue the other party has to work through before they reach the original request, which is the opposite of the intended effect.

And it spends a limited resource. A counterparty will take urgency seriously perhaps twice before the signal stops working, and spending one of those on an interval that was never a delay leaves one.

Where the anxiety actually comes from

Not usually from the duration. From the absence of any signal that the thing arrived.

A request sent into silence is indistinguishable from a request that went to the wrong address, or to somebody who has left, or into a mailbox nobody reads. The waiting party cannot tell the difference, and the uncertainty is what produces the chase rather than the elapsed time.

This is why the most effective single intervention is not faster answers but earlier acknowledgements, and it is why it is worth asking for one explicitly when something matters.

No need to answer this today — but could you drop me a line to confirm it reached the right person?

That is a request somebody can satisfy in ten seconds at any point in their day, and it removes the entire class of worry.

Building the wait into what you promise

The second use of the calculation is on the way out rather than the way in.

If the earliest possible answer is their Sunday, then anything promised to a colleague or a customer on the strength of that answer has to be promised for after their Sunday. Promising it for Friday because Friday is four days away produces a broken promise on this side for a reason entirely located on the other.

This is the main avoidable damage in the whole section: not the delay, which is usually modest, but the onward commitment made without it.

When it really is late

It happens, and the response is different from a chase.

The useful form names the original instant, asks a specific question, and offers a way out.

I sent this on the 10th and I think it may have gone to the wrong person — is there somebody else I should be asking? I need an answer by the 17th to hold the slot.

That does three things: it supplies the date so nobody has to search, it offers a face-saving explanation, and it states the real constraint rather than a general demand for speed. In practice it gets answered more often than a stronger message does, and it keeps the escalation available for the occasion that actually requires it.

Keeping the list on their calendar

Where several things are outstanding with several counterparties, the useful list is sorted by when each one becomes chaseable rather than by when it was sent.

That is a small change and it removes almost all of the wasted chasing. An item sent to a Sunday-to-Thursday office on a Thursday evening appears on the list for the following Tuesday; one sent to a six-day shop on a Friday appears for Monday. Nothing surfaces before it can usefully be acted on.

The by-product is a quieter week. Most of the energy spent on outstanding items goes on looking at them repeatedly before anything can be done, and a list that only shows what is actionable today removes that without removing anything real.

It also makes the genuinely overdue visible, which a list sorted by age does not: in an age-sorted list the item that is four days old and not yet due sits above the one that is two days old and a week late.