Four-Day Work Week Policy Guide for Indian Employers

A four-day work week policy is no longer a fringe experiment in India. Founders who have watched automation absorb routine work, HR leaders fighting attrition in tight talent markets, and operations heads trying to make hybrid schedules less chaotic are all asking the same question: can we deliver the same output in fewer days, and what would it take to run it legally and cleanly on payroll?

This guide answers that question the way an HR or payroll team actually needs it answered. Not as a philosophy piece, but as a design manual: the models available, the working-hours and weekly-off rules you must respect in India, how to structure a pilot that produces evidence rather than anecdotes, how attendance, leave and payroll configuration must change, and the policy language you can adapt. If you are evaluating a compressed work week, a 32-hour week, or a rotational four-day roster, this is the full operating picture.

What people actually mean by a "four-day work week"

The phrase covers at least five distinct arrangements, and confusing them is the single most common reason pilots fail. Before you debate whether it will work, be precise about which model you are debating.

1. The compressed week (4 x 10, or "4/40")

Employees work the same total weekly hours, packed into four longer days. A 40-hour week becomes four 10-hour days; a 48-hour week becomes four 12-hour days, which in most Indian jurisdictions runs straight into daily-hour and spread-over limits.

• Total hours: unchanged
• Pay: unchanged
• Main appeal: a genuine third day off without reducing contracted hours
• Main risk: long days, fatigue, statutory daily-hour ceilings, and childcare or commute strain

2. The reduced-hours week (often called 100-80-100)

Employees work roughly 32 hours across four days, keep 100% of pay, and commit to maintaining 100% of output. This is the model behind most of the international trials that generated headlines. It is the most demanding version because it requires real work redesign, not just rescheduling.

• Total hours: reduced by about 20%
• Pay: unchanged
• Main appeal: the productivity and wellbeing story that leadership usually wants
• Main risk: if work is not redesigned, the fifth day's work silently migrates into evenings and weekends

3. The rotational or staggered four-day roster

The business stays open five, six or seven days. Individuals work four days; teams are rostered so coverage never drops. Support desks, retail, clinics, logistics and manufacturing usually land here if they land anywhere.

• Total hours: typically unchanged per person
• Pay: unchanged
• Main appeal: works for businesses that cannot close
• Main risk: roster complexity, weekly-off tracking, and perceived unfairness about who gets Friday versus who gets Tuesday

4. The conditional or earned four-day week

The short week applies only when defined conditions are met: sprint commitments delivered, SLA thresholds held, no open escalations. Sometimes framed as a monthly or fortnightly benefit rather than a standing entitlement.

• Main appeal: low risk, easy to withdraw
• Main risk: feels like a carrot-and-stick scheme and can quietly punish teams with unpredictable workloads

5. Seasonal or partial variants

Alternate-Friday closures, half-day Fridays year round, a compressed summer schedule, or a four-day week during specific low-volume months. These are the most common real-world starting points in Indian SMBs because they are reversible and cheap to test.

A practical rule: decide the model in writing before you socialise the idea internally. Employees will hear "four-day week" and imagine option 2. Leadership often means option 1 or option 5. That gap creates disappointment that no communication plan can fully repair later.

Why Indian employers are revisiting this now

Three forces are converging.

Automation is changing the shape of the working day. As AI tools absorb drafting, summarising, first-pass coding, ticket triage and report assembly, the remaining work is more concentrated and more cognitively demanding. Organisations that capture those efficiency gains face a choice: take the gain as more output, as headcount savings, or as time. A shorter week is one way to convert the gain into a retention asset.

Hybrid work has plateaued and needs a second act. Many Indian employers settled into two- or three-day office patterns and found that the flexibility story stopped being differentiating. A schedule benefit that is visible and easy to describe carries more weight in a candidate's decision than another hybrid tweak.

Attrition economics. Replacing an experienced professional costs a multiple of monthly salary once you count recruiter fees, notice-period gaps, onboarding time and the productivity dip. Schedule benefits are recurring, non-cash and often cheaper than a compensation correction, provided output holds.

None of that guarantees a shorter week will work in your business. It does explain why the question keeps arriving on HR's desk.

The legal frame in India: what you must respect

This is where enthusiasm meets statute. India regulates working time through central labour legislation and, critically, through state-level rules that differ meaningfully from one another. Treat the following as the structure of the problem, and verify current provisions and thresholds for your states and establishment type before you commit anything to a policy document.

