The 32-Hour Exposure Audit: Log the Scheduling Decision

Open the payroll file before the news feed. Sen. Bernie Sanders and Rep. Mark Takano reintroduced the Thirty-Two Hour Workweek Act on Sept. 8. Rep. Mark Takano first introduced the idea in 2021, and earlier versions did not advance. The bill may not become law, but a small team still needs a record of the week it actually runs. A payroll surprise is worse than a policy debate, and the audit turns scheduling into an operating decision.

The exposure is the hours you already run

The bill would lower the weekly overtime threshold in stages, moving from 40 hours to 38, then 36, then 34, and ultimately 32 hours. After the phase-in is complete, a covered employee on a 40-hour week would generally receive time-and-a-half for the last eight hours. The bill would also create daily overtime: employees would earn 1.5 times regular pay after the eighth hour in a day and twice regular pay after the twelfth hour. Those numbers are the test for the schedule you already run, not a forecast of a future law.

The phase-in changes the cost of the same week. A schedule that looks normal today can become expensive tomorrow. The daily rules add another layer, because a long day can create exposure even when the week looks clean. The audit needs both weekly and daily marks, so the team can see which hours are already close to the proposed triggers.

The audit is a decision that fits on a page

A small team does not need a legal forecast. It needs a record of the week it actually runs. A non-exempt hours audit should separate the roles, the hours, and the triggers. If the answer is unclear, the schedule is the problem.

Pull the time clock, the payroll file, and the calendar. Do not try to build a perfect system. You only need enough detail to see the typical week and the daily spikes. If a role is exempt, leave it out. If a role is non-exempt, put it in. If the hours are unclear, treat the role as exposed until the record says otherwise.

The checklist keeps the decision honest

The list is short because the decision is short. Each item is meant to be testable quickly. The audit is a record that can be defended in a payroll review.

The opening items create the population. The middle items mark exposure. The closing items force a choice and a record.

• List every non-exempt role and the person currently assigned to it.
• Log typical weekly hours for each role over recent weeks.
• Mark weekly hours above 32 as exposure.
• Mark any day over 8 hours as daily exposure and any day over 12 hours as double-time exposure.
• Choose the standard week: a 32-hour cadence or a 40-hour week priced at time-and-a-half for hours above 32.
• Record the choice in the decision log with owner, date, and review trigger.

If the audit shows most weeks already sit above 32 hours, the standard week is a pricing decision. If the team can absorb a shorter cadence, the standard week becomes a scheduling decision. Employers could still schedule 40-hour workweeks under the proposal. The choice is between a compressed week and a priced week, not between compliance and growth.

The choice should be made by the person who owns payroll, not by the person who owns the calendar. The owner should be able to say which week the team runs and what the extra hours cost. If the answer is a guess, the audit is not done.

The owner should also note what the team will stop doing if the standard week changes. A schedule is only useful when it has a boundary. The boundary can be a start time, a stop time, or a coverage rule.

The decision log entry should name the owner, the date, the standard week, and the trigger that forces a re-audit. A re-audit is due when a role changes, when a new non-exempt hire starts, or when the bill moves again. The log should be short enough to read in a meeting and complete enough to show why the week was chosen.