Managing Unpaid Time Off: A Guide for Growing Teams

A manager gets a message at 7:12 a.m. An employee has already used their PTO, but now needs a full week away for a family issue. Payroll closes tomorrow. The team is short-staffed. Nobody in the building is asking a theoretical policy question. They're asking whether this absence is allowed, how it should be coded, and what happens next.

That's where most growing companies get into trouble. They treat every unpaid absence as the same thing. It isn't. Some unpaid leave is legally protected and can't be denied if the employee qualifies. Other unpaid time off is discretionary and depends on company policy, staffing needs, and consistent manager judgment.

If you run HR at a company that's still building its processes, this distinction matters more than almost anything else in leave administration. Get it right, and you protect the business while treating people fairly. Get it wrong, and you create compliance risk, payroll errors, resentment, and a pattern of approvals nobody can explain later.

The Unpaid Time Off Dilemma

An unpaid time off request rarely arrives in a clean, easy form. It usually lands when PTO is already exhausted, coverage is tight, and someone needs an answer before payroll closes or the schedule is posted.

That pressure is what causes mistakes.

The problem is usually not whether the employee should be treated with empathy. The problem is classification. A request that looks like "I need next week off and I have no PTO left" can point to several different obligations, and each one calls for a different response.

• Protected leave that may trigger rights under laws such as FMLA or USERRA
• Discretionary unpaid time off that the company may approve or deny under its policy
• Payroll handling that requires the hours to be coded correctly and applied to pay without errors
• Consistency risk if similar requests are handled differently across managers or departments

Those are not small differences. They affect who makes the decision, what documentation is required, whether the absence can be denied, and how the time should appear in payroll and attendance records.

I see the same breakdown in growing companies again and again. A frontline manager wants to help, approves the request informally, and only later realizes the employee may have raised a protected leave issue. By then, the company is no longer making a clean decision at the start. It is trying to repair a process problem after promises have already been made.

Unpaid time off also tends to get lumped together with PTO, which creates more confusion. If your team needs a clearer baseline on how paid leave works, start with this guide to how PTO policies work in practice.

The operational risk is straightforward. If your policy does not define who reviews unpaid absences, which requests go to HR, and what standards apply to discretionary approvals, supervisors will make case-by-case calls with no shared framework. One employee gets flexibility because their manager is accommodating. Another gets denied because a different manager is stricter about coverage. That is how employee relations problems start, and it is how preventable compliance issues get buried inside ordinary scheduling decisions.

A workable process starts with one rule. Before anyone approves unpaid time away from work, determine whether the request is legally protected or purely discretionary. Everything else follows from that distinction.

Paid Leave vs Unpaid Time Off

Paid leave and unpaid time off solve different problems. Companies that blur them usually end up with confusing approvals, inconsistent payroll treatment, and frustrated employees who don't know what options they have.

A useful way to think about it is this. PTO is a funded savings account for time. Employees earn it, hold a balance, and spend from that balance. Unpaid time off is an approved line of credit. It can create flexibility, but there's no wage payment attached to the hours away.

Here's the visual version of that distinction:

What changes in day-to-day administration

The paid versus unpaid difference affects much more than pay.

Topic Paid leave Unpaid time off How it starts Usually accrued or granted under policy Usually requested as needed Wage impact Employee remains paid during approved time Employee is not paid for approved time Balance tracking Requires accrual, carryover, and usage rules Requires approval and payroll coding rules Manager mindset “Does the employee have time available?” “Is this protected or discretionary, and can we support the absence?” Employee expectation More predictable because time is earned More conditional because approval often depends on policy and circumstances

That distinction matters because employees don't always use the paid leave they already have. In the 2025 FlexJobs Work & PTO Pressure Report, surveyed between August 18 and August 31, 2025, 23% of 3,063 U.S. workers said they took no vacation days at all in the prior year, even though 82% reported having PTO. The same survey found workload pressure (43%) and fear of falling behind (30%) were among the most common reasons people avoided time off.

That tells you something important. A leave strategy can't stop at “we offer PTO.” If employees don't feel able to use it, or if life events outlast the paid balance, unpaid time off becomes part of the actual policy framework.

For a deeper look at how paid leave itself is structured, Redstone HR's guide on how PTO works and what policies need to define is a useful companion.

