Fair Workweek Compliance Checklist for Retailers

The first time I heard "fair workweek," I was standing behind a counter mid-Saturday, and someone at a retail meetup mentioned it in passing like I obviously already knew. I didn't. I nodded, made a mental note, and then didn't think about it again for a year — because it sounded like something that applied to big-box chains and fast-food franchises, not to a single storefront with a handful of part-timers.

That assumption is the risk. Fair workweek isn't a federal law. It's a patchwork — a handful of cities, one state, a few industry carve-outs, some size thresholds. Most independent retailers I've talked to assume it doesn't apply to them, and most of them are right. But the ones who are wrong usually find out from a complaint, not from a lawyer's newsletter.

So this isn't a legal brief. It's the pre-flight check I wish someone had walked me through before a busy season — four short checklists you can answer with yes, no, or "I need to check." If enough of the answers point one direction, the next call is to your employment lawyer or accountant. This piece gets you ready for that conversation. It doesn't replace it.

Step 1 — Find out if you're actually covered

Coverage is the whole game. If you're not in a covered jurisdiction, in a covered industry, above the size threshold, the rest of the checklist is optional reading. If you are, everything else matters.

• Is your store located in a city or state with an active fair workweek ordinance (currently: NYC, Philadelphia, Chicago, Seattle, San Francisco, Los Angeles, Emeryville, Oregon statewide, and a couple of others)? Yes / No / I need to check
• Does the ordinance in your jurisdiction cover retail specifically, or only fast food and hospitality? Yes / No / I need to check
• Do you employ more than the threshold count of workers globally (not just at this store — most laws count total employees across all locations, and some count franchise networks)? Yes / No / I need to check
• Are you above any revenue threshold your jurisdiction sets? Yes / No / I need to check
• Do any of your staff work at multiple locations across a covered jurisdiction line? Yes / No / I need to check

For the city-by-city breakdown — thresholds, industries, effective dates — see our fair workweek guide. This checklist is the layer above it: the operational questions you ask after you've figured out which rules apply.

If you answered "no" or "I need to check" to all five, you're probably not covered — but "probably" is where the trap is. Employee counts creep up. Cities pass new ordinances. Check again before every busy season.

Step 2 — Check your advance-notice window

This is where most operators who are covered get caught. The rules are boring but specific: you generally have to post the schedule 14 days in advance (some jurisdictions say 10, some say 7 during a phase-in). Changes after posting can trigger predictability pay — extra wages you owe the employee for the disruption.

• Do you publish the week's schedule at least 14 days before the first shift starts? Yes / No / I need to check
• Is "publishing" happening in a way you can prove — a timestamped notification, not a printed copy taped to the break room fridge? Yes / No / I need to check
• When you do change a shift after publishing, do you know which changes trigger predictability pay (adding hours, cutting hours, moving the shift) versus which don't (an employee-requested swap in writing)? Yes / No / I need to check
• Do you have a written record — with a timestamp — of every schedule change and who initiated it? Yes / No / I need to check

If any of those are "no," the fix isn't heroic. It's habit. Pick a publish day. Stick to it. Make sure changes are logged with who asked and when.

Step 3 — Review your swap and callout paper trail

Here's the distinction most fair workweek ordinances draw: manager-initiated changes are the ones that cost you. Employee-initiated, employee-consented changes generally don't — but only if you can show the consent was actually voluntary and actually recorded.

That's where a text-message trail, a group chat, and a folder of scribbled notes stop being enough.

• When an employee asks to swap a shift, is the request in writing (in-app, SMS, email — not a hallway conversation)? Yes / No / I need to check
• Does the covering employee's acceptance also get recorded in writing? Yes / No / I need to check
• When someone calls out, do you have a record of the callout time, who was contacted next, and who accepted the coverage? Yes / No / I need to check
• If a jurisdiction inspector asked for the last 90 days of schedule changes tomorrow, could you produce a clean, timestamped record within a day? Yes / No / I need to check

You don't need a filing cabinet. You need a system where every swap, every callout, every published change carries a timestamp and a name. That's the whole trail.

Step 4 — Look at what your time clock actually shows

This is the part I underestimated the longest. An audit doesn't just look at the schedule you posted. It looks at the gap between the schedule you posted and the hours your staff actually worked. If the posted shift ended at 6 and the clock-out was at 6:47, someone is going to ask why — and whether that extra 47 minutes was manager-directed (which might trigger predictability pay) or employee-volunteered (which might not).

• Do your clock-in and clock-out times tie back to a specific posted shift, or are they a separate spreadsheet that doesn't know what the roster said? Yes / No / I need to check
• Can you spot, in one view, every clock-in that doesn't match the posted shift? Yes / No / I need to check
• Are your clock-ins verified by location, so you know the person actually showed up at the store instead of a manager punching them in? Yes / No / I need to check
• If someone called out and a backup covered, can you show the notification chain that led to the swap? Yes / No / I need to check

This is where Schedaddle's geofence time clock earns its keep. Staff clock in from their own phone at the store — the location is verified, the clock-in is timestamped, and it's tied back to the shift you posted. When there's a gap between posted and actual, you can see it in one screen instead of stitching together a spreadsheet, a text thread, and a memory. That's not compliance. That's the record your compliance conversation is built on.

One pricing note before you go

Fair workweek doesn't get easier as you add staff. If anything, it gets harder — because the advance-notice rules assume you have enough bench depth to cover callouts without last-minute manager-initiated changes. The tools that charge you per employee punish you exactly when you're trying to build that bench.

Schedaddle is per-location, not per-seat. Hire the tenth part-timer to give yourself a real backup rotation and your bill doesn't move. That's not a compliance feature. But it stops your scheduling tool from working against the habit fair workweek is trying to build.

Closing

None of this replaces a conversation with your employment lawyer or your accountant. What it does is make that conversation shorter and cheaper — you walk in already knowing which of the four checklists you're weak on, instead of paying someone to figure it out from scratch. If most of your "I need to check" answers landed in Step 1, start there. Read the fair workweek jurisdiction breakdown, figure out if you're covered at all, and if you are, work down the list.

Before the next busy season lands — what would an audit actually see if it pulled your last four weeks of schedules? If you had to answer that question by Friday, where would you start looking?