Working Hours & Weekly Offs Under India's Labour Codes

Working Hours & Weekly Offs Under India's Labour Codes

Few topics generate more confusion in Indian HR teams than working hours. Everyone knows the broad shape — roughly eight hours a day, roughly forty-eight a week, one day off — but the moment you ask a specific question, certainty evaporates. Can we run a four-day week? How long can a shift be? Does a lunch break count as work? What about employees who "work from home in the evening"? Is a compressed roster legal?

This guide covers working hours and weekly offs under India's labour codes in practical terms: the principles employers should design around, the policy decisions you need to make, and the attendance systems and records that make your position defensible. Because the codes are implemented through state rules and notifications that vary and continue to evolve, treat every specific number here as something to verify with your state's current rules and with a labour law advisor before you rely on it.

The framework in principle

India's labour law on working time has historically been spread across several statutes — factories legislation, shops and establishments legislation in each state, and sector-specific rules — with the labour codes consolidating much of this into a smaller set of instruments. Whatever the instrument, the underlying architecture has been remarkably stable for decades and revolves around six concepts.

1. A daily hours limit. A maximum number of hours an employee may ordinarily be required to work in a day.

2. A weekly hours limit. A maximum number of ordinary working hours in a week, historically framed around forty-eight.

3. A spread-over limit. The maximum elapsed time from start to finish of a working day, including breaks. This is what stops an employer from splitting a shift across sixteen hours of the day.

4. A mandatory rest interval. A break after a defined stretch of continuous work.

5. A weekly off. At least one full day of rest in a week, with rules on substitution.

6. Overtime. Work beyond ordinary hours, paid at a premium rate, subject to a cap over a defined period.

Almost every practical question you have is an application of one of these six. When you cannot find an answer, ask which of the six the question really concerns — that usually narrows it fast.

The four-day week question

This is the question HR teams are asked most often, usually by a founder who read about it.

The concept being discussed in India is not the same as the four-day week discussed in Europe. The European version generally means fewer total hours for the same pay. The Indian version under discussion is a compressed week: the same weekly hours, packed into fewer, longer days, with correspondingly more weekly off days.

That distinction matters enormously:

Three practical points:

• A compressed roster runs straight into daily hours and spread-over caps. If your state's rules cap daily hours below what a compressed week requires, you cannot implement it regardless of employee willingness — unless the applicable rules provide an explicit mechanism.
• Compressed weeks generally require employee consent and often a formal notification or approval. Do not roll one out unilaterally.
• Reduced-hours models are a compensation and productivity decision, not a legal one. Nothing stops an employer paying full salary for a 32-hour week. The constraint is commercial.

If a founder asks for a four-day week, the first question back should be: "Same hours in fewer days, or fewer hours?" The answers diverge completely from there.

Designing your working-hours policy

A defensible policy answers these questions explicitly. Most policies fail because they leave several blank.

Scope and classification

• Which employees does the policy cover? Full-time, part-time, fixed-term, interns, consultants?
• Do you differentiate between shift-based roles and salaried roles with flexible timing?
• Which locations, and therefore which state rules, apply to each group?

Multi-state employers should build a state matrix: one row per state, columns for daily cap, weekly cap, spread-over, rest interval, weekly off rules, overtime rate and overtime cap, night-work provisions, and the registration or notification requirements. Maintain it, date it, and cite the source rule for each cell. When a query arises two years later, this matrix is the fastest path to an answer.

Ordinary working hours

• Standard start and end times, per location and per shift
• Total daily and weekly ordinary hours
• Whether hours are fixed, flexible within a band, or fully flexible
• Core hours during which everyone must be available, if any

Breaks

• Duration and timing of the meal break
• Whether short breaks are counted as working time
• Whether the meal break is paid or unpaid, and whether it counts toward spread-over
• Rules for roles where the employee cannot leave their post

Be precise here. "One hour for lunch" is not a policy. "A 45-minute unpaid meal break to be taken between 12:30 and 14:30, not counted as working time but counted within spread-over" is a policy.

Weekly off

• Which day is the weekly off, per location and shift
• Rules for substitution when an employee works on the weekly off
• The maximum number of consecutive days that may be worked
• How the weekly off is granted for rotating shifts

Overtime

• What constitutes overtime and who may authorise it
• The premium rate applied
• The cap over the defined period and how you monitor it
• Whether compensatory time off may be given instead of payment, and under what conditions
• How overtime is captured and approved before payroll cut-off

Shift work and rosters

• How rosters are published and how far in advance
• Minimum rest between shifts
• Rules for rotating between shifts
• Night shift provisions, including transport and safety obligations
• Swap and cover rules

Remote and hybrid work