A short explainer can also help when you're training managers:

Why companies need both

Most growing employers need both a paid leave policy and an unpaid time off process because they address different realities.

• Paid leave supports planned absences. Vacation, appointments, personal days, and recovery time work best when employees have a defined bank to use.
• Unpaid time off handles exceptions and spillover. It gives the company a structured response when PTO is exhausted or a situation falls outside normal balances.
• Protected unpaid leave covers legal obligations. Many teams struggle with this aspect, because the approval logic is different from a standard discretionary request.

If you only build for paid leave, your managers will improvise when unpaid situations arise. They'll do it in email, chat, or hallway conversations. That usually creates a bigger problem than the original absence.

The Critical Legal Distinction Protected vs Discretionary Leave

This is the line managers need to understand cold. Protected unpaid leave and discretionary unpaid time off may both result in an employee being away without pay, but they are not governed by the same rules.

Protected leave exists because a law gives the employee rights. Discretionary leave exists because the employer chooses to allow it under policy.

The practical risk is misclassification. As noted in Shiftflow's analysis of unpaid leave administration, a major gap in HR guidance is the boundary between legally protected unpaid leave, such as FMLA, and discretionary unpaid time off, which is employer-controlled. The same discussion notes that misclassifying a request is a primary source of compliance risk for small teams.

Protected leave means the law is driving the process

When a request may involve protected leave, the manager's job isn't to make a business judgment first. The manager's job is to recognize the trigger and route it correctly.

Typical signals include:

• A serious health or family issue
• Military-related service or obligations
• A request tied to a legal accommodation or statutory leave right
• Language suggesting ongoing treatment, caregiving, incapacity, or a qualifying event

Once those signals appear, the question is no longer “Can we spare this person next week?” The first question is whether the request falls under a protected category.

Practical rule: If a manager hears facts that might trigger legal protection, the request should leave the manager's inbox and move into an HR or leave review process immediately.

That's why a simple definition page can help. A shared internal reference such as this unpaid leave glossary entry gives managers a baseline vocabulary, which is often half the battle.

Discretionary leave means policy and consistency are driving the process

Discretionary unpaid time off is different. It usually applies when there is no legal entitlement, but the company may still approve time away based on business needs and written policy.

Examples often include extending a trip after PTO runs out, taking time for personal matters that don't fall into a protected category, or bridging a short gap when an employee needs flexibility.

In those cases, employers usually control:

Question Protected leave Discretionary unpaid time off Can the request be denied for staffing reasons? Generally not if the employee qualifies Usually yes, depending on policy Do job protections apply? Yes, where required by law Only if company policy says so Are benefit and service rules fixed? Often governed by legal requirements Usually governed by company policy Who should review it? HR or trained leave administrator Manager with HR guidance or standard approval workflow

A workable decision model

Managers don't need to become leave lawyers. They do need a repeatable triage habit.

Use this order:

• Listen for legal triggers first. Don't ask only about dates. Ask why the time is needed in a neutral, job-related way.
• Pause informal approvals. A fast “sure, no problem” can create downstream issues if the request should have entered a protected leave process.
• Separate qualification from scheduling. Protected leave review comes before staffing convenience.
• Use policy only after legal screening. If no protected trigger applies, then move to your discretionary unpaid time off criteria.
• Document the basis for the decision. The record should show why the request was routed one way or the other.

What doesn't work is treating every request as a manager preference issue. What works is a gatekeeping model where legal review happens before discretionary approval logic starts.

Designing Your Unpaid Time Off Policy

A manager approves two unpaid days for an employee who says they need time away for a family issue. HR later learns the request may have fallen under a protected leave law. Now the company has two problems at once. It may have mishandled a legal obligation, and it has no clear standard for whether similar discretionary requests should be approved in the future.

That is why the policy has to do more than say unpaid time off is available. It needs to separate legally protected leave from employer-approved unpaid time off, give managers a clear approval framework, and tell payroll and benefits teams what the decision means in practice.

State and local leave rules add complexity, as noted earlier. A written policy helps you avoid blending statutory leave rights with a discretionary benefit the company can approve or deny based on business needs.

The clauses every policy needs

Start with eligibility and approval standards. If those points are implied rather than stated, managers fill the gaps on their own, and consistency disappears fast.

