How to Set Up and Manage PTO Policies Through Justworks: A Practical Walkthrough

You’ve signed with Justworks. Good. Now comes the part nobody warns you about: actually configuring your PTO policies so they work correctly, stay compliant, and don’t create payroll chaos three months down the road.

PTO setup is almost always one of the first operational tasks new Justworks clients tackle during onboarding. And it’s one of the most common places where things go sideways. Not because Justworks is hard to use — the platform is genuinely clean and intuitive — but because most business owners underestimate the compliance layer sitting underneath the configuration. Set up accrual rules without checking your state’s termination payout laws, and you’ve just built a liability. Lump sick leave and vacation into one bucket without knowing your state’s sick leave mandate, and you may already be out of compliance before your first employee submits a request.

This guide is not a primer on what PTO is or why it matters. You know that. This is a practical walkthrough for business owners and HR leads who need to get PTO policies live inside Justworks — correctly — without creating compliance gaps or administrative headaches on the back end.

By the time you’re done, you’ll have a functioning PTO framework configured in Justworks, a clear picture of where the platform’s limitations sit, and a sense of when you might need to layer in additional tools or processes to fill the gaps.

One note on scope: this is a focused, operational guide. If you’re still evaluating whether Justworks is the right PEO for your business, or want a broader picture of what PEO onboarding actually involves, you’ll want to start with a full Justworks review and a PEO onboarding overview before diving into configuration. This guide assumes you’ve already made the decision and need to execute.

Let’s get into it.

Step 1: Audit Your PTO Obligations Before You Log In

This step happens before you touch Justworks. It’s also the step most businesses skip, which is exactly why they end up reconfiguring everything two months later.

The core problem is this: PTO policy configuration in any system is only as good as the policy decisions behind it. If you don’t know your legal obligations first, you’re just guessing — and guessing wrong on PTO compliance has real consequences.

Start with your employee locations. Pull a list of every state where you have active employees. This matters more than your company’s headquarters state. If you’re a New York-based company with employees in California, Colorado, and Illinois, you’re subject to the leave laws in all three of those states — not just New York. Each state has its own rules around mandatory sick leave, accrual minimums, and what happens to unused PTO when someone leaves.

As of 2026, states with mandatory paid sick leave requirements include California, New York, Colorado, New Jersey, Washington, Oregon, Connecticut, Massachusetts, Illinois, Minnesota, and others — and the list continues to grow. Several cities have their own ordinances that go beyond state law. This is a moving target. Before you configure anything, verify current requirements for every state where you have employees directly through that state’s labor department or with an employment attorney.

Understand the termination payout question. Some states, California and Colorado among them, treat accrued PTO as earned wages. That means you’re legally required to pay out unused balances at termination. Other states allow “use it or lose it” policies. This distinction directly affects how you’ll configure carryover caps and accrual limits inside Justworks. If you set up a forfeiture rule in a state that prohibits it, you’ve created a wage claim waiting to happen. Understanding risk management and EPLI coverage is critical context for navigating these compliance exposures.

Document your intended policy structure. Before logging in, write down the answers to these questions:

Accrual model: Are you going accrual-based or unlimited? If accrual-based, what’s the rate and frequency?

Policy buckets: Will you use a single combined PTO bank, or separate vacation, sick, and personal day buckets? (More on why this matters in Step 2.)

Carryover rules: Do unused hours roll over? Is there a cap? Do balances reset annually?

Waiting periods: Do new hires start accruing immediately, or after 30, 60, or 90 days?

The success check here is simple: you should have a written summary of your PTO obligations by state and your desired policy structure before you open Justworks. If you can’t answer the questions above, you’re not ready to configure yet.

Step 2: Configure Your PTO Policy Types Inside Justworks

Now you’re ready to build. Inside Justworks, PTO configuration lives under the Time & Attendance section. Navigate there, and you’ll find the PTO Policies area where you can create and manage policy types.

Justworks gives you a few starting points: preset templates for standard accrual, unlimited PTO, and custom configurations. Here’s how to think about which one fits your situation.

Unlimited PTO is the simplest to configure — there’s no accrual tracking, no balance management, and no carryover math. It works well for companies with salaried exempt employees in states that don’t require accrued PTO payout at termination. If you have California employees, think carefully before going unlimited: the legal landscape around unlimited PTO in California is genuinely complicated, and you’ll want legal guidance before choosing this path there.

