Guide

Time-Off Basics for First-Time Managers

A practical guide for first-time managers on handling PTO requests: approvals, coverage planning, fairness, and keeping clean records.

TS
The SimplyPTO Team
Aug 25, 2025 · 8 min read
SimplyPTO

Managing time off is one of the first real tests of being a new manager, and it is also one of the easiest places to lose your team's trust. The job comes down to four things: approving requests fairly, making sure work still gets covered, treating everyone by the same rules, and keeping records you can defend later. Get those right and time off becomes a non-event instead of a recurring headache.

Start with the four jobs of time-off management

Every PTO decision you make touches at least one of these four areas. When something feels messy, it is almost always because one of them got skipped.

  • Approvals. Saying yes or no in a timely, consistent way.
  • Coverage. Making sure the work does not fall over while someone is out.
  • Fairness. Applying the same rules to everyone, including yourself.
  • Records. Tracking what was requested, approved, and used so balances stay accurate.

You do not need a thick policy manual to do this well. You need a few clear rules and the discipline to follow them every time.

Approvals: respond fast, decide consistently

The single biggest complaint employees have about time off is silence. They submit a request, hear nothing for a week, and start to wonder if they can book the flight. Slow approvals also create a quiet unfairness, because the person who pesters you the most ends up getting answers first.

Set a turnaround standard and put it in writing. A reasonable rule for most small teams:

  • Acknowledge every request within two business days.
  • Give a final answer within five business days, or sooner for short requests.
  • Require more notice for longer absences. A common scale is one day of notice per day off, with at least two weeks' notice for any absence of a week or more.

When you approve, confirm the exact dates back to the employee so there is no confusion about whether a half-day or a return date is included. When you deny, give the reason and, where possible, an alternative.

Acknowledge is not the same as approve

A quick "Got it, I'll confirm coverage and get back to you Thursday" buys you time to check the calendar without leaving the employee hanging. The acknowledgment is what builds trust; the decision can follow.

Build a simple decision checklist

Before you approve anything, run through the same short list. It keeps your decisions consistent and gives you a ready answer if someone asks why a request was denied.

  1. Does the employee have enough balance to cover the days?
  2. Is anyone else already off during that window?
  3. Does the request land in a blackout period or known crunch?
  4. Is the notice period met?
  5. Is the work that person owns covered or reassignable?

If all five are clear, approve it. If one is a problem, that is your starting point for the conversation.

Coverage: plan the work, not just the absence

Approving time off is the easy half. The harder half is making sure the customer call still gets answered and the invoice still goes out. New managers often approve a week off in March and get blindsided in April when they realize nobody knows how to run payroll while Dana is in Portugal.

Coverage planning has three moving parts:

  • Visibility. A shared calendar so everyone can see who is out and when. Surprises come from absences nobody knew about.
  • Cross-training. At least one backup for every critical task. If only one person can do something, every vacation becomes a risk.
  • Capacity limits. A cap on how many people can be off at once, especially in small teams.

A practical capacity rule for a team of five to ten people is to allow no more than two people off on the same day, and only one during your busy season. Write the rule down so the third person to request a popular week understands why the answer is no.

Use a working days calculator to figure out exactly how many business days a request actually consumes, since a "two-week vacation" might only be eight or nine working days once weekends and holidays are removed. That changes both the coverage math and the balance deduction.

A lightweight coverage plan

For any absence longer than two days, ask the employee to jot down a one-paragraph handoff before they leave: what is in flight, who is covering it, and where the files live. It takes ten minutes and saves the person covering an hour of guessing.

Fairness: same rules, written down, applied to everyone

Fairness is where good intentions go to die. You are not being unfair on purpose, but if you approve Sam's Friday off with a text and make Priya fill out a form, you have created two systems. Over time, people notice. The fix is to make the rules explicit and then refuse to bend them based on who is asking.

Here is what consistent treatment looks like across common situations:

SituationFair approachWhat to avoid
Two requests for the same weekApply a written tiebreaker, such as first submission timestampQuietly favoring your stronger performer
A last-minute requestUse the same notice rules for everyone, with room for emergenciesApproving for friends, denying for others
Manager taking time offFollow the same notice and coverage rules you setExempting yourself from the policy
Recurring religious or cultural daysAccommodate proactively and consistentlyTreating some observances as more valid than others
Sick days versus vacationKeep categories separate and clearPressuring sick employees to "just use vacation"

The tiebreaker rule deserves special attention. Popular weeks like the one between Christmas and New Year's, or the week of spring break, will always be oversubscribed. Decide your rule in January, not in December when emotions are running high. First-come-first-served by timestamp is the easiest to defend because it removes you from the judgment entirely.