Daily and weekly hour ceilings

Indian working-time law generally caps both the hours in a day and the hours in a week, and the daily cap is what constrains compressed schedules. A 4 x 12 arrangement that produces a 48-hour week will typically exceed ordinary daily-hour limits in most jurisdictions, which means the extra hours either need an exemption where one is available or must be treated as overtime. A 4 x 10 pattern is closer to workable but still needs checking against the daily ceiling and the permitted spread-over.

Spread-over

Separate from hours worked, rules commonly limit the total elapsed time between the start and end of a working day, inclusive of breaks. If your ten-hour day includes a long lunch and two breaks, the spread-over may be the binding constraint rather than the hours themselves.

Rest intervals

Rules typically require a break after a defined stretch of continuous work. Longer days mean more mandated breaks, and those breaks usually sit outside working hours, which lengthens the spread-over. Model the full day on paper, minute by minute, before assuming a ten-hour schedule ends at 7 pm.

Weekly off

A weekly rest day is a statutory requirement, and rules generally limit how many consecutive days an employee may work before that rest day falls due. A four-day week gives employees more rest, not less, so this is rarely the binding issue, but rostered models must still ensure no individual strings together too many consecutive working days across a roster boundary.

Overtime

Where hours exceed the statutory normal limits, overtime becomes payable at a premium rate, and the labour codes framework has moved toward a clearly defined premium for overtime hours. This matters enormously for compressed schedules: if your model pushes daily hours past the ordinary limit, you may have created a permanent overtime liability rather than a productivity initiative. Quarterly overtime ceilings may also apply.

Shops and establishments versus factories

Office-based employers are usually governed by the shops and establishments legislation of the state in which the establishment is registered, and those Acts differ on hours, spread-over, opening and closing times, and the notification or approval formalities for altering working hours. Manufacturing units face a separate and generally stricter regime. Multi-state employers must expect to run different variants of the same policy in different states.

Women employees and night shifts

If a compressed schedule pushes shift end times later, night-shift provisions for women employees may be triggered, which commonly carry conditions around consent, transport, security and facilities. A schedule change that quietly creates a night shift is a compliance problem, not a perk.

Records, registers and displayed hours

Working hours, rest intervals and weekly offs are typically required to be recorded and, in many states, displayed or notified. If you change the standard working day, your registers, notices and employment documentation should reflect the new pattern. The shift toward digital record-keeping under the consolidated labour codes framework makes accurate, exportable attendance data more important, not less.

Two practical cautions. First, contract language: if appointment letters specify working days or hours, a unilateral change may require documented consent or a formal addendum. Second, adverse change: reducing pay or benefits alongside a schedule change is a different and much more sensitive legal question than changing schedule alone. Take qualified legal advice on your specific establishments, states and employee contracts before rollout, and confirm current rates, ceilings and notification requirements with the applicable authorities.

Is your business actually a candidate?

Run this readiness assessment honestly. Score each statement from 0 (not true) to 2 (clearly true).

1. Our output is measurable in something other than hours present.
2. Managers already run weekly priorities, not ad-hoc task assignment.
3. Meetings consume less than about a quarter of the average week, or we are willing to cut them hard.
4. Client or customer commitments are defined by deliverables and response times, not by "available all week".
5. Work is documented well enough that a colleague can cover an absent teammate.
6. Our attendance and leave systems can handle non-standard weekly-off patterns.
7. Leadership will accept a genuine pilot, including the possibility of stopping it.
8. We have a small number of roles where a four-day pattern is clearly impossible, and we are prepared to handle them differently and transparently.

A score below 8 means you are being asked to solve a management problem with a calendar. Fix the management problem first. A score of 12 or above means a pilot is likely to produce usable evidence.

Roles that usually adapt well

• Engineering, product, design and analytics teams that work in sprints
• Marketing, content and creative teams with deliverable-based output
• Finance, HR and back-office functions outside peak cycles
• Inside sales teams with defined activity targets

Roles that need a rostered model instead

• Customer support and service desks with coverage SLAs
• Retail floor, warehouse and logistics roles
• Clinical and healthcare staffing
• Production lines with fixed shift patterns
• Field sales and service engineers tied to customer availability

Roles where it rarely works without extra headcount

• Single-person functions with no backup (the only payroll executive, the only compliance manager)
• Roles with statutory or contractual daily obligations
• Any role where absence directly stops revenue and no cross-training exists

