Purpose
On Amazon Delivery Service Partner (DSP) accounts, UZIO creates and assigns up to four time-off policies for you. You do not set them up, and you should not recreate them. This article states exactly what is created, what triggers it, and who ends up assigned, so you know what your workforce already has before you add anything else.
Who this affects: DSP accounts. One policy is scoped to Delivery Associates. The other three are scoped by work location, and reach every active employee at that location, not only Delivery Associates.
Who can view and manage these policies: users whose role includes permission to manage time off, which the Employer Administrator has by default. The policies are created by UZIO rather than by a user, so they appear without anyone having added them.
Note: UZIO never creates a duplicate. If a policy with the same name already exists on your account, creation is skipped. Each policy's matching payroll earning is created and linked at the same time, so the time off reports correctly on payroll.
1. Paid PTO
Created when an employee is first placed in the Delivery Associates job category. It is then assigned to every employee in that job category.
How UZIO keeps Paid PTO up to date
Paid PTO is designed for Delivery Associates, and UZIO manages who has it for you:
- When an employee is added, rehired or moved into Delivery Associates, UZIO assigns Paid PTO automatically.
- Whenever an employee's information is updated, for example their job or pay, UZIO checks their job category again.
- If the employee is not in Delivery Associates, UZIO removes Paid PTO from them. Their existing balance is kept, and accrual stops from that point.
You can assign Paid PTO to staff in other job categories, such as managers or office staff. It will be removed at the next update to their information, as in step 3. For these employees, set up a separate policy, such as "Office PTO", so their time off is not affected by changes to their record. See Adding and Managing Time Off Policies.
Keep the policy as UZIO set it up. Paid PTO's settings follow the Amazon DSP program, and UZIO uses the policy name to recognise it. Leave the settings and the name unchanged. If you need something different, contact UZIO.
| Setting | Value |
|---|---|
| Policy name | Paid PTO |
| Effective / start date | December 1, 2025 |
| Leave type | Paid |
| Accrual method | Flat amount on hours worked, at 0.04 hours accrued per hour worked |
| New-hire waiting period | None |
| Proration | None. The grant is not prorated for a mid-period start |
| Carryover | Yes, capped at 120 hours, on a calendar-year basis |
| Payout on termination | Yes. The balance is paid out when the employee is terminated |
2. NY City Unpaid Sick Policy
Created when a New York City work location is saved on the account. It is then assigned to all active employees at your New York City work locations, not only Delivery Associates.
| Setting | Value |
|---|---|
| Policy name | NY City Unpaid Sick Policy |
| Effective / start date | January 1, 2026 |
| Leave type | Unpaid |
| Accrual method | Yearly. 32 hours granted each January 1 |
| New-hire waiting period | None |
| Proration | None |
| Carryover | No |
| Payout on termination | No |
3. NY State Prenatal Leave
Created when any New York State work location is saved on the account. It is then assigned to all active employees working in New York State, not only Delivery Associates. It exists to meet New York's paid prenatal leave law, which took effect on January 1, 2025.
| Setting | Value |
|---|---|
| Policy name | NY State Prenatal Leave |
| Effective / start date | January 1, 2025 |
| Leave type | Paid |
| Grant | 20 hours up front, with no waiting period and no proration |
| Balance cap | 20 hours. The balance can never exceed the grant, even after a cancelled request refunds hours |
| Renewal | On the First Usage Anniversary cycle. The 52-week clock starts when the employee first uses the leave, and the balance resets when that rolling year completes. See Understanding Accruals and Carryover |
| Carryover | No, locked by the First Usage Anniversary rule |
| Request increments | Whole hours |
| Payout on termination | No |
4. Chicago Paid Sick and Safe Leave
UZIO creates and assigns this policy automatically for DSPs with a work location in the City of Chicago. You don't need to set it up or assign it yourself. It exists to meet the City of Chicago's paid sick and safe leave ordinance.
Who receives it
- Every active employee at a Chicago work location, whatever their job category.
- Only locations inside the City of Chicago are included, as the city ordinance requires. Locations elsewhere in Illinois, such as Arlington Heights or Palatine, are not.
How it works with Paid PTO
Chicago Paid Sick and Safe Leave is a separate sick-leave balance that sits alongside the employee's regular PTO:
- A Delivery Associate at a Chicago location has Paid PTO and Chicago Paid Sick and Safe Leave.
- Other staff at a Chicago location have their own PTO policy, such as Office PTO, and Chicago Paid Sick and Safe Leave.
Both stay active together, and each keeps its own balance on the employee's Time Off tab and pay stub.
| Setting | Value |
|---|---|
| Policy name | Chicago Paid Sick and Safe Leave |
| Effective / start date | January 1, 2026 |
| Leave type | Paid sick leave |
| Grant on assignment | 40 hours, credited when the policy is assigned to the employee |
| Accrual method | Yearly. 40 hours granted each January 1 |
| Waiting period before use | 30 days. The hours cannot be used until the waiting period has passed |
| Proration | None |
| Carryover | Yes, capped at 80 hours, on a calendar-year basis |
| Request increments | Whole hours |
| Payout on termination | No |
Some settings are locked. The city ordinance fixes three of this policy's settings, so UZIO refuses any edit that changes them: carryover, the 80-hour carryover cap, and payout on termination, which stays off. You also cannot add or remove accrual rows on this policy, because each row carries its own carryover cap. Every other setting stays editable. If you try to change a locked setting, the save is refused with a message such as:
"Carry over cap is fixed by city ordinance on the Chicago Paid Sick and Safe Leave policy and cannot be changed. It must stay 80. Every other setting on this policy remains editable."
Keep the policy as UZIO set it up. Leave the other settings and the policy name unchanged too, so the policy stays aligned with the ordinance and UZIO keeps recognising it. If you need something different, contact UZIO.
Your home page can also list Chicago employees who are not on this policy. See Your Employer Home Page (Compliance Dashboard).
Settings all four share
| Setting | Value |
|---|---|
| Units | Hours, based on an 8-hour working day |
| Work days | All seven days of the week |
| Approver | Manager |
| Negative balance | Not allowed |
| Shows on the pay stub | Yes |
What this means for you
- The policies are already assigned. You do not need to create or assign them, and you should not build your own versions alongside them.
- Paid PTO follows the job category on its own. Adding, rehiring or editing an employee assigns or removes Paid PTO to match their job category, as described above.
- Check the location-based policies for later hires. UZIO assigns the New York and Chicago policies to the employees who qualify at the moment each policy is created. For employees who join or move location afterwards, confirm the policy is on their record before assuming it is. See Assigning Time Off Policies. If someone is missing, assign them there.
- You can still add your own policies. See Adding and Managing Time Off Policies.
- Payroll picks the balances up automatically. A matching time-off earning is created and linked for each policy, so time off taken under it flows to the pay run without any earning setup. See Company-Level Earnings.
- Only Paid PTO pays out. The balance reaches the final paycheck like any payout-enabled policy. See PTO Balance Payout on Termination. The New York and Chicago policies do not pay out.
- Non-DSP employers with New York or Chicago locations do not get these policies automatically. Their administrators create and assign them by hand.
Warning: Do not change or discontinue an auto-created policy because it looks wrong. These policies carry Amazon program settings and New York and Chicago statutory settings, and changing an accrual rule mid-year affects balances that have already accrued. Ask UZIO before editing one.
Need help?
If a policy you expect is missing, if an employee is not assigned to one, or if you need a setting changed, contact your UZIO Customer Success Manager, or UZIO Support at support@uzio.com or +1-571-601-1752. Send the policy name, the employee name and ID, the employee's work location and job category, and a screenshot of the employee's Time Off tab.
Related articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article