
Here is the answer most people are looking for: in the United States, there is no single legal number that makes a job full-time. Most employers land on 40 hours a week. Plenty use 35. And federal law only pins down a hard threshold for one narrow purpose, health benefits, where 30 hours a week counts as full-time.
That gap between what people assume and what the law says causes a lot of confusion. A manager schedules someone for 38 hours and figures they are "basically full-time." An employee works 32 hours and wonders why they do not qualify for insurance. Both are reading a rule that does not exist the way they think it does.
So let's clear it up. Below is what federal law actually defines, where the 30, 35, and 40 hour figures come from, and how to set a full-time policy that will not trip you up later.
Full-time usually means 40 hours a week. That is the number burned into most people's heads, and for good reason: it lines up with the standard workweek and with the point where overtime pay kicks in.
But "usually" is doing heavy lifting there. The 40-hour figure is a convention, not a statute. Your employer sets the line, and different federal rules use different numbers for different reasons. One agency says 35. One law says 30. Neither of them is wrong. They are just answering different questions.
Three federal reference points come up whenever full-time hours are on the table. They rarely agree, and that is the whole problem.
| Source | Full-time threshold | What it governs |
| Fair Labor Standards Act (FLSA) | No definition | Overtime pay after 40 hrs/week |
| Affordable Care Act (ACA) | 30 hrs/week (or 130 hrs/month) | Employer health-coverage mandate |
| Bureau of Labor Statistics (BLS) | 35+ hrs/week | Labor statistics and reporting |
This surprises people. The Fair Labor Standards Act, the main federal wage-and-hour law, does not say what full-time means. The U.S. Department of Labor states it plainly: whether an employee is full-time or part-time "is generally to be determined by the employer."
What the FLSA does define is overtime. Cross 40 hours in a single workweek and non-exempt employees earn time and a half. So the 40-hour mark matters, a lot, but it is an overtime line, not a full-time badge. You can work 45 hours and be "part-time" on paper; you can work 32 hours and be called full-time. The label and the overtime trigger are two separate things, and treating them as one is where scheduling errors start.
The Affordable Care Act draws the one federal line that has real teeth. For the employer mandate, a full-time employee is someone who works an average of at least 30 hours a week, or 130 hours in a month. That definition sits in the tax code, at 26 U.S.C. 4980H, and the IRS enforces it.
Here is why it bites. If you are an applicable large employer, meaning you averaged 50 or more full-time-equivalent employees the prior year, you have to offer affordable health coverage to anyone hitting that 30-hour average, or face a penalty. So for benefits, and only for benefits, 30 hours is the number that counts. Not 40.
The Bureau of Labor Statistics needs a consistent yardstick for its surveys, so it treats anyone working 35 or more hours a week as full-time. This is where a lot of "the average full-time worker" statistics come from. It has no legal weight over your payroll. But if you have ever seen a headline about full-time employment numbers, 35 hours is almost certainly the cutoff behind it.
Since federal law leaves most of the decision to you, the real question becomes a policy question. In practice, US employers set full-time somewhere between 30 and 40 hours a week, and they write that number into the employee handbook.
Take a 14-table brunch spot in Austin. The owner classifies anyone averaging 32 hours or more as full-time, partly because it is easy to explain to a young front-of-house crew and partly because it keeps the schedule predictable. Now compare that to a three-store hardware chain in Columbus, Ohio, with 61 employees on the books. That business crossed the 50-employee ACA threshold two years ago, so its "full-time" definition is not really a choice anymore; anyone averaging 30 hours triggers a coverage obligation, and the owner tracks weekly hours like a hawk because a miscount is a tax penalty.
Same country, same rules, two completely different lines. That is normal. What matters is that the number is written down, applied consistently, and matched to how the business actually runs.
At Shyfter, we see the opposite more often than we would like: no written threshold at all, just a vague sense that around 40 is full-time. That works until it doesn't. The moment someone disputes their benefits eligibility, or a seasonal hire creeps up to 34 hours a week for three straight months, the absence of a clear policy turns into a headache nobody scheduled for.
The label is not just semantics. It decides who gets what.
Benefits eligibility is the big one. Health insurance, paid time off, retirement contributions, sometimes life insurance: most of these are tied to full-time status. Draw the line at 30 and more of your team qualifies. Draw it at 40 and fewer do. That is a real cost decision, and it is why some employers keep part-timers capped at 28 or 29 hours on purpose.
Then there is overtime, which runs on a completely separate track. Remember, overtime is about the 40-hour FLSA line, not your full-time policy. A part-time employee who picks up extra shifts and blows past 40 in a week still earns time and a half. If you want to see exactly how that math works, our guide on how to calculate overtime hours walks through it.
Scheduling is where all of this collides. Managers juggling a 30-hour benefits cliff, a 40-hour overtime cliff, and a rota that changes every week are doing real-time arithmetic on the fly, and the errors are expensive in both directions. Overshoot and you owe overtime or trigger benefits you did not budget for. Undershoot and you understaff the floor. If your team runs on shift-based work, the way you structure those weeks matters as much as the thresholds; a well-built rotating shift schedule keeps hours balanced without anyone quietly drifting over a line.
And morale. This one is quieter but real. Workers notice when the person next to them gets benefits and they do not, especially when the hours look almost identical. A transparent, written threshold beats a fuzzy one every time.
Federal rules set the floor. States can, and do, add their own wrinkles for specific purposes.
A handful of states define full-time for things like unemployment eligibility, paid sick leave accrual, or state-run benefit programs, and those numbers do not always match the federal 30 or the customary 40. The definitions tend to be tied to a particular program rather than a blanket "this is full-time in this state" rule, which is exactly why they get missed.
The practical move is simple. Check the rule for the specific thing you care about, in the specific state you operate in, rather than assuming one number covers everything. A restaurant group operating in both Nevada and California cannot run one blanket full-time policy and hope it holds in both places; the sick-leave and scheduling rules differ, and so can the hour thresholds attached to them.
After years of watching small businesses wrestle with this, the pattern behind the ones that get it right is boring, and that is the point. They decide on a number, they write it down, and they hold the line.
A few things worth getting right:
Beyond those two, the rest is discipline. Watch the part-timers who keep creeping up. Flag anyone approaching a threshold before they cross it, not after. And keep your definition consistent with how you actually schedule; a policy that says 40 while your managers routinely build 36-hour weeks is a policy nobody believes.
This is the part software earns its keep. Shyfter tracks every employee's hours in real time, flags when someone is closing in on a full-time or overtime threshold, and gives managers the weekly view they need before the schedule locks. No spreadsheet reconciliation at month-end. No nasty surprise when a 29-hour part-timer turns out to have averaged 31.
Want to see how that looks for your team? Book a free demo and we will walk through it with your actual schedule.
Is 32 hours a week full-time?
It can be, if your employer says so. There is no federal rule making 32 hours full-time or part-time. For ACA health-benefit purposes, though, 32 hours clears the 30-hour threshold, so an applicable large employer would generally owe that person coverage.
Is 40 hours full-time or is that just the overtime line?
Both things are true at once, and that trips people up. 40 hours is the customary full-time standard and it is the point where overtime pay begins under the FLSA. But the 40-hour figure is not a legal definition of full-time; it is an overtime trigger that most employers also treat as their full-time mark.
Does federal law require full-time employees to get benefits?
Only in one case. Under the ACA, employers with 50 or more full-time-equivalent employees must offer affordable health coverage to those averaging 30 hours a week. Outside that mandate, benefits for full-time staff are set by the employer, not required by federal law.
What is the minimum number of hours for full-time?
There is no federal minimum. The lowest commonly used threshold is the ACA's 30 hours a week. The BLS counts 35 hours for statistics. Most employers settle on somewhere between 30 and 40, and write their choice into policy.
Can a part-time employee earn overtime?
Yes. Overtime depends on hours worked in a week, not on job title. Any non-exempt employee who works more than 40 hours in a workweek earns time and a half, whether you call them part-time or full-time. Our breakdown of shift differential pay covers how premium rates stack on top of that.
How do breaks factor into full-time hours?
Break rules are separate from the full-time question, but they affect how you count a shift. If you are building longer shifts, our guide on how many breaks belong in an 8-hour shift explains what counts as paid time.