Designing your four-day work week: a nine-step method

Step 1: Name the objective and the constraint

Write one sentence: "We are testing a four-day week to [objective] without [constraint]." For example: "to reduce voluntary attrition in engineering without slipping sprint commitments" or "to improve candidate conversion for support roles without breaching first-response SLAs". Every later decision refers back to this sentence. Vague objectives ("improve wellbeing") produce pilots that nobody can call successful or unsuccessful.

Step 2: Choose the model and write it down

Use the five-model taxonomy above. Specify hours, days, and whether the fifth day is genuinely non-working or merely non-scheduled. State explicitly whether pay changes (in almost all serious designs, it does not).

Step 3: Map the legal position for every state and establishment

Build a simple matrix: state, establishment type, current standard hours, daily cap, spread-over limit, break requirements, weekly-off rule, overtime treatment, notification or approval formalities, women's night-shift conditions. Fill it with verified current information for each location. If one state makes the model unworkable, decide early whether you run a different variant there or exclude that location from the pilot.

Step 4: Redesign the work, not just the calendar

This is the step organisations skip, and skipping it is why the fifth day's work reappears in the evenings. Before the pilot starts, each team commits to specific changes:

• Meeting audit. Cancel, shorten or convert to written updates at least 25% of recurring meetings. Default meeting length drops from 60 to 30 minutes and from 30 to 15.
• Decision rules. Define which decisions no longer need a meeting, and who can make them alone.
• Focus blocks. Protect at least two uninterrupted blocks per person per week in the calendar.
• Response-time norms. Replace "reply fast" with explicit internal response expectations per channel.
• Automation targets. Name three recurring manual tasks that will be automated or eliminated before the pilot begins, not during it.
• Work intake discipline. Requests arrive through a defined channel with a defined triage, not through direct messages to whoever is online.

Require each team to submit a one-page work redesign plan as a condition of joining the pilot. Teams that cannot produce one are not ready.

Step 5: Solve coverage explicitly

For every team, document who covers what on each off-day, how urgent items are escalated, and what the maximum acceptable delay is. Publish a coverage grid. For rostered models, build the roster for the entire pilot period in advance so employees can plan personal commitments and so you can spot consecutive-days problems before they happen.

Step 6: Configure attendance, leave and payroll before day one

Detailed below, but the sequencing matters: configuration must be tested with a dry run before the first live week, not patched afterwards.

Step 7: Communicate with employees, clients and candidates

Employees need the model, the pilot duration, the metrics, the review dates, and an unambiguous statement of what happens if it does not work. Clients need coverage and response-time commitments, ideally before they notice a slower reply. Recruitment needs approved language so candidates are not promised a permanent benefit during a pilot.

Step 8: Run the pilot with fixed review gates

A 90-day pilot with a formal review at day 30 and day 60 and a decision at day 90 works well. Shorter pilots are dominated by novelty; longer pilots become de facto permanent without ever being evaluated.

Step 9: Decide, document and either scale or stop

The decision must be written, dated and communicated. Either the policy becomes permanent (with a formal policy document and updated employment terms where required), or it is extended with named changes, or it ends. Pilots that quietly continue without a decision destroy trust in every future pilot.

Writing the policy: clause by clause

Below is a clause structure with adaptable language. Have your policy reviewed against your state rules and employment contracts before issue.

1. Purpose and scope

"This policy describes the four-day work week arrangement applicable to employees in the departments and locations listed in Annexure A. It does not apply to employees in roles listed in Annexure B, whose schedules are governed by the shift and roster policy."

2. The schedule

State the exact pattern: working days, start and end times, break timings, total daily hours, total weekly hours, and the designated non-working day. For rostered models, state how rosters are published and how far in advance.

3. Compensation

"Monthly gross and cost-to-company remain unchanged under this arrangement. Salary structure, statutory contributions and benefits are unaffected."

4. Attendance and availability

Define availability expectations on working days, whether any monitored channel remains active on the non-working day, and who may be contacted in a genuine emergency. Silence here produces informal always-on expectations.

5. Leave

Specify how leave is debited under the new pattern, how a leave day is defined in hours if your model uses non-standard days, how half-days work on a ten-hour day, and what happens when a public holiday falls on the non-working day.

6. Overtime and additional work

State whether the arrangement changes overtime eligibility, how work performed on the non-working day is treated, and the approval route required before any such work.

7. Performance expectations

