Time-off requests are one of the most consistent sources of friction between managers and hourly employees. Not because managers are trying to be unfair — but because "fair" is hard to define when you're making decisions on the fly.
The solution isn't to say yes to everyone or to develop an iron-fist policy. It's to build a process that makes decisions consistent and transparent.
Get requests in writing, always
Verbal time-off requests are a liability. Managers forget. Employees swear they said something. Schedules get published without the time off blocked and someone shows up expecting to be off.
All requests should go through a single channel — your scheduling system, a form, an email thread, something with a timestamp. When the request is in writing, there's no ambiguity about whether it was received.
Set a request deadline
If your schedule goes out on Friday for the following week, time-off requests should be due by Monday or Tuesday. This gives you time to build around confirmed absences rather than publishing a schedule and then retracting it.
Post the deadline and hold to it. Late requests should be accommodated when possible but not guaranteed. Employees who consistently submit late requests are telling you they don't take the process seriously — address that directly.
Decide on a rule for conflicts
When two people request the same day off, how do you decide? You need a rule, and it should be the same every time:
- First come, first served — whoever submitted first gets priority
- Seniority — the longer-tenured employee gets preference
- Rotation — if the same conflict keeps happening, rotate who gets the holiday each year
Any of these can be fair. What's not fair is deciding case by case with no stated criteria. That's how favoritism accusations start.
Blackout dates are legitimate — communicate them early
During your busiest periods — holiday weekends, peak season, large events — you may need to restrict time off entirely. That's reasonable.
The key is communicating blackout dates far enough in advance that employees can plan around them. Announcing a blackout one week before Christmas is not the same as communicating it in October. The earlier you set expectations, the fewer last-minute conflicts you're managing.
Keep a log of approved requests
A time-off log serves two purposes. First, it prevents scheduling mistakes — before publishing, you check the log and confirm all approved requests are reflected. Second, it gives you data over time.
If the same employee requests off six Saturdays in a row, you need to decide whether that's sustainable. If you're approving 30% more time-off requests for some employees than others, ask why.
Protect against pattern abuse
Some employees will test what they can get away with. An employee who consistently requests off high-value shifts, or who calls out every time a request is denied, is a scheduling problem and a management problem.
Document the pattern, address it directly, and don't let it become the norm. Fairness to your full team means not letting one employee's behavior repeatedly put others in a harder position.
ShiftsLine centralizes time-off requests, tracks approvals, and blocks approved dates automatically when you build the schedule. Join the waitlist.