You want PTO and leave policy at your company to be accurate, applied the same way for everyone, and set up correctly in ADP TotalSource. By the end of this guide you’ll have a documented PTO policy, a clear split of which policy decisions belong to you and which to ADP TotalSource, and a short list of checks to run before and after go-live.
Before you start, gather your current handbook, PTO balances by employee, the state and local leave obligations for each of your work locations, and your PEO service agreement or proposal. Several steps below point back to that agreement, because service scope varies by contract.
Step 1: Confirm what ADP TotalSource handles and what stays with your company
Start with the co-employment arrangement. In a PEO relationship, the PEO and your company share certain employer responsibilities, such as payroll processing, benefits administration, and parts of HR support. Your company still runs the workplace. You decide how generous your time off is, how it fits your culture, and how managers apply it day to day.
Ask ADP in writing which handbook and policy support is included in your service agreement and which pieces are optional. Scope differs by contract and plan, so check your proposal rather than assuming a handbook review, template library, or policy consultation is part of your package. Keep the written answer with your agreement.
Then list the decisions that remain yours. At minimum:
- How much time employees accrue, and how that changes with tenure
- Whether unused time carries over, and how much
- Whether you pay out balances at separation, where the law allows you a choice
- How time-off requests are approved, and by whom
- Who can approve exceptions to the written policy
Put a name next to each item. If “the owner” and “the office manager” both think they approve exceptions, you already have an inconsistency.
Common mistake: assuming the PEO owns compliance for your policy choices. ADP can provide guidance and tools, but the client typically remains accountable for its own policy decisions. Confirm how responsibility is allocated in your service agreement and risk management scope, and ask your employment counsel if the language is unclear.
Step 2: Audit your current PTO and leave policies before you migrate
Pull your existing handbook and build a one-page inventory. List every type of paid and unpaid time off you offer: vacation, sick leave, holidays, bereavement, jury duty, parental leave, unpaid leave, and floating days. For each, note who is eligible, how it accrues or is granted, any cap, and whether it’s paid out when someone leaves.
Next, mark which items are legally required where you operate. Paid sick leave, paid family and medical leave, and local ordinances differ by state and sometimes by city or county, so check each work location. Your state labor department website is the right place to start, and the U.S. Department of Labor covers federal FMLA basics. These rules change, so record the date you checked (for example, “verified November 2026”) next to each requirement.
Then look for what was never written down. Managers granting an extra day after a long project, a sick-day policy that is enforced differently by team, or a standing promise made to a long-time employee: these informal practices become exposure the moment you formalize policy. Decide for each one whether to adopt it, end it, or grandfather it, and document that choice.
Finally, export current balances by employee and reconcile them to your payroll records. Compare hours accrued, hours taken, and the resulting balance. Discrepancies are normal, especially if time was tracked in spreadsheets, but you want to resolve them now so the opening numbers you load into the system are defensible. Keep the reconciliation file; you’ll need it again in Steps 5 and 7.
Step 3: Choose an accrual model and write the rules down
Four models cover most employers. Each has one tradeoff worth weighing.
- Front-loaded annual grant: employees receive the full year’s time on day one. It’s simple to explain, but someone who leaves in month two may have used time they haven’t earned.
- Per-pay-period accrual: time builds with each paycheck. It tracks service closely, but employees see small balances early and may feel restricted.
- Hourly accrual for non-exempt staff: time is earned per hour worked. It’s the most precise for variable schedules, and the hardest to audit by hand.
- Unlimited PTO: no balance to track. It reduces accrual administration, but employees often take less time, and managers need clear expectations to apply it fairly.
Whatever you choose, document these decisions: the accrual rate by tenure, the balance cap, the carryover limit, any waiting period before time can be used, and how part-time employees are treated. Vague wording here is what causes disputes later.
Check your state’s rules on two questions before finalizing: must accrued vacation be paid out at separation, and is use-it-or-lose-it permitted? These rules are not uniform nationwide. California is commonly cited as a state with restrictions on forfeiting earned vacation, but verify the specifics with the California Department of Industrial Relations rather than relying on a summary. Check every state where you have employees.
Mistake to avoid: choosing an accrual rule your configured system can’t calculate. Before you finalize the policy, ask ADP whether the model you want, including your tenure tiers, caps, and part-time treatment, is supported in the platform as of your implementation. If it isn’t, adjust the policy now instead of working around it with manual spreadsheets later.
Step 4: Align your handbook with ADP TotalSource’s policy support
Request the handbook resources or templates ADP makes available under your agreement. Lay them next to the inventory from Step 2 and compare line by line. Where the template is silent on something you offer, add it. Where your policy is more generous or more specific than the template, keep your language. A template is a starting point, not a requirement to match its wording.
Have employment counsel review the final PTO and leave sections. Template language may not fit multi-state operations or local ordinances, and a clause that works in one state can conflict with the rules in another. If you have employees in several jurisdictions, ask counsel whether you need state-specific addenda. This matters even more if you manage a remote workforce across several states.
Plan the employee acknowledgment before you publish anything. Decide:
- Whether employees acknowledge by signature or electronically
- What version date appears on the policy
- Where the signed or recorded receipt is stored, and who can retrieve it
If a dispute arises over what an employee was told, the dated acknowledgment is your best evidence.
Troubleshooting: if the handbook says one thing and the system configuration does another, stop and reconcile them before launch. Maybe the handbook promises a carryover of 40 hours and the plan setting caps at 20, or the handbook describes waiting periods the system doesn’t enforce. Decide which one is correct, then change the other to match. Resolving it after the first employee complaint is far more expensive than resolving it now.
Step 5: Configure PTO plans, balances, and approval workflows in the platform
Build in a deliberate order so each layer rests on the one before it:
- Create the plan types (vacation, sick, floating, and so on).
- Set the accrual and cap rules for each plan.
- Load opening balances from your reconciled file.
- Assign employees to the correct plans.
- Set manager approval routing.
Decide in advance who approves a request when a manager is out, and who is allowed to override or adjust balances. Keep adjustment rights with a small group, ideally HR or a designated administrator, and require a note explaining each change. Widespread edit access is how balances drift away from the written policy.
Before anyone relies on the setup, test it. Pick two or three sample employees: a new hire, a long-tenure employee, and a part-time employee. Calculate by hand what each should accrue over a pay period and a year, then compare that to what the system produces. Mismatches usually come from tenure tiers, proration for part-time schedules, or cap rules applied in the wrong order. Fix and retest until the output matches.
A note on specifics: ADP’s screens, menu names, and capabilities change over time, and what’s available can depend on your plan and service agreement. Treat any description of the tooling, including this one, as general, and confirm exact steps and current features with your ADP implementation team. Ask them to put any limitations in writing, especially on accrual rules and approval routing.
Step 6: Communicate the policy and train managers before go-live
Build a short rollout kit that employees will actually read. Include a plain-language policy summary, how to request time off, how balances are calculated, and who to contact with questions. One or two pages beats a forty-page handbook excerpt for day-to-day use.
Managers need their own training, because they decide how the policy feels in practice. Cover three things:
- Consistent approvals: apply the same criteria to everyone, and write down the reason when a request is denied.
- Protected leave: a request tied to a medical condition, a family member’s illness, or a new child may be covered by FMLA or a state leave law. Managers shouldn’t ask probing medical questions or decide eligibility themselves.
- Escalation: any possible FMLA or state leave situation goes to HR immediately, not after the manager has formed a view.
Set the effective date and write a cutover note for any balances that will change. If someone’s balance goes up or down under the new rules, tell them before the date, with the number and the reason. Surprises in a balance are the fastest way to lose trust in a new policy.
Mistake to avoid: launching during a peak holiday period without a freeze or a clear cutover rule. Employees will submit requests while balances are being loaded, and approvals made against old numbers create conflicts. Either avoid the busiest weeks or state exactly how requests submitted before the cutover will be handled.
Step 7: Monitor, audit, and revisit your policy after launch
Run a first-cycle check after the first one or two pay periods. Compare system balances to payroll deductions and accruals, using your reconciliation file from Step 2 as the baseline. Look for accruals that are too high or too low, time taken that didn’t deduct, and employees assigned to the wrong plan. Correct problems quickly and document what you changed.
Then set a quarterly review that looks at:
- Negative balances, which may signal an approval gap or an accrual error
- Balances near the cap, where employees are about to stop earning or lose time
- Unapproved absences, which point to either a process problem or a management one
Tie an annual policy review to two triggers: changes in state and local law, and your PEO renewal. Service scope and fees can change at renewal, so read the new terms against what you documented in Step 1 to see whether policy support has shrunk, grown, or been repriced. Your signed agreement, not a sales conversation, is the source of truth. It also helps to understand what a PEO contract actually says about cancellation and exit costs before renewal talks begin.
If policy support, flexibility in the HR system, or renewal terms are weak points for you, a side-by-side look at other providers is the way to test whether a different PEO would fit better. Our PEO versus payroll company comparison and our guide to PEO providers that take workplace investigations seriously are useful places to start that comparison.
Before you auto-renew, check what policy support you’re paying for
Once the policy is live, re-read your signed service agreement and your state requirements. Confirm that what ADP provides still matches what you documented in Step 1, and that your written policy still matches current law where you operate.
Before you sign that PEO renewal, make sure you’re not leaving money on the table.
Many businesses unknowingly overpay because of bundled fees, hidden administrative markups, and contracts designed to limit flexibility. We give you a clear, side-by-side breakdown of pricing, services, and contract terms, so you can see exactly what you’re paying for and choose the option that truly fits your business. If policy management is a deciding factor for you, that comparison is a good place to test it.