The Skip-Level Handshake: Holding the Line When Your Manager Goes Mid-Quarter

There is a particular kind of silence that follows a manager leaving mid-quarter. The calendar still has their meetings in it. The team still has their deadlines. Someone from two levels up sends a cheerful note saying a replacement will be confirmed “in due course”, which in UK workplace language can mean anything from three weeks to the other side of the next financial year.

And then everyone looks at you — often the least senior person in the room — because you are the one who knows where the files are.

This is not a promotion. It is a gap. Leading through it is less about grabbing authority and more about keeping the work steady while the organisation catches up. Get it right and you become known as someone who can be trusted with ambiguity. Get it wrong and you become known as someone who either went quiet or started acting like the job was already theirs.

First 72 hours: stabilise, don’t speculate

The temptation in the first few days is to fill the silence with theories. Was it planned? Is the team being restructured? Who is really in charge now? Resist most of that. You will not have good answers, and guessing out loud creates more anxiety than it settles.

Instead, do three unglamorous things.

First, confirm the reporting line in writing. A short note to the skip-level manager is enough: “Just to confirm — until the vacancy is filled, should day-to-day queries come to me, or would you prefer a different route?” That question sounds small. It is not. It gives the more senior person a chance to clarify without you demanding a title.

Second, make a simple list of what the team owes and when. Deadlines, commitments, pending approvals, anything that will break if nobody touches it. Keep it to one page. You are not building a case for yourself; you are building a map for whoever steps in.

Third, hold a short team huddle. Not a dramatic all-hands. Fifteen minutes, same day, with a clear message: “We are keeping things moving while the arrangements are confirmed. If something needs a decision above me, I will route it and come back to you.” People do not need certainty to feel calmer. They need a route.

The skip-level agreement

Once the initial dust settles, ask the skip-level manager for twenty minutes. Go in with an agenda, not a speech. The aim is to agree three things: what you can decide, what needs their sign-off, and how often they want an update.

Use plain language. “For the next fortnight, how would you like customer refunds handled?” is a better question than “Am I in charge?” The first gets you a practical answer. The second makes everyone uncomfortable.

It also helps to agree a review date. “Shall we check this arrangement again in three weeks?” sounds temporary and sensible. It signals that you are not trying to annex the role, while also giving you a natural moment to raise problems if the gap drags on.

If the skip-level is remote or very senior, keep the agreement to a short email after the call. Three bullet points is plenty: decisions you will make, decisions they will make, and the update rhythm. That email is not a bid for attention. It is a working agreement.

Protect the workload, including your own

When a manager leaves, their inbox does not disappear. It gets redistributed, often by gravity, to whoever answers quickest. You can easily end up doing three jobs badly and calling it leadership.

So set a simple triage rule for the team: new requests get acknowledged, not automatically accepted. “I’ll check where that fits and come back to you” is a complete sentence. It buys you time without being rude.

Then look at what can wait. Some work is genuinely urgent. Some is urgent because someone else is anxious. Some is just habitual. In a gap, you have licence to ask whether a recurring report still needs to exist this month, or whether a non-critical project can slip a week. Ask the question politely and in writing.

You also need cover for your own work. It is easy to absorb the missing manager’s tasks and forget that your own deadlines have not moved. Tell the skip-level plainly: “I can cover these two things well, but if the third stays with me, my own project will slip. Which would you rather I prioritise?” That is not a complaint. It is a trade-off being made visible.

Document decisions without looking like you’re auditioning

A decision log is your friend. Keep it boring: date, decision, who agreed it, and when it will be reviewed. Share it with the people who need it. Do not write it like a personal diary of your achievements. Nobody needs “I led the discussion” in a document that is meant to keep work moving.

A weekly two-line update to the skip-level is usually enough: what moved, what is stuck, what you need. That is the quiet paper trail. It protects you if a decision is questioned later, and it makes handover easier when the new manager finally arrives.

What you do not need is a trail of unnecessary CCs designed to prove you were there. Visibility is not the same as usefulness. Copy the people who need to know, not everyone who might be impressed.

Keep your own head above the water

The gap can last longer than anyone promised. If it does, ask for a temporary arrangement to be formalised — not because you want the title, but because the team needs clarity and you need cover. A short review date, a named escalation route, and an agreement about workload are reasonable asks.

And keep an eye on your own development. Leading through a gap teaches you things a tidy job description never will: how to prioritise, how to communicate upwards, how to make decisions with incomplete information. Note what you are learning. Ask for feedback from the skip-level while the experience is fresh. That is not auditioning. That is using the situation well.

When the new manager eventually walks in, the best thing you can hand them is a team that still works, a decision log that makes sense, and a clear list of what needs their attention first. The gap is not your coronation. It is your chance to be steady. In most organisations, steady is rarer — and more valuable — than eager.