Standard accrual is the most common setup for small and mid-size teams. You’ll set an accrual rate (hours earned per pay period, per month, or annually), a maximum accrual cap, and carryover rules. Justworks lets you configure accrual frequency as per pay period, monthly, annually, or front-loaded (where the full year’s allotment is granted upfront). Front-loading simplifies administration but creates complexity if someone leaves early in the year with a full balance already granted.

The policy bucket question is critical. You might be tempted to create one combined PTO policy and call it done. Resist that. If you operate in states with mandatory sick leave laws, those laws often specify minimum accrual rates, permitted uses, and documentation requirements that apply specifically to sick leave — not general PTO. Lumping everything into one bucket makes it harder to demonstrate compliance and harder to track whether employees are actually meeting the minimum sick leave thresholds required by law. For a comparison of how other platforms handle this, see how Insperity approaches PTO policy management.

Create separate policy types for vacation, sick leave, personal days, and any other leave categories you offer. Yes, it’s a bit more setup work upfront. It’s significantly less work than explaining to a state labor board why your combined PTO policy doesn’t clearly satisfy the mandatory sick leave accrual requirement.

Carryover rules deserve careful attention. Justworks lets you set whether unused hours carry over, and if so, whether there’s a cap. Here’s the common mistake: setting a “use it or lose it” carryover rule for employees in states that prohibit PTO forfeiture. Cross-reference your state audit from Step 1 before finalizing any carryover configuration. If a state requires payout of accrued leave at termination, a forfeiture rule in your system creates a direct legal conflict.

Once you’ve built your policy types, review each one against your Step 1 documentation before saving. The configuration is only correct if it matches your actual legal obligations and your stated policy intent.

Step 3: Assign Policies to Employee Groups and Handle Edge Cases

Building the policies is step one. Assigning them correctly is where the real complexity lives, especially if you have a multi-state team or a mix of hourly and salaried employees.

Justworks lets you assign different PTO policies to different employee groups. Use this. A single company-wide policy rarely serves everyone correctly when you’re operating across multiple states or have different employee classifications.

Common assignment groupings to consider:

Salaried vs. hourly: These groups often have different accrual structures, and PTO affects their payroll differently. Hourly employees’ PTO hours directly affect gross pay calculations, which matters when you get to Step 5.

State-specific policies: Employees in states with mandatory sick leave requirements need a policy that explicitly satisfies those requirements, regardless of what your company-wide policy looks like. Build state-specific sick leave policies and assign them accordingly.

Tenure-based tiers: If your policy gives employees more PTO after two or five years, you’ll need separate policy tiers and a process for moving employees between them at the right time. Justworks doesn’t automate tenure-based policy transitions, so you’ll need a manual process or a calendar reminder to handle those upgrades.

Importing existing balances is where a lot of migrations get messy. If you’re bringing current employees onto Justworks mid-year, they likely have existing PTO balances that need to carry over. Justworks allows manual balance entry during setup. Do this carefully. Common errors include entering hours instead of days (or vice versa depending on how your policy displays balances), forgetting to account for PTO already used in the current year, and entering balances for employees who haven’t yet passed their waiting period.

Pull your PTO records from your previous system or payroll provider before migration and reconcile every balance individually. It’s tedious, but a wrong starting balance creates a cascading error that’s annoying to unwind six months later. If you’re considering leaving your current provider, understanding the Justworks cancellation process can help you plan the transition timeline.

Edge cases to handle explicitly:

Part-time employees: Check whether your accrual rates are configured to prorate correctly for employees working less than full-time hours. Some states require proportional accrual for part-time workers.

Contractors: Independent contractors should not be in your PTO system at all. If you’re using Justworks for contractor payments, make sure no PTO policies are assigned to those individuals. Assigning PTO to contractors creates misclassification risk and muddies your compliance picture.

Employees who recently changed states: If someone relocated from a state without mandatory sick leave to California, their policy assignment needs to be updated immediately. Build a process to catch these changes — don’t rely on employees to flag it themselves.

Success check: every active employee has the correct PTO policy assigned, with accurate starting balances, before you move to workflow configuration.

Step 4: Configure Approval Workflows and Manager Permissions