"The arrangement is contingent on maintaining agreed output, quality and service levels. Individual or team performance shortfalls may result in return to the standard schedule for the individual or team concerned, following documented discussion."

8. Duration, review and withdrawal

State the pilot period, the review dates, the metrics, and an explicit reservation of the employer's right to modify or withdraw the arrangement with defined notice. This clause is what allows you to stop cleanly.

9. Exclusions and exceptions

List role categories excluded and the process for requesting an exception. Handle exclusions generously and visibly, or the policy becomes a fairness grievance.

10. Governing rules

"This policy is subject to applicable law, including working-hours, rest-interval, weekly-off and overtime provisions. Where any provision conflicts with applicable law or with an employee's terms of employment, the law or the contract prevails."

Payroll, attendance and leave mechanics

The operational detail is where a four-day week either runs quietly or generates a monthly queue of tickets.

Salary and statutory contributions

In every serious design, monthly salary is unchanged, so gross, basic, allowances and the resulting provident fund, state insurance, professional tax and tax-deducted-at-source calculations continue exactly as before. The four-day week is a scheduling change, not a compensation change. If leadership proposes reducing pay proportionally with hours, stop and treat it as a compensation restructuring project with entirely different legal, contractual and communication requirements.

Loss-of-pay proration

This is the most common configuration error. If your payroll system prorates loss of pay using calendar days, nothing changes. If it prorates using working days, the divisor changes when the working-day count changes, and one unpaid day is suddenly worth more. Decide the treatment, document it in the policy, and test it with a dry run.

Worked example, monthly gross of Rs 60,000 in a 30-day month:

• Calendar-day basis: one unpaid day = 60,000 / 30 = Rs 2,000. Unchanged by the schedule.
• Working-day basis, 22 working days: one unpaid day = Rs 2,727.
• Working-day basis, 17 working days under a four-day pattern: one unpaid day = Rs 3,529.

Both approaches are defensible; inconsistency between the policy, the payroll configuration and what employees were told is not.

Leave accrual and consumption

Decide whether leave continues to accrue in days or moves to hours.

• Days basis (simpler): one leave day equals one scheduled working day, even if that day is ten hours. Employees on a compressed schedule effectively consume more hours per leave day, which is usually accepted if it is stated clearly up front.
• Hours basis (fairer, more work): convert balances to hours, debit actual scheduled hours. Requires an attendance and leave system that supports hourly balances and clean reporting.

Whichever you choose, publish the conversion rule with an example before the first leave request lands. Also define half-day handling on long days, and whether sick leave on a ten-hour day debits a full day.

Public holidays

Define what happens when a declared holiday falls on the employee's non-working day. The three common approaches are: no compensation (simplest, sometimes resented), a floating day credited to the employee, or a shifted non-working day for that week (cleanest for rostered teams but roster-heavy). Pick one and apply it consistently across teams.

Attendance capture and shift masters

Your attendance system needs a shift or work-pattern master that supports the new pattern, weekly-off calendars that vary by individual for rostered models, and regularisation workflows that understand the longer day. Common configuration items:

• New shift definitions with correct start, end, break and grace values
• Weekly-off patterns assigned per employee or per roster group
• Overtime rules mapped to the new daily threshold
• Late-mark and early-exit rules recalibrated so a ten-hour day does not generate false exceptions
• Reports that show scheduled versus actual hours per week, not just per day

Overtime and comp-off

If the model creates any hours beyond statutory normal limits, those must be treated as overtime at the applicable premium. If employees work on their non-working day, decide in advance whether that generates compensatory off, overtime, or neither, and enforce a pre-approval requirement. Unapproved weekend work that later becomes a comp-off claim is a predictable and avoidable dispute.

Full-and-final and mid-month exits

Check how your exit settlement logic counts working days in the final month. Notice periods expressed in days should be clarified as calendar days to avoid arguments about whether a four-day week extends a notice period.

Running the pilot: metrics that actually settle the argument

Collect a baseline for at least the eight weeks before the pilot. Without a baseline, every result becomes an opinion.

The last one deserves emphasis. The classic failure mode of a shorter week is invisible: the work simply moves into evenings and the off-day. If your only metrics are output and satisfaction, you will declare victory while quietly building burnout. Track after-hours activity and ask about it directly in the pulse survey.

Decision gates. Define them numerically before you start. For example: continue if output stays within 5% of baseline, SLA breaches do not increase, overtime cost does not rise more than a stated threshold, and off-hours activity does not increase. Publishing the thresholds in advance is what prevents a post-hoc argument about whether the pilot "worked".

