How Many Hours Are in a Week? 168 Hours and How to Use Them

A week has 168 hours. That number never changes—not for a long month, a short month, or a leap year. The math behind how many hours in a week is simple: 7 days multiplied by 24 hours equals 168. Two weeks, then, add up to 336 hours. What does change is how you spend those hours, and for HR leaders running small teams, that distinction is everything.

This guide covers the raw numbers first, then bridges them to something more useful: a practical way to budget the 168-hour week for capacity planning, healthy workloads, and OKRs.

How Many Hours Are in a Week? The Quick Answer

There are 168 hours in a week. The calculation is straightforward:

• 7 days per week × 24 hours per day = 168 hours per week

This is a fixed constant. Unlike days in a month, the hours in a week don't shift with the calendar. Every week—January or July, leap year or not—delivers exactly 168 hours.

Need a longer window? Just multiply. Two weeks come to 336 hours (168 × 2). A four-week stretch gives you 672 hours. Once you anchor on 168, every other timeframe is simple arithmetic.

The Week at a Glance: Common Hour Breakdowns

Here's how those 168 hours split across the units people search for most:

That last row matters. If you sleep a healthy eight hours a night, you spend 56 hours a week asleep—leaving 112 waking hours to divide among work, commuting, family, meals, and rest. Suddenly the 40-hour work week looks like a smaller slice of the pie than it feels.

How Many Work Hours Are in a Week?

In the U.S., a standard full-time schedule is 40 hours a week, usually structured as five 8-hour days. That's the baseline most employers, benefits rules, and payroll systems assume.

Full-time isn't a single fixed number, though. According to TimeTrak, full-time work commonly ranges from 35 to 40 hours per week, depending on the employer and role. Some companies count 37.5 hours (a 7.5-hour day with an unpaid lunch) as full-time; others hold firm at 40.

Here's the perspective that gets lost: 40 work hours is under 24% of the total 168 hours in a week. Even a full-time job leaves roughly three-quarters of the week for everything else. A seven-day work week at eight hours a day would be 56 hours—still only a third of the week on the clock. Framing work this way helps HR teams set realistic expectations rather than treating employees as if the whole week belongs to the job.

What's the Average? Real Hours People Actually Work

Official numbers and lived reality don't always match. The U.S. Bureau of Labor Statistics puts the average workweek at around 34.6 hours, per Indeed—a figure pulled down by part-time roles and varied industries.

Gallup tells a different story for salaried staff. Its polling found the average full-time workweek is closer to 47 hours, and one in five workers reports logging more than 60 hours, with some pushing past 80, according to WeWork.

The anecdotes back this up. In public forums like Reddit, workers describe departments running 56-hour scheduled averages, with individual weeks swinging between 48 and 72 hours depending on the rotation.

Is 42 hours a week a lot? Not dramatically. It's two hours of overtime beyond the standard 40—common in many roles and well below the 47-hour average many salaried employees report. It becomes a problem only when 42 quietly creeps toward 50, 55, or 60 week after week without anyone tracking it.

The Ideal Work Week: How Many Hours Should You Really Work?

More hours don't mean more output. Atlassian's research points to 38 hours as the productivity sweet spot—enough to get meaningful work done without tipping into fatigue. Beyond roughly 50 hours a week, returns diminish sharply, and past that, extra hours can actually reduce total useful output.

That has real consequences for small teams, where one burned-out person is a much bigger percentage of your capacity. Sustained overwork drives mistakes, disengagement, and turnover—all expensive when you have five or fifteen people, not five hundred. Protecting job engagement under a manageable workload is far cheaper than replacing someone who quietly burned out.

Hour limits vary by situation too:

• Part-time employees typically work fewer than 35 hours a week, often in the 20–30 range.
• Teen workers face legal caps. During the school year, 14- and 15-year-olds are limited to 18 hours a week under federal rules, and hours for 16- and 17-year-olds are often restricted by state law around school schedules.

The takeaway for managers: aim workloads at the sustainable zone, not the maximum a person can technically survive. When overload does show up as chronically slipping output, a structured performance improvement plan works better than piling on more hours.

Budgeting the 168-Hour Week for Small Teams

Here's where the raw math becomes a management tool. Stop thinking of 168 as trivia and start treating it as a capacity ceiling. Each employee has a fixed budget of work hours per week—usually 40—and your job is to allocate that budget on purpose instead of letting it fill up by accident.

A simple way to divide a standard 40-hour week:

• Deep work on priorities (20–24 hrs): the focused time that actually moves OKRs forward.
• Meetings and collaboration (6–10 hrs): stand-ups, one-on-ones, and cross-team syncs, capped so they don't crowd out real work.
• OKR check-ins and reviews (1–2 hrs): short, regular pulse on goals and progress.
• Admin, email, and context-switching (6–8 hrs): the overhead every role carries.

When you plan against a 40-hour budget rather than an open-ended one, overload becomes visible. If a project needs 55 hours of someone's week, the numbers say it out loud: you either move work, extend the timeline, or add hands. That's healthier than discovering the overload later through missed deadlines or a resignation. It also keeps employee engagement intact when work is distributed fairly.

For a startup founder or HR manager, this reframing solves a real problem. Spreadsheets can hold the hours, but they don't connect capacity to goals or flag when someone is quietly running at 60 hours. That's the gap HR HiFi is built to close for small teams—tying performance reviews, OKRs, and workload into one AI-native HR OS, so you can see who's overloaded, distribute work fairly, and keep goals on track without stitching together five tools. If you're still weighing options, our guide on how to choose HR software for a small business covers the features that matter most. The 168-hour week stops being an abstraction and becomes something you can actually manage.

Frequently Asked Questions

How many hours are in 7 days?

168 hours. Seven days multiplied by 24 hours per day equals 168.

How many hours is a 7-day work week?

If someone worked all seven days at eight hours each, that's 56 hours. The week itself still contains 168 total hours; the 56 is only the working portion.

How much is 40 hours in a week?

Forty hours is the standard U.S. full-time schedule—five 8-hour days. It represents just under 24% of the 168 total hours in a week.

Is 42 hours a week a lot?

Not particularly. It's two hours above the 40-hour standard and below the roughly 47-hour average many salaried workers report. It's only a concern if it becomes a launch pad for consistently longer weeks.

How many hours are in a week minus sleep?

About 112 hours. Subtracting 56 hours of sleep (8 hours a night across 7 nights) from 168 leaves 112 waking hours.

How many hours should a part-time employee work per week?

Part-time roles generally fall under 35 hours a week, commonly in the 20–30 hour range, though exact definitions vary by employer and benefits rules.