State-by-State Labor Compliance Guide: Breaks, Overtime, Leave, Minimum Wage Laws, and More

What this means for your organization: With nothing layered on top at the state level, every wage and hour question in Alabama runs straight through federal FLSA recordkeeping requirements. That makes accurate time records more important here, not less, since there’s no state-level buffer if a punch is missed or an employee is misclassified.

What this means for your organization: Alaska runs its own daily overtime clock on top of a rising minimum wage and a brand-new sick leave mandate. If your scheduling and time tracking setup isn’t already flagging 8-hour daily thresholds here, overtime liability builds up one shift at a time without showing up until payroll closes.

What this means for your organization: Arizona’s paid sick time mandate applies to organizations of every size, so even a five-person retail location has accrual and usage tracking obligations. Your headcount against the 15-employee threshold determines whether staff earn 24 or 40 hours of paid sick time, so confirm it every year. Getting that wrong in either direction creates a compliance gap.

What this means for your organization: Arkansas’s rules are some of the lightest in this guide, but the four-employee threshold on both minimum wage and overtime is worth double-checking. A location that dips below four employees, even temporarily, shifts to the federal $7.25 floor, which is easy to miss if your payroll setup treats every location the same.

What this means for your organization: California’s minimum wage and overtime rules layer by shift length, day of the week, and industry, not just one hourly rate. If your scheduling and time tracking solution’s records only total weekly hours instead of flagging daily thresholds and the right pay tier per role, you’re carrying premium pay exposure that won’t surface until payroll or an audit catches it.

What this means for your organization: Colorado’s 12-hour daily overtime trigger catches organizations used to thinking only in weekly totals, especially in healthcare and hospitality where 12-hour shifts are standard. Pair that with a sick leave law that applies from day one, and Colorado needs both daily hour tracking and immediate leave accrual working correctly from an employee’s first shift.

What this means for your organization: Connecticut’s sick leave threshold drops every year until it covers every employer in 2027, so if your organization is exempt today it likely won’t be exempt next year. Building accrual tracking into your setup now, even below the current 11-employee threshold, means you won’t be doing it under deadline pressure a year from now.

What this means for your organization: Delaware’s new paid leave program carries real payroll deduction and eligibility tracking obligations for any organization with 10 or more employees, even though it isn’t branded as traditional sick leave. If your time and leave records don’t already track hours toward the program’s 1,250-hour eligibility threshold, start now, since claims began processing in January 2026.

What this means for your organization: D.C. is the opposite of the federal-baseline states elsewhere in this guide. It layers its own paid sick leave and paid family leave programs on top of federal law, sets a minimum wage more than double the federal floor, and adjusts that wage every year without waiting on legislation. If you’re used to Virginia or Maryland rules, don’t assume they carry over across the district line. Payroll setup, leave accrual tracking, and tipped-wage calculations all need a D.C.-specific policy, not a regional one.

What this means for your organization: Florida’s minimum wage increase lands on September 30, not January 1 like most states, and payroll calendars built around a January cycle can miss it entirely. Flag that date now for every hourly and tipped role, since the jump from $14.00 to $15.00 hits fast-food, retail, and hospitality employers hardest.

What this means for your organization: Georgia’s Family Care Act only kicks in once an organization voluntarily offers paid sick leave in the first place. If you’re weighing whether to add sick leave as a benefit at a 25-plus-employee location, build the family-care carve-out into the policy from day one instead of adding it later.

What this means for your organization: Hawaii replaces the paid sick leave model most organizations expect with a wage-replacement insurance program, so a payroll setup built for accrual-based sick leave states won’t map cleanly onto Hawaii’s rules. Confirm your carrier or self-insured plan meets the Temporary Disability Insurance minimum before assuming your existing leave policy already covers it. 

What this means for your organization: Idaho doesn’t layer any state requirement on top of the federal floor for breaks, overtime, leave, or minimum wage, which makes it one of the simpler states to schedule for. Federal recordkeeping standards still apply just as strictly here as anywhere else, so document what happens when someone works through a break voluntarily rather than assuming the lack of a state rule means less exposure.

What this means for your organization: One statewide policy won’t cover an Illinois workforce that spans Chicago, Cook County, and everywhere else. Minimum wage, paid leave, and even overtime timing (because of ODRISA’s seventh-day rule) all shift based on where an employee physically clocks in, so your scheduling and employee time tracking setup needs to key off location, not just role.

What this means for your organization: Indiana’s lack of state-level rules on breaks, overtime, and leave means your compliance exposure here is largely a function of how well you track hours against the federal floor. If you operate outside Indiana too, don’t let its light-touch rules become your default template.