Twelve failure modes and how to avoid them

1. No work redesign. The calendar shrinks, the workload does not. Mandate the redesign plan as an entry condition.
2. Meetings survive untouched. Four days of the same meeting load leaves almost no focused time. Cut recurring meetings before, not during.
3. Coverage improvised. Everyone takes the same day off, then panics on the first client escalation. Publish a coverage grid.
4. Payroll configured late. Leave debits and loss-of-pay proration go wrong in month one and destroy confidence. Dry-run first.
5. The daily-hour ceiling ignored. A 4 x 12 model is built, then discovered to breach limits or trigger permanent overtime liability. Check statute at design stage.
6. Contracts not addressed. Appointment letters specify hours; the change is made unilaterally. Use addenda or documented consent where needed.
7. Excluded roles handled badly. Support and plant staff watch the office take Fridays off with no equivalent benefit. Design something meaningful for them at the same time.
8. The pilot becomes permanent by drift. No decision is ever made, so withdrawal becomes impossible without a morale event. Hold the decision date.
9. Managers not trained. Some teams protect the off-day, others erode it, and fairness complaints follow. Brief managers on non-negotiables.
10. Success measured by sentiment only. Everyone loves it; nobody checks output. Use the metric table.
11. Client commitments unchanged and uncommunicated. Customers discover the new schedule through a delayed response. Tell them first.
12. Recruitment over-promises. Candidates are told about a permanent four-day week during a pilot. Control the language in job posts and offer conversations.

Sector notes for Indian employers

IT services and product engineering. The best fit overall. Sprint-based delivery gives natural output metrics. Watch client contracts for availability commitments and support windows, and confirm on-call arrangements separately from the schedule policy.

Business process and customer support. Rostered four-day patterns work well and often improve coverage on weekends, but require genuine workforce management: forecast volume by interval, build the roster to the forecast, and track adherence. Do not attempt this on spreadsheets beyond a small team.

Manufacturing. Longer daily hours collide hardest with statutory limits and shift design, and machine utilisation economics usually dominate. Where a shorter week is attempted, it is typically a rostered four-day, longer-shift pattern with careful attention to rest intervals, overtime and safety fatigue rules.

Retail and hospitality. Person-days matter more than person-hours. A four-day roster generally means hiring more heads or accepting reduced coverage. Treat it as a workforce-planning decision with a cost attached.

Healthcare and diagnostics. Compressed shifts already exist in many settings. The constraint is patient safety and fatigue management rather than productivity.

Agencies and professional services. Billable-hour models make a reduced-hours week structurally difficult; compressed or seasonal variants are more realistic. If you bill by time, a shorter week is a pricing decision.

Startups under 50 people. The seasonal or conditional variants are the sensible entry point. A full reduced-hours week in a company still finding product-market fit tends to be reversed within a quarter, which costs more trust than it buys.

Manager enablement: the part that determines success

Give managers a short, concrete brief. The following non-negotiables travel well:

• Protect the off-day. No meetings, no expectation of replies, no "quick calls". If a manager contacts someone on their off-day, the manager explains why in the team channel.
• Plan weekly, not daily. Publish priorities at the start of the week so nobody wastes a longer day waiting for direction.
• Kill your own meetings first. Managers convene most recurring meetings. They cut them.
• Watch for leakage. If a team member is consistently active after hours, that is a workload signal to act on, not a work ethic to praise.
• Escalate coverage gaps early. Do not let individuals quietly absorb the gap.
• Be explicit about crunch. Name the periods when the arrangement is suspended (audit season, product launch, festival peak) in advance rather than improvising.

Communicating with clients and customers

Draft a short note that covers three things: the schedule, the coverage, and the commitment. Something like: "From [date], our team works Monday to Thursday. Our response commitments are unchanged: [X] hours for standard requests and [Y] hours for urgent issues. For urgent matters on Fridays, contact [channel], which is monitored by [team]."

Send it before the first affected week, not after the first delayed reply. For contracted service commitments, check whether the agreement specifies business days or business hours and whether a schedule change requires notice.

Alternatives worth considering first

A four-day week is not the only way to buy back time, and for many Indian SMBs one of these delivers most of the benefit at a fraction of the risk:

