How to ask for coverage before your parental leave

Most product managers going out on leave don't ask for coverage. Not because they don't want it — because asking feels like admitting you're a problem to be solved.

It isn't. Raising coverage is the single most useful thing you can do for the team you're leaving behind, and it happens to also be the thing that protects what you come back to. The trick is framing, and the framing is simple: this is a continuity plan, not a personal request.

Start earlier than feels necessary

Three to four months out. That sounds absurdly early when you're still not sure you've told everyone, but the timeline isn't about you — it's about how budget works. Your manager needs to scope the gap, find money that probably wasn't allocated, and get it approved by someone who wasn't in the conversation. That's a six-week process at a healthy company and longer at a big one.

Ask at six weeks out and the honest answer will be that there's no time and no budget. Ask at four months and you're a manager who plans ahead.

Do the inventory before the conversation

Walk in with a document. Not a polished deck — a working list that makes the shape of the gap visible, because your manager almost certainly cannot see it. They know your outcomes. They don't know the forty small things you hold.

Sort what you own into three buckets:

• Must keep moving. Anything with a customer commitment, a contract date, or a dependency another team is building against.
• Can pause. Be generous here. Volunteering what's deferrable makes the first bucket credible, and a list where everything is critical reads as self-important rather than thorough.
• Someone else already partly holds it. The threads where a designer or an engineering lead is already half-owning the work.

Then add the part nobody documents: the stakeholder relationships that run through you, the decisions expected to land during your window, and the reasoning behind the last two quarters of tradeoffs. That last one is the real asset. It exists only in your head, and it's what makes the difference between coverage and someone sitting in your chair.

Frame it as risk, not as need

This is where most of these conversations go sideways. "I'm worried about what happens to my projects" invites reassurance — don't worry, we'll figure it out, focus on the baby — which is kind and resolves nothing.

"Here's what's exposed in Q2 and here's what I'd do about it" invites a decision. Same content. Entirely different conversation.

Notice what that does. It names the exposure specifically. It names who absorbs the cost otherwise. It proposes a solution rather than presenting a problem. And it offers your own effort toward the fix, which is what separates a plan from a complaint.

Expect the three objections

"The team can absorb it." Sometimes true — worth taking seriously rather than arguing past. The useful response is specific rather than general: which person, for which piece, on top of what they're already carrying? Absorption sounds free right up until it has a name attached to it.

"There's no budget." Often means there's no allocated budget, which is a different problem and a solvable one four months out. It also usually means the cost of not covering hasn't been priced. A slipped quarter has a number. So does replacing a PM who leaves within a year of returning, which is what happens to about a third of women after parental leave — and the research points at what they came back to, not at what they wanted.

"We'll sort it out closer to the time." The most common and the most costly. Closer to the time means no overlap, and the overlap is where nearly all the value sits. Someone starting two weeks before you leave can absorb your context directly. Someone starting the week after has to reconstruct it from artifacts, which takes twice as long and loses the parts that were never written down.

Ask to be part of the handoff

If coverage gets approved, ask for two to three weeks of overlap while you're still in seat — shadowed standups, stakeholder introductions, a walk through the decisions behind the roadmap. It's the difference between a baton pass and a folder dump.

And ask for something on the return: a decision log kept while you're out, and a real briefing when you come back. Not a thousand unread emails and a calendar that filled itself. That request is easy to grant and almost never made.

One last thing

You're not asking for a favor. You're identifying a foreseeable risk to work the company cares about and proposing a way to manage it, months ahead, with a plan attached. That's the job. It's arguably the most product-manager thing you'll do all year.

If it helps to point your manager at something concrete, this walks through the three options and what each actually costs, and this is how a coverage engagement is structured.

If it helps to send your manager something written for them, this lays out the three options and what each costs.