Nearly 3,000 employees across 141 companies in six countries just finished a six-month trial of the four-day workweek, and the results were published in Nature Human Behaviour — arguably the most rigorous evidence yet on whether cutting a workday actually works. Burnout scores dropped. Job satisfaction rose. Productivity held steady or improved. And 90% of the companies that ran the trial decided to keep the new schedule after it ended.
If you own or run a small business, the science question is basically settled. The harder question is the one the study doesn't answer: how do you actually restructure payroll, overtime, and hourly scheduling to make a four-day week legal and financially sane? That's where most small employers get stuck, and it's where a shockingly large number of pilots quietly fail — not because employees hated the extra day off, but because nobody ran the compliance math first.
What the Study Actually Found
The trial, coordinated by researchers tracking 2,896 employees at 141 organizations in Australia, Canada, Ireland, New Zealand, the UK, and the US, tested an income-preserving four-day week — employees worked fewer hours for the same pay, rather than compressing 40 hours into four longer days. Over six months:
- Burnout fell from an average of 2.83 to 2.38 on a 5-point scale.
- Job satisfaction rose from 7.07 to 7.59 on a 10-point scale.
- Improvements were driven by better sleep, less fatigue, and improved work ability — not just "feeling happier about having a day off."
- Productivity did not drop. Researchers had hypothesized that condensing the same workload into less time might spike stress, but the opposite happened: employees reported feeling more capable, not more squeezed.
- 90% of participating companies kept the four-day week after the trial ended.
This echoes — and at a larger scale, confirms — earlier pilots. A separate multi-year 4 Day Week Global program tracking dozens of companies found revenue gains as high as 35% year-over-year during pilot periods, a 57% drop in staff attrition, and a 65% reduction in sick days. None of this is a fringe result anymore; it's a replicated pattern across hundreds of employers.
The Part the Headlines Skip: Two Very Different Models
"Four-day workweek" gets used as shorthand for two structurally different arrangements, and confusing them is the single biggest mistake small employers make when they try to pilot one.
1. The 100-80-100 model (reduced hours, same pay). Employees work roughly 32 hours instead of 40, for the same salary, on the theory that focused output over four days can match output over five. This is what the Nature study measured. It's straightforward for salaried, exempt employees — you're not touching hourly wage calculations at all. For hourly workers, it means real payroll cost per employee goes up relative to hours worked, which is the tradeoff you're accepting in exchange for the retention and productivity gains above.
2. The compressed workweek (same hours, fewer days). Employees still work 40 hours, just packed into four 10-hour days instead of five 8-hour days. Nobody's pay changes, but the scheduling and overtime rules get much more involved — and this is where compliance mistakes actually cost money.
Compressed Schedules and the Overtime Trap
If you're considering the compressed model for hourly staff, the federal baseline is workable but unforgiving on the details. Under the Fair Labor Standards Act, overtime is triggered by hours worked over 40 in a single workweek — not by hours worked in a single day. That means an employee working four 10-hour days, for a total of 40 hours, doesn't trigger federal overtime at all. The math only breaks if someone goes over 40 for the week, and averaging hours across two weeks to avoid that threshold is explicitly not allowed — each workweek stands alone.
Two details trip up small employers every time:
- Your workweek definition is fixed once you set it. A workweek is any consistent, recurring 168-hour period — it doesn't have to match the calendar week, but once you define it for payroll purposes, you have to apply it consistently. Sloppy or shifting workweek definitions are a common source of wage-and-hour disputes.
- State law can override the federal 40-hour rule entirely. California, for example, requires overtime after 8 hours in a single workday for non-exempt employees, regardless of the weekly total. A 4/10 schedule that's perfectly legal federally can generate daily overtime liability in California unless you follow a specific process: California requires employers to hold a disclosure meeting at least 14 days before a vote, get a two-thirds secret-ballot approval from the affected work unit, and file the results with the state labor agency before the new schedule can legally take effect. Skip that process and every "compressed" hour past 8 in a day is overtime, retroactively.
If you operate in a state with daily overtime thresholds — check before you assume the federal rule is the only one that applies — budget for either the formal election process or the overtime premium, not neither.
Building the Business Case Before You Pilot
Before rolling out a four-day week company-wide, run a small, time-boxed pilot with one team and track the numbers you'll need to defend the decision either way:
- Payroll cost per output unit. Compare labor cost against a consistent output metric (units shipped, tickets closed, billable hours) for the same team in the month before and during the pilot. This isolates whether the shorter week is actually cheaper or more expensive per unit of work, not just per hour.
- Overtime and premium pay exposure. If you're running a compressed schedule, track every instance of daily or weekly overtime separately from base pay so you can see the real marginal cost of the schedule change, not just gut-feel about whether "it seems fine."
- Absenteeism and turnover, even over a short window. The published data trends are large (a 57% attrition drop in some trials) precisely because sick days and resignations are expensive and often under-tracked in small-business books. A few months of clean data on your own team tells you whether that pattern holds for your business specifically.
This is exactly the kind of decision that's easy to get wrong on gut feel and hard to get wrong when the numbers are sitting in front of you. If your bookkeeping already separates labor cost by team, project, or output category, a pilot like this is just a matter of pulling the right report before and after. If it doesn't, a four-day-week trial is a good forcing function to build that structure now — you'll want it for the next staffing decision anyway.
Keep Your Payroll Data Clean Before You Experiment
A four-day-week pilot only tells you the truth if your books can isolate labor cost, overtime, and output cleanly enough to compare before-and-after. Beancount.io gives you plain-text accounting that's transparent and easy to query down to the transaction — no black-box reports, no vendor lock-in, just a ledger you can slice however the experiment demands. Get started for free and see why developers and finance-minded owners are switching to plain-text accounting.