FLSA Workweek: How to Set It and Compute Overtime

The first time somebody asked me what our workweek was, I said Monday to Friday. That was wrong in two ways at once. It named five days instead of seven, and it described when people happened to work rather than the window our overtime was measured in. Nobody had ever written that window down. We had one anyway.

That is the part employers miss. The workweek is not a policy you adopt when you get around to it. It is a legal unit that already exists in your business the moment you pay anybody overtime, because your payroll had to measure forty hours against something. Whatever it measured against became your workweek, established by conduct. If that seven-day span is not the one you would have chosen, you find out during an audit rather than during a planning session.

This guide is the employer side of that: what the workweek is in law, how you establish one, why each one stands entirely alone even when your pay period covers two, what it takes to move the boundary without breaking the rule, how to compute the pay period where a move lands, the 8 and 80 alternative that hospitals get, and what has to be on file to prove any of it. I build people and records tooling at FirstHR, and this is general information rather than legal advice.

What an FLSA Workweek Is

An FLSA workweek is a fixed and regularly recurring period of 168 hours: seven consecutive 24-hour periods. It may begin on any day of the week and at any hour of the day, and once it begins it recurs on that same boundary regardless of what anybody actually works.

The statutory language is worth reading once, because it does the work. Section 7(a)(1) prohibits employing a covered employee for a workweek longer than forty hours without paying at least one and a half times the regular rate for the excess (29 USC 207). Everything else follows from the phrase "a workweek". The unit is singular, and it is weekly.

What throws people is that the workweek has nothing to do with how many days somebody works. A person who works three shifts still has a 168-hour workweek, because the window exists independently of the activity inside it. The window is how you know which three shifts get added together.

How a Workweek Gets Established, Including the One You Already Have

You establish a workweek by choosing a start day and a start hour and then applying it consistently. There is no filing, no notice to any agency, and no approval. There is also no requirement that you write it down before it becomes real, which is the part that catches employers.

A workweek can be established by conduct alone. If your payroll has been totaling hours from Sunday morning to Saturday night for two years, you have a Sunday-to-Saturday workweek, whether or not any document says so and whether or not anyone decided it deliberately. Somebody configured a payroll system once, and that configuration became a legal fact about your business.

The practical consequence is a sequence. Find the workweek you are running, decide whether it is the one you want, and only then write it down. Writing down a boundary that contradicts two years of payroll behavior does not fix the past; it documents the discrepancy.

One more thing about establishment: it is per employee, not per company, at least in the sense that the record has to exist for each person. You may apply one boundary to everybody, but the wage and hour rules describe the workweek as an attribute of an employee’s payroll record rather than a single company-level setting.

Your Workweek Is Not Your Pay Period, Your Calendar, or Your Schedule

The workweek and the pay period are different objects that happen to be measured in the same units. The workweek is what overtime is computed on. The pay period is how often you hand over money. They are allowed to disagree, and on most pay cycles they do.

A biweekly pay period contains exactly two workweeks, which is tidy. A semimonthly pay period contains about 2.17 workweeks, which is not tidy at all: workweeks routinely straddle the boundary between one semimonthly check and the next. That is normal and lawful. What it means is that a workweek split across two checks still has to be totaled as one workweek, with any overtime paid on the check covering the period in which the workweek ended, or as soon as practicable after.

The calendar week is a third object, and it is the one people confuse with the workweek most often. A calendar week starts Sunday or Monday depending on who is asking. Your workweek starts wherever you put it. If your production week genuinely runs Wednesday to Tuesday, a Wednesday workweek is the honest choice, and choosing Sunday because it looks normal only creates arithmetic you did not need.

The schedule is the fourth. A 9/80 schedule is the clearest case, because it only works when the workweek boundary is deliberately placed in the middle of the alternating Friday, splitting that day into four hours on each side. The schedule was designed around the workweek, not the other way around, and that is the correct direction of travel.

Each Workweek Stands Alone, and Averaging Is Unlawful

Each workweek stands alone. Overtime is computed on the hours worked inside one workweek and nothing else, so a short week never offsets a long one and two weeks are never averaged together. This holds no matter how you pay, including on a biweekly cycle where the two weeks land on the same check.

The rule is not a technicality. It exists because the point of the overtime premium is to discourage long weeks, and averaging would let an employer schedule sixty hours in one week and twenty in the next at no premium at all. The statute measures "a workweek longer than forty hours" one workweek at a time, and there is no provision anywhere for smoothing.