Sample clause Employees may request discretionary unpaid time off after meeting the company's eligibility requirements. Approval is not guaranteed and depends on business needs, staffing coverage, and the employee's compliance with the request process.

That wording matters. It confirms the option exists, but it does not create an entitlement.

Then draw a firm line around what the policy does not cover.

Sample clause This policy applies only to discretionary unpaid time off. Requests that may qualify for protected leave under federal, state, or local law will be reviewed under the applicable leave policy and legal requirements.

I recommend this language in almost every policy review because it closes a common compliance gap. Without it, managers often treat all unpaid absences as a scheduling issue and miss the legal review step.

What to spell out explicitly

A usable policy answers operational questions before a real request lands on someone's desk:

• Who can request it Define eligibility clearly, such as all employees, regular full-time employees only, or employees after a set length of service.
• How much notice is required Set expectations for foreseeable absences and a separate process for unexpected situations.
• Who can approve it Name the decision-maker, whether that is the direct manager, HR, or a combined workflow.
• What approval factors apply Use business-based criteria such as team coverage, overlapping absences, peak periods, and project deadlines.
• How long it can last Set a normal approval limit and require added review above that threshold.
• How it affects pay, benefits, and accruals Explain how unpaid time is handled for wages, benefit deductions, and leave accruals, subject to plan terms and law.
• Whether paid leave must be used first If employees must exhaust PTO before taking discretionary unpaid time off, say so plainly.
• What documentation may be required Keep it limited and appropriate. Do not ask for documentation in a way that interferes with protected leave rights.

Short policies often create the most trouble. They sound flexible, but they leave too much to manager judgment.

The approval standard should be specific

“Management may approve unpaid time off at its discretion” gives the company legal room, but it does not give managers enough direction to make fair decisions.

Use language employees and supervisors can both apply:

Model language Requests for discretionary unpaid time off are evaluated based on advance notice, team coverage, overlapping absences, recent attendance issues, and the employee's ability to return to regular work as scheduled.

That standard is easier to defend because it ties decisions to business factors instead of personality, pressure, or who asked first.

Build the policy for real-world use

A good policy does not try to predict every personal circumstance. It sets guardrails.

What works in practice:

• A separate review path for requests that may involve protected leave
• Written approval criteria managers can use consistently
• A clear rule on whether PTO must be exhausted first
• A documented record of the request and decision
• A stated impact on pay, benefits, and accruals

What creates problems:

• Case-by-case approvals with no consistent standard
• Vague promises of flexibility
• Manager-only handling of legally sensitive requests
• Silence on benefits continuation, return dates, or pay treatment

The goal is not to make every request easy. The goal is to make decisions consistent, legally sound, and clear to the employee who has to live with the outcome.

Payroll and Administrative Headaches to Avoid

The approval itself is rarely the hardest part. The problems usually start after someone clicks “approved” and assumes the rest will sort itself out.

That's risky because unpaid leave is a recurring transaction, not an occasional anomaly. According to the BLS release on employee leave access and usage, 78% of U.S. wage and salary workers had access to unpaid leave in 2017 to 2018, and 21% took leave in an average week. Among those taking leave, the average duration was 13.7 hours. That pattern tells you the same thing experienced payroll teams already know. Unpaid leave often shows up in partial-day increments, intermittent schedules, and messy real-world timing.

Error one is sloppy hour tracking

If your system only handles full days neatly, you'll miscode partial absences. That creates payroll discrepancies, inaccurate leave histories, and poor documentation if a request later intersects with a protected leave issue.

Use hour-level tracking whenever the absence isn't a clean full-day block. The BLS average duration above is a good reminder that intermittent leave is common enough to plan for.

Error two is separating approval from payroll execution

A manager approves unpaid time in email. Payroll never sees the message, or sees it too late. The employee gets paid incorrectly, and now someone has to decide whether to recover wages, adjust the next check, or manually reconcile the error.

That's not just annoying. It damages trust fast.

A safer process includes:

• A single approval record that payroll can see
• A coded leave type so unpaid time isn't buried in notes
• A cutoff rule for when approved unpaid time affects the current pay cycle
• A review step for partial-day absences and retroactive adjustments

Error three is ignoring downstream effects

