How to Write a Fair Time Off Request Policy for Shift Teams

A fair time off request policy starts getting tested the Friday before a holiday weekend, when two cooks, one shift lead, and your most reliable closer all ask for the same three days off.

Nobody is trying to make your life harder. One person bought flights months ago. Another has a wedding. Someone else has used almost no PTO all year and finally wants a break. You still have a schedule to cover, customers to serve, and a team watching how you make the call.

If your rules live only in your head, every decision feels personal. A written policy gives managers a clear path and gives employees a fair shot at planning their lives.

A fair time off request policy explains how employees ask for time off, how much notice they should give, when requests may be limited, and how managers decide between competing requests. The best policies are written plainly, applied consistently, and shared before busy seasons, not during them.

What a Fair Time Off Request Policy Needs to Cover

Define what counts as time off

Start by naming the kinds of requests your team can make. Keep the language simple enough that a new hire understands it on day one.

Common categories include PTO, unpaid time off, sick time, personal days, bereavement leave, jury duty, school obligations, and protected leave that may be covered by federal, state, or local law. Do not treat all of these the same. A vacation request and a legally protected leave request need different handling.

For labor-law topics, write the policy in plain terms and have the current rules checked for your location. Sick leave, predictive scheduling, family leave, and final wage rules can vary by state, city, industry, and employee status.

Set the normal notice window

Most shift teams need advance notice because coverage depends on specific roles, skills, and availability. A salon cannot simply replace a licensed stylist with a receptionist. A clinic cannot cover a certified role with an unqualified employee. A warehouse may need forklift-certified staff on certain shifts.

Your policy should say how far ahead employees should submit normal requests. For example, you might ask for two weeks of notice for one or two days off and 30 days for vacations of a week or more. Use numbers that match your scheduling cycle.

Also state what happens with short-notice requests. If someone asks late, the answer is not always no, but the policy should explain that approval depends on coverage, business needs, and applicable leave rules.

Name who approves requests

Employees should know where requests go. If one manager approves by text, another approves verbally, and a third waits until the schedule is posted, confusion is guaranteed.

List the approver by role, not by person. For example: “Time off requests are reviewed by the department manager” or “Store managers approve requests for their location.” If a general manager or owner has final approval during peak periods, say that too.

PTO Request Policy: Make the Process Easy to Follow

Use one request path

A PTO request policy falls apart when requests arrive through five channels. A manager might miss one in a group chat. An employee might think a verbal mention was an approval. A note on the office wall can disappear under new paperwork.

Pick one request path and make it official. The path could be scheduling software, a form, or a written request system. The key is that every request has the same basic record: employee name, dates requested, reason category if needed, date submitted, approval status, and manager decision.

This protects both sides. Employees can see that their request was submitted. Managers can review requests in order and avoid relying on memory.

Separate “received” from “approved”

One of the most common sources of conflict is the phrase “I told you about this.” Telling a manager is not the same as getting approval.

Your policy should say that a request is not approved until the employee receives confirmation through the official process. That sentence saves many arguments later.

Use direct wording:

Policy item	Clear wording to use
Request method	Submit time off requests through the approved scheduling process.
Approval status	A request is pending until a manager marks it approved.
Schedule conflict	Employees should not assume time off is approved until confirmed.
Late request	Late requests may be reviewed, but approval depends on coverage and leave rules.
Recordkeeping	Managers keep request records so decisions can be reviewed if questions come up.

Give managers a response deadline

Employees need time to make plans. Managers need time to check coverage. Your policy should set a reasonable response target, such as “Managers will respond within five business days when possible.”

That does not mean every answer must be yes. It means employees are not left guessing while flights get more expensive, childcare plans change, or family commitments need an answer.

Time Off Approval Rules That Employees Can Trust

Use objective approval factors

Time off approval rules should be specific enough that employees understand the decision even when they are disappointed.

Good approval factors include:

• Date the request was submitted
• Staffing levels for the requested shift
• Required qualifications for that shift
• Employee’s available PTO balance, when applicable
• Prior approved time off on the same dates
• Blackout dates or peak periods already announced
• Legal requirements for protected leave

