He Worked 60 Hour Weeks Covering a Coworker’s “Compassionate Leave,” Then Found His Mom’s Fine and He’s in Bali
Three weeks ago, a coworker went to management in tears claiming his mother had been diagnosed with a severe, late-stage illness overseas, requesting extended paid leave under the compassionate care policy. Management approved it immediately, paid him out, and split his workload between two remaining team members. Since then, the weeks have run 60-plus hours, real exhaustion absorbed willingly under the belief that this was genuinely helping someone through a devastating loss.
Yesterday, while setting up a shared directory using his old work profile, an open personal browser tab revealed an active travel itinerary for a month-long luxury vacation in Bali, booked weeks before he ever made the leave request. A WhatsApp Web message from his mother, sent that same day, asked whether he’d remembered to water her plants back at her house down the street. She isn’t sick. She’s fine, and living nearby.
Context Matters
The distinction between what was seen and how it was seen matters here, and it’s worth being clear-eyed about it. This wasn’t the result of deliberately searching through someone’s personal accounts. It happened while doing legitimate, work-related setup on a shared company device using his logged-in work profile, and the information appeared unprompted, not sought out. That context matters both for personal peace of mind and for how this gets framed if it needs to be raised formally later.
Staying Silent Isn’t a Real Option Long-Term
Continuing to absorb another month or more of doubled workload while knowing the underlying justification is fabricated isn’t sustainable, physically or emotionally. The resentment already building will only compound the longer this continues, and burnout from unsustainable hours doesn’t resolve itself just because the reason behind it stays hidden. Beyond the personal cost, there’s also a legitimate integrity issue at stake, a paid leave policy meant for genuine compassionate circumstances is actively being exploited, and staying quiet means indirectly enabling that exploitation to continue.
Reporting This Doesn’t Require Framing It as Personal Suspicion
Going to a manager or HR doesn’t need to be framed as “I think Dan is lying” based on a hunch or gut feeling. It can be framed factually and narrowly: information was inadvertently seen while performing legitimate work tasks that raises serious concerns about the basis for the approved leave, and given the workload impact this has created, it needs to be flagged. That framing keeps the report grounded in observed fact rather than personal accusation, and it appropriately shifts the actual investigation and verification work onto HR, where it belongs, rather than requiring anyone else to play detective or make a final judgment call themselves.
This Isn’t About Being a Snitch
There’s a meaningful difference between reporting a coworker’s minor personal choices out of spite or nosiness, and flagging a fabricated medical emergency that’s directly resulted in a colleague working unsustainable hours for weeks while paid leave gets granted under false pretenses. This isn’t a petty grievance or an attempt to get someone in trouble for its own sake. It’s a legitimate workplace integrity concern with direct, ongoing personal impact, exactly the kind of situation HR processes exist to handle.
Worth remembering too that this isn’t a victimless situation being kept quiet for someone’s benefit. Real hours, real stress, and real personal cost have already been paid to cover this fabricated story, and that cost is set to continue indefinitely if nothing changes.
Documenting Everything Before Raising It Formally
Before going to HR or management, writing down exactly what was seen, the specific browser tab, the itinerary details, the WhatsApp message content, along with the date and circumstances under which it was encountered, creates a clear, factual record to work from. Screenshots weren’t necessarily taken in the moment, which is understandable, but writing down as much specific detail as possible while it’s still fresh strengthens the eventual report and reduces the risk of it being dismissed as vague or unreliable secondhand information.
Protecting Standing by Going Through the Right Channel
Approaching HR directly, rather than management alone, is likely the better first move here, since HR is specifically equipped to investigate policy misuse without the same interpersonal complications that come with going through a manager who’s already emotionally invested in believing the original story. Framing the report around workload sustainability and policy integrity, rather than around exposing a lie for its own sake, keeps the focus on legitimate business concerns rather than personal conflict, which protects standing within the team regardless of how the investigation ultimately unfolds.
Where This Leaves the Decision
Reporting this factually and through HR, rather than absorbing continued unsustainable hours to protect someone else’s fabricated story, is the reasonable path forward. The discomfort of triggering an investigation in a small team is real, but it doesn’t outweigh the ongoing cost of silence, both personally and in terms of enabling a clear misuse of a policy meant for people actually facing the situation being claimed. Staying factual, documenting what was seen, and routing it through HR rather than informal team gossip gives the best chance of resolving this without it becoming personal, even though some disruption to the team’s dynamic is likely unavoidable once the truth comes out.
Featured on Happy From Home:
