Discretionary Time Off: A Guide for Modern Employers

If you're running HR at a growing company, this usually starts the same way. Someone asks how much time they have left. A manager approves a week off without checking another team's schedule. Payroll needs a termination payout number. Your "system" is a spreadsheet, a Slack thread, and whatever your managers happen to remember.

That mess is why many small and midsize employers look at discretionary time off. On paper, it sounds clean. Fewer accrual calculations. Less debate about balances. More flexibility for employees. But for companies hiring across states, or across countries, DTO isn't just a culture choice. It's a compliance decision with real financial exposure if you structure it poorly.

What Is Discretionary Time Off

Discretionary time off, often shortened to DTO, is a leave policy where eligible employees don't accrue a fixed bank of vacation days. Instead, they request time off as needed, and managers approve those requests based on workload, coverage, and policy rules.

A shift from accounting to trust

The biggest change isn't administrative. It's philosophical.

Traditional paid leave treats time off like an earned balance. Discretionary time off treats it more like a managed benefit tied to business needs and employee judgment. That difference matters. It changes how employees think about taking leave, how managers approve it, and how HR documents it.

As of 2025, approximately 11% of U.S. employers offer unlimited PTO policies, and traditional leave still commonly follows a fixed allocation model that averages 14 days after 1 year of employment. At the same time, 46% of workers who receive any form of PTO use less time than offered, which helps explain why employers keep exploring alternatives such as DTO, according to FlexJobs' PTO statistics overview.

For employers used to accrued leave, the appeal is obvious. You stop spending time answering balance questions, managing carryover rules, and cleaning up old records. If you need a baseline on how fixed leave policies are typically structured, this guide on what paid leave means in practice is a useful comparison point.

Practical rule: DTO only works when employees know they're genuinely allowed to use it. If the policy says "take what you need" but managers quietly discourage requests, employees will treat it like a trap.

What DTO is not

DTO isn't the same as "no rules." A workable policy still needs:

Eligibility boundaries so employees know who qualifies
Approval standards so managers use the same decision logic
Coverage expectations so business operations keep running
Written guardrails for extended absences, blackouts, and protected leave interactions

A good DTO policy removes unnecessary accounting. It doesn't remove management.

DTO vs Traditional PTO and Unlimited Leave

Most companies use these terms loosely, and that creates trouble. I've seen employers say they offer "unlimited PTO" when what they really have is a manager-discretion vacation policy with unwritten limits. I've also seen companies call a policy DTO while still tracking "soft caps" in spreadsheets, which can undermine the whole structure.

A simple way to think about it is this. Traditional PTO is like a preloaded card. DTO is closer to a company-approved expense. The employee doesn't own a balance up front. The company decides whether the request fits the rules and the business context.

Where the differences actually matter

Traditional accrued PTO is straightforward. Employees earn time over time. HR tracks balances. In some states, unused balances may create payout obligations when employment ends.

DTO removes accruals, but not decision-making. Employees still request time off. Managers still approve or deny requests. HR still needs policy language, consistency, and records.

"Unlimited leave" is often used as a broad label in the market. In practice, many unlimited policies function as discretionary time off. The employee doesn't have a tracked vacation bank, but approval still depends on business needs, manager discretion, and internal norms.

The reason employers keep looking at alternatives is financial as well as cultural. The estimated liability for unused PTO in the United States exceeds $1 trillion annually, or about $7,600 per full-time worker, and only 57% of employees use all their earned PTO, according to SHRM's reporting on unused vacation liability.

Leave Policy Comparison

Attribute Discretionary Time Off (DTO) Traditional Accrued PTO Unlimited PTO Accrual method No fixed accrual Earned over time Usually no fixed accrual Balance tracking Minimal or no vacation balance tracking Required Often minimal, but practices vary Approval basis Manager review, workload, policy guardrails Balance plus scheduling needs Manager review and company norms Payout risk Depends on policy design and jurisdiction Often clearer under wage and payout rules Can still create risk if poorly structured Administrative burden Lower on accruals, higher on manager judgment Higher on tracking and calculations Similar to DTO if truly discretionary Employee experience Flexible, but can feel ambiguous Clear and predictable Flexible, but can feel political Best fit Mature teams with strong manager discipline Structured operations needing clarity Employers using DTO-style flexibility under another label

A policy name doesn't protect you. What matters is how the policy operates in practice, how consistently managers apply it, and what state law says about it.

If you want examples of how employers document different leave structures, this collection of PTO policy examples is helpful for side-by-side drafting ideas.

The Benefits and Risks of a DTO Policy

Discretionary time off can work well. It can also create a fairness problem faster than leaders expect. The difference usually comes down to manager behavior, not policy branding.

What works

When DTO fits the business, it solves a few real problems.