• Meeting-free days. One or two days per week with no internal meetings often recovers more focused time than a schedule change.
• Flexible start windows. Letting people start between 8 and 11 solves commute pain without touching hours.
• Compressed fortnight. Alternate short weeks: lower coverage impact, easier to staff.
• Half-day Fridays. The most common and most durable partial version in Indian offices.
• Additional annual leave. Simpler to administer, easier to reverse, and often valued similarly.
• Core-hours model. Fixed overlap hours with flexibility around them, which supports distributed teams better than a shorter week does.

A 90-day pilot plan you can copy

Weeks -8 to -1 (baseline and build). Collect baseline metrics. Confirm legal position by state. Select pilot teams. Require work redesign plans. Configure attendance, leave and payroll. Draft policy, employee FAQ, client note and manager brief. Run a payroll dry run on test data.

Week 0 (launch). All-hands briefing covering model, duration, metrics, review dates, and the explicit statement that the arrangement may be withdrawn. Publish coverage grid and roster. Manager briefing session.

Weeks 1 to 4. Weekly operations check: coverage gaps, SLA breaches, overtime, off-hours activity. Fix configuration issues immediately. Day-30 review against decision gates.

Weeks 5 to 8. Pulse survey. Client feedback check. Mid-pilot review at day 60 with a written summary shared with participants.

Weeks 9 to 12. Final data collection. Day-90 decision meeting. Written outcome communicated to everyone, including non-participating teams. If adopting, issue the permanent policy, update employment documentation where required, and update induction materials so new joiners are onboarded onto the correct schedule.

Frequently asked questions

Is a four-day work week legal in India? There is no general prohibition on scheduling four working days, but working time is regulated: daily and weekly hour limits, spread-over, rest intervals, weekly-off requirements and overtime provisions all apply, and the details vary by state and by establishment type. A compressed model that pushes daily hours past the statutory ceiling can create an overtime liability or a compliance breach. Verify current provisions for each of your locations and take legal advice before implementing.

Do we have to reduce salary if employees work fewer hours? No, and most credible designs do not. The arrangement is framed as a productivity and retention initiative in which pay is unchanged. Reducing pay changes the nature of the exercise entirely and raises contractual and legal issues that a scheduling policy cannot resolve on its own.

How does provident fund or state insurance change? If salary is unchanged, contributions are unchanged. The schedule does not alter the wage base. What can change is attendance-linked data such as paid days in a loss-of-pay month, so confirm how your payroll system derives paid days.

What happens to leave balances? That depends on whether you track leave in days or hours. Under a days basis, one leave day equals one scheduled working day even if it is longer; under an hours basis, you debit actual scheduled hours. Both are workable. Publish the rule with a worked example before the first leave request.

What if a public holiday falls on the non-working day? Choose one treatment and apply it consistently: no compensation, a credited floating day, or a shifted off-day for that week. Rostered teams usually find the shifted off-day cleanest; office teams often prefer the floating day.

Can we apply it to some teams and not others? Yes, and most employers must. The risk is fairness perception. Exclusions should be explained on operational grounds, reviewed periodically, and paired with a comparable benefit for excluded teams, such as additional leave, a rostered short week, or a shift allowance.

How long should the pilot run? Ninety days is the practical sweet spot: long enough to survive the novelty period and at least one month-end cycle, short enough that the organisation still treats it as reversible. Set the review dates before you start.

What is the single biggest predictor of failure? Not redesigning the work. Every durable implementation cut meetings, automated recurring tasks and tightened work intake before shortening the week. Every failed one simply removed a day and hoped.

Bringing it together

A four-day work week is an operations project wearing a benefits costume. The legal work determines whether your model is viable; the work redesign determines whether output holds; the attendance, leave and payroll configuration determines whether employees trust the arrangement after their first payslip. Get those three right, run a real pilot with published metrics and a real decision date, and you will have an answer specific to your business rather than a headline borrowed from someone else's.

Start small, measure honestly, and be willing to stop. A well-run pilot that ends with a documented "not yet" is a better outcome than a permanent arrangement that nobody evaluated.

If you are planning a pilot, the configuration work is where most of the effort lands: shift patterns, individual weekly-off calendars, leave rules that behave correctly on longer days, and payroll proration that matches what you promised in the policy. CozyHR handles flexible shift and roster patterns, individualised weekly offs, leave and attendance rules, and payroll processing in one place, so a schedule change is a configuration decision rather than a spreadsheet project. Try CozyHR to model your four-day week before you announce it.