This is the area where most policies are silent and most disputes now originate.

• Are remote working hours the same as office hours?
• How are hours recorded for remote workers?
• Is there a right to disconnect outside working hours?
• What is the expectation on responsiveness to messages after hours?
• How is overtime handled for remote work?

Attendance systems: making your position provable

A policy you cannot evidence is a policy you do not have. Your attendance system needs to produce, on demand, for any employee and any date range:

• Actual in and out times
• Break durations
• Total hours worked per day and per week
• Weekly offs taken
• Overtime hours, with the approval record
• Leave and holiday overlays
• Regularisation requests and their approvals, with reason

Choosing a capture method

Most companies of any size end up with two or three methods running in parallel. That is fine, provided they all feed one attendance record. What is not fine is a biometric log for the factory, a spreadsheet for the office and WhatsApp messages for the field team, reconciled manually at month end.

Regularisation: the control that matters

Every attendance system produces exceptions — missed punches, device failures, offsite meetings, travel. The regularisation workflow is where accuracy is won or lost.

A good regularisation process:

1. Employee raises the request within a defined window (say, five working days)
2. Reason is selected from a controlled list, with free text for detail
3. Manager approves or rejects with a comment
4. HR reviews patterns — an employee regularising fifteen days a month is a signal, not an administrative item
5. Approved regularisations flow to payroll automatically
6. Everything is logged with timestamps

Without a defined window, regularisations arrive after payroll cut-off and force retrospective salary adjustments. Set the window and enforce it.

Overtime: getting it right

Overtime is where working-hours compliance most often becomes a financial exposure.

The four requirements

1. Authorisation before the fact. Overtime should be requested and approved before it is worked, not discovered afterwards. This is a cost control as much as a compliance control.
2. Accurate capture. The hours must come from the attendance system, not from a manager's recollection.
3. Correct rate. The premium rate and the wage base on which it is computed both matter. If the definition of wages used for overtime differs from your payroll's default definition, your overtime is wrong.
4. Cap monitoring. Overtime is typically capped over a quarter or similar period. You need a running report, not a year-end discovery.

The wage base trap

Overtime is generally computed on a defined wage base, not on the full cost to company and not necessarily on basic salary alone. If your salary structure has a small basic and a large set of allowances, the wage base used for overtime — and for retirement contributions, gratuity and statutory bonus — may be higher than you assume. Model this. It is one of the most common sources of underpayment liability in Indian payroll.

Compensatory off instead of pay

Many employers prefer to grant compensatory time off for extra hours worked. Whether this is permissible in place of statutory overtime pay depends on the applicable rules and the category of employee. Even where permitted, run it properly:

• Comp-off must be credited automatically when qualifying work is recorded
• It must have an expiry, or your liability accumulates indefinitely
• It should be visible to the employee in self-service
• Encashment on expiry or exit should be defined in policy

An untracked comp-off practice — "just take a day off sometime" — creates disputes at exit and an unquantified liability on your books.

Weekly offs and continuous work

The weekly-off rule is simple in principle and messy in shift operations.

The principle: an employee should not work more than a defined number of consecutive days without a full day of rest, and where the weekly off is worked, a substituted off should be granted within a defined period around it.

The mess: rotating rosters, festival coverage, month-end peaks, and employees who volunteer for extra shifts because they want the overtime.

Practical controls:

• Build the consecutive-days check into the roster tool. The system should refuse to publish a roster that breaches the limit, rather than relying on a scheduler to notice.
• Track substituted offs as a balance, like leave. If an employee works their weekly off, a substitute off is credited with a deadline.
• Run a monthly exception report: employees who worked more than the permitted consecutive days, employees with unsubstituted weekly offs, employees exceeding overtime caps.
• Do not let employee willingness override the limit. Consent is generally not a defence to a statutory working-hours breach.

Records and registers

Working-hours compliance is evidenced by records. Typically you will need to maintain, in the format prescribed by the applicable rules:

• A register of employees
• An attendance or muster record
• A wage register showing ordinary and overtime wages
• An overtime register
• A record of weekly offs and substituted offs
• Leave records
• Notices of working hours displayed at the workplace

Increasingly these may be maintained electronically, provided they are retrievable and in the prescribed form. Two practical rules:

1. Retention. Keep records for the prescribed retention period after an employee leaves, not just while they are employed.
2. Retrievability. An inspector or a court wants a specific employee's record for a specific period, produced quickly. A system that can export that in minutes is worth a great deal more than one that requires a week of reconstruction.

Special categories

Night shift workers

Night work generally attracts additional obligations: consent, transport, security, facilities, and sometimes restrictions or conditions for particular categories of worker. Build a specific night-shift annexure to your policy rather than trying to handle it in the general text.

