Her Manager Gave Her Maternity Leave Work to a Male Colleague — Then HR Had a Much Longer Conversation Than Expected

By the time her out-of-office email switched on, Mara thought she’d done everything the “right” way. She’d mapped out deadlines, trained a backup, and left a clean handoff doc for the month she’d be out after giving birth. Her team had praised the planning, and her manager had thanked her for being so organized.

Two weeks into leave, a colleague texted her a screenshot that made her stomach drop. A project Mara had been leading for nearly a year—one tied to performance reviews and a bonus pool—had been reassigned to a male coworker, along with a handful of her higher-visibility accounts. The message wasn’t framed as temporary coverage. It read like a reshuffle.

The “coverage plan” looked like a quiet replacement

Mara didn’t want to be the person working during maternity leave, but she also knew the cost of staying silent. The project in question was the kind that gets brought up in leadership meetings, the kind that turns into an “impact story” later. And the new owner wasn’t just any teammate; it was a mid-level analyst who’d been vocal about wanting “more face time” with executives.

She checked her work apps and saw calendar invites she wasn’t included on anymore. Notes from meetings were being filed in a folder she no longer had permission to edit. When she asked her manager—politely, and in writing—whether the change was temporary, she got a short reply: the team was “moving fast” and needed “steady coverage.”

That phrasing stuck with her. She had been steady. Her planning had been steady. The only change was that she wasn’t physically at her desk.

Then the requests started coming back to her anyway

The weirdest part was that Mara was still being pulled in to do pieces of the work. She began receiving forwarded emails from her manager with questions attached, even though the male colleague now “owned” the project. The coworker would ask for the context behind decisions Mara had made months earlier, or where a particular file lived, or how she’d handled a temperamental stakeholder.

At first, she answered quickly. She told herself it was one-time. Then it happened again, and again. She was feeding someone the institutional knowledge to run the exact work she’d been removed from, during a period of time she was supposed to be recovering, sleeping in fragments, and adjusting to an entirely new routine.

After a week of that, Mara started saving everything. Screenshots of reassignment messages. The email thread where her manager used “steady coverage” as a reason. Calendar changes. Even the small stuff, like a Slack message where the coworker mentioned presenting “my project” to directors.

She looped in HR expecting a quick clarification

Mara didn’t come in swinging. She asked HR for guidance on whether it was standard practice to permanently reassign a role’s signature project during protected leave, and whether she was expected to keep supporting it. She offered to jump on a brief call—ten minutes, she said—because she didn’t want to make a big deal out of something that could be a misunderstanding.

The meeting invite that arrived wasn’t ten minutes. It was scheduled for an hour, and it included an HR business partner plus someone from HR compliance. Her manager was also invited, which changed the tone immediately. This wasn’t a friendly “let’s clear it up.” It was a sit-down.

Before the call, HR asked Mara to forward any documentation she had regarding the reassignment and any work requests she’d been receiving while on leave. She sent a neat packet of emails and screenshots in chronological order. She also included her original coverage plan, which clearly described the project as returning to her when she came back.

The conversation got longer, and her manager got careful

Once everyone was on the call, HR didn’t start with pleasantries. They asked Mara to describe the sequence of events, then asked her manager to explain why the project had been moved and whether it was intended to return to Mara after leave. The manager initially framed it as “redistribution” because of business needs.

Then HR asked why the male colleague had been given the leadership-facing pieces specifically, while Mara’s lower-visibility tasks were left in a shared queue. They asked why Mara’s access permissions had been changed. They asked why she was being contacted for work during leave if she wasn’t the project lead anymore.

The manager’s answers got more and more vague. HR kept circling back to the same point: if Mara was on leave, she should not be expected to perform work. And if she wasn’t the lead, the company needed to be able to justify why a long-term assignment was reassigned during her absence, and what the plan was for returning it.

That’s when the “quick clarification” turned into a longer-than-expected discussion about policy, documentation, and risk. HR asked for the reassignment decision trail and who approved it. They asked whether similar reassignments had happened when other employees took medical leave. The manager started using phrases like “temporary” and “interim” that hadn’t appeared in writing before.

The practical consequences showed up fast

Within a day, Mara noticed changes. The male colleague stopped messaging her for help. A group email went out clarifying that Mara remained the project owner and that the colleague was “covering execution” while she was out. Her folder permissions were restored.

But it didn’t feel like a clean win. The coworker had already presented in meetings she should have led, and stakeholders had started treating him as the main contact. There was also the unspoken reality that her manager now knew she’d gone to HR, and she would eventually have to return to that same manager’s team.

HR scheduled a follow-up, this time without her manager, and asked Mara what she wanted as an outcome. She asked for three things: no work contact during leave unless there was a true emergency, a written plan confirming the project would return to her on her return date, and a commitment that her performance review would reflect her work up to leave, not a comparison against someone covering while she was out.

HR didn’t promise everything immediately, but they did put the requests in writing and said they’d be reviewed with leadership. They also asked Mara to flag any retaliation concerns, which was a sentence that landed with weight.

People focused on paper trails and boundaries

When Mara described the situation to a few trusted peers, the advice was blunt and practical. Keep everything in writing. Stop “helping” unless HR says she’s expected to work. If she had to respond to anything, respond once and redirect: she’s on leave, and the coverage lead should handle it.

Others told her to document the before-and-after: what she owned prior to leave, what changed, and what was being said about ownership in meetings. A couple of colleagues pointed out that the most dangerous part wasn’t the reassignment itself—it was the quiet rewrite of her value while she was gone. If leadership got used to seeing a different name on the deck, the “temporary” arrangement could turn permanent in practice even if HR reversed it on paper.

Several people emphasized boundaries for a different reason: if she kept contributing while on leave, it could muddy the issue. It could be reframed later as her “choosing” to work, or as proof the team “needed” the reassignment. The cleanest line was a true leave: no tasks, no deliverables, no coaching someone into taking credit.

Mara ended up sending one final email to her manager and the coverage colleague, with HR copied, reiterating her leave dates and directing all project questions to the interim lead. After that, she went quiet.

The project will still be there when she returns, at least on the org chart. The bigger question is whether she’ll be walking back into the same role she left, or into a version of it that’s been slowly reshaped around someone else’s visibility. For now, she has the one thing that tends to matter most in these workplace fights: a clear trail showing exactly what changed, when it changed, and who tried to make it seem normal.