Compliance, before it’s a problem

Amazon’s hours rules are a rolling seven days, not a calendar week; they follow the person across every station they work at; and they are cheaper to keep than to break. OpsBrio checks them in three places — while you plan, while the day runs, and before payroll. This is the map of all three.

The limits, the warnings, the alarms

Settings › Hours rules

12 hours

In a day.

60 hours

In any rolling seven days — today and the six behind it. Not Sunday to Saturday.

10 hours

Of rest between shifts.

6 days

In a row. The seventh breaks it.

Warnings

From 50 hours in the seven, and from a fifth day in a row: allowed, but worth knowing.

Alarms

On the road past 11 hours today, or past 58 in the rolling week: the desk is rung.

Those are Amazon’s numbers, and every company starts with them. If yours are stricter, change them on Settings › Hours rules: the schedule’s warnings, the board’s checks, extra-shift offers, the desk’s alarms and Home follow at once. Landing exactly on a limit is allowed — 60 exactly is at the limit, not over it, and the sheet says so: “exactly the limit, with no room left”.

While you plan: the schedule refuses

Schedule › open a day

Open a day for a driver and the sheet adds the hours they have already worked to the hours scheduled ahead — across every station — and reads the result back before you save. It answers in one of three ways:

Clear

“Within every limit. Peaks at 46h over the rolling 7 days.”

Warned

“Allowed, but worth knowing.” 50 hours or more in the rolling seven, or a fifth or sixth day in a row.

Refused

“This would break a rule.” A sentence says which — “Arlo would reach 62 hours over the rolling 7 days ending Friday. The limit is 60.” — and Save stays off.

So a driver five days and 52 hours into the week cannot be given a full ten-hour sixth day — and opening their row on HR & Compliance › Compliance shows the gauge: 8.0 hours of headroom left. That is the shift they can work. A sixth day in a row is allowed and flagged; a seventh is refused. A change that breaks a rule and lands in a warning shows both, and only what the change itself causes or makes worse is counted.

While the day runs: the 11-hour call

Every five minutes, at every station: a driver still out 11 hours after their check-in — or at 58 hours in the rolling week and still on the road — rings every office phone at that station that can see Dispatch, quiet hours or not. The 11 hours count from the driver’s own Check in (or the desk marking them in), not the shift start. Each alarm rings once per driver, and drivers who cross in the same five minutes arrive as one push. The board wears a red chip, 11h+ on road or 58h+ week, and Home says it in red, until they check out.

Your appnow

Arlo Fenwick: 11.1h on the road, not checked out

Past the 11h mark at DFL2. Get them back or check them out.

Before payroll

HR & Compliance

Where the record and the road disagree. Nobody broke a rule; something needs fixing, and the same day is when somebody still remembers.

Compliance

One Sunday-to-Saturday week — this one, or an earlier one — with the days still ahead read from the schedule: who is over, near or clear, and missing punches and a punch with no route counted beside the rules. Next week’s picture is the schedule’s own chips.

Breaks

Three clocks for one meal: the break the driver pressed in Amazon’s app, the payroll punches, and the van’s own unplanned stops. A rest over 15 minutes exceeds; over 18 it is a potential meal; payroll may carry a meal up to 5% shorter than the app — longer is fine. The lines are yours, on Settings › Breaks.

Timecards

A payroll clock-out more than 15 minutes after the Flex sign-out. The driver is told on their phone — “Possible timecard mismatch” — and answers I’ve fixed it or It’s correct; HR sees who has answered.

Missed punches

After the check-in form, Home asks the driver to clock in on your payroll app at their shift time; after the check-out form, to clock out — and one push follows ten minutes later, only if they have not pressed.

Paperwork with a clock on it

Documents

An MVR or base-access document turns amber 30 days before its date and red after.

Incident report

Four questions on the accident step decide Amazon’s two-hour drug and alcohol test. Four no’s, no test and no clock; any yes — or Amazon’s own flag — starts it, and the two hours count from when the incident happened.

Uniform

A note from the board reaches the driver’s phone and waits on their Home until they tap Got it. The coaching ladder counts each one for 90 days — your number: at its coaching step a coaching goes with the note; past it, a written warning is drafted for whoever issues.

The I-9

A reminder a day, three at most, by email and text, stopping on the training day. The pictures are kept while the person works for you, then until the later of three years after hire or one year after their last day; the SSN goes 30 days — your number — after HR marks it entered in payroll.

Hours at Amazon

A red flag on Finance › Hours and the person’s page when a driver’s punches are not reaching Amazon — almost always their Payroll information in Cortex.

Where the money side lives

Paid against clocked is Finance › Hours — the Owner’s, unless they share it. What Amazon owes for the routes you ran is Operations › Routes, held against Amazon’s Work Summary. Both are in the guide Finance.