What this means for your organization: Iowa’s preemption law means you don’t need to check individual city ordinances the way you would in a state like Ohio or Illinois. One statewide policy genuinely covers every Iowa location. Like Indiana, that consistency doesn’t carry over to other states in a multi-state footprint, so don’t build a template around it.

What this means for your organization: Kansas sits at the federal floor across the board, so like Indiana and Iowa, the real compliance risk is in assuming every neighboring state works the same way.  Cross into Colorado, Missouri, or Nebraska and the rules change, so your time and scheduling setup needs to apply rules by location even where Kansas itself is straightforward.

What this means for your organization: Kentucky’s seventh-day overtime rule is easy to miss because most payroll setups only watch the 40-hour weekly threshold.  If you run continuous coverage in healthcare, public safety, or 24/7 retail, your setup needs to flag a seventh consecutive workday specifically, not just a running weekly hour count.

What this means for your organization: If you staff seasonal hospitality and tourism work in Louisiana, especially around events and festivals, every hour still runs through federal FLSA rules with no state break, leave, or wage floor underneath it. Build your policy around federal recordkeeping standards rather than assuming a lighter state framework means lighter documentation.

What this means for your organization: Maine’s earned paid leave and its new Paid Family and Medical Leave program cover different situations and run on different clocks, so don’t assume one satisfies the other. An employee using accrued paid leave for a doctor’s visit and an employee filing a 12-week medical leave claim are moving through two entirely separate systems.

What this means for your organization: Maryland’s retail-specific break rule is easy to miss because it isn’t a general state law the way California’s or Colorado’s is. If you operate retail locations in Maryland, confirm whether the Healthy Retail Employee Act applies to your specific store format before assuming the standard federal break baseline covers you.

What this means for your organization: Massachusetts and Maryland both split paid versus unpaid sick leave by employee count, but at different thresholds (11 in Massachusetts, 15 in Maryland). If you operate in both states, don’t apply one state’s headcount rule to the other.

What this means for your organization: Michigan’s employee-count threshold for sick leave days (10 or fewer versus 11 or more) sits right at a size many mid-market retail and hospitality locations hover around. A location that adds or loses one employee can flip from a 5-day to a 9-day obligation, so headcount needs to be checked regularly, not just once at setup.

What this means for your organization: Minnesota’s overtime threshold depends on whether  federal law covers you, and it covers almost every employer  of any real size, so the 40-hour rule applies in practice. Confirm that classification once rather than assuming, since getting it backward means underpaying overtime on a technicality that’s rarely tested until a claim is filed.

What this means for your organization: With no state law on breaks, overtime, leave, or wages, Mississippi’s compliance burden runs entirely through the federal FLSA. Treat your time tracking data as the primary evidence of compliance, since there’s no secondary state standard to fall back on if it’s incomplete.

What this means for your organization: If your organization built a leave policy around Missouri’s brief 2025 paid sick leave mandate, that requirement went away in August 2025, but the $15.00 minimum wage from the same ballot measure survived the repeal. Update your Missouri-specific policy documentation to reflect that split outcome rather than treating the whole measure as still in effect or fully undone.

What this means for your organization: The $4.00 sub-minimum exception in Montana almost never applies to mid-market or enterprise organizations, since it’s reserved for tiny operations outside FLSA coverage. Don’t let it distract from the real number: $10.85 applies to essentially every employer of any size.

What this means for your organization: Nebraska’s tipped minimum staying at $2.13 while the standard rate jumped to $15.00 creates one of the widest tip-credit gaps in the country. Double-check the payroll math for every tipped role specifically, since a formula built around a smaller gap in another state won’t catch a shortfall here.

What this means for your organization: Nevada’s daily overtime rule is wage-dependent, not universal, so a payroll setup needs to check each employee’s rate against the $18.00 threshold every time it changes, not just once at hire. A raise that pushes someone just above or below that line changes which overtime rule applies to their next shift.

What this means for your organization: New Hampshire’s paid family leave marketplace is easy to confuse with the mandatory programs next door in Massachusetts and Connecticut, but it’s genuinely opt-in here. Don’t assume an employee transferring from a Massachusetts location already has equivalent coverage in New Hampshire unless your organization specifically enrolled.

What this means for your organization: New Jersey layers a standard accrued sick leave law with a separate wage-replacement family leave program, and the two are easy to confuse since they cover overlapping situations like a new baby or a sick family member, but they work completely differently. Accrued time off and insurance-style wage replacement need separate tracking in your leave management setup.

What this means for your organization: New Mexico’s sick leave law has no size exemption, so a five-person satellite office carries the exact same accrual obligation as a 500-person location. Don’t assume a small New Mexico location is exempt just because similar-sized locations in other states might be.

What this means for your organization: New York runs geography-based minimum wage and organization-size-based sick leave tiers at the same time, so if you run multiple New York locations, payroll needs both a location field and an employee-count field feeding it, not just one or the other.