Fairness also means modeling the behavior. If you answer email from the beach and brag about never taking time off, your team learns that real commitment means skipping vacation. That is how you end up with burnout and unused balances that turn into a payout liability.

Records: track everything, accurately, in one place

Records are the boring part that protects you. When an employee disputes their balance, or you get audited, or someone leaves and you owe a payout, the question is always the same: what does the record say? If your record is a mix of texts, a whiteboard, and your memory, you have a problem.

At a minimum, every time-off event should capture:

  • The date the request was made
  • The dates requested and the leave type
  • Your approval or denial and the date of that decision
  • The running balance after the change

Many states require you to keep payroll and leave records for two to four years, and several paid-sick-leave laws have their own retention and accrual-display requirements. Keeping clean records is not optional bookkeeping; it is compliance.

A worked example

Say an employee accrues PTO at 1.25 days per month, which is 15 days a year. They start the year with a 3-day carryover balance. Here is how the running record should look:

DateEventChangeBalance
Jan 1Opening carryoverplus 3.003.00
Jan 31Monthly accrualplus 1.254.25
Feb 28Monthly accrualplus 1.255.50
Mar 14Approved vacation, 2 daysminus 2.003.50
Mar 31Monthly accrualplus 1.254.75

The point is that the balance is always derived from the record, not the other way around. If you cannot reconstruct the balance from a list of events, the balance is just a guess. To check your own accrual math or set up a new rate, the PTO accrual calculator does the per-period arithmetic for you.

Common first-year mistakes and how to avoid them

A few traps catch almost every new manager. Knowing them in advance is half the battle.

  • Approving by gut, denying by gut. Without a checklist, your decisions drift and start to look biased even when they are not.
  • No coverage cap. You approve three overlapping requests because each one seemed fine in isolation, then the week arrives and nobody is at their desk.
  • Mixing sick and vacation. Blurring the categories invites legal trouble in states with mandated sick leave and confuses your accrual tracking.
  • Letting balances run silent. Employees should be able to see their balance any time. If they have to ask you, you have created a bottleneck and a dispute waiting to happen.
  • Ignoring the cost. Time off is real money. Run the numbers with a PTO cost calculator so you understand the payout liability sitting on your books, especially in states where unused vacation is treated as earned wages.

Put it on autopilot

You can run all of this on a spreadsheet, and plenty of small teams do at first. The trouble is that spreadsheets do not enforce your rules. They will happily let someone go negative, let three people book the same week, or let a balance drift out of sync. The moment your team passes about five people, the manual approach starts costing you more time than it saves.

That is the problem SimplyPTO is built to solve: requests, approvals, a shared calendar, automatic accruals, and a clean record of every transaction, all in one place that your team can see. You set the rules once, and the system applies them the same way every time, which is the whole point of fairness. If you are tired of chasing approvals over text and reconstructing balances by hand, start a free SimplyPTO account and let the tool handle the bookkeeping while you focus on the people.

Frequently asked questions

How quickly should I respond to a time-off request?

Aim to respond within two business days, even if the answer is 'let me check coverage and confirm by Friday.' A fast acknowledgment respects the employee's planning and reduces back-and-forth. Set a written turnaround expectation so the whole team knows what to expect.

Can I deny a PTO request?

Yes, if you have a legitimate business reason such as a coverage gap, a blackout period, or too many people already off. Explain the reason, offer alternative dates when you can, and apply the same standard to everyone. Avoid denying requests based on who asked first only when it is convenient.

What records do I need to keep for time off?

Keep the request date, the dates requested, the type of leave, your decision, and the running balance after the request. Many states require you to retain payroll and leave records for two to four years, and some sick-leave laws have their own retention rules. A shared tracker or PTO app keeps this consistent and audit-ready.

How do I handle two people requesting the same week off?

Decide on a tiebreaker rule before it happens and write it down. Common rules are first-come-first-served by submission timestamp, rotating priority for popular weeks, or seniority. Whatever you choose, apply it the same way every time so the decision feels fair rather than personal.

Should unused PTO carry over to the next year?

That depends on your policy and your state. Some states treat accrued vacation as earned wages that cannot be forfeited, so a strict use-it-or-lose-it policy may be illegal there. A common middle ground is to cap carryover at a set number of days or hours and communicate the cutoff date well in advance.

Related in Small Business HR

Stop tracking PTO in a spreadsheet

SimplyPTO tracks balances, requests, and approvals automatically — with a shared team calendar. Free for up to 10 people, no credit card.

Get started free →