Less balance administration means HR spends less time on accrual disputes, carryover cleanup, and payout calculations tied to ordinary vacation banks.
More autonomy for employees can strengthen trust, especially in salaried environments where performance matters more than face time.
Cleaner recruiting message can help when candidates value flexibility over rigid vacation accounting.
Fewer end-of-year games happen because employees aren't trying to use days before they expire.

DTO tends to work best in companies with clear performance expectations, experienced managers, and roles that don't require tightly coordinated shift coverage. It also works better when leaders model time off themselves. If executives never unplug, employees will read the room.

Where it breaks down

The operational weakness is visibility.

Discretionary time off policies create coverage blindness because they reduce centralized leave tracking and push planning down to the manager level. Without aggregated forecasting, managers may miss overlapping absences or minimum staffing risks, which can shift extra work onto employees who don't take as much leave, as noted in BrynQ's explanation of DTO coverage challenges.

That issue shows up in a few predictable ways:

Teams approve in isolation and don't see cross-functional coverage gaps.
High performers self-limit because they don't want to burden coworkers.
Assertive employees take more leave while quieter employees take less.
Managers become bottlenecks because every decision relies on their judgment.

The trade-off most employers underestimate

DTO reduces one kind of administration and increases another.

You may do less accrual bookkeeping, but you'll do more policy interpretation, exception handling, and manager coaching. If your managers aren't trained to approve requests consistently, employees won't experience flexibility. They'll experience uncertainty.

Companies don't fail with discretionary time off because the policy is too generous. They fail because nobody defines what fair use looks like.

A practical DTO environment needs coverage tools, shared calendars, approval standards, and recurring review of usage patterns. Not balances. Patterns. You want to know who never disconnects, who repeatedly requests peak periods, and where workload gets dumped after approvals.

Navigating DTO Legal and Compliance Risks

The most common misconception about discretionary time off is that it's legally simpler than accrued PTO. It often isn't.

For a small employer operating in one state with a narrow employee population, DTO can be manageable. For a growing company with remote employees in multiple states, mixed worker classifications, and plans to hire internationally, the compliance picture gets much harder.

The California problem employers gloss over

A lot of vendors and articles treat DTO as a neat way to avoid unused vacation payout. That assumption is risky. California courts have ruled that DTO policies can trigger vesting requirements under Labor Code Section 227.3, requiring employers to pay out unused vacation time upon termination, which creates a major blind spot for multi-state employers, as discussed in Ogletree's analysis of California unlimited vacation rulings.

That means a policy labeled "discretionary" or "unlimited" doesn't automatically avoid payout obligations. If the policy functions like earned vacation in practice, or if it has implied limits that make it look vested, an employer can still face wage claims.

FLSA and classification boundaries

DTO is typically not a broad workforce policy. It's usually limited.

Under Fair Labor Standards Act compliance considerations, DTO is primarily offered to salaried exempt employees and generally excludes hourly non-exempt workers. Companies such as Microsoft have also limited DTO eligibility to U.S.-based employees only because international jurisdictions may require minimum leave entitlements and statutory tracking that conflict with a discretionary model, according to AIHR's glossary entry on discretionary time off.

That matters for growing SMBs because many have mixed populations:

salaried exempt employees
hourly employees
part-time staff
remote hires in different states
contractors outside the U.S.

A single DTO policy usually won't fit all of them.

Where SMBs get exposed

The legal risk doesn't come only from statutes. It comes from bad drafting and inconsistent practice.

Common failure points include:

Vague eligibility language If your handbook doesn't clearly define who qualifies, managers may apply the policy unevenly.
Unwritten caps If leaders say the policy is open-ended but punish people for taking "too much," you may create evidence that the leave wasn't truly discretionary.
No documentation of approvals Without records, you can't show that denials were tied to business needs rather than favoritism or retaliation concerns.
One policy across jurisdictions Remote work breaks lazy policy drafting. The employee's work location can change your obligations.

Compliance lens: If you operate in multiple states, assume your DTO policy needs legal review before rollout and again whenever your hiring footprint expands.

For many small employers, the safest answer isn't "yes" or "no" on discretionary time off. It's "only for a defined employee group, with counsel-reviewed language, and with separate leave rules where the law requires them."

How to Implement a Discretionary Time Off Policy

A discretionary time off policy should be built like a controlled operating process, not a perk announcement. The companies that get in trouble usually move too fast. They announce flexibility first and write the rules later.

Start with scope before policy language

Decide who the policy is for before drafting anything.

Use these filters first:

Employee classification Keep DTO limited to roles where a discretionary model is legally and operationally appropriate. For many employers, that means salaried exempt employees only.
Work location Separate U.S.-based eligible employees from workers in jurisdictions that require statutory leave tracking or minimum entitlements.
Operational dependency If a team needs strict coverage, a traditional leave structure may fit better even if the company uses DTO elsewhere.