What this means for your organization: North Carolina relies on the federal floor for all four categories in this guide, a pattern shared with several other Southeastern states. That consistency across the region simplifies scheduling for a Southeast-heavy footprint, but don’t extend that assumption north or west without checking each state individually.

What this means for your organization: North Dakota’s break rule only applies when 2 or more employees are scheduled together, so a solo-staffed shift, common in rural retail and convenience formats, falls outside the requirement entirely. Build your break policy around actual staffing patterns rather than a blanket rule that may not apply to every shift.

What this means for your organization: Ohio ties its minimum wage and overtime coverage to an employer’s annual gross receipts rather than employee count alone, which is unusual nationally. Confirm which threshold applies to each Ohio location rather than assuming every location in the state pays the same floor.

What this means for your organization: Oklahoma’s $2.00 sub-minimum applies to a narrow band of employers outside FLSA coverage. For payroll planning purposes, treat $7.25 as the applicable rate. It’s worth knowing the exception exists only if you’re reviewing very small franchise or seasonal operations.

What this means for your organization: Oregon runs a three-tier minimum wage by geography on top of a manufacturing-specific daily overtime rule, so a single statewide policy doesn’t work even within Oregon. Location and industry both need to feed into the pay calculation, not just role or hours worked.

What this means for your organization: Pennsylvania’s local patchwork cuts in only one direction: cities can mandate sick leave but not a higher minimum wage. A Philadelphia or Pittsburgh location needs the city’s leave ordinance layered on top of the state wage floor, not a different wage rate entirely.

What this means for your organization: Rhode Island’s break rule size threshold (5 or more employees) mirrors the pattern in several other Northeast states, but each one sets its own headcount. Don’t assume the same trigger point applies across your whole New England footprint without checking each state’s specific rule.

What this means for your organization: South Carolina’s preemption law blocks any city from creating a local sick leave or wage ordinance the way Chicago and Philadelphia have elsewhere. That makes a single statewide South Carolina policy genuinely reliable, with no local exceptions to track.

What this means for your organization: South Dakota’s minimum wage adjusts every January without new legislation, so it’s easy to miss if your payroll calendar isn’t set up to check for it annually. Confirm the current rate each January rather than assuming last year’s number still holds.

What this means for your organization: Tennessee’s break rule, with its 5-employee threshold and tipped-employee waiver, is a real state requirement despite the state having no minimum wage law of its own. A state with no minimum wage law can still carry break rules, and Tennessee does, so the requirement needs a documented policy.

What this means for your organization: Texas has the lightest statutory floor of any state on this list. That still leaves you dependent on federal FLSA recordkeeping to back up your pay practices, since there’s no state break or leave rule to fall back on. It only holds up if your time tracking data stays accurate and consistent from the first punch.

What this means for your organization: Utah’s break, overtime, leave, and minimum wage rules all default to federal law, the same pattern as Mountain West neighbors Idaho and Wyoming. That makes a shared policy across those three easier to build, but Colorado and Nevada set very different rules despite being close by, so check each state individually rather than treating the region as one block.

What this means for your organization: Vermont’s 1-hour-per-52-hours accrual rate is slower than the 1-hour-per-30-hours formula used by most other sick leave states, including its New England neighbors. Don’t copy a Massachusetts or Rhode Island accrual formula into a Vermont-specific policy; the math is genuinely different here.

What this means for your organization: Virginia’s broader sick leave mandate is still ahead of you, with phase-in dates running through 2029. Build the accrual tracking into your roadmap now, based on your organization’s size, rather than waiting for the first compliance deadline to arrive.

What this means for your organization: Washington’s paid sick leave has no employer-size cutoff, unlike Maryland, Massachusetts, or Connecticut, so even a single-location organization with a handful of employees carries the same accrual obligation as a statewide chain. Don’t assume a small Washington footprint is exempt just because a similar-sized location elsewhere would be.

What this means for your organization: West Virginia’s $8.75 rate is easy to overlook because it sits between the federal floor and the headline $15-plus rates. Give it its own line in your payroll setup instead of rounding it down to $7.25 or grouping it with nearby states.

What this means for your organization: Wisconsin’s preemption law blocks a city like Milwaukee or Madison from creating a local sick leave ordinance, unlike Illinois just across the border, where Chicago and Cook County both layer on extra rules. A single statewide Wisconsin policy is genuinely reliable in a way a similar Illinois policy isn’t.

What this means for your organization: Wyoming’s on-the-books $5.15 rate looks like an outlier next to the federal $7.25 floor, but in practice almost every covered organization already pays the higher federal rate. Treat $7.25 as the real number for planning, the same way you would in Georgia.