Here's a conversation every manager has had:
"I need more hours."
"OK, can you work Saturday morning?"
"This Saturday? I can't do this one."
And the next Saturday. And the one after that.
It's the overtime paradox. Half your team says they want more hours. But when you actually offer the shifts, acceptance rates drop off a cliff. You end up short-staffed on the exact shifts you thought you had covered.
This isn't laziness. It's human nature. Understanding why it happens is the first step to scheduling around it.
Why the gap exists
When someone says "I want more hours," they're really saying "I want more money." Those sound like the same thing, but they're not.
More money is abstract. It feels good. It's financial breathing room, a paid-off bill, a weekend trip. When employees think about overtime, they picture the paycheck. Not the alarm clock at 5 AM. Not the missed birthday dinner.
When the actual shift shows up on their phone, the calculation changes. The money is still there, but now it has a price tag attached. A specific day. A specific time. A real tradeoff.
That's the paradox. The idea of overtime is always worth it. The reality of overtime depends on what else is happening that day.
The numbers are stark
Managers who start tracking overtime acceptance rates (not just requests) usually find something like this:
- Employees who say they want overtime: 60-70% of the team
- Employees who accept overtime when offered: 30-40%
- Employees who reliably accept overtime: 10-15%
That means for every 10 people who say "give me more hours," maybe 1 or 2 will consistently show up when you need them.
If you're planning your staffing based on who says they want overtime instead of who actually takes it, you're understaffed every weekend.
What actually works
1. Stop asking who wants overtime. Start tracking who takes it.
The list of people who say they want more hours is useless for scheduling. What matters is the list of people who actually accept shifts when offered.
Track it over 3-4 months. You'll quickly see that your team splits into three groups:
- Always yes (10-15%) -- these people almost always accept. Schedule them first for overtime needs.
- Sometimes yes (20-30%) -- they'll take overtime if the timing works. Offer to them, but have a backup.
- Rarely yes (50-60%) -- they say they want hours but almost never accept. Don't count on them for coverage planning.
Most scheduling tools can track offer-to-acceptance rates. Turnozo does it through the open shift system. You post the shift, see who claims it, and over time the data tells you who's reliable.
2. Make overtime opt-in, not assigned
When you assign overtime, people feel trapped. Even the ones who would have volunteered now resent it because they didn't get a choice.
Post extra shifts as open. Let people claim them. The ones who genuinely want the hours will grab them. The ones who don't will stay quiet instead of committing and then calling out.
This does two things:
- You get people who want to be there (better work, fewer no-shows)
- You stop wasting time negotiating with people who were never going to say yes
If nobody claims the shift? Now you have real information. The shift isn't desirable. Maybe it's the wrong time, or the team is legitimately burned out. That's a signal, not a staffing failure.
3. Understand the shift quality hierarchy
Not all overtime is equal. Your team ranks shifts whether you realize it or not:
Most desirable:
- Weekday evenings (home by bedtime, still get the day)
- Shifts right before or after existing shifts (already at work)
- High-tip shifts (Friday/Saturday dinner for restaurants)
Least desirable:
- Early mornings on days off
- Sundays (family time, recovery day)
- Overnight shifts
- Holidays (unless you pay double)
If you're always offering the least desirable shifts as overtime, acceptance rates will be terrible. Consider rotating the good and bad overtime opportunities fairly. That brings us to the fairness problem. When the same people always get offered the good overtime, everyone else stops bothering to say yes.
4. Cap overtime before burnout eats your savings
Here's the second paradox: the 10-15% who always say yes will work themselves into the ground if you let them.
That sounds like a solution. But an employee working 55 hours a week for three months straight will eventually:
- Make more mistakes (fatigue)
- Call out sick more (burnout)
- Quit entirely (they found a job with normal hours)
Set maximum weekly hours in your scheduling system. Even for the people who want more. A cap of 48 hours protects them, protects your labor costs, and forces you to build a schedule that doesn't depend on a few people carrying the whole team.
5. Do the math on hiring vs. overtime
If you're consistently offering 20+ overtime hours per week, you've passed the break-even point. Hiring another part-timer is almost certainly cheaper.
Quick math:
- Employee at €15/hour, overtime at €22.50/hour
- 20 hours of weekly overtime = €450/week = €1,950/month
- New part-timer at 20 hours/week = €300/week = €1,300/month
That's €650/month in savings, plus you get someone fresh instead of someone on their 50th hour.
Run the actual numbers for your team. The overtime paradox often hides a hiring problem. You're not short on willingness. You're short on people.
Most managers make overtime decisions based on feelings. Who seems willing. Who asked for hours last month. Who didn't complain about the last Saturday shift.
The fix is turning feelings into data:
- Track offer-to-acceptance rates per employee
- Track which shifts get claimed and which sit open
- Track actual hours vs. scheduled hours
- Track overtime costs against the cost of a new hire
- For the complete picture: Employee Time Tracking Guide
With three months of data, your overtime planning goes from "I think Jake wants more hours" to "Jake accepts 85% of offered overtime, mostly evening shifts, and has averaged 6 extra hours per week this quarter."
That's the difference between hoping your schedule works and knowing it will.
Calculate your actual overtime costs → Use our free overtime calculator to see what overtime is really costing your team.
Stop managing requests. Start managing patterns.
Your team will always say they want more hours. That's never going to change. The trick is building a system that shows you who means it, what kind of overtime they'll actually take, and when it's time to stop offering overtime and start posting a job listing.
Overtime and labor costs start with how you build the schedule. See our complete guide to employee scheduling for the full process.
The overtime paradox isn't a people problem. It's an information problem. And information problems have solutions.
