Four Day Work Week: Benefits, Risks & Practical Rollout Plan

A four-day workweek can improve focus and help you keep good people longer. It works best when the schedule model matches your roles and your coverage needs.

In this guide, you will learn what a four day work week really means and which schedule options are most common. You will also see the benefits, the risks, and a practical step-by-step rollout plan. You can test the plan on one small team without breaking your daily operations.

Key Takeaways

A four-day workweek can mean compressed hours (four 10-hour days) or reduced hours (four 8-hour days, or 32 hours). The difference changes your cost, your coverage, and your overtime risk.
The best rollout starts with picking the right roles and planning coverage, not with changing the calendar.
Clear rules on hours, pay, availability, and timekeeping prevent most failures.
Run a time-boxed pilot with a scorecard that tracks productivity, quality, customer impact, and people metrics, and keep a rollback plan ready.

What Is a Four Day Work week? (Simple definition)

A four-day workweek is a work schedule where employees finish their job in four days instead of five. Most teams do this to give people a three-day weekend while the business keeps its results.

There are two main ways to build it, and each one treats hours and pay in a different way.

Four-day workweek vs. compressed workweek

A compressed workweek keeps the same weekly hours but spreads them over fewer days. A common example is 40 hours in four days. Each day gets longer, but the week has one less workday.

This model is easy to explain to your team. Pay usually stays the same because the total hours stay the same.

Four-day workweek vs. reduced-hour workweek

A reduced-hour workweek cuts the total hours people work each week. A common example is 32 hours in four days. The goal is to get the same output in less time.

This model asks the team to plan and work in a smarter way. It also puts more pressure on planning, since there is less time for the same amount of work.

Quick glossary

Compressed schedule: the same weekly hours packed into fewer days.
Reduced schedule: fewer total hours each week.
Staggered coverage: teams take different days off so the business stays open five days.
Pilot: a small, time-limited test that you run before a full launch.
Outcomes-based performance: judging people by the results they deliver, not by the hours they sit at a desk.

Four-Day Workweek Models (Choose the right schedule)

There is no single way to run a four-day week. Each model below suits a different type of team, so pick the one that fits your work and not the one that sounds the most exciting.

Model A: 4×10 (40 hours in 4 days)

This model keeps the 40-hour workweek but fits it into four longer days. It is a good match for roles that can handle long shifts and do not pass work to others very often.

Best for: roles that can handle longer shifts and have low handoff complexity.

Watch-outs: long days cause fatigue, meetings can grow to fill the extra time, and overtime can spill over when a task runs past the end of the day.

Model B: 4×8 (32 hours) with same pay

This is the 32-hour workweek with full-time pay. It fits knowledge work where the output is easy to see and measure. Design, writing, finance, and software teams are common examples.

Best for: knowledge work with clear outputs.

Watch-outs: the same work now has to fit into less time. If you do not redesign the work first, people will feel squeezed.

Model C: 4×8 (32 hours) with prorated pay

In this model, hours go down and reduced pay follows in the same proportion. Some companies offer it as an optional choice or as a short step during a change.

Best for: optional arrangements and transitional flexibility.

Watch-outs: many people see this model as a pay cut, which can hurt trust and retention if you do not explain it well.

Model D: Rotating/staggered day off (coverage-friendly)

Some teams must stay open five days a week. In this model, people take different days off, so one group is off on Monday while another group is off on Friday.

Best for: customer support, sales, and operations teams that need five-day coverage.

Watch-outs: it takes more coordination, and you need clear fairness rules about who gets which day.

Model E: Seasonal/“summer hours” pilot

This is the lowest-risk way to test the idea. You offer the four-day schedule for a set season, such as the summer months, and then review the results.

Best for: lower-risk testing.

Watch-outs: expectations can drift if you do not write them down, so put the start date, the end date, and the rules in one short document.

Model	Hours per week	Pay impact	Coverage impact	Best-fit roles	Main risk
A: 4×10	40	Same	Medium	Roles with few handoffs	Fatigue and overtime
B: 4×8, same pay	32	Same	Medium to high	Knowledge work	Workload squeeze
C: 4×8, prorated pay	32	Lower	Medium	Optional programs	Retention concerns
D: Rotating day off	32 to 40	Varies	Low	Support, sales, operations	Coordination
E: Seasonal pilot	32 to 40	Varies	Low	Any team testing the idea	Unclear rules

Is It Right for Your Business?

You do not need a perfect company to start. You do need a few basics in place, and the lists below work as a quick screen.

Strong signals it can work

Your team’s work is measured by outputs, not just by time spent at a desk.
Managers can run a weekly planning meeting and coach their people.
You are willing to redesign meetings and workflows.

Red flags (fix these first)

You are always short on staff, and nobody tracks workloads.
You have no baseline numbers for productivity or service levels.
Customers often make last-minute demands, and you have no backup coverage.

Go/No-go checklist. Answer yes or no to each point below. If you say no to more than three, fix those gaps before you start.

We can describe good output for each role.
We know our current output, quality, and response times.
Every team has a clear owner.
Our managers hold a weekly planning check-in.
We have a plan for customer coverage on every workday.
We can cut or shorten at least some of our meetings.
We track hours in one reliable system.
We can explain the new rules in plain language.
Our leaders agree on the goal of the test.
We have a way to roll back if results drop.

Benefits of a Four-Day Workweek (What improves—and why)

A shorter week can help both your people and your business. The gains are strongest when the company redesigns its work before it changes the schedule.

People benefits

A shorter week supports employee well-being and employee satisfaction. People get more time to rest, handle personal tasks, and be with family. That helps reduces workplace stress and the risk of workplace burnout.

These gains also help with employee recruitment and retention. A four-day option gives you something fresh to offer in a tight job market, and good candidates often ask about flexibility before they ask about pay.

Business benefits

When time is limited, people stop doing low-value tasks. Meetings get shorter, priorities get clearer, and teams spend more time on deep, focused work. This can lift employee productivity and employee engagement.

Operational benefits (when designed well)

A good rollout can improve how work flows through your company. Teams write more things down, use more asynchronous updates, and hand off tasks in cleaner ways. These habits help your business even if you return to a five-day schedule later.

What research and large trials often show

In a six-month trial of nearly 3,000 workers, employees reported less burnout and higher job satisfaction. They also reported better mental and physical health, and the companies that kept a five-day schedule did not see the same gains. Keep in mind that the companies chose to join the trial, so your own results may differ.

Business results looked strong as well. In the largest pilot results, more than nine in ten companies planned to keep the shorter week. Those companies also reported lower absenteeism, and fewer people left during the trial.

Risks and Downsides (What can go wrong)

A four-day week is not a magic fix. Each risk below has clear warning signs and a simple fix, so you can plan for it ahead of time.

Workload compression (same work, less time)

Symptoms: people rush through the day, skip breaks, and finish work at night. Quality drops, and stress goes up.

Fixes: remove low-value tasks before you change the schedule, set limits on meetings, and use simple tools to automate repeat work. Check workloads every week so that problems show up early.

Coverage gaps and customer experience issues

Symptoms: customers wait longer for answers, and calls go unanswered on days when many staff members are off.

Fixes: use flexible work arrangements such as staggered schedules or rotating days off. Update your service hours when needed, and share the new hours with customers early.

Inequity across roles (not everyone can do 4 days)

Not every job can move to four days. A warehouse shift or a front desk may need five-day coverage, and this can leave some staff feeling left out.

Solutions: offer role-based options and let shift workers bid for the days they prefer. Give other kinds of workplace flexibility to roles that cannot change, such as extra paid time off or flexible start times.

Manager strain and unclear performance expectations

Managers carry more weight in a shorter week. They must plan the work, protect focus time, and judge results fairly.

Solutions: set outcomes-based goals, hold a short planning meeting each week, and train managers to coach people and to spot overload early.

Burnout risk under 4×10

Long days can wear people down, especially in physical jobs or jobs that need a lot of focus.

Solutions: make sure people take their breaks, set reasonable workload caps, and run safety checks on the longest shifts. Ask for feedback often and watch for signs of fatigue.

How Many Hours Is a Four-Day Workweek? (Full-time vs part-time)

A four-day workweek usually runs between 32 and 40 hours. The exact number depends on the model you pick.

A quick math check can help here. A full week has 168 hours in total, and four days have 96 hours. Four weeks make up 28 days. A five-day schedule has about 260 workdays in a year, while a four-day schedule has about 208. These numbers matter when you plan annual pay and leave.

If you want a deeper look at how companies define a standard week, read this guide on how many hours in a week is full-time. It explains the common hour counts in simple terms.

Common hour setups (and what they imply)

40 hours (compressed): the same weekly hours in four longer days. Pay and benefits usually stay the same.
32 hours (reduced): fewer weekly hours. Pay may stay the same or may be prorated.
36 hours (hybrid): a middle step that some companies use as a bridge between the two models.

If you plan your schedules by month, this guide on working hours in a month can help with the math.

Define “full-time” internally (policy clarity)

Write down what full-time means in your own policy. Three ideas often get mixed up, so keep the language consistent across your handbook:

Classification means how the company labels a worker.
Scheduling means the days and hours the worker is on duty.
Benefits eligibility means who qualifies for company benefits.

A person who works 32 hours may be full-time at your company, or may be part-time. Your policy must say which one applies. For a clear comparison, see this article on full-time vs. part-time employment.

You can also read how many hours is a part-time job to see where the part-time line usually falls, and how many hours is full-time for the full-time baseline.

Benefits, PTO, and holiday handling decisions

A new schedule raises new questions about time off. Decide these points before you launch:

PTO accrual method: will you count paid time off in hours or in days? Hours are fairer when the length of the day differs between roles.
Holiday rules: what happens when a holiday falls on a person’s day off? Some companies give a swap day, and others give extra paid hours.
Partial-week PTO: decide how many hours a sick day or a vacation day takes from a person’s balance under each model.

If an employee works	Benefits rule	PTO rule	Holiday rule
40 hours in 4 days	Same as full-time	Count in hours	Give a swap day or paid hours
32 hours in 4 days, same pay	Same as full-time	Count in hours	Give a swap day or paid hours
32 hours in 4 days, prorated pay	Set in policy	Prorate by hours	Prorate by hours

Pay, Overtime, and Timekeeping (Practical compliance checklist)

Pay rules do not change just because the schedule changed. This section is a practical guide and not legal advice, so check with a qualified expert before you finalize any plan.

Hourly vs. salaried: what changes with a new schedule

Hourly workers need clear timekeeping rules. Set start times, end times, breaks, and approval steps, and tell people what counts as work time.

Salaried workers also need clear boundaries. If someone has a day off, they should not answer messages on that day unless there is a true emergency. Write this rule down so it is fair for everyone.

Overtime risk points to plan for

Overtime can sneak in when schedules change. Plan for these common risk points:

Training sessions that run long
Travel time for work
After-hours messages and calls
Coverage shifts when someone is out
Busy seasons

Long days in a 4×10 model need extra care. Before you launch, make sure you know how the overtime rules apply to your workers. An agreement between you and a worker usually cannot waive those rules.

Exempt vs nonexempt role fit (practical, non-legal)

Exempt roles are not paid overtime, while nonexempt roles are. Roles that are not paid overtime often handle compressed days with less risk.

For hourly roles, a reduced-hours model is often the safer choice. It lowers the chance of long days that trigger extra pay.

Documentation to update

Update these items before launch so that everyone sees the same rules:

Offer letters
The employee handbook
Your scheduling policy
Job expectations
Timekeeping rules

A good tool makes this part easier. Time & Attendance from HavernHR records check-ins, shifts, and breaks from a phone, then sends the data straight into payroll. That helps you spot overtime early while you test the new schedule.

Coverage Models That Work (Pick one and standardize it)

Pick one coverage model and use it across the company. Mixed rules confuse people and lead to missed work.

Company-wide closure (everyone off the same day)

Pros: it is simple to run and easy to explain.

Cons: customers cannot reach you on that day, so urgent issues need a clear emergency plan.

Best-fit conditions: teams with few outside customers, or businesses that can pause for one day.

Staggered off-days (teams pick different off-days)

Pros: the business stays open five days a week.

Cons: it is harder to schedule meetings and shared work.

Coordination rules: set a minimum number of people for each day, and make sure every key task has a backup.

Split-team rotation (A off Monday, B off Friday)

Pros: two equal halves can cover for each other with little change to service.

Cons: work can stall if the two halves do not share information well.

Handoff practices: use a short written note at the end of each shift, and hold a quick check-in on the days when both groups are in.

Core hours + flexible edges

Everyone is online during set core hours, such as 10 a.m. to 3 p.m. People choose their own start and end times outside that window.

Pros: people get flexibility, and teams still have shared time to meet.

Cons: it can be hard to know who is available at the edges of the day.

Meeting rules: hold all meetings inside the core hours, and protect the rest of the day for focused work.

Customer-first coverage (service hours redesign)

You redesign your service hours around the times when customers need you most, and then you build the team schedule to match.

Pros: customers get fast help when it matters.

Cons: some shifts may be less popular than others.

Escalation plan: name one person on duty each day who can make decisions, and share the escalation chain with the whole team.

Coverage planning worksheet. Fill in these items for each team:

Peak demand days and times
Service level targets
The escalation chain
A handoff checklist
A backup person for each key task

Practical Rollout Plan (Step-by-step)

This plan keeps the change small and safe, so follow the steps in order.

Step 1: Set goals and guardrails

Decide what success looks like. Write down your output expectations and your customer coverage needs. Add a firm rule that there will be no hidden overtime.

Step 2: Choose model + define eligibility

Pick a model from the list above, and decide which teams and roles can join. Set any rules about tenure or performance, and write down how people can ask for an exception.

Step 3: Redesign work before changing the calendar

This is the most important step. Cut the meetings that add little value, and move routine updates into written messages. Set a steady planning rhythm for projects, and clean up any tools that slow people down.

Step 4: Train managers and communicate the change

Give managers clear talking points. Explain why the company is making the change and how the plan stays fair. Share a short list of common questions with answers, and tell people where to go when they have a problem.

Step: Run a small test with weekly check-ins

Start with one team instead of the whole company. Choose a team with clear goals and a steady workload, and run the test for a set period that matches your business cycle.

Hold a short check-in each week. Ask what is working, what is not, and where work is leaking onto the day off. Fix small issues right away so they do not grow.

Step 6: Decide and document (scale, adjust, or stop)

At the end of the test, review your scorecard and choose one of three paths: scale up, adjust, or stop. Write down the decision and the reasons behind it, and keep your rollback plan ready in case results fall short.

Pilot Scorecard (What to measure to prove it works)

A scorecard turns opinions into facts. Measure the same items before, during, and after the test so you can compare them fairly.

Productivity and quality metrics (by function)

Cycle time
Output volume
Error rate
On-time delivery

Customer metrics

Response times
Service level hits
Customer satisfaction

People metrics

Engagement pulse surveys
Retention
Absenteeism
Signs of burnout

Studies point to sleep, fatigue, and work ability as key links between a shorter week and better health. You can ask a few simple questions about these in your pulse surveys.

Cost and risk metrics

Overtime hours
Extra staffing needs
Missed coverage incidents

Baseline → Target → Actual scorecard template:

Metric	Baseline (before)	Target	Actual (after)	Notes
Output per week
Error rate
Response time
Engagement score
Overtime hours

FAQs

Is a four-day workweek the same as a 32-hour workweek?

Not always. A four-day workweek can be 32 hours or 40 hours. The 32-hour version cuts total hours, while the 40-hour version only moves the same hours into four longer days.

Will employees be paid the same?

It depends on your model. In a compressed schedule, pay usually stays the same. In a reduced schedule, you choose between full pay and prorated pay, so state your choice in writing before launch.

How do we handle roles that need five-day coverage?

Use a rotating or staggered day off. Each person works four days, but the team covers all five. Set a minimum staffing level for each day so that service stays steady.

What happens to PTO and holidays?

Count PTO in hours so that it stays fair across different day lengths. Decide ahead of time how to handle a holiday that lands on a person’s day off.

How do we prevent people from working on the off day?

Set a clear rule and model it from the top. Ban meetings on off days, and ask managers to avoid sending messages on those days. Review hours in your timekeeping system each week to catch problems early.

What’s the best team to pilot first?

Choose a team with clear goals, a steady workload, and a manager who is ready to coach. Teams with strong written processes tend to do well.

What if productivity drops?

Check your scorecard first, and look for workload problems, meeting overload, or coverage gaps. Adjust the plan and test again. If results stay poor, use your rollback plan and return to the old schedule.

Conclusion

A four-day workweek can work well for the right business. The key is to choose the right model, protect your customer coverage, and measure the outcomes.

Start with a pilot and a written policy instead of an informal schedule change that people have to guess about. Clear rules and good data protect both your team and your customers.

If you would like help with the rollout, talk to HR about designing the plan. Tracking hours, shifts, and overtime with a reliable system is a strong first step, and it keeps your pilot honest and your payroll clean.