If you manage an on-call rotation, complaints come with the territory. But here's what most managers don't realize: the vast majority of on-call complaints stem from just three root causes. Fix those three things, and you'll eliminate most of the noise.
This isn't theory. It's a practical playbook for systematically reducing the friction in your on-call program.
The Three Root Causes of On-Call Complaints
After analyzing complaint patterns across hundreds of on-call teams, three issues account for roughly 80% of all grievances:
- Perceived unfairness — "I always get the worst shifts"
- Poor communication — "I didn't know I was on call" or "Nobody told me the schedule changed"
- Lack of control — "I can't swap shifts" or "My preferences don't matter"
Notice something? None of these are about on-call duty itself. People generally accept that on-call is part of the job. What they don't accept is a poorly managed on-call program.
Fix #1: Make Fairness Visible
The keyword is visible. It's not enough to distribute shifts fairly — your team has to be able to see that it's fair.
What visible fairness looks like:
- A dashboard or report showing total shifts per person, broken down by weekday, weekend, and holiday
- A fairness score (like OnCall Builder's 0–100 rating) that quantifies distribution equity
- Historical data showing how holidays have been distributed over the past 1–2 years
- Published rules explaining how assignments are made
When someone says "I always get the worst shifts," you can point to the data. Either the data proves them right (and you fix it), or it shows the distribution is actually fair (and the complaint dissolves). Either way, the data resolves the dispute.
Common mistake: trusting your gut
Many managers believe the schedule is fair because they tried to make it fair. But without data, you can't be sure — and neither can your team. "Trust me, it's fair" is not a convincing argument to someone who just worked their third Saturday in a row.
Fix #2: Over-Communicate the Schedule
"I didn't know I was on call" should never be a valid excuse in your organization. If it is, the problem isn't your team — it's your communication system.
The notification stack:
- Schedule publication: SMS + email to every team member when a new rotation is published
- Shift reminders: 24 hours before a shift starts, send an automatic reminder
- Change alerts: Any time the schedule is modified (swaps, additions), notify affected parties immediately
- Calendar integration: On-call shifts should appear in team members' personal calendars automatically
The cost of over-communicating is zero. The cost of under-communicating is missed coverage, late-night scrambles, and resentful team members.
Single source of truth
Every team member should know exactly one place to check the current schedule. Not an email from two weeks ago, not a pinned message in Slack, not a shared drive folder with three versions. One URL, one dashboard, one answer.
Eliminate Complaints at the Source
OnCall Builder provides visible fairness scores, automatic notifications, and one-click swaps — the three fixes that cut complaints by 80%.
Try It Free →Fix #3: Give People Control
Humans handle inconvenience much better when they have agency. Being on call on Saturday is annoying. Being on call on Saturday with no ability to swap, no input into the schedule, and no way to flag conflicts? That's infuriating.
Control mechanisms that work:
- Blackout dates: Let people mark dates they can't be on call before the schedule is generated
- Swap requests: A self-service system where team members can propose and complete swaps with minimal manager involvement
- Preference input: Ask which shifts or days people prefer (not guarantee — prefer). Even partial accommodation reduces resentment significantly.
- Advance visibility: Publishing the schedule far in advance (4+ weeks) gives people time to plan and request changes
The approval balance
Swaps need enough structure to prevent abuse (coverage gaps, fairness imbalances) but enough flexibility that they actually get used. One-click manager approval is the sweet spot — the team member initiates, the manager confirms, and the system handles the rest.
Measuring Your Progress
How do you know if your complaint-reduction efforts are working? Track these metrics:
- Formal complaints per quarter: Any grievance raised to management about on-call scheduling
- Swap request volume: High swap volume can indicate either good flexibility (positive) or poor initial scheduling (negative). Context matters.
- Survey scores: A quarterly one-question survey — "How fair is the on-call rotation?" on a 1–5 scale — gives you a trend line
- Turnover correlation: Track whether departing employees cite on-call duty in exit interviews
Quick Wins You Can Implement This Week
You don't need to overhaul your entire system at once. Start with these high-impact, low-effort changes:
- Publish a fairness summary alongside your next schedule showing shifts per person by type
- Set up automated reminders 24 hours before on-call shifts start
- Create a swap request channel (even a simple shared document or form) where people can request trades
- Send the next schedule out 2 weeks earlier than you normally would
- Ask your team what their #1 on-call complaint is — you might be surprised
The Bigger Picture
Reducing complaints isn't about making everyone happy — on-call duty will never be popular. It's about removing the unnecessary friction that turns a manageable inconvenience into a morale-killing grievance.
When your scheduling is visibly fair, clearly communicated, and offers real flexibility, the remaining complaints will be about the inherent nature of on-call work — and those are much easier to manage with empathy and fair compensation.
Fix the system, and the complaints take care of themselves.