PTO requests that sit in limbo frustrate employees and create scheduling problems. Getting your approval workflow right before you go live saves a lot of reactive firefighting.

In Justworks, you can configure who receives and approves PTO requests. The typical options are direct managers, department heads, or HR admins. Think through your actual org structure here rather than defaulting to “HR approves everything.” Centralizing all approvals through HR works for a 10-person team. At 50 or 80 employees, it creates a bottleneck and pulls HR into operational decisions that managers should own.

Assign approval responsibility at the manager level wherever possible, with HR as a fallback for employees without a direct manager assigned. Make sure every employee in Justworks has a manager designation before you activate the workflow — orphaned approval chains mean requests go nowhere. If you’re unsure how Justworks handles support escalation for issues like these, their account management model is worth reviewing.

Justworks’ approval workflow is functional but not sophisticated. You can set up a single-tier approval chain, but if your organization needs multi-level approvals (manager approves, then department head confirms), you’ll hit the platform’s limits quickly. This is one of the areas where more robust HRIS platforms have a clear edge. If you need complex approval hierarchies, plan for a manual escalation process outside Justworks rather than assuming the platform will handle it.

Blackout dates and restricted periods are worth configuring if your business has seasonal demand spikes or critical operational windows. Justworks allows you to flag restricted periods where PTO requests require additional scrutiny or are limited. This doesn’t automatically block requests, but it creates a visible signal in the approval flow. Make sure managers understand what to do when a request comes in during a restricted period — the system flags it, but the human decision still happens manually.

Enable employee self-service. Justworks’ self-service portal lets employees check their own balances, submit requests, and view team calendars without going through HR. Turn this on. It reduces the volume of “how much PTO do I have?” messages HR fields every week, and it gives employees visibility that builds trust in the system.

Before you go live, run a test. Submit a dummy PTO request from a test employee, trace it through the approval chain, approve it, and verify that the balance updates correctly. It takes 10 minutes and catches configuration errors before they affect real employees.

Step 5: Sync PTO Tracking to Payroll and Verify the Connection

This is the step with the most downstream consequences if you get it wrong. PTO and payroll need to be correctly connected — especially for hourly employees where approved PTO hours directly affect gross pay calculations.

Justworks handles the core sync automatically. When a PTO request is approved, it feeds into the payroll system and the hours are reflected in the next payroll run. For salaried employees, this is primarily a balance tracking function. For hourly employees, it’s a pay calculation function — approved PTO hours replace regular hours worked and need to be paid at the correct rate.

Verify the payroll connection explicitly rather than assuming it’s working. After you’ve completed your policy configuration and employee assignments, run a test payroll cycle or review a payroll preview with a known PTO scenario. Check that:

1. Approved PTO hours are appearing on the payroll run correctly

2. The PTO hours are being paid at the right rate for hourly employees

3. The employee’s PTO balance has been reduced by the correct amount

4. The pay stub shows PTO as a separate line item so employees can see it clearly

What Justworks does not automate: This is important to understand before you go live. Several scenarios require manual intervention.

Retroactive PTO corrections: If an employee submitted a sick day but forgot to log it, and you’re now two pay periods later, correcting the balance and payroll record requires manual adjustment. Justworks doesn’t have a clean retroactive correction workflow — you’ll need to work through their support process or make manual balance edits.

Mid-cycle policy changes: If you change an accrual rate or carryover rule mid-year, the system doesn’t automatically recalculate existing balances to reflect the new rule. You’ll need to manually adjust balances for affected employees.

Termination payout calculations: In states that require payout of accrued PTO at termination, Justworks will show you the employee’s current balance, but calculating the exact dollar amount owed and ensuring it appears correctly on the final paycheck is something you need to verify manually. Don’t assume this is handled automatically — check it every time. Teams running into frequent manual corrections at scale may want to explore whether Justworks still fits at 200 employees.

Common sync errors to watch for: PTO hours not appearing on the payroll run (usually a timing issue with when the request was approved relative to the payroll cutoff), balance discrepancies after a policy change, and hourly employees’ PTO being calculated at the wrong pay rate. Most of these are fixable, but they’re easier to catch before paychecks go out than after.

Step 6: Use Reporting to Monitor Balances and Stay Ahead of Issues

