When the Ball Is in Another Court: A Calm Escalation Ladder for Year-End Dependencies
Year-end work has a particular weakness: the final delivery often depends on someone else's small piece of work. A client has to approve copy. A supplier has to confirm a date. A colleague has to send a figure, a signature, or a decision. The deadline is yours, but the next move is not. In that situation, polite chasing is necessary. A sequence of polite chases without trigger points, however, is just anxiety with better manners.
Chasing is not escalating
Chasing repeats the request. Escalating changes the conditions around the request. A second reminder may be appropriate. A fourth reminder sent quietly, with no change in visibility or ownership, is usually a sign that the process has stopped working.
The ladder below is designed to keep the relationship formal and intact while making the risk visible early enough to act on it. It works best when it is set up before the pressure arrives.
Start with a dependency register
Before sending any email, list every item you are waiting for. For each item, record the deliverable, the named owner, the date it was promised, the date you actually need it, and the effect if it is late. A named person is essential. A team inbox is not an owner; it is a hope.
The register does not need to be complex. A single sheet with five columns is enough. The discipline is in reviewing it every Monday and Thursday during the final six weeks of the year. If an item is not in the register, it is not being managed.
The four-rung ladder
Use working days rather than calendar days. Year-end has enough weekends and bank holidays without adding confusion.
Rung one: confirm at T-10
At least ten working days before your deadline, confirm the item, the owner, and the agreed date in writing. This is not a chase. It is a record.
Subject: Confirming the approved copy for 18 December
Hello Sam,
I am planning the final pack against the 18 December deadline. Please confirm that you will send the approved copy by Wednesday 9 December. If that date has changed, please reply with the new date and any effect on the pack.
Thank you, Alex
Rung two: nudge at T-5
Five working days before the deadline, send a short date check. Keep it factual. Do not add a paragraph about how busy you are.
Subject: Copy for 18 December — date check
Hello Sam,
A short check against the date we agreed. The approved copy is due on Wednesday 9 December. Is it still on track? A one-line reply is enough.
Thank you, Alex
Rung three: direct chase at T-2
Two working days before the deadline, ask for a decision rather than a general update. The useful question is not whether the item is being worked on. It is whether it will arrive in time.
Subject: Approved copy — decision needed by 12pm Thursday
Hello Sam,
I need to know whether the approved copy will arrive by Wednesday 9 December. If it will not, I need the new date today so I can re-plan the review and design stages. Please reply by 12pm on Thursday with either confirmation or the revised date.
Thank you, Alex
Rung four: flag risk at breach
If the agreed date passes, or if the remaining real working days are no longer enough to complete the task, stop chasing quietly. Send a risk note to the owner and copy the relevant sponsor or account lead. State the facts, the impact, and the decision required.
Subject: Risk to 18 December pack — approved copy not received
Hello Sam,
The approved copy was due on 9 December and has not arrived. The remaining working days are not enough to complete review and design without moving the 18 December date. I am flagging this as a risk today. Please confirm by 12pm tomorrow whether the copy can be sent by 10 December. If not, we will need to agree a revised delivery date.
Thank you, Alex
When to flag risk rather than keep chasing
The rule is simple. Flag risk when any one of the following is true:
- The agreed date has passed.
- The remaining real working days are fewer than the task needs, including buffer.
- Two chases have produced no substantive reply.
- The dependency affects an external commitment, such as a client launch or a regulatory date.
- The owner has changed, left, or become unavailable.
At that point, do not send a fourth polite nudge. Send a risk note with a decision request. The note should make clear what is needed, by when, and what happens if it is not received.
Keep the tone formal and factual
Use dates, not adjectives. Avoid urgent, as per my last email, and any suggestion that the other person has failed. Say what is needed, when it is needed, and why the date matters. If a call would be faster, make the call and then confirm the outcome in writing. A short written record is not distrust; it is how dependencies stay manageable.
Make the ladder visible
A follow-up ladder only works if it is known to exist. Share it with your team, record the rung dates in the calendar, and review the dependency register twice a week. The aim is not to threaten the other party. It is to protect both the relationship and the deadline by making the next step predictable. When the ball is in another court, the calmest thing you can do is agree when you will ask for it back.
