PTO vs Vacation vs Sick Leave: What's the Difference?

The short version: vacation and sick leave are specific reasons for taking paid time away from work, while PTO (paid time off) is usually a single bank of hours that covers any reason at all. The terms overlap, which is exactly why they get confused. The real decision for any employer is whether to lump all your paid time into one flexible pool or split it into separate, purpose-specific buckets, and that choice affects compliance, cost, and how often people show up to the office with the flu.

What each term actually means

These three words get used interchangeably in casual conversation, but they describe different things on paper.

Vacation

Vacation is planned, paid time off for rest, travel, or personal enjoyment. It is the time an employee requests in advance, gets approved, and uses on their own schedule. Vacation is almost always treated as an earned benefit, which is why it accrues over time (you might earn 1.25 days per month) and why, in many states, unused vacation must be paid out when employment ends.

Key traits of vacation:

• Requested and approved in advance
• Used at the employee's discretion for non-medical reasons
• Frequently accrues and carries a cash value
• Often subject to payout laws at termination

Sick leave

Sick leave is paid time off specifically for illness, injury, or medical needs, usually your own but sometimes a family member's. Unlike vacation, sick leave is reactive: you can't reliably plan to have the flu next Tuesday. It is often taken with little or no notice.

The big distinction is legal. A growing number of states and cities (California, New York, Colorado, Washington, and many municipalities) mandate paid sick leave with specific accrual rates and protections. These laws frequently say sick time can be used for things like doctor's appointments, mental health, or caring for a sick child, and they may protect employees from discipline for using it.

Key traits of sick leave:

• Used reactively, often same-day
• Tied to medical or caregiving reasons
• Frequently legally mandated with specific rules
• Usually not paid out at termination

PTO (paid time off)

PTO is the umbrella term. In its most common form, a PTO bank combines vacation, sick, and personal days into one pool the employee draws from for any reason. Need a beach week? Use PTO. Woke up with a migraine? Use PTO. Kid's school play at 2 p.m.? PTO.

PTO can also be used loosely to mean "all paid time off of every type," which is where the confusion starts. When someone says "we offer 15 days of PTO," they might mean one combined bank, or they might be adding up several separate buckets. Always ask which.

Key traits of a PTO bank:

• One pool for any kind of absence
• Maximum flexibility and minimal questions
• Simpler to administer than multiple buckets
• Often subject to the same payout rules as vacation

How they overlap (and why it gets confusing)

Here is the relationship in one sentence: vacation and sick leave are categories; PTO is either an umbrella covering those categories or a single merged bank that replaces them.

Think of it like a bank account. Separate buckets are like having a checking account labeled "vacation" and a savings account labeled "sick." A combined PTO plan is one account you spend from however you like. Both hold money (time); the difference is how strictly you label what each dollar (hour) is for.

The overlap causes three recurring headaches:

1. Reporting confusion. When everything is "PTO," you lose visibility into how much time is actually being lost to illness versus planned travel. That data matters for staffing.
2. Compliance gaps. If you merge sick into PTO but operate where paid sick leave is mandated, you may unknowingly violate the law, because the mandate still applies to the sick-eligible portion of your bank.
3. Payout surprises. Combining sick time into PTO can accidentally make those formerly non-payout sick hours into payout-eligible wages, raising your liability when people leave.

When to combine vs. when to separate

There is no universally correct answer. The right structure depends on your size, location, and tolerance for administrative work.

Combine into one PTO bank when:

• You're a small team that values simplicity over tracking detail.
• You want to reduce friction so people don't have to justify why they need a day.
• You operate without state or local paid-sick-leave mandates (or you build a compliant sick minimum into the bank).
• You'd rather not police whether someone is "really sick."

Keep separate buckets when:

• You're in a jurisdiction with paid-sick-leave laws and want clean, auditable compliance.
• You want to discourage presenteeism, people dragging themselves in sick because they're hoarding PTO for a trip.
• You want to limit payout liability by keeping sick time non-payable.
• You need accurate data on illness-driven absence for scheduling or insurance reasons.

A worked example shows the stakes. Say you have 12 employees each carrying an average of 6 unused sick days, and your average daily wage is 200 dollars. If sick leave is a standalone, non-payout bucket, those days expire with no cost. Merge them into a payout-eligible PTO bank and you've just created roughly 12 times 6 times 200 dollars, which is 14,400 dollars of potential payout liability sitting on your books. If you want to model this for your own team, the PTO cost calculator will run the numbers.

Pros and cons at a glance

What a typical policy looks like

To make this concrete, here are two realistic small-business setups.

Combined PTO model (10-person marketing agency, no state sick mandate):

• 15 days of PTO per year for full-time staff, accruing at 1.25 days per month
• Carryover capped at 5 days into the next year
• Unused balance paid out at separation per state rules
• No distinction between sick and vacation; same-day notice allowed for emergencies

Separate-bucket model (25-person retail business in a paid-sick-leave state):

• 10 vacation days per year, accrued, payable at termination
• 6 sick days per year, accrued at the legally mandated rate, not paid out
• 2 floating personal days that expire annually
• Sick time usable for the employee or an immediate family member

Notice that both models still rely on accruals. Whichever structure you choose, you'll need a consistent way to calculate how time builds up. Our PTO accrual calculator handles the per-pay-period math, and if you're scheduling around coverage gaps, the working days calculator helps you see how many actual workdays a request spans.

A simple decision framework

If you're starting from scratch, run through these questions in order:

1. Are you in a state or city with paid-sick-leave laws? If yes, you must guarantee a compliant amount of sick time, whether standalone or carved out within PTO. Start here, because it's non-negotiable.
2. How much do you care about absence data? If staffing depends on knowing why people are out, separate buckets win.
3. What's your payout exposure? If a large combined bank would create uncomfortable termination liability, keep sick time separate and non-payable.
4. How much admin can you handle? A solo office manager juggling everything by hand may genuinely benefit from one simple bank. A team with HR support can manage more nuance.
5. What does your culture reward? If you want people to actually stay home when sick, a dedicated sick bucket sends a clearer signal than a shared pool everyone is rationing for vacation.

There's no prize for over-engineering this. Many small businesses do perfectly well with a single PTO bank plus a written note that sick-related absences are never penalized. Others need the structure. The mistake is choosing by default instead of on purpose.

Common mistakes to avoid

• Calling everything "PTO" in your handbook without defining it. Spell out whether PTO is one bank or an umbrella over separate buckets, so nobody is surprised at payout time.
• Merging sick into PTO in a mandate state without a sick floor. You can offer a combined bank, but you usually still have to honor the minimum protected sick hours the law requires.
• Forgetting to address carryover and caps. Unlimited rollover quietly inflates your liability year over year.
• Treating "unlimited PTO" as no policy. Unlimited plans still need guardrails on approval, minimum usage, and how sick-leave law applies, or they create as many problems as they solve.

If you'd rather not draft the language yourself, the PTO policy generator produces a clean starting document you can adapt, and you can browse the rest of our free tools for accrual and cost planning.

The bottom line

Vacation is planned time for living your life. Sick leave is reactive time for being unwell, and it often comes with legal strings attached. PTO is the flexible container that can hold both, or stand in for all paid time entirely. Combining them is simpler and more popular; separating them gives you control, compliance clarity, and lower payout risk. Pick the structure that matches your state, your size, and the behavior you want to encourage, then write it down clearly.

When you're ready to stop tracking all of this in a spreadsheet, SimplyPTO lets you set up vacation, sick, and combined PTO balances, automate accruals, and approve requests in a few clicks. Start a free account and have a clean, compliant policy running for your team this week.