Avoid vague standards like “manager discretion” as the only rule. Managers need judgment, but the policy should tell them what to weigh.

Apply the rules consistently

Fair does not always mean everyone gets the same answer. Fair means people are judged by the same standard.

If two servers request the same Saturday off, and one asked six weeks earlier while the other asked two days earlier, approving the earlier request can be fair. If a manager denies one person for “coverage” but approves a friend for the same shift without a clear reason, trust breaks quickly.

Consistency matters even more in small teams, where every decision is visible. If you manage hourly teams across departments or locations, keep the same core rules and allow only necessary local differences.

For broader scheduling policy work, see the workforce hub at /category/CATEGORY.

Keep manager notes factual

Managers should document the reason for approval or denial in neutral language. Use facts, not opinions.

Better: “Denied because two approved PTO requests already leave only one qualified closer available.”

Worse: “Denied because Sam asks off too much.”

Factual notes help if an employee asks why their request was denied. They also help owners spot patterns, such as one department constantly running too lean to approve normal PTO.

Blackout Dates Policy: Be Clear Before Peak Season

Define blackout dates narrowly

A blackout dates policy tells employees when time off may be restricted because the business expects unusually high demand or limited coverage. Examples might include holidays, inventory week, major local events, annual sales, school breaks, or seasonal rushes.

Use blackout dates carefully. If half the calendar is blacked out, employees will see the policy as a way to avoid approving time off at all. Keep blackout periods tied to real operational needs.

A restaurant might restrict requests for Mother’s Day weekend. A hotel might limit PTO during a citywide convention. A retail store might set special rules for the final shopping days before Christmas. A gym might need coverage during a January membership rush.

Announce blackout dates early

The most important rule for blackout dates is advance notice. Employees can accept limits more easily when they know them before making plans.

Publish blackout dates at the start of the year, quarter, or season. If your business depends on event calendars, update the list as soon as major dates are known.

Your policy should also explain whether blackout dates mean “no requests approved” or “requests approved only with manager review.” Those are different rules. Many businesses are better served by the second option because there may still be coverage for limited requests.

Allow exceptions where required

Do not write a blackout dates policy that ignores sick leave, protected leave, religious accommodations, disability accommodations, jury duty, or other rights that may apply. Time off restrictions for vacation do not erase legal obligations.

Use practical language: “Blackout dates may limit discretionary time off requests, but the company will review requests required by law or covered by applicable leave policies.”

Then verify the details with current local rules for your business.

How to Handle Competing Time Off Requests Without Drama

Pick tie-breakers before you need them

To handle competing time off requests fairly, decide your tie-breakers in advance. Waiting until two employees want the same holiday off invites pressure, favoritism claims, and last-minute bargaining.

Common tie-breakers include first submitted, rotating holiday priority, seniority, prior approvals during the same period, and critical qualifications needed for coverage.

Each has tradeoffs. First submitted rewards planning. Rotation helps spread holiday time off. Seniority is easy to understand but may frustrate newer employees. Qualification-based decisions protect operations but need careful explanation.

Use a rotation for high-demand holidays

For holidays and annual events, rotation is often fairer than pure first come, first served. Otherwise, the same organized employees may capture every popular date.

A simple rotation might say: employees who received Thanksgiving off this year are lower priority for Thanksgiving next year, assuming all other factors are equal. You can also rotate groups for Christmas Eve, New Year’s Eve, spring break, or local peak events.

This is especially useful for restaurants, hotels, retail, healthcare support teams, and security teams where holidays are normal workdays for the business. If your team also struggles with tight turnarounds, pair this with sane rules around /posts/clopening-shifts.

Do not make employees fight for coverage

Some businesses require employees to find their own replacement before time off can be approved. That can work for informal shift trades, but it should not be the whole policy.

Managers own the schedule. Employees can help identify coverage, but final approval should still depend on qualifications, overtime risk, availability, and labor cost. Otherwise, popular employees get help and newer or quieter employees get stuck.

