- By Admin
- 09/24/2026 12:12:40
ALL
India Labour Codes 2026: Timesheets & Leave
On 8 May 2026 the Government of India notified the final Central Rules under all four Labour Codes, and with that, labour codes 2026 compliance stopped being a policy discussion and became an operational one. A 48-hour week, overtime paid at double the ordinary rate, a hard cap of 144 overtime hours per quarter, mandatory appointment letters and grievance committees now sit on top of every Indian employer running project teams, site crews or billable consultants.
The uncomfortable part for most organisations is not the substance of the rules. It is the evidence. Almost every obligation in the four Labour Codes India has now consolidated — hours worked, rest intervals, overtime, wage components, leave accrual and encashment — is enforceable only if the employer can produce an auditable, employee-level record. A shared Excel attendance tracker maintained by an office administrator, reconciled at month end and overwritten each cycle, is not that record.
This article walks through what the notified Central Rules actually require you to capture, why the 144-hour quarterly overtime cap changes how project managers plan crunch periods, and how Indian firms are replacing fragmented spreadsheets with a single system of record for attendance, overtime and leave before their state rules land later in 2026.
Key takeaways
- The final Central Rules under all four Labour Codes were notified on 8 May 2026, consolidating 29 central labour laws into a single enforceable framework.
- Working hours are fixed at 48 hours per week, with overtime payable at twice the ordinary rate of wages and a hard ceiling of 144 overtime hours per quarter per worker.
- Every employee must receive a mandatory appointment letter, and establishments above the prescribed threshold must constitute internal grievance redressal committees.
- Registers of hours, overtime, wages and leave must be maintained in a form that survives an inspection — which in practice means digital, employee-level and timestamped.
- State-level rules are still rolling out through the rest of 2026, so multi-state firms should build one compliant process now rather than reconciling several later.
Why labour codes 2026 compliance matters right now in India
India spent nearly six years between the passage of the four Codes and the notification of workable Central Rules. That gap created a habit: employers treated the Codes as pending, kept running on the old Factories Act, Shops and Establishments and Payment of Wages routines, and assumed there would be a long transition. The 8 May 2026 notification closed that window. The Code on Wages, the Industrial Relations Code, the Social Security Code and the Occupational Safety, Health and Working Conditions Code now operate together, and the Central Rules give inspectors a concrete checklist of registers and returns to ask for.
The second reason this is urgent is the definition of wages itself. The Code on Wages Central Rules 2026 anchor the statutory definition of wages to a floor where basic and allied components must not fall below 50% of total remuneration. For Indian IT services firms and engineering consultancies that have historically structured cost-to-company packages with a small basic and a large basket of allowances, that recalculation flows straight through to gratuity, EPFO contributions, leave encashment and overtime rates. Overtime at double the ordinary rate on a restructured wage base is a materially larger number than most 2025 payroll models assumed.
The third reason is timing risk across states. Labour is a concurrent subject, so central notification is only half the picture. Several states have published draft rules, others are still consulting, and the sequencing will continue through the remainder of 2026. A firm with a development centre in Bengaluru, an engineering office in Pune and site teams in Gurugram will end up subject to three slightly different sets of state rules on registers, working-hour flexibility and overtime approval. The organisations handling this well are not maintaining three processes. They are capturing one clean dataset — who worked, when, on what, and under whose approval — and configuring the state variations as policy on top of it.
What it means for HR, payroll and operations leaders at Indian firms
If you lead HR, payroll or operations at an Indian IT or tech consultancy, an engineering firm or a construction contractor with anywhere between 20 and 500-plus employees, the practical burden of the Codes falls on you rather than on legal counsel. Counsel will interpret the clause; you have to produce the register. Three shifts follow from that.
Attendance stops being an HR artefact and becomes a delivery record. Under the old regime, attendance existed largely to drive payroll and leave balances. Under the Occupational Safety and Health Code rules, the record of hours worked, spread-over and rest intervals is a safety and welfare compliance document. That is a meaningfully higher bar for construction contractors and engineering firms whose people are on site, at client premises or moving between locations, because a muster roll signed at a site office does not travel with the worker. Mobile capture with a location and timestamp is now the pragmatic answer, not a nice-to-have.
Overtime becomes a planning constraint, not a payroll adjustment. The 144-hour quarterly ceiling works out to roughly 11 hours of overtime per week across a 13-week quarter. For an IT services team running a go-live, or an EPC contractor pushing a commissioning window, that budget can be consumed in three weeks of genuine crunch, leaving ten weeks in which the same people legally cannot be asked to work extra hours. Delivery managers who cannot see a running quarterly overtime balance per person will discover the breach after it has happened, when payroll reconciles — and by then the exposure is both a wage liability and a compliance finding.
Leave has to be tracked to the day, with an accrual trail. The Codes standardise annual leave entitlement and eligibility thresholds and require encashment treatment on exit. Organisations still running leave in a shared spreadsheet routinely carry silent errors: leave taken but never deducted, approvals given over messaging apps with no record, carry-forward applied inconsistently between offices. Each of those is a small number until an employee exits or an inspector asks for a leave register covering the last twelve months, at which point the reconstruction cost is enormous and the answer is unverifiable.
Three practical implications for your operating model
Timesheets become the compliance record
The same weekly timesheet that drives project costing can satisfy the hours-worked register — but only if it captures actual start, end and interval data per employee rather than a lump total typed in on Friday evening.
Overtime needs a live running balance
A quarter-to-date overtime counter per worker, visible to the manager approving the extra hours, is the only reliable way to stay under 144 hours. A month-end payroll report is too late to prevent a breach.
Field and site attendance must be mobile
Construction crews, commissioning engineers and consultants at client sites cannot sign a register at head office. Mobile capture with timestamps produces a defensible record wherever the work actually happened.
Spreadsheets, point tools or a connected platform for timesheet compliance in India
| Capability | Spreadsheets | Point tools | Arcprojects.io |
|---|---|---|---|
| Employee-level hours register | Rebuilt monthly, overwritten each cycle | Present, but usually isolated from project data | Continuous, timestamped and tied to project and task |
| Quarterly overtime cap tracking | Manual formula, rarely current | Rarely supported as a rolling balance | Running quarter-to-date balance per employee |
| Approval trail for extra hours | Email or messaging app, unverifiable | Partial | Recorded approver, timestamp and comment retained |
| Leave accrual and encashment data | Separate sheet, drifts from payroll | Separate leave product required | Accrual, approval and balance in the same record set |
| Site and field attendance | Paper muster roll, keyed in later | Desktop-first, weak offline capture | Mobile capture for site and client-premises teams |
| Multi-state policy variation | One sheet per state, reconciled by hand | Usually a single global policy | Configurable policies over one clean dataset |
| Inspection readiness | Days of reconstruction, version-dependent | Export from several systems, then merge | Report generated on demand from one source |
How Arcprojects.io helps you meet labour codes 2026 compliance
Arcprojects.io maps directly onto the three record sets the Codes demand: Timesheets & Time Tracking for hours, overtime and rest intervals; Holidays & Leave Management for entitlement, accrual, approval and encashment; and the Mobile App for site and field attendance capture where the work physically happens. The point is not that these modules exist separately, but that they write to the same employee record, so a compliance report and a project cost report are drawn from one dataset rather than reconciled between three.
- Turn attendance into an auditable hours registerMove from monthly attendance summaries to weekly timesheet submission with start, end and interval capture per employee. Site crews and consultants at client premises log hours from the mobile app with a timestamp, so the register reflects where and when work was actually performed rather than when someone reached head office.
- Put a running overtime balance in front of the approverConfigure the 48-hour standard week and surface a quarter-to-date overtime figure against the 144-hour ceiling at the moment a manager approves additional hours. Approvals carry the approver's identity, timestamp and reason, which is exactly the trail an inspection or an internal grievance committee will ask for.
- Run leave as an accrual system, not a spreadsheetSet entitlement, carry-forward and encashment policy per location, let employees apply and managers approve in the system, and keep the full history. Leave-aware capacity in resource planning then stops delivery managers from committing people who are already on approved leave — a compliance win and a scheduling win in the same action.
See what an inspection-ready hours register looks like
Walk through timesheets, overtime tracking, leave management and mobile site attendance with a specialist who works with Indian project-based firms.
Request a demo"The Codes did not change how much your teams work. They changed how precisely you have to be able to prove it — per employee, per day, per quarter."
"We had three attendance trackers: one for the office, one for the engineering team and a paper muster roll at site. When the Central Rules were notified we realised we could not produce a twelve-month hours register for a single worker without a week of effort. Moving everything onto one timesheet with mobile capture took a fortnight and removed the entire argument."
Compliance checklist for HR, payroll and operations leaders
- Confirm every employee, including contractors on your rolls, has a written appointment letter on file.
- Recalculate wage structures so basic and allied components meet the 50% floor, then re-derive overtime, gratuity and EPFO exposure.
- Fix a single organisation-wide definition of a working day, week and rest interval, and configure it once.
- Enable a rolling quarter-to-date overtime balance per employee and alert managers before the 144-hour ceiling.
- Replace paper muster rolls at site with timestamped mobile attendance capture.
- Move all leave applications and approvals into a system that retains the accrual history.
- Constitute the grievance redressal committee where the establishment threshold applies and record its proceedings.
- Map which of your operating states have notified rules and which are still in draft, and diarise the gaps.
- Run a dry inspection: ask for one worker's twelve-month hours, overtime and leave register and time how long it takes to produce.
Frequently asked questions
How do India's new labour codes affect timesheets and attendance records?
The Codes shift attendance from a payroll input to a statutory register. Employers must be able to show hours worked, rest intervals, spread-over and overtime at an individual employee level, for each day, retained across the prescribed period. A monthly attendance summary or a spreadsheet that is overwritten every cycle will not satisfy that, because it cannot demonstrate what was recorded at the time or who approved it. In practice this pushes Indian firms towards weekly digital timesheets with an approval trail, and towards mobile capture for staff who work at sites or client premises. A useful summary of the notified rules is available in this flash alert on the final Central Rules.
What is the 144-hour quarterly overtime limit under the labour codes?
Overtime is capped at 144 hours per worker per quarter, and any overtime worked must be paid at twice the ordinary rate of wages. Because the base working week is fixed at 48 hours, the cap averages to roughly 11 additional hours per week across a quarter — but it is a quarterly pool, not a weekly allowance, so an intense delivery push in month one directly reduces what is legally available in months two and three. The practical control is a running quarter-to-date balance visible to whoever approves the extra hours, rather than a payroll reconciliation after the fact.
What records must an employer keep under the Occupational Safety and Health Code rules?
The Occupational Safety, Health and Working Conditions Code rules require establishments to maintain registers covering employee particulars, hours of work and rest, overtime, wages, leave and, where applicable, safety and welfare provisions, along with the appointment letter issued to each employee. Returns must be filed in the prescribed form and records retained for the specified period. The consolidation is helpful in one respect — a single set of registers replaces overlapping obligations under several older statutes — but it raises the evidential standard, because there is no longer a plausible argument that a given record sat under a different Act. Further detail on the notified obligations is set out in this analysis of the 2026 Central Rules.
One dataset, not four trackers
The four Labour Codes India has now brought into force are, at heart, a demand for a single reliable version of the truth about your workforce. Every organisation already holds most of that data — it is simply scattered across an attendance sheet, a leave tracker, a project timesheet and a payroll export, each maintained by a different person to a different standard. Compliance failures rarely come from a deliberate decision; they come from three of those four records disagreeing when someone finally checks. Consolidating them is the whole exercise.
Arcprojects.io was built for project-based Indian firms that need the same hour to serve two purposes: costing a project and evidencing compliance. Explore how the timesheet, leave and mobile modules fit together on the features and benefits page, see the kinds of organisations already running on it at who uses Arcprojects, or review pricing. You can also start a 30-day free trial and load one department to see how quickly a clean hours and leave register assembles itself.