Working-Hour Limits for Delivery Associates

Purpose

Amazon requires Delivery Service Partners to keep Delivery Associates (DAs) within working-hour limits. UZIO enforces two: 12 hours in a day and 60 hours in any rolling 7-day window. It checks them at scheduling time, when a shift is created, published, or reassigned, and warns before the schedule breaches a limit. It also tells you the next morning about breaches that actually happened.

When to use this: you do not turn it on or configure it. The limits are set by UZIO for DSP accounts and are not an employer setting. Use this article to understand when the warning appears, how the hours are counted, and what to do about a breach.

Who sees the warnings: users who create, publish, or approve shifts (typically the Employer Admin, and Reporting Managers within their team scope). The daily breach notifications go to employer administrators.

When the system evaluates compliance

1. Shift create with Save and Publish. UZIO first checks shift overlap for every impacted employee and shows any overlap. If there is none, it creates and publishes the shift, then evaluates working-hour compliance for the DAs on it and shows a warning for any breach.
2. Publish shift. UZIO shows the publish summary, then evaluates DA compliance and shows a warning for any breach.
3. Shift offer or claim approval. On approving a claim or offer, UZIO evaluates the daily and weekly limits for the DA who will receive the shift.
4. Shift swap approval. On approving a swap, UZIO evaluates both limits for both employees.

Open (unassigned) shifts are not evaluated until someone claims them.

How the limits are calculated at scheduling time

Daily limit: more than 12 hours in a day. A day is a calendar day starting at midnight. For each impacted DA:

• Existing hours are taken from worked time for past days (time-entry hours including breaks and any running entry, excluding break premiums) and from scheduled time for today and future days (published and unpublished shifts).
• The new shift's hours are added.
• If the total exceeds 12, the shift is flagged.

Rolling 7-day limit: more than 60 hours in 7 days. For each shift date being published or assigned, UZIO evaluates the window of that date plus the six days before it (08/08/2025 evaluates 08/02 to 08/08):

• Existing hours use the same definitions.
• The new shift's hours are added.
• If the total exceeds 60, the shift is flagged.

Daily notifications for actual breaches

At the start of each day, employer administrators receive two in-app notifications:

• DAs who breached the 12-hour daily limit on the previous day.
• DAs who breached the 60-hour rolling 7-day limit over the 7 days ending yesterday.

These use worked hours, not scheduled hours. A time entry still in progress is counted up to midnight. Example: at 00:10 on 09 Aug the daily check evaluates 08 Aug and counts a running entry from 11:00 AM as 11:00 AM to 11:59 PM. The 7-day notification sums worked hours over 02 Aug to 08 Aug and fires when the total exceeds 60.

What to do about a breach

• Before it happens: when the warning appears on publish or approval, shorten the shift, move it to another day, or assign it to a different DA. The warning does not stop you from publishing.
• After it happens: review the DA's time entries on the Employees Timesheet to confirm the hours are genuine (a forgotten clock-out inflates a day fast), and adjust the coming week's schedule so the rolling total drops below 60.
• Keep the missing clock-out flag and long-running reminders on (Controlling How Employees Clock In and Out); most false breaches are unclosed entries.

Related articles

• Manager Override Monitoring for Delivery Associate Time Entries
• Getting Started with Scheduling in UZIO
• Managing Shifts: Creating, Publishing, Editing, and Deleting
• DSP on UZIO: What's Different