Two things make employers drift into averaging without deciding to. The first is a payroll system configured with a fourteen-day accumulation instead of two seven-day ones, which quietly produces the wrong answer for every bunched schedule you run. The second is thinking in salary terms about hourly people: eighty hours in a two-week period feels like full-time normality, and the split inside it stops registering.

The exposure compounds because it applies per employee per cycle and is invisible on the pay stub, so it runs for years before anyone notices. Federal back pay generally reaches two years, or three where the violation was willful, and unpaid overtime is commonly doubled as liquidated damages. The related trap is treating paid leave as hours worked, which the guide to whether PTO counts towards overtime works through in detail.

How the Same Hours Produce Completely Different Overtime

Because overtime is computed per workweek, where you put the boundary changes what you owe on an identical schedule. This is not a loophole, it is arithmetic, and it is at its most dramatic on bunched schedules where somebody works a long consecutive block and then nothing.

Take an employee on a 7-on, 7-off pattern at $20 an hour: seven consecutive twelve-hour shifts running Wednesday through the following Tuesday, then seven days off. That is 84 hours across a fourteen-day stretch, and the schedule never changes. Now watch what the boundary does to it.

Under the Sunday workweek the block splits four days into one week and three into the next: 48 hours produces 8 hours of overtime, and 36 hours produces none. Under the Wednesday workweek all seven shifts land inside one workweek, so 44 of the 84 hours are overtime. Same person, same shifts, a $360 gap every cycle, which is $9,360 a year on one employee.

Choosing the boundary at the outset is entirely lawful, and there is no rule requiring you to pick the most expensive one. What you may not do is treat the boundary as a dial to turn when a busy stretch arrives. The moment it moves in response to the schedule rather than the other way around, it stops being fixed, and a workweek that is not fixed is not a workweek.

Different Workweeks for Different Employees and Locations

You may use more than one workweek. Different employees, different departments, different job classifications, and different locations may each have their own, provided each one is fixed and regularly recurring on its own terms and applied consistently to the people it covers.

This is genuinely useful. A restaurant group with a kitchen on a Wednesday cycle and an office on a Monday cycle is not doing anything unusual. A manufacturer whose plant runs a rotating pattern and whose sales team works weekdays has two real operating rhythms, and forcing both into one boundary only creates split shifts and reconciliation work.

The cost of the flexibility is administrative discipline, and it is where multi-workweek employers actually fail. Each group needs its boundary documented, configured in payroll, and reviewed when anything changes. The failure I have seen most often is a transfer: someone moves from the plant to the office and keeps the plant workweek in the payroll record for months, because nobody thought of the workweek as a field that travels with a person.

Two guardrails are worth adopting even though no rule requires them. Keep the number of distinct workweeks small enough that you can recite them from memory, and never let a workweek differ between two people doing the same job at the same site. Different boundaries for identical work invite the argument that the assignment was about overtime rather than operations, which is the exact suspicion the change rule is built to police.

How to Change Your Workweek Without Breaking the Rule

You may change the beginning of the workweek, for one employee or for a group, if the change is intended to be permanent and is not designed to evade the overtime requirements of the Act. Those are the two hurdles, stated in that order, and both have to clear.

Permanence is the operative word. A change made in September and reversed in January is not a permanent change, it is a seasonal adjustment, and it will be read as exactly what it looks like. The regulation has no concept of a temporary workweek, so a boundary that moves twice has effectively never been fixed at all.

The evasion prong is where courts have divided. In Abshire v. Redland Energy Services (Eighth Circuit, 2012), an employer permanently redesignated the workweek so that fewer hours of an unchanged schedule counted as overtime, and the court held the change lawful, reasoning that once permanence is established the employer’s reasons are not the question. Other courts weigh business justification more heavily, so the safe practice is to have and record one regardless of where you operate.

Computing Overtime in the Pay Period Where the Change Lands

When you move the workweek boundary, some hours necessarily fall inside both the old workweek and the new one. The regulations resolve this by requiring you to compute the transition twice, once counting the overlapping hours only in the old workweek and once counting them only in the new, and pay the greater of the two results.

The overlap is unavoidable rather than a mistake. Section 778.301 describes it plainly: shifting a plant workweek from Monday to Sunday means the hours from Sunday to Monday are both the last hours of the old workweek and the first hours of the new one. You cannot make the overlap disappear, so the rule tells you how to price it.

Work an example. Your workweek runs Monday to Sunday and you are moving it to Saturday. In the transition, the employee works ten hours on Monday through Thursday, nothing Friday, and eight hours on Saturday and on Sunday, then eight hours on Monday through Wednesday of the following stretch. The Saturday and Sunday, sixteen hours, are the overlap.

