Six weeks. That’s how long a mid-size Boston agency scrambled to cover one account coordinator’s workload after she went out on approved leave, and the mess was entirely avoidable. Nobody had written down who owned her recurring tasks. The client found out from a missed deadline instead of a handoff email. The team survived, but the account nearly didn’t.
The leaves themselves usually aren’t the hard part. The coverage plan is. If you manage people or sit on a small team where everyone’s work touches everyone else’s, you’ll eventually face a stretch where a teammate is out for a few afternoons a week, or gone for a month, because they’re getting treated for anxiety. How you handle the handoff decides whether that person comes back to a functioning desk or a pile of resentment.
Here’s the part most coverage plans miss: the person going out is already carrying a full plate of logistics. Also, the team at MassBay Behavioral Health tend to see patients arrive at leave planning exhausted from trying to schedule around a job, so anything you as a manager can absorb on the admin side buys them energy for actual recovery. Your job in the next few weeks isn’t to ask why. It’s to build the net.
What does coverage actually look like when leave is intermittent?
Intermittent leave is the sneaky one. Under frameworks like the federal Family and Medical Leave Act, covered employees can take leave in separate blocks or on a reduced schedule, and state programs often follow the same pattern. Read the basics on the Department of Labor site if you want the framing straight from the source.
Translated into your Tuesday: someone is gone every Monday and Thursday morning for therapy or a partial program, and the rest of the week they’re at their desk. That’s harder to plan around than a clean one-month absence, because the work keeps flowing and the gaps keep shifting.
My rule for intermittent coverage is blunt. Pick two or three tasks that only you or one other person touch while the leave is active, and freeze the rest of their plate. A frozen plate looks bad on a status board. It beats a half-covered one that quietly rots.
Build the handoff map before anyone walks out the door
This is where the agency in my opening example went wrong, and where most teams repeat the mistake. Nobody ran a handoff map, so the coordinator’s calendar commitments lived only in her head.
The handoff map is simple and takes about an hour. Sit with the person and list every recurring commitment: standing meetings, weekly reports, vendor check-ins, the Slack channel where they’re the de facto answer person. For each item, write down three things.
- The trigger, meaning when it happens and what kicks it off
- The owner while they’re out, by name
- The thin version, which is the smallest acceptable output so nothing has to be perfect
That third column is the one people skip and later regret. If the person normally produces a polished twelve-slide client recap, the thin version is a five-bullet email. Naming that out loud gives the stand-in permission to do less, and permission is what keeps them from burning out mid-cover.
Protect the person’s privacy without hiding the leave
You don’t owe the team a diagnosis. You do owe them enough honesty to prevent gossip and guessing. The workable middle ground is a short, factual note: she’ll be out on approved medical leave through the middle of next month, here’s who’s covering which piece, route questions to that person.
What you never do is speculate in a team channel or let a rumor set the narrative. Under the Equal Employment Opportunity Commission rules, treating an employee differently because of a medical condition can cross into discrimination, and loose talk is where those cases often start. Say less, say it clearly, and enforce the boundary when someone pushes.
One more thing I’d push back on with any manager who’ll listen: don’t ask the person to draft the announcement while they’re still processing the decision. Draft it yourself. Let them approve it in two lines.
A concrete scenario, because abstractions hide the pain
Picture a nine-person customer support team where one agent handles all the tier-two escalations. She starts weekly treatment and takes a reduced schedule of thirty hours. If you do nothing, the other eight agents route escalations to her name out of habit, she returns to a triage backlog, and the whole team learns that going out on leave means coming back to punishment.
Do it differently. Two other agents split escalations by product line, and the queue gets a visible tag for anything that used to route to her. The team meets for ten minutes on Friday to review what got stuck. The whole fix costs maybe thirty minutes a week and removes the returning-employee landmine entirely.
The re-entry checklist nobody writes down
Return is a separate project from the leave itself. Work through this the week before they’re back.
- Clear the inbox of anything older than the first week, or archive it with a summary note.
- Hold all non-urgent decisions that touched them until day two or three, not day one.
- Schedule a short, informal check-in for the end of their first week and keep it about workload, not feelings.
- Update the handoff map in reverse, moving items back only when they say they’re ready.
Readiness at work usually trails readiness everywhere else. Someone can feel fine at home and still fold under their old calendar in week one, so give the ramp room to be slow.
Where managers get it wrong
The costly mistake isn’t scheduling or slack coverage. It’s treating the leave as a personal failing that the team must absorb quietly. That attitude leaks. It shows up as eye rolls in standup, as workload assigned to the returning employee out of “fairness,” as comments about who’s really pulling their weight.
Mental health conditions are common in the workforce, which is why organizations like the National Alliance on Mental Illness spend so much time on workplace awareness. The practical point: your team already knows someone who needs this kind of time. How you run the coverage signals whether the next person asks for help or hides it until things break.
What good coverage actually buys you
A coverage plan is a small piece of documentation you’ll use every time, not just for this leave. It catches vacations, parental leave, and sudden absences too. Build it once, keep it in the shared drive, and update it quarterly.
That’s the whole play. Map the work, name the owners, write the thin versions, and protect the person’s privacy while being honest with the team. Do that and the six-week scramble I described never happens, because nobody’s calendar is a secret held by one person.
If you’re the one who needs the leave, or the manager figuring out where to point your teammate for care, start with the coverage plan and let the paperwork follow. Which task on your team’s plate has exactly one owner right now?