Young workers and apprentices

Where your workforce includes apprentices, trainees or workers below defined ages, additional restrictions on hours and night work typically apply. Flag these employees in the HRMS so the roster tool enforces the restriction automatically.

Field and sales teams

Employees who travel do not have a clean start and end time. Decide and document: does travel time count as working time? What about travel outside ordinary hours? Is a client visit logged as attendance? Use geofenced mobile attendance with a clear privacy notice and a defined radius, and be transparent with employees about what is collected and why.

Senior and managerial roles

Some categories of employee may be excluded from certain working-hours provisions depending on the applicable rules and their actual functions. Do not assume that a job title with "manager" in it creates an exclusion — the test generally looks at actual duties and authority. Get advice before classifying a group as exempt.

Implementation: a rollout plan

Changing working-hours policy is a change-management exercise, not a document exercise.

Weeks 1–2: Assess. Build the state matrix. Audit current practice against it. List every gap. Pull three months of attendance data and quantify: average hours worked, overtime volume, consecutive-day breaches, regularisation rates.

Weeks 3–4: Design. Draft the policy answering every question in the design section above. Model the cost impact of correcting any gaps — particularly overtime wage base and comp-off liability.

Weeks 5–6: Consult. Share with operations leaders and, where applicable, worker representatives. Working-hours changes affect earnings; expect and welcome pushback at this stage rather than after launch.

Weeks 7–8: Configure. Set up shift patterns, roster rules, overtime approval workflows, comp-off accrual and expiry, regularisation windows and exception reports in your HRMS.

Weeks 9–10: Communicate and train. Managers first, then employees. Managers need to understand approval obligations; employees need to understand punching, regularisation and their entitlements.

Weeks 11–12: Run and monitor. Go live with a weekly exception review for the first two months. Track: regularisation volume, overtime hours versus budget, consecutive-day breaches, and manager approval turnaround.

Frequently asked questions

How many hours a week can an employee legally work in India? Ordinary working hours have historically been framed around forty-eight per week with a daily limit, plus permitted overtime subject to a cap. The exact figures, and the treatment of compressed schedules, depend on the applicable code, the state rules and the establishment type. Verify against your state's current rules.

Is a four-day work week legal in India? A compressed four-day week — same weekly hours in fewer, longer days — depends on whether the applicable daily-hours and spread-over caps permit it, and generally requires employee consent and possibly a notification. A reduced-hours four-day week at full pay is a commercial decision with no statutory barrier. Confirm the position for your state and establishment type before implementing.

Does the lunch break count as working hours? Typically a meal break is not counted as working time but is counted within the spread-over limit. Whether it is paid is a policy matter for most employers. State this explicitly in your policy.

Can we ask employees to work on their weekly off? Generally only with a substituted off granted within a defined period, and subject to consecutive-day limits. Track substituted offs as a balance with a deadline, not as an informal understanding.

Do remote employees have working-hours protections? The underlying obligations generally apply to the employment relationship, not to the physical location. The practical challenge is evidence. Define recording expectations for remote work explicitly, and set a clear position on after-hours availability.

Is compensatory off a valid substitute for overtime pay? It depends on the applicable rules and the employee category. Where permitted, comp-off must still be tracked as a credited balance with an expiry and an exit-settlement rule. Get advice before adopting comp-off as the default for statutory overtime.

What records do we need to keep, and for how long? At minimum: employee register, attendance record, wage register including overtime, overtime register, weekly-off record and leave record — in the prescribed form, for the prescribed retention period. Electronic maintenance is increasingly permitted; confirm the format requirements for your state.

Can employees agree to waive working-hours limits? Generally no. Statutory limits usually cannot be contracted out of, and employee consent is not a defence to a breach. Consent may be a requirement for certain arrangements, such as night work or compressed schedules, but it does not remove the underlying cap.

How do we handle employees who work extra hours voluntarily? Recognise that unrecorded extra work is still a risk. Either capture and compensate it, or actively manage it down. The worst position is knowing it happens and having no record.

Bringing it together

Working-hours compliance is not primarily a legal-drafting problem. It is a systems problem. The companies that get it right have four things: a maintained state matrix, an attendance system that captures actual hours across all worker types, a roster tool that enforces limits rather than trusting schedulers, and a monthly exception report that someone actually reads.

With those four in place, the legal questions become answerable and the records become producible. Without them, even a perfectly drafted policy is unenforceable and unprovable.

CozyHR handles shift rosters, biometric and geofenced attendance, overtime approval workflows, comp-off accrual with expiry, regularisation with audit trails, and the exception reporting described here — across multiple locations and state rule sets. See how CozyHR handles attendance and shifts if your current process depends on a spreadsheet and a lot of goodwill.