A better rule is: “Employees may suggest qualified coverage, but managers must approve all schedule changes.”

A Sample Fair Time Off Request Policy You Can Adapt

Plain-language policy example

Use this as a starting point, then adjust it for your location, industry, and legal requirements.

“Employees should submit time off requests through the approved scheduling system as early as possible. Requests for one or two days off should be submitted at least two weeks in advance when possible. Requests for three or more consecutive workdays should be submitted at least 30 days in advance when possible.

A request is pending until a manager approves it. Managers review requests based on staffing needs, required qualifications, request timing, previously approved time off, PTO balance when applicable, blackout dates, and applicable leave laws.

When multiple employees request the same dates, managers will use the published tie-breaker rules. The business may limit discretionary time off during announced blackout dates, but requests covered by law or other leave policies will be reviewed under those rules.

Employees should not assume time off is approved until they receive confirmation. Managers will respond to requests within five business days when possible.”

Manager checklist before approving or denying

Before you answer, walk through the same checklist every time.

Question	Why it matters
Was the request submitted through the official process?	Keeps records complete and decisions trackable.
Is the request covered by PTO, unpaid time, sick leave, or another leave type?	Different request types may have different rules.
Does the employee have the needed balance, if PTO applies?	Prevents payroll and expectation problems.
Are enough qualified people available?	Coverage is about skills, not just headcount.
Would approval create overtime or labor-cost issues?	Helps avoid hidden schedule costs.
Are blackout dates involved?	Applies peak-period rules consistently.
Are there competing requests?	Triggers tie-breakers before decisions feel personal.
Is any law or protected leave rule involved?	Requires careful handling and current local guidance.

Train managers on the policy

A written policy only works if managers use it the same way. Review the policy before holiday seasons, summer vacation periods, school breaks, and major business peaks.

Train managers to avoid casual promises like “That should be fine” before checking coverage. Teach them to give short, factual answers: “Approved,” “Pending while I check coverage,” or “Denied because two qualified closers are already approved off that night.”

For broader team expectations, your time off rules should connect with call-out standards and communication norms. See /posts/last-minute-call-outs-policy and /posts/team-communication-shift-workers.

How ShiftSynch helps

ShiftSynch helps you run a stable, well-managed team: organize staff into teams, track availability and qualifications, manage time-off, watch overtime before it becomes a payroll surprise, and see it all in clear reports on web and mobile.

Start free — no credit card required (1 team, up to 10 staff); paid plans start at $19/month with a 14-day trial.

Start free on ShiftSynch

A fair policy will not make every denial pleasant. It will make the decision easier to explain and harder to misunderstand.

Write the rules before the rush, use the same process for every employee, and keep the records clean. Your team may not always get the answer they want, but they should always understand how the answer was reached.

Frequently Asked Questions

Q: What should a PTO request policy include? A PTO request policy should include the request method, required notice, who approves requests, when a request becomes approved, how PTO balances are checked, and how conflicts are handled. It should also explain late requests, blackout dates, and any separate handling for sick leave or protected leave based on current local rules.

Q: What are fair time off approval rules for shift workers? Fair time off approval rules use clear factors such as request date, staffing needs, required qualifications, PTO balance, prior approvals, blackout dates, and applicable leave laws. The rules should be written down, shared with employees, and applied consistently so managers can explain approvals and denials without relying on personal preference.

Q: How should a blackout dates policy work? A blackout dates policy should identify peak periods when discretionary time off may be limited, such as holidays, inventory, major events, or seasonal rushes. Announce dates early, keep them narrow, and explain whether requests are blocked entirely or reviewed case by case. Always verify how local leave laws affect exceptions.

Q: How do you handle competing time off requests fairly? To handle competing time off requests fairly, choose tie-breakers before conflicts happen. Common options include first submitted, rotating holiday priority, seniority, prior approved time off, and required qualifications for coverage. Use the same tie-breakers each time, document the reason, and avoid making employees negotiate coverage on their own.**