Unpaid time off can affect more than wages. Depending on your plan rules and policies, it may interact with benefits deductions, service time, accrual behavior, or leave calculations tied to other obligations.

Don't treat unpaid time off as “just don't pay them for that day.” The absence may have ripple effects across payroll, benefits, and employee status records.

Many smaller employers struggle. They approve a request as a human matter, which is often the right instinct, but they fail to translate that approval into a clean administrative record.

The fix is discipline, not complexity. Use one naming convention, one approval path, and one handoff to payroll every time.

From Spreadsheets to a Streamlined System

Most companies don't start with a broken process. They start with a process that was good enough when the team had twelve people.

Then the company grows. Requests come through Slack, Teams, text, and email. A manager keeps a color-coded spreadsheet. HR has another version. Payroll has a note in a folder somewhere. Nobody is intentionally disorganized, but no one source is reliable.

That's exactly when unpaid time off gets mishandled. The issue isn't only recordkeeping. It's decision quality. If a manager can't see overlapping absences, team coverage, prior approvals, or policy rules in one place, they're making judgment calls with partial information.

Manual tracking breaks at the exact moment you need consistency

A spreadsheet can list dates. It can't reliably enforce process.

Here's what tends to go wrong with manual leave administration:

• Requests disappear into conversation threads
• Managers approve exceptions without seeing team-wide impact
• Payroll receives incomplete or late information
• HR can't easily review patterns across locations or supervisors
• Employees get different answers depending on who they ask

That last point matters more than many organizations realize. An inconsistent leave process doesn't just create admin friction. It changes how employees judge fairness.

The burnout angle matters too. A peer-reviewed review on unlimited PTO policies found that organizational norms can constrain leave usage, leading to longer hours, more work during leisure time, and higher work-non-work conflict, as summarized in this review of unlimited PTO effects. Systems that show leave patterns can help managers spot whether flexibility exists on paper but not in practice.

What a better system should do

A leave management platform should centralize requests, route approvals, maintain the record, and give managers context before they approve.

For small and midsize teams, that usually means:

• One request intake point instead of scattered messages
• Policy-based routing so possible protected leave doesn't get mixed with routine discretionary requests
• Calendar visibility for overlapping absences and minimum coverage concerns
• Payroll-ready exports so approved unpaid time doesn't have to be retyped
• Pattern reporting so HR can see underuse, hotspots, and repeat exceptions

A tool such as Redstone HR's PTO tracking app fits this category by centralizing leave requests, approvals, balances, and reporting in one place. That kind of setup is especially useful when one person is handling HR, operations, and payroll coordination at the same time.

The point isn't software for software's sake. The point is replacing memory, inboxes, and side conversations with a process the company can defend.

Frequently Asked Questions About Unpaid Time Off

Can we require employees to use PTO before taking unpaid time off

Yes, many employers choose to require employees to exhaust available PTO before discretionary unpaid time off is considered. If you do that, put it in writing and apply it consistently.

The caution is legal screening. If a request may involve protected leave, don't let a manager rely only on the “use PTO first” rule without routing the request properly.

Can part-time employees request unpaid time off

They can, if your policy allows it. The key is to define eligibility and approval standards clearly rather than assuming unpaid time off is only for full-time staff.

If your business excludes part-time employees from discretionary unpaid time off, state that directly. Ambiguity creates disputes.

Is unpaid time off the same as a furlough

No. Unpaid time off is usually an employee-initiated or employee-specific absence request handled under leave policy. A furlough is generally an employer-driven reduction in work or temporary suspension of work.

The distinction matters because the business reason, documentation, and payroll implications are different.

Can managers approve unpaid time off on the spot

They can approve discretionary requests if your policy gives them that authority, but they shouldn't do it casually. Managers need a clear rule for escalating anything that might be legally protected.

A fast approval is not always a safe approval. The better habit is quick intake, then correct classification.

If you want fewer surprises, train managers on one simple sentence: “Thanks for letting me know. I'm going to make sure we route this correctly before I confirm the leave details.”

If your team is still managing unpaid time off through email threads, spreadsheets, and separate payroll notes, Redstone HR gives you one place to handle requests, approvals, balances, calendar visibility, and audit-ready records without rebuilding your process from scratch.