Appendix A: The multi-state working-hours matrix

If you operate in more than one state, this single artefact will save you more time than anything else in this guide. Build it as a spreadsheet with one row per state (and, where relevant, per establishment type within a state) and these columns:

Two disciplines make the matrix useful rather than decorative:

• Date every row. A matrix without verification dates is a matrix nobody trusts, and untrusted documents get re-researched from scratch every time.
• Review on a fixed cadence. Twice a year, plus whenever a state issues a notification affecting your locations. Assign the review to a named owner with a calendar entry.

Appendix B: Monthly working-hours exception report

This is the report that turns policy into practice. Run it before payroll cut-off every month and require a written explanation for every line. Suggested contents:

Section 1 — Statutory limit breaches

• Employees exceeding the daily hours cap on any day
• Employees exceeding the weekly hours cap in any week
• Employees exceeding the spread-over cap
• Employees who worked more than the permitted consecutive days
• Employees with an unsubstituted weekly off beyond the substitution deadline
• Employees exceeding the overtime cap for the period to date

Section 2 — Process failures

• Attendance records with missing punches not regularised within the window
• Overtime worked without prior approval
• Regularisation requests approved after payroll cut-off
• Rosters published later than the required notice period
• Shift swaps executed without approval

Section 3 — Watch signals

• Employees regularising more than a threshold number of days
• Teams with overtime exceeding a threshold percentage of ordinary hours
• Comp-off balances approaching expiry
• Employees with zero leave taken in the last six months
• Locations with attendance capture rates below a threshold

Section 4 — Financial

• Total overtime hours and cost, by location and department, versus budget
• Comp-off liability outstanding, in days and estimated value
• Month-on-month movement in both

Circulate to operations leaders, not just HR. Working hours are managed by the people who build the rosters, and the report only changes behaviour if it reaches them with their name against the exceptions.

Appendix C: Manager briefing — the ten rules

Most working-hours breaches are created by a well-meaning line manager solving a short-term coverage problem. Give every manager a one-page card with these rules:

1. You may not ask anyone to work beyond the daily hours cap, even if they offer.
2. Overtime must be approved by you before it is worked, in the system.
3. Nobody works more than the permitted consecutive days without a rest day. No exceptions for peak periods.
4. If someone works their weekly off, a substituted off must be scheduled within the permitted window — put it in the roster immediately.
5. Publish rosters by the required notice deadline. Late rosters are a compliance issue, not an inconvenience.
6. Approve or reject regularisation requests within two working days.
7. Do not approve a regularisation you cannot explain. Your approval is the evidence.
8. Respect the minimum rest gap between shifts when scheduling swaps.
9. After-hours messages are not an instruction to work unless you say so explicitly. If you need after-hours work, approve it as overtime.
10. If you are unsure whether something is permitted, ask HR before it happens, not after.

Have managers acknowledge the card annually. It takes five minutes and materially changes what happens on the floor.

Appendix D: Costing a working-hours change before you make it

Any change to shift patterns, roster rules or overtime policy has a cost. Model it before you announce it, using three months of actual attendance data rather than assumptions.

Step 1 — Establish the baseline. For the last three months, per location and department: ordinary hours worked, overtime hours worked, overtime cost, headcount, and hours of coverage delivered.

Step 2 — Model the new pattern. Apply the proposed roster to the same coverage requirement. Compute: ordinary hours, overtime hours, headcount needed to deliver the same coverage without breaching limits.

Step 3 — Price the difference. Include all of these, not just base pay:

• Change in overtime cost
• Change in headcount cost, including recruitment and onboarding for any net additions
• Change in shift allowance or night allowance payouts
• Change in transport cost where night transport is provided
• Change in comp-off liability accrued
• Change in retirement contributions and gratuity accrual if the wage base moves
• One-off cost of system reconfiguration and manager training

Step 4 — Stress-test. Re-run the model at peak volume, at holiday coverage, and with an absence rate two points higher than average. A roster that works at average demand and breaks at peak will simply be violated at peak.

Step 5 — Check the employee-earnings impact. If a change reduces overtime opportunity, some employees will take home materially less. That is a legitimate business decision, but it must be a decision, communicated honestly and in advance, not a side effect discovered on payday. Quantify the number of affected employees and the average reduction, and prepare the communication before you launch.

Companies that skip step 5 face the sharpest resistance, because the people affected are usually the ones working the hardest shifts.

This article provides general guidance for HR practitioners and is not legal advice. Working-hours provisions differ by state, establishment type and worker category, and continue to evolve. Verify all specifics against current rules and consult a qualified labour law advisor.