The short version
- When a delivery lead is away, the plan does not stop existing. It stops being retrievable, which looks identical from the outside.
- The lead holds three things nobody else has: the sequence, the commitments, and the reasons behind both.
- Scope the coverage to the project rather than to the person. Stakeholders need answers about the project, not about the lead.
- The project's own record should answer where things stand and what was agreed, while the deputy handles trade-offs.
A delivery lead's absence has a distinctive signature. Nothing dramatic happens on day one. By day three, two decisions are pending. By day five, a stakeholder is asking someone who does not know, getting a hedged answer, and escalating. By the second week the project has not moved and nobody can point to the moment it stopped.
"The project pauses for a week because the one person who knows the plan is skiing."
What the delivery lead actually holds
Three things, and only the first is in the plan.
The sequence. Why this before that, which dependencies are real and which are conventional, and what can be resequenced without cost. The board shows the order and not the reasoning.
The commitments. Who was promised what, in what words, and how firm each promise was. Much of this lives in conversations rather than documents.
The trade-off space. What can be cut, what cannot, and what has already been offered up in a previous negotiation. This is the part a deputy most needs and least often gets.
What stops, and what only appears to
| What people need | Genuinely blocked? |
|---|---|
| "Where is this up to?" | No, this is retrieval |
| "What did we agree with the customer?" | No, if it was written down |
| "Can we move this to next sprint?" | Only if nobody has the authority |
| "Do we cut scope or move the date?" | Yes, this needs a decider |
Only the bottom row genuinely requires a person with authority. The rest is retrieval, and it is the reason a project appears to pause: the plan exists, and the only interface to it was a person who is now on a mountain.
Cover the project, not the person
Here is the useful shift. Coverage is usually arranged around the absent individual, which is how it is described in the plan and how everyone thinks about it. But the people asking questions do not care about the individual, they care about the project.
So scope the record to the project. StandIn supports this directly with a Project StandIn: the project's own brief, drawn from what the people working on it wrote down, so anyone can ask where things stand, what was agreed, what is blocked, and who owns the call, and get an answer with a source under it, in the words of whoever recorded it. It never guesses, and when the answer is not in the record it says so and names who to ask.
That is a better fit than routing everything through a deputy, for two reasons. Stakeholders get a consistent answer regardless of who is away, and it keeps working when the lead is merely in a meeting, which is most of the time. See how StandIn works and retire your out-of-office.
What the deputy needs
With retrieval handled, the deputy's job narrows to trade-offs, which is what a deputy can actually do well. Give them three things before the lead leaves.
- The trade-off map. What can be cut, in what order, and what has already been promised away. One page.
- A spending and scope limit. Specific, with numbers. "Move anything within the sprint; do not change the release date."
- Named stakeholder contacts. Who to tell when something changes, and which ones need warning rather than notification.
And tell the stakeholders who the deputy is, in writing, before the leave starts. A deputy the stakeholders have not been introduced to will be bypassed within two days.
Common Questions
How do you keep a project moving when the delivery lead is away?
Make the project's state and agreements retrievable without the lead, and give one named deputy explicit authority over trade-offs within stated limits. Most of what appears blocked is retrieval, not decisions.
Should the deputy be a team member or another lead?
Usually a team member who knows the work, with another lead available for escalation. Someone who knows the project and lacks authority is a better deputy than someone with authority and no context, provided you grant the authority explicitly.
What about the stakeholders who only ever ask the lead?
Introduce the deputy in writing before the absence and give the stakeholders a way to get state answers without a person. Stakeholders route to the lead out of habit, and habits change when the alternative is faster.
How do we avoid a queue building up for the lead's return?
Require that anything deferred is recorded with a date and a reason, and reviewed mid-absence by the deputy. Silent deferrals are what produce a two-week queue, and half of them turn out to be things the deputy could have handled.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.