A Manager's Guide to Approving Time Off

Approving time off is mostly a checklist, not a judgment call. If an employee has the balance, has coverage, and follows your notice rules, the answer is almost always yes, and you should give it fast. The hard part is the small percentage of requests where you have to weigh competing needs, say no without damaging trust, and make sure you treat the next person exactly the way you treated the last one.

This guide covers the principles behind good approvals, the specific things to check, when saying no is the right call, and how to stay consistent so your decisions hold up months later.

The default answer is yes

Start from the position that time off is a benefit you already promised. When you hired someone and offered them 15 days a year, you committed to letting them use those days. Treating each request as something to be earned again creates a culture where people hoard PTO, take it while sick anyway, or burn out.

The data backs this up: in the US, workers leave a meaningful chunk of their paid days unused every year, often because they feel approval is uncertain or frowned upon. Unused PTO is not a savings to celebrate. It is a sign your approval process feels risky.

So your job is not to decide whether people deserve time off. It is to manage the logistics of when. That reframing makes most decisions easy and keeps the hard ones rare.

What to check before you approve

Run every request through the same four checks. If all four pass, approve it. Most requests pass all four in under a minute.

1. Does the balance cover it?

The employee needs enough accrued or available days to cover the request. This sounds obvious, but it is the most common reason an otherwise fine request becomes a problem later, especially with accrual-based plans where the balance grows over the year.

Watch for two traps:

• Future accrual. Someone may have eight days now but be requesting time in three months when they will have twelve. Decide in advance whether you allow people to book against time they have not earned yet. Many small teams allow it up to a small limit; some do not allow it at all.
• Pending requests. A balance can look healthy while two unapproved requests are already in the queue against it. Always check available balance after subtracting anything pending.

If you are unsure how a balance got to its current number, our PTO accrual calculator shows exactly how days build up over a year so you can sanity-check the math.

2. Is there coverage?

Coverage is the real question behind most approvals. Will the work get done while this person is out? For one day, the answer is usually yes by default. For a week during a busy stretch, you may need a plan.

Ask:

• Who handles their critical tasks while they are gone?
• Are any deadlines, client deliverables, or shifts at risk?
• How many other people are already off during those dates?

A simple guardrail many teams use is a cap on how many people can be off at once. For a five-person team, that might be one. For a 20-person team, it might be three or four, and it might be department-specific.

3. Do the dates collide with anything?

Some dates carry more weight than others. Check the request against:

• Blackout periods. Retail in December, accounting at tax time, a SaaS team during a major launch. If you have blackout windows, they should be published at the start of the year, not invented when a request lands.
• Other approved time off. Two people out is fine; half the team out the same week is not.
• Coverage-critical days. Month-end close, a board meeting, the one day the only person who knows the payroll system is needed.

When you are counting how many actual working days a request consumes around weekends and holidays, the working days calculator saves you from miscounting a "one week off" that actually spans nine calendar days.

4. Does it follow your notice policy?

If your policy says two weeks' notice for single days, hold people to it, but leave room for genuine emergencies. Notice rules exist to give you time to arrange coverage, not to punish people. A reasonable structure looks like this.

Adjust the numbers to your team, but keep the principle: longer absences need more notice because they need more planning.

When to say no

Saying no should be uncommon, specific, and tied to one of the checks above. A good denial points at a reason the employee can understand and often work around. A bad denial sounds like a mood.

Legitimate reasons to deny or push back:

• Insufficient balance. "You have three days available and this is for five. Want to take three now and the rest once you've accrued more?"
• Coverage gap. "Priya and Marcus are already out that week, and we can't run support with three people gone. Can we look at the following week?"
• Blackout period. "That's during our December freeze, which we set back in January. Any window in November or after the 27th works."
• Notice too short for a long absence. "Two weeks off with three days' notice is tough to cover. If you can push it two weeks, I can make it work."

Notice the pattern: every no comes with a why and, where possible, a yes to something else. You are negotiating timing, not rejecting the person.

Reasons that are not acceptable to deny:

• The person took time off recently and you feel it is "too much," even though they have the balance.
• You are annoyed they did not ask in person.
• It is legally protected leave (jury duty, voting time in some states, mandated sick leave, FMLA-covered leave). These follow their own rules and are usually not yours to decline.

When you must deny a legitimate request, do it quickly and in writing, so the employee can replan while options still exist. A no on Monday is a manageable disappointment. The same no on Friday, after they have told their family, is a betrayal.

Consistency is the whole game

Here is the test that matters: if two employees brought you identical requests, would they get identical answers? If the honest answer is "it depends who's asking," you have a consistency problem, and consistency problems are how favoritism claims and morale spirals start.

Three habits keep you consistent.

1. Write the rules down before you need them. Notice periods, blackout dates, the max number of people off at once, whether you allow borrowing against future accrual. A team that has these written settles 90 percent of decisions without you weighing in at all. If you do not have a policy yet, the PTO policy generator gives you a clean starting template you can adjust in a few minutes.

2. Decide popular dates by an objective rule. When two people want the same week and only one can go, use a tiebreaker you set in advance. First-come, first-served by request timestamp is the easiest to defend. Some teams rotate priority for holidays so the same person does not always lose. Whatever you pick, the rule decides, not your gut.

3. Keep a record. You do not need a spreadsheet of justifications, but you do need to see who requested what and when, and what you decided. A timestamped log is your best defense if anyone ever claims unequal treatment, and it stops you from accidentally double-booking coverage.

A worked example

Two requests land for the same week in July, when you can only spare one person.

• Dana submitted on June 1, has 11 days available, and her tasks are easy to hand off.
• Sam submitted on June 8, has 4 days available for a 5-day request, and covers the only client-facing role on the team.

The consistent decision: approve Dana. She asked first (your tiebreaker), has the balance, and has coverage. Sam's request has two independent problems, the balance shortfall and the coverage gap, either of which justifies a no on its own. You tell Sam the same day, explain both reasons, and offer the week before or after. No favoritism, no guesswork, fully defensible.

A quick approval routine

Putting it together, here is a routine you can run in two minutes per request:

1. Open the request and check the balance after pending items are subtracted.
2. Glance at the calendar for overlapping time off and blackout dates.
3. Confirm coverage for anything time-sensitive in those dates.
4. Check it against your notice policy.
5. Approve, or deny with a specific reason and an alternative, in writing, within a day or two.

The faster this becomes muscle memory, the less time off feels like a negotiation and the more it feels like the benefit you promised.

If you also want to understand what time off actually costs you when you are weighing coverage decisions, the PTO cost calculator translates days into real dollars, which can make the "can we afford this absence" question concrete.

The bottom line

Good time-off approval is boring on purpose. You apply the same four checks to everyone, say yes by default, say no only with a clear reason and an alternative, and write down enough rules that most decisions make themselves. Do that and you get two things at once: a team that actually uses its PTO, and decisions that hold up when someone asks why.

SimplyPTO turns this routine into something you barely have to think about. Balances, pending requests, coverage conflicts, and blackout dates all sit in one place, and every approval is timestamped so consistency is automatic instead of something you have to remember. Start a free SimplyPTO account and make approvals the easy part of managing your team.