A leave system should reflect those differences. Some employers manage that with an HRIS and manual exceptions. Others use dedicated leave tools. For example, Redstone HR's leave management program is built to centralize approvals, visibility, and policy rules across different employee groups.

Sample policy language

Use this as a drafting starting point only. Legal counsel should review any final policy, especially if you employ people in multiple states.

Eligible salaried exempt employees may request discretionary time off for vacation and personal time, subject to manager approval, business needs, and departmental coverage requirements. Discretionary time off is not accrued, earned, or vested, and no specific number of days is promised or carried over from year to year. Approval decisions will be based on workload, scheduling needs, and consistent application of company policy. The company may deny or defer requests that would materially disrupt operations. This policy does not alter any rights employees may have under applicable federal, state, or local leave laws, nor does it replace legally required protected leave.

Implementation checklist

The rollout should be deliberate.

Get legal review first Have counsel review the draft for payout risk, wage treatment, and state-specific issues tied to where employees physically work.
Define excluded categories State clearly which workers are not covered, such as hourly non-exempt employees or international employees subject to statutory leave regimes.
Set approval rules in writing Define notice expectations, peak-period rules, escalation for longer absences, and who has final authority on disputed requests.
Train managers before launch They need one standard for approving, denying, and documenting requests. Without this, every department invents its own DTO policy.
Create visibility tools Use a shared calendar, approval workflow, and team-coverage view so managers can assess requests against real staffing conditions.
Address protected leave separately Family, medical, sick, or statutory leave should not be buried inside a casual DTO policy.
Write the employee FAQ at the same time If employees can't tell how to request leave, how much notice to give, or whether long vacations are realistic, the policy will generate anxiety instead of trust.

If your policy needs side conversations to explain what it "really" means, it's not ready to launch.

Communication and Management Best Practices for DTO

A discretionary time off policy lives or dies with manager behavior. The written document matters, but employees decide whether a policy is real by watching who gets approved, who gets questioned, and who gets praised for never taking leave.

What managers need to hear clearly

Tell managers that DTO is not a reward for favorites and not a test of loyalty. Their job is to apply the same standards across the team, document decisions, and protect coverage without discouraging use.

Train them to look at context, not instinct:

Check team availability before responding to a request
Use the same approval criteria for high performers and quieter contributors
Flag patterns early when someone never takes leave or repeatedly leaves teammates exposed
Escalate edge cases instead of creating ad hoc rules

What employees need to hear repeatedly

Employees need more than "take what you need." That phrase is too vague to be useful.

Say what responsible use looks like in your company. Explain how far in advance to request longer trips. Clarify whether there are blackout periods. Confirm that taking time off won't hurt performance reviews when the work is covered and expectations are met.

Managers should encourage time off out loud. If they only approve requests silently, employees won't know whether the policy is supported or merely tolerated.

The healthiest DTO cultures also normalize examples. A manager who says, "I'm offline next week and here's who covers what," does more to support the policy than a handbook paragraph ever will.

DTO Policy FAQs for HR Managers

How should DTO interact with protected leave

Keep them separate. Discretionary time off is a company policy. Protected leave is a legal entitlement where applicable. Your handbook, workflows, and manager training should make that distinction obvious so no one treats a legal leave request as an ordinary discretionary approval.

Should new hires get DTO immediately

That depends on your risk tolerance and operating model. Some employers allow use after onboarding because the policy isn't accrued. Others set an introductory period for practical reasons, such as training coverage and manager assessment. The important part is consistency and clear written eligibility.

What if one employee takes very little time off

Treat that as a management issue, not a personal virtue. Employees who never disconnect can drive burnout, create hidden dependency risk, and distort team norms. Managers should encourage actual use and check whether workload, guilt, or fear is driving the pattern.

What if one employee takes far more than peers

Look at outcomes, team impact, and consistency of approvals. A raw comparison between employees usually isn't enough. If the leave is creating operational strain or fairness concerns, address it through documented coaching and clearer approval standards.

Can managers deny a DTO request

Yes, if the denial is tied to business needs, coverage, or policy rules and applied consistently. A denial should never feel arbitrary. Require managers to explain the reason and, when possible, suggest an alternative timeframe.

Is DTO a good fit for every SMB

No. It fits some organizations well and creates avoidable risk for others. If your company has mixed worker classifications, tight coverage needs, or hiring across multiple jurisdictions, a hybrid approach is often more practical than forcing one leave model on everyone.

If you're weighing whether discretionary time off fits your company, Redstone HR can help you centralize leave requests, approvals, team availability, and policy administration in one place so managers have clearer context and HR has cleaner records across different employee groups and locations.