Email escalation is a workplace art form. It follows a consistent pattern, with each rung of the ladder representing a higher level of formality, urgency, and implied consequence.
Rung 1: The Initial Request
A friendly email. Conversational tone. No deadline stated. "Hey, when you get a chance, could you take a look at this?" The sender expects a response within a day or two. This is the baseline.
Rung 2: The Gentle Follow-Up
"Just wanted to follow up on my email from Tuesday." Still friendly. Slightly more formal. The sender is signalling that they noticed the lack of response. The recipient understands this. A response is now expected promptly.
Rung 3: The Formal Reminder
"I wanted to circle back on this as we're approaching the deadline." The tone has shifted. There is now a deadline. The word "circle back" is doing significant work. The recipient understands that the situation has moved from casual to tracked.
Rung 4: The CC Addition
A manager or senior colleague is added to the CC field. No explanation is given for the addition. None is needed. The recipient understands that the communication is now on record and that a third party is aware of the situation. Response time drops significantly.
Rung 5: The Formal Escalation
A new email is sent directly to the manager, with the original thread forwarded. "I wanted to make you aware of this situation." This is no longer a request. It is a report. The original recipient is now in a reactive position.
Rung 6: The Meeting Request
A meeting is scheduled to discuss the email thread. The email has become a meeting. This is the final escalation. Whatever was in the original email is now a formal agenda item.
How to avoid the ladder
Respond to emails. Specifically, respond to emails that require a response, even if the response is "I've seen this and will get back to you by Thursday." An acknowledgement prevents escalation. Silence invites it.
The observation: Most email escalations are preventable with a single timely response. The escalation is not caused by the original request. It is caused by the absence of a response to it.