The “Pretend Time Off” Trap

Employees are “taking” PTO while secretly still working. It burns people out, wrecks morale when behaviors and expectations vary within the organization, and creates genuine legal liability. What is the use of “PTO” culture at your organization?  This is not what is stated, of course, but it’s the reality for you and your team? 

We all see it: an employee takes an official PTO day, yet despite the “out of office” message, the status dot stays stubbornly green. We check our email. We pop in for a quick meeting. We answer our phone. Our outfit, laptop setup, and physical location may change, but work “presence” remains the same. 

This is “Pretend Time Off” (also known as “quiet vacationing”). Employees step away from the office physically, but stay mentally chained to the grid—held hostage by fear, guilt, or the terror of a haunted inbox.  Public sector, private sector—it makes no difference. The data is blunt: nearly half of workers admit they cannot fully unplug on vacation. The result is not a refreshed teammate; it’s an exhausted employee who has traded their office desk for a beach chair while answering emails.

Why “Fake Rest” Harms the Whole Business

An employee who works through during PTO might look dedicated, but in reality, they’re a walking alarm for your organization.

  • The Illusion of Recovery: Brains do not recharge while monitoring an inbox. Coming back from a fake vacation feels like waking from a nap taken with one eye open.
  • Single-Point-of-Failure Risk: If a process collapses when someone steps away for three days, that is not loyalty—it is a critical lack of cross-training, even if it is presented as loyalty.
  • Cultural Contagion: When leaders “just check in real quick” from a beach, junior staff hears the real message: PTO is just remote work with better scenery.

⚠️The Compliance Risk Hidden in Plain Sight

This isn’t just an organizational vibe issue—it’s a legal exposure risk:

  1. Unpaid Overtime Liability: If non-exempt employees process emails during PTO, that time may be legally compensable, quietly racking up overtime costs.
  2. “Right to Disconnect” Rules: A growing number of jurisdictions are introducing strict regulations surrounding after-hours work communication.
  3. Unused Accrual Liabilities: In states where accrued PTO is treated as earned wages, team members who never truly step away (and thus accumulate unused leave) create massive balance-sheet liabilities.

How Leaders Can Fix It Today

Stopping this isn’t about rewriting the handbook; it’s about shifting behavior. Here is the playbook:

1. Practice “Loud Disconnection”

Leaders must go first. Draft an out-of-office auto-reply that states clearly:

“I am fully offline until [Date] and will not be checking messages.”

Then—wild concept—actually mean it. When teams watch a manager vanish and return completely fine, it permits everyone else to do the same.

2. Designate Real Air Cover

People rarely monitor email on vacation for fun; they do it because they fear the mountain of work upon their return. Assign a specific point-person to handle urgent requests before the vacation starts. Nothing stops the urge to “just check in” like knowing someone else has it covered.

3. Honor the Out-of-Office Boundary

Avoid sending “No rush, just flagging for when you’re back” messages. The notification will pop up, interrupting their mental break anyway. Let a boundary be a real boundary.

The Bottom Line

Rest is not a soft perk—it is critical maintenance required to keep high performers operating at their best.  If your organization offers PTO, ensure your people can actually use it. Leadership is not replying to Slack messages from a hammock; it is stepping away, trusting your team, and coming back sharp instead of just tan.

Work/Life balance issues are challenging enough without this trend. We need to be actively discussing the importance of taking a break and “give permission” to ourselves and our team to truly disconnect and recharge.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *