A 4 day work week gives employees a full extra day off each week, usually with no cut to pay. Instead of the standard five-day, 40-hour schedule, staff work four days and take three off. For small teams, it can be one of the cheapest ways to boost retention and morale, without adding a line to the payroll budget.
The idea is no longer fringe. In the largest coordinated trial to date, 91 companies and roughly 3,500 employees ran a six-month four-day week across the US, UK, Ireland, Canada, and Australia. Revenue rose, burnout fell, and almost none of the companies went back. This guide breaks down what the four-day week actually is, the two main models, the real benefits and drawbacks, and a step-by-step plan to test it with a team of 5 to 100.
What is a 4-day work week?
A four-day work week is a schedule where full-time employees work four days instead of five, most often while keeping the same salary and benefits. The most talked-about version reduces weekly hours from 40 to 32, based on the principle that a focused, well-rested team can produce the same output in less time.
It is not the same as part-time work. Employees stay full-time, keep full pay, and keep their titles and benefits. What changes is how the week is structured, and often how much low-value work (long meetings, status updates, busywork) gets cut to make the shorter week possible.
The concept gained real momentum after Andrew Barnes, founder of New Zealand estate-planning firm Perpetual Guardian, ran a company-wide trial and wrote The 4 Day Week. His guiding formula, now widely cited, is 100-80-100: 100% of pay, 80% of the hours, in exchange for 100% of the output. That last number is the catch, and the reason implementation matters so much.
4-day work week models: compressed vs. reduced hours
"Four-day week" is an umbrella term. There are two very different versions underneath it, and choosing the wrong one for your team is the most common early mistake.
The compressed work week (4x10). Employees work the same 40 hours, squeezed into four 10-hour days. Total hours don't change; the number of days does. This is technically a compressed schedule, not a true reduction. It's easier to adopt because output expectations stay flat, but the longer days can be draining, and it does little for the burnout the four-day week is famous for solving.
The reduced-hours week (4x8 / 32 hours). Employees work four normal 8-hour days for a real 32-hour week, at full pay. This is the version behind the headline trial results. It demands genuine changes to how work gets done, because you're removing eight hours a week and still expecting the same results.
Here's how the two compare at a glance:
| Factor | Compressed (4x10) | Reduced hours (4x8) |
|---|---|---|
| Weekly hours | 40 | 32 |
| Pay | Unchanged | Unchanged |
| Days worked | 4 | 4 |
| Main benefit | Three-day weekend | Three-day weekend + shorter total hours |
| Main risk | Long, tiring days | Fitting output into fewer hours |
| Best for | Roles with steady, predictable workloads | Knowledge work with cuttable busywork |
A quick note on overtime: under the federal Fair Labor Standards Act, non-exempt employees earn overtime after 40 hours in a workweek, so a standard 4x10 usually stays under the threshold. But a handful of states (California and Alaska, for example) require daily overtime after 8 hours, which can make a 10-hour day expensive. Always check your state rules on the DOL site before rolling out a compressed schedule. If you're mapping out shift lengths, a free work hours calculator makes the daily math easy.
Benefits of a 4-day work week (with data)
The strongest case for the four-day week isn't a hunch, it's trial data. The nonprofit 4 Day Week Global coordinated the largest study, and the results, reported by MIT Sloan, are hard to ignore.
Across the 91 participating companies:
- Revenue rose about 35% compared with a similar period the year before.
- 71% of US employees reported reduced burnout by the end of the trial.
- 39% said their stress had decreased.
- Employees slept more (about 42 extra minutes a week) and exercised more.
- Almost every company chose to keep the four-day week when the trial ended.
Beyond the trial numbers, four benefits show up again and again for small teams:
1. Retention gets cheaper. A three-day weekend is a perk competitors with fatter budgets often can't match. Employees in the trial said they'd need a 10-50% raise to go back to five days, which tells you how much they valued the time. That's real leverage when you're competing for talent on culture instead of cash. It pairs naturally with other low-cost employee retention strategies small companies rely on.
2. Recruiting improves. A four-day week is a headline in a job post. Smaller companies that offer one often see stronger applicant pools, because the perk signals trust and a healthy culture, not just a nice schedule.
3. Focus goes up. Removing a day forces teams to cut the meetings and busywork that quietly eat the week. Many companies find they were never really using that fifth day well to begin with.
4. Fewer sick days and less absenteeism. Rested people take fewer unplanned days off. Some of the "extra" day off simply absorbs the errands and appointments that used to eat into work time.
Challenges and drawbacks to consider
The four-day week is not free, and pretending it is will sink the rollout. Being honest about the tradeoffs up front is how you keep it from quietly failing.
Coverage gaps. If everyone takes Friday off, who answers the client email on Friday? For customer-facing or support roles, you often need staggered days off so someone is always available. That's harder to coordinate on a small team where one person may be the only one who knows a given system.
The "cram it into four days" trap. The most common failure mode is keeping a 40-hour workload and just deleting a day, so people work frantic 10-hour days or quietly log on during their day off. Andrew Barnes is blunt about this: the point is to redesign the work, not compress it. Without cutting low-value tasks, you get the same output and more burnout, which is the opposite of the goal.
Client and customer expectations. Some clients expect five-day availability. You may need to set clear response-time expectations, route urgent issues to whoever is on that day, or stagger schedules so coverage never drops.
Not every role fits. Retail, healthcare, manufacturing, and other shift-based work can't simply drop a day without hiring more staff. A four-day week works best where output is measured by results, not hours at a station.
Measurement is hard. For knowledge work, "did productivity hold?" is a genuinely tricky question to answer. You need to agree on what you're measuring before the trial starts, or you'll end up arguing about vibes at the end.
How to implement a 4-day work week (step-by-step)
The companies that succeed treat the four-day week as a designed change, not a blanket announcement. Here's a practical sequence for a team of 5 to 100.
Step 1: Define the goal and the model. Decide what you're actually trying to fix (burnout? retention? recruiting?) and pick compressed (4x10) or reduced-hours (4x8). For most knowledge-work teams chasing burnout and retention, the 32-hour reduced week is the version worth testing.
Step 2: Involve the team early. Don't hand this down from the top. Ask employees where the week's wasted hours are: which meetings, reports, and rituals could go. The trials that worked used staff to find the productivity gains, not managers guessing.
Step 3: Cut the low-value work first. Before you remove the day, remove the busywork. Trim recurring meetings, shorten them, batch communication, and kill status updates that a shared doc could replace. This is the step people skip, and it's the one that makes or breaks the shorter week.
Step 4: Choose your day-off structure. Everyone off the same day is simplest and protects real team-wide focus. Staggered days off protect coverage but reduce overlap. Pick based on how much your work depends on real-time collaboration versus always-on availability.
Step 5: Set clear, measurable success metrics. Agree in advance on 3-5 numbers: revenue or output, customer response times, error rates, employee satisfaction, sick days. Write them down before the trial so the review is about data, not opinions.
Step 6: Run a 3-6 month trial. Don't commit permanently on day one. A pilot lets you learn, adjust the day-off structure, and give people an honest out if it isn't working. Communicate clearly that it's a trial with a defined review date.
Step 7: Review, adjust, and decide. At the end, compare your metrics against the baseline. Keep it, tweak it, or roll it back, and be transparent about the reasoning either way.
Throughout the trial, you'll need a clean way to see who's off when, especially with staggered days. A shared team calendar that tracks time off and custom schedules keeps coverage visible so no day gets accidentally uncovered.
4-day work week policy template
A short written policy prevents most of the confusion a schedule change creates. Copy this, fill in the brackets, and adapt it to your team.
[Company Name] Four-Day Work Week Policy
Purpose. This policy sets out how [Company]'s four-day work week operates. Our goal is to support employee well-being and focus while maintaining our standards of work and service.
Schedule. Full-time employees work [4 days / 32 hours] per week at full salary and benefits. The standard non-working day is [Friday], unless a staggered schedule is assigned to maintain coverage.
Coverage. [Team/Client-facing roles] follow a staggered schedule so that [department] is available [days/hours]. Managers are responsible for ensuring adequate coverage each day.
Availability. Employees are not expected to work or respond to messages on their non-working day. Urgent matters are routed to [on-call contact / whoever is scheduled].
Expectations. The four-day week depends on maintaining output and quality. Success is measured against [agreed metrics]. This is not a reduction in responsibilities.
Time off and holidays. PTO, sick leave, and holidays are tracked against the [4-day] schedule. [One PTO day = one scheduled workday.]
Trial and review. This policy runs as a [6-month] trial beginning [date]. It will be reviewed on [date] and may be continued, adjusted, or ended based on the results.
Two details are easy to get wrong. First, decide how PTO accrues and is counted against a shorter week, so a day off is still a fair day of leave; our guides on PTO accrual and building a PTO policy template walk through the math. Second, update your employee attendance policy so the "normal" schedule reflects four days, not five.
Industries and roles where it works best
The four-day week isn't equally suited to every business. It works best where output is measured by results rather than hours at a station, and where there's genuine slack (meetings, busywork) to cut.
Strong fit:
- Software and product teams
- Marketing, design, and creative agencies
- Professional services and consulting
- Nonprofits and administrative teams
- Most remote-first knowledge work
Harder fit (possible, but needs more staff or staggering):
- Retail and hospitality
- Healthcare and care work
- Manufacturing and warehousing
- 24/7 support operations
For distributed teams, the shorter week pairs well with async-first habits, since both reward cutting unnecessary real-time coordination. If you're already running a flexible setup, our remote team management guide and hybrid work policy template cover the coverage and communication norms that make a four-day week easier to sustain.
Real-world case studies and results
Concrete examples make the tradeoffs clearer than any statistic.
Perpetual Guardian (New Zealand). Andrew Barnes's estate-planning firm ran the trial that started the modern movement. Productivity held or improved, and employee stress and work-life balance measurably got better, which led the company to make the four-day week permanent.
The 4 Day Week Global trials. Beyond the headline 35% revenue jump and 71% burnout drop, the striking result was persistence: when the six-month trial ended, the overwhelming majority of the 91 companies kept going. Very few schedule experiments survive contact with real quarterly pressure, and this one did.
The pattern across companies. The organizations that succeeded shared three habits: they cut low-value work before cutting the day, they measured output honestly, and they involved employees in finding the efficiencies. The ones that struggled usually skipped the redesign and just tried to do five days of work in four. As Harvard Business Review notes, the shorter week improves well-being without hurting productivity "but only when implemented effectively."
For a small team, the takeaway is encouraging: you don't need enterprise resources to run this. You need a clear model, honest metrics, and a simple way to track schedules and time off. A tool like Tiny Team handles the calendar side, tracking PTO, custom schedules, and holidays in one place, which matters more than usual when your "normal" week is now four days and some people are staggered. It's free for teams up to 10, so a small company can pilot the change without adding software cost.
If you're weighing this alongside other flexibility perks, an unlimited PTO policy and a strong workplace culture often reinforce the same goal: trusting people with their time in exchange for results.
Frequently asked questions
Does a 4-day work week mean less pay?
Usually no. The most common and most-studied version keeps salary and benefits unchanged while cutting hours from 40 to 32. The trade the employer makes is fewer hours for the same output, achieved by cutting low-value work. A compressed 4x10 schedule keeps both hours and pay the same.
What is the difference between a compressed and a reduced 4-day week?
A compressed week (4x10) keeps all 40 hours, just packed into four longer days, so total hours don't change. A reduced-hours week (4x8) cuts the total to 32 hours at full pay. The reduced version is the one behind the well-known burnout and retention results, but it requires genuinely redesigning how work gets done.
Is a 4-day work week legal in the US?
Yes. There's no federal law preventing it. The main thing to watch is overtime: under the FLSA, non-exempt employees earn overtime after 40 hours a week, and a few states (like California and Alaska) require daily overtime after 8 hours, which affects 4x10 schedules. Check your state's overtime rules before rolling out a compressed schedule.
How do you handle client coverage on a 4-day week?
Most teams either stagger days off so someone is always available, set clear response-time expectations with clients, or route urgent issues to whoever is scheduled that day. On a small team, a shared calendar that shows who's off when is essential so no day gets accidentally left uncovered.
How long should a 4-day work week trial run?
Three to six months is the standard. That's long enough to move past the initial novelty, work out coverage and scheduling kinks, and gather real data on output and well-being, while still being clearly reversible if it isn't working.
What metrics should I track during a trial?
Agree on 3-5 measures before you start: revenue or output, customer response times, error or quality rates, employee satisfaction, and sick-day usage. Recording a baseline first is what lets you judge the trial on data instead of opinions at the end.