Configuration is a one-time event. Management is ongoing. Justworks has built-in PTO reporting that gives you visibility into accrual balances, usage patterns, and outstanding requests across your team.

Pull these reports regularly — at minimum quarterly, more frequently if you have a large team or high turnover. What you’re looking for:

High accrual balances: Employees sitting on large unused PTO balances represent a liability on your books, especially in states that require payout at termination. Flagging these early lets you encourage usage before balances become a financial exposure.

Zero usage patterns: Employees who never take time off are sometimes a culture signal, sometimes a system error. If someone’s usage is showing zero but you know they’ve taken days off, there’s a tracking problem to investigate. This kind of gap is also worth flagging through Justworks’ performance management tools to ensure managers are having the right conversations.

Accrual anomalies: If an employee’s balance is growing faster or slower than the policy should produce, something is misconfigured. Catch it early.

Annual policy reviews matter. As your team grows, expands into new states, or your business model shifts, your PTO policies need to keep pace. Review your policy structure at least once a year. Ask whether your accrual rates are still competitive, whether you’ve added employees in states with new leave requirements, and whether your carryover rules still make sense given your current workforce size.

Keep documentation of your policy decisions and any changes you make. If an employee disputes a balance or a state agency audits your leave records, having clear documentation of your policy history is what keeps a minor dispute from becoming a significant problem.

Where Justworks PTO Management Works — and Where It Doesn’t

Here’s an honest assessment, because the platform’s limitations matter as much as its capabilities.

Justworks handles straightforward PTO well. For teams under roughly 150 employees with relatively simple policy structures — standard accrual, a few policy types, single-tier approvals — the platform does what you need it to do. The UI is clean, the self-service experience is solid, and the payroll integration works reliably for standard scenarios.

Where it gets harder: complex multi-tier accrual schedules, granular reporting beyond basic balance summaries, advanced scheduling integrations, and multi-level approval workflows. If your business has grown to the point where PTO management requires sophisticated policy logic or deep analytics, you may be pushing against the platform’s ceiling. For smaller teams, the experience is quite different — a 20-employee Justworks setup typically stays well within the platform’s sweet spot.

Signs you may be outgrowing Justworks’ PTO capabilities:

You’re spending significant HR time on manual PTO corrections that should be handled systematically.

You’ve expanded into several new states with varying leave requirements and the manual compliance tracking is becoming untenable.

Your managers are working around the approval workflow because it doesn’t match how your organization actually operates.

If any of these sound familiar, it’s worth evaluating whether a different PEO or a dedicated time-tracking integration would serve your needs better. Before making a switch, checking Justworks’ BBB rating and reputation alongside competitor reviews can give you useful context. That’s a broader conversation than this guide covers — but it’s a real one worth having before your next renewal.

Before you go live, run through this verification checklist:

1. State obligations audited and documented for every employee location

2. Separate policy types created for vacation, sick leave, and any other leave categories

3. All active employees assigned to the correct policy with accurate starting balances

4. Approval workflows tested end-to-end with a dummy request

5. Payroll sync verified with a test payroll cycle or preview

6. Reporting activated and baseline balances confirmed

Getting PTO Right Is Mostly About the Work Before the Setup

The actual configuration inside Justworks isn’t complicated. The platform is intuitive, and if you’ve done your homework, the setup moves quickly. What trips most businesses up isn’t the software — it’s skipping the compliance audit in Step 1 and then discovering mid-year that their carryover rules violate state law or their sick leave policy doesn’t satisfy a mandatory minimum.

The sequence matters: obligations first, configuration second, assignment third, workflow fourth, payroll verification fifth, ongoing monitoring sixth. Follow that order and you’ll avoid most of the common pitfalls.

Quick recap of what needs to be true before you consider PTO setup complete: state-by-state obligations are audited, policy types are correctly configured with compliant carryover and accrual rules, every employee has the right policy assigned with accurate balances, approval workflows are tested, payroll sync is verified, and reporting is active.

If you’re still evaluating whether Justworks is the right fit for your team — or whether its PTO capabilities match your actual needs — it’s worth comparing your options before committing. Most businesses overpay for PEO services due to bundled fees and unclear administrative markups. We break down pricing, services, and contract structures so you can make a smarter decision. Compare your options before your next renewal.