Your Team Isn't Taking Vacation. That's a Management Problem

It's October. Your strongest engineer has 19 days of vacation left, and when you ask, you get "I'll probably take some in December." You both know how December goes. They'll evaporate against the carryover cap or turn into a distracted half-week between holidays that rests nobody.

The comfortable reading: this person is dedicated. The accurate one: something on your team makes taking vacation feel expensive, and finding it is your job, not theirs.

Almost nobody is actually told no

When Pew Research Center surveyed US workers in February 2023, 46% of those with paid time off said they take less than they're allowed. The reasons are the interesting part: 49% worried about falling behind, 43% felt bad about co-workers absorbing their work, 19% thought it might hurt their advancement. Only 12% said a manager actively discourages them.

Notice the gap: the leave goes untaken with almost nobody told no. The discouragement is structural, so "please take your vacation!" announcements achieve nothing. You have to remove the reasons the permission feels fake. (American numbers, but I've yet to meet a European team where the mechanics differ.)

Four causes, and the tell for each

Coverage anxiety. They're the only person who can do X, and they know it. Vacation means X stops, or gets done from a beach. The tell: they only ever book the weeks when "nothing is happening," and there is no such week. Ask what would have to be true for a two-week September holiday; the answer is a handover list with no names on it.

Manager modeling. You say vacation matters. You took four scattered days last year and answered Slack on all of them. People calibrate on what you do, because that's what gets rewarded. The tell: requests arrive with apologies. When someone says "sorry, I know the timing's bad" about a contractual right, they learned somewhere that using it is an imposition.

"Unlimited" ambiguity. A number is permission you can point at: "I've used 12 of my 26." Unlimited removes the number and replaces it with a judgment call about what's "reasonable," made by the person with the most to lose from guessing high. The tell: you run an unlimited policy and can't say what a normal year of vacation looks like on your team. Nobody else can either, so everyone rounds down.

Review-season signaling. If time off reads as lower commitment in calibration discussions or big-project staffing, people notice long before anyone says it out loud. The tell: requests go quiet in the run-up to performance reviews, and your highest performers hold the largest balances.

Which of these is true on your team? Usually two at once, and one of them is modeling.

What actually moves the number

Take a real vacation yourself. This is the highest-leverage act available, and it's free. Two consecutive weeks, actually offline, decisions delegated by name before you leave. A manager who vanishes for a fortnight and comes back to a functioning team has said "this is safe" more convincingly than any policy document. If you can't, you've found a real operational problem, with the seniority to fix it.

Set minimums, not unlimited. Generosity works better as a floor: everyone takes at least 20 days a year, including one block of two consecutive weeks. A minimum is measurable, and it converts "am I taking too much?" into "have I met the bar?"

Make coverage a plan, not a scramble. Coverage anxiety feeds on vagueness, so kill it with structure: every request names who covers, the cover agrees, and the handover is a written list. When covering for each other is routine traffic, the guilt drains out of being covered for.

Book the big blocks in Q1. In January, everyone puts their main vacation block on the shared calendar. Provisional is fine. Conflicts surface in February when they cost nothing, and coverage gets planned months ahead instead of days.

What doesn't

The year-end use-it-or-lose-it panic. It produces half the team off at once in the year's worst coverage window, burning days because they'd expire rather than because anyone planned to rest. If Q4 is a scramble, the failure happened in Q1.

Wellness emails. A "remember to recharge!" note landing on a team whose manager hasn't taken a full week in two years reads exactly the way you'd expect. When words and behavior disagree, everyone believes the behavior.

The script for the hoarder conversation

Have it in a 1:1, by October at the latest.

Open with the number, not with concern: "You've got 19 days left and it's October. I want at least ten of them booked, and the first week on the calendar by Friday."

They'll say there's no good time. "There isn't one. Pick the least bad week and coverage becomes my problem: tell me what needs holding and I'll put a name next to each item."

They'll say the project will slip. "The project can survive a week. If it truly can't survive a week without you, we have a bigger problem than your vacation, and I'd rather find it during a planned week than in an emergency."

The unspoken worry is usually "will this be held against me," so answer it unprompted: "Nothing about this counts against you. The opposite. I'm asking because I want you doing this job next year, not resigning from it in March."

Then keep the promise. No "quick calls" during their week. Drag one person back from a beach and you've undone every word of that script, for the whole team, for a year.

The version your accountant sees

The burnout cost is real but fuzzy; the financial cost is neither. Every accrued, untaken day is a debt owed at that person's current salary, and it gets more expensive with every raise. In SquadBear it's a report, not a spreadsheet dig: Insights → Leave reports snapshots each person's remaining balance per leave type for the year, with a CSV for finance. Unlimited leave types carry no balance, so they never appear there. One more thing "unlimited" hides.

Where the plumbing helps

Full disclosure: we make an HR tool, and this playbook shaped it. A vacation request in SquadBear can't be submitted without naming a replacement, the colleague accepts or declines the cover themselves, and the assignment is checked for scheduling conflicts. So "who's holding this while you're out" is answered before the approval, not discovered after it.

If your team runs a connected AI assistant, there's one more gentle unblock: it can read the team calendar and suggest quiet weeks. Turning "there's no good time" into three concrete candidates is often all the nudge a hoarder needs.

Start free or ask the demo to find the biggest balance on the sample team.

Related reading: the Bradford factor on reading absence patterns without weaponizing them, and PTO accrual, explained for the carryover mechanics behind the December scramble.