Method 1 pays 40 hours at $20 plus 16 hours at $30, which is $1,280, then 24 hours at $20, which is $480, for $1,760. Method 2 pays two forty-hour weeks at straight time, which is $1,600. The employee is owed $1,760 (29 CFR 778.302).

The point of the greater-of rule is that it removes the incentive to time a change around a heavy week. Whichever reading of the overlap pays more is the one that governs, so a change made for the wrong reason gains nothing in the period it takes effect. Build the two computations in a spreadsheet before the transition rather than after, because doing it retroactively means reissuing a check.

The 8 and 80 Alternative for Hospitals and Residential Care

One narrow alternative to the seven-day workweek exists in federal law. Hospitals and establishments primarily engaged in the care of the sick, the aged, or the mentally ill who reside on the premises may substitute a fixed fourteen-consecutive-day work period and pay overtime for hours over eight in a single day and over eighty in the period.

It comes from section 7(j) of the Act and requires an agreement or understanding with the employee reached before the work is performed. The agreement does not have to be written, but an undocumented one triggers extra recordkeeping and is hard to prove later, so treat writing as mandatory even though the statute does not.

Return to the seven twelve-hour shifts. Under 8 and 80, each shift produces four hours of daily overtime, so 28 of the 84 hours are overtime. The remaining 56 straight-time hours never reach eighty, so no further premium is owed, and the total is $1,960. That sits between the two ordinary workweeks in the earlier table, which is the honest summary of 8 and 80: it is not a discount, it is a different shape.

Two cautions. Qualifying is narrower than people assume, and a medical practice, a clinic, or a home care agency without residential care generally does not qualify. And the election is meant to be a settled arrangement rather than something you switch into for heavy periods, exactly like the workweek itself. On twelve-hour shift patterns the daily trigger usually makes 8 and 80 more expensive, not less.

Shifts That Cross Midnight or the Workweek Boundary

A shift that crosses midnight counts entirely in the workweek in which it started. You do not split it at the calendar change. If the workweek begins Sunday at 12:00 a.m. and someone works 10:00 p.m. Saturday to 6:00 a.m. Sunday, all eight hours belong to the workweek that just ended.

This convention keeps one continuous shift from being torn across two overtime calculations, and it is the reason overnight operations remain manageable under a weekly standard. The same logic applies to the daily unit for employers using the 8 and 80 system, where the eight-hour trigger needs a defined start hour for the day and the shift is attributed to the day it began.

The harder case is a shift that crosses the workweek boundary itself, which happens when the start instant sits inside operating hours. Then the hours really do have to be allocated to each side of the line, because the boundary is the thing the overtime total is measured against. Splitting a single shift across two workweeks is legal and correct; it is just work you have to do on every affected timesheet.

The fix is placement. Put the start instant in the quietest hour you have, which for a Monday-to-Friday business is any time over the weekend and for a continuous operation is usually the gap between the thinnest shifts. A 9/80 schedule is the deliberate exception, where the boundary is placed mid-shift on purpose. Whatever you choose, make sure the clock records the crossing accurately, since rounding practices at a workweek boundary quietly move hours between two separate overtime calculations.

What to Write Down, and the Records That Prove It

Federal wage and hour recordkeeping requires the time of day and day of week on which each employee’s workweek begins to be preserved as part of that employee’s payroll record, alongside hours worked each day and each workweek. It is a required field, not a nice-to-have.

That requirement sits in the recordkeeping regulation at 29 CFR 516.2, which lists the workweek start alongside the identifying details, the regular hourly rate, daily and weekly hours, straight-time earnings, and the total premium pay for overtime. Payroll records generally have to be kept at least three years, with the time cards and computation working papers behind them kept at least two.

Four artifacts, kept together, answer every question anybody will ask. A timekeeping policy that states the day and hour the workweek begins, in those terms rather than as a day name. A payroll configuration that matches it, verified rather than assumed. A dated memo for any change, with the business reason and the announcement. And per-employee payroll records carrying the workweek field.

Absence of records is not neutral, which is the part worth internalizing. Where an employer has no documented workweek, the workweek gets inferred from payroll behavior, and the inference will favor whichever reading supports the larger claim. The same principle governs hours themselves: incomplete timesheets shift the evidentiary burden onto the employer.

The last check is the one people skip. Once a year, pull three employees at random, read the workweek in the payroll record, read the workweek in the handbook, and read the workweek the last overtime calculation actually used. If all three agree, the topic is closed for another year. Classification sits next to this, so confirm who is exempt or non-exempt at the same time, since the workweek only matters for the people it protects under the Fair Labor Standards Act.

Frequently Asked Questions