PunchWhat Is a Workweek Under the FLSA? (And Why It Decides Your Overtime)
What Is a Workweek Under the FLSA? (And Why It Decides Your Overtime)
The short answer: A workweek is a fixed, regularly recurring period of 168 hours, seven consecutive 24-hour days, and it is the unit the Fair Labor Standards Act uses to calculate overtime. It does not have to match the calendar week or your pay period. It can start on any day and any hour, as long as it stays put. The rule that trips up small employers most: each workweek stands alone, so you cannot average hours across two weeks, and you cannot use a two-week or semi-monthly pay period as the basis for overtime. Overtime is owed on hours over 40 in a single workweek. A time-tracking app like Punch anchors your workweek, calculates overtime per week even on a bi-weekly pay cycle, and lets you set the start day that matches how you actually run payroll.
Most overtime mistakes are not about the rate. They are about the window. If you measure "over 40" against the wrong span of days, every overtime calculation downstream is wrong, and it is wrong the same way every period. Getting the workweek right is the foundation everything else sits on.
The FLSA Definition of a Workweek
The Department of Labor defines a workweek as a fixed and regularly recurring period of 168 hours: seven consecutive 24-hour periods. Three words in that definition do the work.
Fixed. Once you set your workweek, it does not move to match a schedule. It is the same seven-day window every week, whether an employee works two days or six.
Regularly recurring. It repeats on the same cadence, week after week, without gaps or overlaps.
168 hours. Seven days times 24 hours. The window is a full week of clock time, not just the hours someone happens to be on the job.
The workweek does not have to line up with the calendar. It can begin on any day of the week and at any hour of the day. A crew that starts its week Sunday at midnight and a crew that starts Monday at 6 a.m. are both compliant, as long as each one is consistent. You can even set different workweeks for different groups of employees, but a single employee's workweek cannot flip around based on the hours they work that week.
Each Workweek Stands Alone
This is the rule that quietly costs small employers the most. For overtime and minimum wage, each workweek stands alone. There is no averaging of two or more weeks.
Here is what that means in practice. Say an employee works 30 hours one week and 50 hours the next. Averaged across the two, that is 40 hours a week, which looks like no overtime. But the FLSA does not let you average. Week one has zero overtime hours. Week two has 10 hours over 40, and those 10 hours are owed at time and one-half. The 30-hour week does not cancel out the 50-hour week. You owe overtime on the second week regardless of how light the first one was.
The same logic runs the other direction. You cannot "bank" hours from a busy week and pay them out as straight time in a slow one. Every week is scored on its own.
The Pay Period Is Not the Workweek
This is the single most common source of overtime underpayment, and it comes from an honest mix-up. Your pay period is how often you cut checks. Your workweek is how you measure overtime. They are two different things, and only one of them decides overtime.
If you pay weekly, the two happen to line up, so the distinction never bites. The moment you move to bi-weekly or semi-monthly, they split apart, and the math has to split with them.
Bi-weekly. A bi-weekly pay period is two workweeks. Overtime is calculated separately for each of the two weeks inside it, then added together. You cannot pool 80 hours across the two weeks and pay overtime only above 80. An employee who works 45 hours in week one and 35 in week two worked 80 hours total, but still earned 5 hours of overtime, because week one crossed 40 on its own. Pooling the pay period would erase those 5 hours.
Semi-monthly. A semi-monthly pay period, paid on the 1st and the 15th, is harder still, because its boundaries do not fall on workweek boundaries. A single workweek can straddle two pay periods. Under the FLSA you still have to break the pay period back into individual workweeks, total each week's hours, and calculate overtime per week, even when those weeks cut across the pay dates. Semi-monthly is the pay cycle most likely to hide unpaid overtime, precisely because the periods and the workweeks never line up.
The rule is the same in every case: overtime is a workweek calculation, never a pay-period calculation. Averaging hours across a bi-weekly or semi-monthly period to stay under the overtime line is not a gray area. It is a violation.
Can You Change Your Workweek?
Yes, but with a guardrail. The regulations permit changing the start of the workweek only if the change is intended to be permanent and is not designed to evade the overtime requirements of the Act. You cannot shift the workweek one week to break up a stretch of long days and dodge the overtime it would trigger. A change made to duck overtime is exactly what the rule forbids.
Legitimate reasons to change exist. You might align the workweek with a new payroll provider, or move it to match when your crews actually start their week. Those are fine, as long as the new workweek is the one you keep. Pick a start day, write it down, apply it to everyone in the group, and leave it alone.
How to Set Your Workweek
Setting a workweek is a decision you make once. Three steps.
Pick a start day and hour. Match it to how your team already works. Field crews often run Sunday to Saturday or Monday to Sunday. Whatever you choose, it becomes the boundary every overtime calculation uses.
Write it into your records. Your workweek should be documented and consistent. If a wage claim ever lands, the first question is what your workweek is, and "we sort of go by the calendar" is not an answer.
Anchor it in your time tracking. Your time clock has to know where each week starts so it can total hours per week and flag anything over 40. If your workweek lives only in a spreadsheet header, every calculation is a manual step waiting to go wrong.
How Punch Handles the Workweek for You
Punch treats the workweek as the unit it actually is. You set your pay period start day in your workspace settings, and every overtime calculation anchors to it. When your crew punches in and out at the job site, the hours land inside the right week automatically.
The bi-weekly case is where this matters most, and it is where hand math slips. On a bi-weekly pay cycle, Punch still calculates overtime per workweek, one week at a time, then rolls the two together for the pay period. It never pools 80 hours and pays overtime only above 80, because that would be wrong. Each week is scored on its own, exactly as the FLSA requires.
Punch also ships more than 50 country and state overtime presets, so the "over 40" line is set correctly for your jurisdiction, including daily and double-time rules where they apply. Managers approve the week or the full pay period, and the approved hours carry straight into Reports and payroll exports, QuickBooks Online and Excel among them. The workweek you set is the workweek every number respects, from the first punch to the paycheck.
And because the record has to hold up, every punch is timestamped to the minute and reviewed at approval. If your crew works from job sites, Punch confirms location with a geofence at punch-in only. It is a boundary on a map, never a camera in anyone's face, and punch-out and lunch are never gated by location.
Frequently Asked Questions
What is a workweek under the FLSA?
A workweek is a fixed and regularly recurring period of 168 hours, meaning seven consecutive 24-hour days. It can start on any day and any hour, does not have to match the calendar week, and stays the same from week to week. It is the window the FLSA uses to decide overtime.
Is the workweek the same as the pay period?
No. The pay period is how often you pay people. The workweek is how you measure overtime. They match only when you pay weekly. On bi-weekly or semi-monthly cycles, you still have to calculate overtime per individual workweek, not per pay period.
Do I owe overtime if hours average out to 40 across two weeks?
Yes, if either week alone went over 40. Each workweek stands alone under the FLSA, so a 50-hour week owes 10 hours of overtime even if the next week is only 30 hours. You cannot average two weeks together.
Can I change my workweek start day?
You can, as long as the change is meant to be permanent and is not designed to avoid overtime. A one-time shuffle to break up a long stretch and dodge overtime is not allowed. A durable change to match your payroll or schedule is fine.
How does Punch calculate overtime on a bi-weekly pay period?
Punch calculates overtime for each workweek separately, then adds the two weeks together for the pay period. It never pools the full period's hours, so overtime that lands in a single week is always counted. You set your workweek start day once and every calculation follows it.
Set the Window Once, Get Every Overtime Number Right
Overtime is only as accurate as the workweek behind it. Measure against the wrong span of days and every calculation is off in the same direction, quietly, every period. Set the workweek correctly and the rest falls into place.
Punch anchors your workweek to the start day you choose, calculates overtime per week even on bi-weekly pay, applies the right rules for your state and country, and keeps a timestamped record for every shift. Every plan includes every feature, and the price is flat per workspace instead of per employee, so the bill does not grow every time you hire. The 14-day free trial starts on signup, no credit card required.