Skip to content
The part of the process nobody writes down
What Nobody ExplainsThe part of the process nobody writes down

Unwritten Rules

How long you have to reply before the delay means something

Every channel carries an expected response time that nobody publishes, and the message is read against that expectation rather than in isolation.

By Amrita Kohli3 min read

Two office workers engage in conversation, creating a professional work ambiance.
Photograph by cottonbro studio via Pexels
Editorial note. Independent reporting and analysis. Nothing here is sponsored or paid for. How we work.

Silence is read as a message

A reply that arrives quickly and one that arrives four days later can contain identical words and be understood entirely differently. That is because every channel of communication carries an expected turnaround, absorbed rather than taught, and any reply is read against it.

Nobody agrees on these expectations explicitly, which is exactly why they cause trouble. Two people can be applying different norms in perfectly good faith, one experiencing a delay as ordinary and the other experiencing the same delay as a deliberate signal.

The expectation follows the channel, not the content

The tightest expectations attach to the channels that reach a person immediately and privately. A message on a personal messaging application implies same-day and often within the hour. A work email implies the same or next working day. A letter implies a week. A message left with a third party implies whenever the person next surfaces.

What is striking is how little the urgency of the content adjusts this. A trivial message sent through a fast channel still generates an expectation of a fast reply, and an important one sent by post does not shorten the letter’s natural rhythm. The medium sets the clock, which is why choosing the channel is a more consequential decision than most people treat it as.

Delivery and read indicators changed the arithmetic

Systems that show a message has been delivered, and particularly those that show it has been opened, removed the ambiguity that used to make delay comfortable. Once the sender knows the message was read, silence becomes a positive act rather than an absence of one.

People have adapted with a set of workarounds — reading from a notification without opening, disabling the indicator, deliberately leaving a message unopened until there is time to answer properly. All of these are attempts to restore a buffer that the technology removed, and the fact that so many exist suggests the buffer was doing something useful.

Acknowledgement is a separate act from answering

The most useful convention in this whole area is the distinction between confirming receipt and providing a response. A short acknowledgement — received, will come back to you tomorrow — resets the clock entirely and costs almost nothing, because what the sender is usually missing is information about whether the message landed rather than the answer itself.

This is why lengthy silence followed by a thorough reply often lands worse than a fast holding note followed by the same reply later. It is also why so much frustration in correspondence is not really about speed. It is about being unable to tell the difference between being considered and being forgotten, which is a distinction one sentence can resolve.

Organisations worked this out some time ago, which is why an automatic acknowledgement is now standard on almost any form of contact. The individual version has spread more slowly, partly because a holding reply feels like a non-answer to the person sending it and partly because it takes a certain confidence to send something that contains no information beyond its own existence. Its existence is the information, and the recipient values it accordingly.

Groups develop their own local rhythms

Within any team, family or long-standing correspondence, expectations settle at some level and then become the local norm regardless of what the channel would otherwise imply. A group used to replying within minutes reads an hour as a delay. A group used to weekly exchanges reads a same-day reply as slightly urgent.

Newcomers cannot see the local rhythm and inevitably misjudge it in one direction or the other. It also drifts: an office that answered messages within the hour during a busy period tends to keep the habit afterwards, and the expectation is then applied to matters that never needed it. Neither the establishment nor the drift is anybody’s decision, which is a fair description of most conventions.

Managing an expectation you did not agree to

The workable approach is to state the rhythm rather than to try and meet an unstated one. Saying which channel reaches you quickly, and roughly when you deal with messages, replaces guesswork with information, and most people adjust to a stated norm without objection.

And when reading a delay, it is worth remembering how many ordinary explanations sit between a message and a reply: filtering, a notification cleared while doing something else, a draft written and never sent, a full week that simply went. Silence is genuinely ambiguous, and the convention that produces most of the trouble here is not the response time itself. It is the widespread habit of treating an absence of words as though it were a choice of them.

Common questions

Does a read receipt oblige a quick reply?

Not formally, but it removes the ambiguity that used to make a delay comfortable, so silence after a visible read is more likely to be interpreted as deliberate. A brief acknowledgement resolves this at very little cost.

Which channel should I use for something urgent?

The one with the fastest conventional turnaround that the recipient actually monitors, which is not always the fastest channel available. Marking a message urgent within a slow channel rarely overrides that channel’s normal rhythm.

Is it acceptable to reply days later?

It depends entirely on the channel and the local norm within the relationship, both of which vary widely. Where a reply will take time, a short note confirming receipt is the convention that prevents the delay from being read as a message in its own right.

Unwritten Rulesconventionmessagesetiquetteunwritten
Amrita Kohli
Contributing editor, What Nobody Explains

Amrita has been reporting on behind the counter, paperwork, queues & waiting since long before it was fashionable and thinks most subjects are more interesting once you know how they work.