Companies With a 4-Day Workweek (Employer Guide)
A four-day workweek is a schedule design, not a single policy. Employers should say whether they are reducing weekly hours, compressing the same hours into fewer days, or staggering days to maintain coverage. Set pay and workload rules, check legal duties, and test the model in a time-limited pilot. Measure service, output, costs, and employee well-being against a baseline before deciding whether to expand it.
A four-day week can help employers compete for talent, but the label alone tells employees little. A 32-hour week at full pay is not the same offer as four 10-hour shifts. Nor does either model work well if the same workload is squeezed into fewer hours without process changes.
I approach this as an operating model, not a perk announcement. The useful questions are practical: What work will stop, change, or move? How will customers reach the organization? What evidence would justify continuing? The guide below sets out a path from diagnosis to evaluation.
Four-Day Workweek Models: Definitions, Evidence, and Employer Fit
A four-day workweek describes several schedules with different effects on hours, pay, and coverage. Employers should name the model precisely before discussing benefits. There is no single universal standard, so publish the weekly hours, pay policy, work expectations, eligible roles, and service plan.
| Model | Weekly hours | Pay approach | Main employer consideration |
|---|---|---|---|
| Reduced-hours week | Fewer hours, such as 32 | Maintain regular pay if that is the offer | Redesign workload and remove low-value work |
| Compressed week | Often the same hours over four days | Pay and hours follow existing terms, subject to law | Longer shifts may not suit every role or employee |
| Staggered four-day schedules | Varies by employee | Depends on the chosen hours model | Coordinate shifts to preserve service coverage |
A reduced-hours model changes the amount of scheduled work time. A compressed model changes when the hours are worked, not necessarily how many. Staggered schedules describe how days off are arranged across a team; they can support coverage but do not, on their own, reduce weekly hours.
What the evidence can and cannot tell employers
The 2022 UK pilot coordinated by 4 Day Week Global involved 61 organizations and about 2,900 workers over six months. Participating organizations tested reduced hours with no pay cut, using different approaches to reorganize work. The 2023 report said 56 organizations continued the arrangement after the trial, including 18 that made it permanent.
The report also described lower employee-reported stress and burnout, fewer reported sick days, and fewer staff departures during the pilot. Among 23 organizations that supplied revenue data, average revenue was reported as 1.4% higher than in the same period a year earlier. These results are useful examples, not a forecast: participating employers chose to join, organizations used different methods, and the comparison does not prove the schedule caused the outcomes.
Key takeaway: Choose the model that fits the work, then define it in plain language. Treat published pilot results as evidence to inform your test, not as a promise of results.
Designing the Schedule: Workload, Pay, Coverage, and Compliance
Schedule design is the set of decisions that makes a four-day week workable in daily operations. Before launch, define hours, pay, workload, eligibility, coverage, and employee safeguards. Consult affected teams and review local rules. A schedule that is clear on paper but fails during busy periods will not earn trust.
1. Diagnose the current operation
Map work by role, location, and customer demand. Record current hours, peak service periods, handoffs, backlogs, overtime, and key performance measures. Look for tasks that can be stopped, simplified, automated, or shifted, rather than assuming employees can complete five days of work in less time.
Set a baseline before changing the schedule. Use enough history to capture normal variation, such as seasonal demand or a known busy period. Record how each measure is calculated, who owns the data, and how often it will be reviewed.
2. Set the terms and workload rules
For a reduced-hours week, state whether salary, benefits, leave accrual, and other terms remain unchanged. Then define what work will be removed or redesigned. If the organization expects the same hours in four longer shifts, label the arrangement as compressed hours and explain shift length and overtime rules.
Document eligibility and exceptions by job duties, not by informal preference. Some roles may need daily coverage or fixed service hours. Consider rotating days off, shift handovers, part-time options, and accommodations. Explain how decisions will be made and how employees can ask for review.
3. Build a coverage plan and complete legal review
Set customer and internal service hours. Name who covers urgent requests, how teams hand work over, and what happens on holidays or during peak demand. Test the plan against real schedules, not just an ideal week. Do not solve gaps by expecting off-day employees to monitor messages.
Before launch, have qualified HR or legal staff review applicable wage-and-hour, overtime, leave, discrimination, accommodation, and collective-agreement requirements. These rules vary by jurisdiction and worker classification. A four-day schedule does not remove existing obligations.
Key takeaway: A sound design protects pay and clarifies workload, while making coverage and compliance explicit. Resolve these issues before announcing a pilot date.
Pilot Implementation: Employee Experience, Measurement, and Iteration
A pilot is a time-limited test with a baseline, written rules, and planned reviews. It lets an employer find service gaps and workload problems before making a permanent decision. Set the duration, measures, and decision criteria in advance, then share findings with employees, including mixed or negative results.
Use real examples carefully
In the UK pilot, participating organizations used varied approaches, including shorter days, reduced weekly hours, and changes to work processes. The six-month trial offers a useful example of a defined test at scale. It does not show that one schedule suits every industry or that every participating employer achieved the same outcome.
Microsoft Japan’s 2019 “Work-Life Choice Challenge” gave employees five consecutive Fridays off during August, with no salary reduction, and the company reported a 39.9% rise in sales per employee compared with the same month the year before. This was a one-month company trial, not proof of a lasting four-day week. The comparison also cannot isolate the schedule’s effect from other changes or year-to-year variation.
Define measures before the pilot
Use measures tied to the organization’s goals. Employee sentiment matters, but it cannot stand in for service quality or financial results.
| Measure | What to track | Collection method |
|---|---|---|
| Output and quality | Completed work, errors, rework, or delivery time | Existing operational systems, reviewed weekly or monthly |
| Service | Response time, missed coverage, complaints, or service-level results | Customer and service records |
| Financial results | Revenue, cost, margin, or another role-relevant result | Finance records, compared with a suitable baseline |
| Workforce outcomes | Absence, turnover, overtime, and vacancies | HR and payroll systems |
| Employee experience | Workload, stress, schedule fit, and ability to disconnect | Anonymous surveys and structured interviews |
Use the same definitions before and during the test. Where possible, compare results with a similar team or location that did not change schedules. Note other changes, such as a new system or seasonal demand, that may affect the outcome.
Review, adjust, or stop
Schedule check-ins early enough to fix problems, for example after the first month and at regular intervals after that. Ask whether work is spilling into days off, overtime is rising, customer response is slipping, or employees feel they must work at an unsafe pace. Review results by role and location; averages can hide uneven effects.
Set decision limits before launch. For example, an employer might require service results to remain within an agreed range of baseline and overtime not to rise beyond a set limit. Those limits are organization-specific, not universal benchmarks. If safeguards fail, pause, revise the schedule, or stop the pilot rather than treating strain as a sign of commitment.
Key takeaway: Monitor employee experience alongside operational results. A popular schedule is not a successful pilot if quality, coverage, or workload safeguards deteriorate.
Business Outcomes: Productivity, Retention, Costs, and Employment Implications
Business outcomes show whether the schedule supports organizational goals over time. Review productivity, service, costs, retention, absence, and employee well-being together. Do not rely on a single headline metric or assume positive employee feedback proves financial success. Publish what changed, what did not, and what the evidence cannot establish.
Assess the full cost and value
A reduced-hours week may affect output, staffing needs, overtime, recruitment, and retention. A compressed schedule may keep weekly hours steady but raise concerns about long shifts, fatigue, or coverage. Calculate direct costs and review indirect effects, such as missed handoffs or delayed customer support.
Use measures that fit the work. A sales team may track revenue and customer response; a service team may track waiting time and resolution quality. For project-based roles, consider delivery time, rework, and stakeholder feedback. Compare results with the baseline and, where feasible, a similar group. Note that a simple before-and-after comparison cannot show that the schedule alone caused a change.
Decide whether to scale
At the end of the pilot, compare results with the criteria set at the start. A decision should account for role differences and trade-offs, not only the overall average. If results are mixed, consider a narrower rollout, a different day-off pattern, or added process changes before expanding.
| Decision | When it may fit | Employer action |
|---|---|---|
| Scale | Service and quality hold, workload is manageable, and agreed goals are met | Extend in stages and continue regular checks |
| Revise and retest | Results vary by team or a fix appears practical | Change the schedule or workflow and set a new review date |
| Stop | Workload, safety, compliance, or service safeguards fail | Restore a workable schedule and explain the decision |
I recommend treating scale-up as a new operating phase, not the end of evaluation. Recheck measures after expansion, since a small pilot may not reveal the effects of wider adoption. Review eligibility, pay practices, coverage, and legal compliance at set intervals.
Key takeaway: Continue only when the evidence supports the model and safeguards remain intact. Document the decision and the reasons behind it.
Conclusion and FAQ
A four-day week is most useful when employers define the model, redesign work, and test results with care. The strongest process starts with a baseline, protects against hidden work intensification, and measures both business performance and employee experience. No single schedule or pilot result can guarantee success across every role or organization.
What counts as a four-day workweek?
It can mean fewer weekly hours, the same hours compressed into four days, or staggered schedules that provide coverage. Employers should state which model they use and disclose weekly hours, pay, and days off.
Does a four-day week mean a 32-hour week?
Not always. A 32-hour schedule is one reduced-hours model. A 40-hour week over four longer days is compressed hours, not a reduction in weekly hours.
Should employees keep the same pay?
That depends on the employer’s stated model and applicable terms. A reduced-hours offer commonly means employees work fewer hours without a pay cut, but employers should document salary, benefits, leave, and other terms clearly.
How long should an employer run a pilot?
There is no universal duration. Set a period long enough to test regular operations and relevant busy cycles. The UK trial lasted six months, but employers should choose a timeframe suited to their work and goals.
What should employers measure?
Track output or productivity, service quality, relevant financial results, overtime, absence, retention, and employee well-being. Define each measure and collection method before the pilot begins.
Can a four-day schedule work in customer-facing roles?
It can, if staffing and handoffs preserve service. Employers may use staggered days off, rotating shifts, or other coverage plans. Test customer response and service quality during the pilot.
Is employee satisfaction enough to make the pilot a success?
No. Satisfaction is valuable, but employers should also check workload, overtime, quality, coverage, and financial or operational results. Positive sentiment alone does not prove the model is sustainable.
What are the main warning signs?
Watch for work spilling into days off, rising overtime, longer backlogs, more errors, missed service targets, or increased stress. Review these signs by role and team, then adjust or stop the pilot if safeguards fail.
Do four-day workweeks always improve productivity or retention?
No. Results depend on the organization, schedule, work redesign, and how outcomes are measured. Pilot findings can guide decisions, but they do not guarantee the same results elsewhere.
What should employers do before launch?
Map the work, set a baseline, choose and define the schedule, consult employees, build a coverage plan, review legal duties, and agree on measures and decision limits. Then communicate the pilot terms before it starts.
(This article was written by one of our staff writers, James Holloway. Visit our Meet the Team page.)
