Labour Codes Compliance Checklist: Post-Rollout Guide

Labour Codes Compliance Checklist: Post-Rollout Guide

If your organisation spent the last couple of years attending webinars, reading advisories, and telling your leadership team "we are tracking the labour codes," you have already done the easy part. The harder, less glamorous part is next: proving it. A proper labour codes compliance checklist is not a slide deck you presented once to the board — it is a living audit process that HR, payroll, and compliance teams run on their own documents, registers, and pay structures to confirm that what is written on paper is actually what is happening in practice. This guide is built for teams that are past the "what are the labour codes" stage and need a structured, repeatable way to verify readiness across wages, contracts, working hours, social security, and workplace safety.

One caveat before we go further, and we will repeat it throughout this article because it matters: the four labour codes have not moved to implementation uniformly across India. Central rules have been notified, and several states have issued or are still finalising their own rules, but the pace, sequencing, and specific requirements vary by state and by establishment type. Nothing in this article should be treated as a substitute for checking the current notification status in your specific state(s) of operation with a qualified labour law professional or compliance consultant. Treat this as an audit framework — the exact thresholds, forms, and deadlines you plug into that framework must come from current, state-specific legal advice.

A Quick Recap: Why a Fresh Audit Matters Now

You do not need another 2,000-word explainer on what the four labour codes are — you have read those already. What is worth a short recap is why "we adapted once" is not the same as "we are compliant now."

The four codes — on Wages, Industrial Relations, Social Security, and Occupational Safety, Health and Working Conditions — were designed to consolidate dozens of older central and state labour laws into four unified frameworks. For employers, that consolidation changed definitions (most importantly, the definition of "wages"), changed documentation expectations (appointment letters becoming near-universal), changed some procedural requirements around industrial relations, expanded social security coverage concepts (including gig and platform workers), and tightened occupational safety obligations for a wider band of establishments.

Because implementation has rolled out unevenly — some states moving faster on draft or final rules, others still catching up, and the central government sequencing notifications over an extended period — many companies did one of two things when the codes first started making headlines:

1. They made a one-time "check the box" adjustment — updated an offer letter template, tweaked a CTC structure spreadsheet, forwarded an advisory to the finance team — and then moved on to other priorities.
2. They waited and watched, assuming that because enforcement dates were unclear, there was no urgency, and they could revisit "when it actually applies to us."

Both approaches leave gaps. A one-time adjustment made 12–24 months ago may not reflect the current state of rules in your operating state, may not have been applied consistently across all business units, or may have been implemented by one team (say, payroll) without corresponding updates by another (say, HR policy or legal). The "wait and watch" approach leaves you exposed the moment your state's rules are notified in a way that applies to your establishment, with little runway to fix structural issues like CTC redesign or register formats.

This is exactly why a fresh, structured audit — not a one-off compliance memo — is the right posture in the current phase. You are not auditing to find out "are the labour codes in effect." You are auditing to find out: if an inspector, auditor, or new-age labour authority reviewed our documents and pay practices today, would they find consistent, defensible compliance evidence?

Who typically drives this audit

In most Indian SMBs and mid-market companies, the audit is jointly owned by:

• HR / People Operations — appointment letters, policies, leave and attendance records, onboarding documentation.
• Payroll / Finance — CTC structuring, wage definition compliance, statutory deductions, payslip formats.
• Compliance / Legal (in-house or outsourced) — registers, returns, licences, coordination with external labour law consultants.
• EHS or Admin teams (for establishments with factories, larger offices, or manufacturing units) — safety committees, welfare facilities, occupational health obligations.

If your organisation does not have a dedicated compliance function, a cross-functional working group with clearly assigned owners for each checklist area works just as well — what matters is that no single area is left "assumed to be someone else's job."

The New Wage Definition: What to Re-Check in CTC and Payroll Structures

The single most consequential change introduced by the labour codes, from a payroll perspective, is the more standardised and broadened definition of "wages" used across the codes. In general conceptual terms (again, confirm exact thresholds and treatment with your compliance advisor), the intent behind the new definition is to:

• Bring more pay components under the umbrella of "wages" by default.
• Cap the portion of remuneration that can be classified as allowances/exclusions outside "wages," so that a meaningfully large share of total compensation — commonly discussed in the market using a "around half of total remuneration" style benchmark — must be treated as basic wages for statutory calculation purposes.
• Reduce the ability of employers to structure CTC in a way that artificially minimises the "wages" base used for calculating provident fund, gratuity, and other statutory dues.

If your payroll team restructured CTC once when this topic first became prominent, that is a good start — but it is worth re-verifying, because many early adjustments were done hastily, based on incomplete rules, or applied only to new joiners rather than the full workforce.

What to actually check during the audit

1. Component-by-component classification. Pull your current CTC breakup templates (for every distinct band or role category — many companies have multiple templates for sales, factory workers, management, contract staff, etc.) and list every pay component: basic, HRA, conveyance, special allowance, LTA, performance pay, retention bonus, and so on. For each component, confirm with your compliance advisor whether it should be included in or excluded from the "wages" calculation under current applicable rules.

1. The basic-pay proportion check. Verify, for each template, what proportion of total fixed pay is classified as "wages" versus excluded allowances. If your structures still route a large share of compensation through allowances specifically to keep the wage-linked base low, this is a structural gap that needs remediation — not a documentation issue but an actual redesign of the CTC template.

1. Consistency across employee categories. It is common to find that management or leadership compensation structures were left untouched during an earlier "quick fix" round because the changes were piloted only on entry-level or unionised roles. Audit every category — including contract workers, fixed-term employees, and any category paid through a different payroll vendor or subsidiary entity.

1. Downstream calculation impact. Once you know which components count as "wages," check whether your provident fund contribution base, gratuity calculation base, and any other statutory-linked calculation (such as overtime rate calculations, where applicable) have actually been recalculated using the updated wage base — or whether the wage definition was updated in the offer letter/policy document but the payroll engine is still calculating deductions on the old, narrower base. This mismatch between "policy says X" and "payroll system does Y" is one of the most common audit findings.

1. Retrospective exposure. If your organisation made changes only prospectively (for new joiners or from a certain date forward), confirm with legal counsel whether there is any residual exposure for the period before the change, and document the rationale for the effective date you chose.

1. Payslip and CTC letter language. Check that payslips and CTC breakup letters use terminology consistent with the current definition, and that employees are not being shown a wage structure that contradicts what payroll is actually calculating.

1. Full and final settlement calculations. Gratuity, leave encashment, and any severance calculations in your F&F process should be checked against the updated wage base — this is an area where legacy formulas in HRMS or payroll software configurations are easy to overlook because they were "set once and never revisited."

A note on gratuity and provident fund thresholds

Because gratuity, provident fund, and similar calculations are directly tied to the wage definition, even a modest change in what counts as "wages" can materially change your statutory cost base. This is not something to quietly absorb — model the cost impact, communicate it to finance leadership, and build it into budgeting cycles rather than discovering it during a year-end audit.

Appointment Letters and Contract Language: What Needs Updating

Appointment letters have moved from "good HR practice" to a near-universal expectation across the codes, particularly under the Industrial Relations and Occupational Safety, Health and Working Conditions frameworks in concept. If your organisation has any employees — including fixed-term employees, and in many cases contract labour engaged through a principal employer-contractor arrangement — without a formal, signed appointment letter, that is a foundational gap that should be at the top of your remediation list.

What to check for every category of worker

• Existence of a written appointment letter. Not an offer letter that was accepted informally, not a verbal confirmation, but a signed appointment letter retained on file (physical or digital, with an auditable trail).
• Fixed-term employment language. If you engage fixed-term employees, confirm that their contracts clearly state the fixed-term nature, the parity principle around wages and benefits relative to comparable permanent employees for the duration of the term, and the conditions for renewal or non-renewal.
• Wage and CTC disclosure consistency. The appointment letter's compensation section should match what payroll is actually processing — including the wage-definition-compliant basic pay proportion discussed above. A mismatch here is one of the easiest things for an inspector or auditor to spot.
• Working hours, weekly rest, and leave entitlement clauses. These should reflect your current state rules (as confirmed with counsel) rather than a generic template inherited from years ago.
• Termination and notice period clauses. Review these against current applicable provisions for retrenchment, layoff, and termination procedures relevant to your establishment size and industry classification — this varies meaningfully depending on employee headcount thresholds, so do not assume your existing template is still calibrated correctly if your headcount has changed.
• Standing orders alignment. If your establishment is required to have certified standing orders, check that your appointment letters and HR policies do not contradict the standing orders on record — inconsistency between the two is a classic audit red flag.
• Contract labour documentation. For contract workers engaged via a labour contractor, confirm that the principal employer-contractor agreement, the contractor's licence status, and the individual worker appointment documentation are all current and mutually consistent.

Practical audit steps for contracts

1. Build a master list of every distinct employment category in your organisation (permanent, fixed-term, contract/outsourced, apprentices, interns, gig or platform-linked roles if applicable).
2. For each category, pull a sample of 5–10 actual signed letters/contracts (not just the template) and compare them against the current template — templates get updated, but historical files sometimes are not reissued.
3. Flag any category where no standard template exists at all, or where the template has not been reviewed since your last major compliance update.
4. Cross-check contract language against your actual HR policy handbook — contradictions between the appointment letter and the policy manual are common when one document gets updated and the other does not.

Working Hours, Overtime, and Leave Record-Keeping: What to Verify

The codes bring changes to how working hours, overtime, and leave are conceptually treated, including discussions around daily working hour limits, spread-over provisions, overtime compensation multiples, and leave encashment/carry-forward rules. Because these vary by state notification, this section focuses on the record-keeping discipline you should verify regardless of the exact numbers your state has settled on.

Attendance and hours tracking

• Confirm that your time and attendance system captures actual clock-in/clock-out data (or shift-based equivalents) for every employee category, not just factory floor or hourly workers. Salaried staff exemptions from overtime rules do not exempt the employer from maintaining accurate attendance records.
• Check that your system correctly flags when an employee crosses into overtime territory based on your current state's daily/weekly hour thresholds, and that this triggers the correct overtime pay calculation — using the updated wage-linked base discussed earlier, not a legacy narrower base.
• Verify that spread-over and rest interval rules (time between shifts, weekly rest day) are actually being observed in scheduling practice, not just documented in policy. Scheduling software or manual rosters should be checked against policy, especially in retail, hospitality, and manufacturing operations with shift work.

Overtime authorisation and payment trail

• Confirm there is a documented authorisation process for overtime (who approves it, how it is recorded) rather than informal, undocumented extra hours that later show up only in payroll without a paper trail.
• Verify overtime payments are reflected correctly on payslips as a separate, identifiable line item, calculated at the correct multiple of the wage rate.
• Check whether any category of workers is being asked to work extended hours without corresponding overtime pay under an informal "it's part of the role" understanding — this is a common but risky practice that becomes much easier for a regulator to identify once wage records are standardised.

Leave records

• Verify that earned/annual leave, sick leave, and casual leave policies reflect current entitlement rules for your state, and that carry-forward and encashment provisions in your HR system match what is documented in policy.
• Check that leave balances in your HRMS are accurate and reconcile with what would be paid out in a full and final settlement — discrepancies here often surface only when an employee exits and disputes their leave encashment.
• Confirm maternity, paternity (where applicable), and other statutory leave categories are correctly configured and that approval workflows do not create informal barriers to availing them.

Registers and records specific to hours and leave

• Muster rolls or equivalent attendance registers, maintained in the format your state rules currently require (digital formats are increasingly accepted, but confirm this with your consultant for your specific state and establishment type).
• Overtime registers, showing hours worked, authorisation, and payment made.
• Leave registers or system-generated equivalents, retained for the statutory retention period applicable in your state.

Social Security Registrations and Gig/Platform Worker Considerations

The Code on Social Security introduced, at a conceptual level, an expanded vision of social security coverage — including provisions aimed at extending some form of coverage to gig workers and platform workers, alongside the more familiar structures around provident fund, employee state insurance, gratuity, and maternity benefits for conventional employees. Implementation of the gig/platform worker provisions has been among the more gradual and state/sector-dependent aspects of the rollout, so this section should be read as a checklist of what to verify is on your radar, not a claim about what is currently mandatory for your organisation.

For conventional employees

• Provident Fund (PF) and Employee State Insurance (ESI) applicability thresholds. Re-verify your establishment's headcount and wage thresholds against current rules — these can change how many employees must be covered, especially combined with the revised wage definition, which can push more employees over wage-linked eligibility lines than before.
• Registration currency. Confirm your PF and ESI registrations reflect your current legal entity structure, especially if you have gone through any mergers, restructuring, or new branch openings since your last registration review.
• Contribution base recalculation. As discussed in the wages section, confirm PF contributions (both employee and employer share) are calculated on the correct, updated wage base.
• Gratuity and maternity benefit compliance. Check eligibility thresholds, calculation bases, and whether your policy documents and actual practice are aligned, including for fixed-term employees who may now have parity entitlements.

For gig and platform workers, if relevant to your business

If your organisation engages gig workers, platform-based workers, or aggregator-model contractors (delivery, logistics, on-demand services, and similar models), this is an area evolving quickly and unevenly by state and by central scheme design. As a general audit posture:

• Maintain clear documentation of the nature of the engagement (independent contractor vs. employee vs. any newly defined intermediate category relevant under current rules) and the basis for that classification.
• Track any state-specific or central welfare cess, registration, or contribution obligations that may apply to aggregators or platforms in your sector — these have been introduced in some contexts and are still developing in others.
• Keep records of worker onboarding, engagement terms, and payment structures in a way that would support your classification if questioned by a regulator.
• Do not assume "gig worker" categorisation exempts you from all obligations — this is one of the fastest-moving and most jurisdiction-specific areas of the entire labour code framework, and generic assumptions carry real risk. This is squarely an area to consult a specialist lawyer familiar with your specific sector and state before finalising your position.

Documentation to pull for this section of the audit

• Current PF and ESI registration certificates and challans for the last few filing cycles.
• Contribution calculation worksheets showing the wage base used.
• Any gig/platform worker engagement agreements and classification rationale documents.
• Maternity benefit and gratuity policy documents alongside actual disbursement records for recent cases.

Occupational Safety, Health, and Working Conditions: Obligations for Eligible Establishments

Not every employer will fall within the full scope of the Occupational Safety, Health and Working Conditions Code's more detailed obligations — many of these are scaled by establishment type (factory, manufacturing, construction, mine, etc.) and by headcount thresholds that vary by state notification. However, every organisation should audit whether it has correctly assessed its own applicability, because misjudging this is itself a compliance gap.

Step one: confirm applicability correctly

• Determine whether your establishment is classified in a way that triggers factory-level or establishment-level safety obligations (this depends on the nature of your operations, headcount, and use of power in manufacturing processes, among other state-specific criteria).
• Re-check this classification if your headcount, floor area, or nature of operations has changed since you last assessed it — many companies assessed this once at a smaller size and never revisited it as they scaled.

For establishments where safety obligations apply

• Safety committees. If your establishment crosses the relevant threshold, verify that a safety committee exists, has a documented charter, meets on a regular recorded cadence, includes appropriate worker representation, and that meeting minutes are retained.
• Welfare facilities. Audit physical facilities — washrooms, drinking water, first aid, canteen/rest areas where applicable, crèche facilities where headcount and gender composition trigger the requirement — against current requirements, not just what was adequate when the office/factory was first set up.
• Health and working condition provisions. Check ventilation, lighting, and general working condition standards where applicable to your establishment type, along with any required health check-up obligations for certain categories of work.
• Working at height, hazardous processes, or machinery-specific safety protocols, if relevant to your operations, including documented risk assessments and training records.
• Appointment of safety officers, where headcount or industry classification requires it, and verification that the appointed individual has appropriate qualifications and is not a purely nominal designation.
• Display of statutory notices and abstracts in the workplace, in the language(s) required, in locations accessible to workers.
• Registers related to safety incidents, accidents, and near-misses, maintained consistently rather than only after an incident prompts a retrospective effort.

For office-based or lower-risk establishments

Even organisations that do not meet factory-level thresholds should confirm basic occupational health and working condition obligations relevant to general establishments — reasonable working conditions, first aid provisions, and any state-specific shops and establishments-linked safety requirements that may still apply. Do not assume a corporate office is entirely outside the scope of every safety-related obligation simply because it is not a factory.

Statutory Registers and Returns: The Documentation Backbone

Across all four codes, the practical evidence of compliance ultimately comes down to registers, returns, and records. This is the area where an audit adds the most immediate value, because gaps here are usually fixable quickly once identified.

Registers commonly expected across establishments (verify exact list and format with your consultant for your state)

• Employee/worker register with complete personal and employment details.
• Wage register reflecting the current wage definition and calculation basis.
• Attendance/muster roll.
• Overtime register.
• Leave register.
• Register of fines and deductions, if applicable.
• Accident/incident register, for establishments where safety obligations apply.
• Register of contract labour, if applicable.

Returns and filings

• Periodic returns to labour departments, PF and ESI authorities, and any state-specific filings, checked for both timeliness and accuracy of the underlying data (a return filed on time but based on an outdated wage calculation is still a compliance gap).
• Annual returns where applicable to your establishment classification.
• Licence renewals for contract labour, factories, or shops and establishments registrations, checked against current validity dates.

What "audit-ready" registers look like

• Consistently formatted, dated, and either digitally timestamped or physically signed as appropriate.
• Retained for the statutory retention period applicable in your state — do not assume a uniform retention period across all record types.
• Reconcilable against each other — your wage register, attendance register, and payroll output should all tell the same story for any given employee in any given month. Inconsistency between these documents is often what turns a routine inspection into an extended one.

The Audit Checklist Table

Use a structured table like the one below as your working audit tracker. Expand it with actual owner names, target dates, and evidence links in your internal version — this is a starting template.

Step-by-Step Internal Audit Process

A structured process prevents the audit from becoming an unstructured document-collection exercise that fizzles out. Here is a practical sequence.

1. Form the audit working group. Include HR, payroll/finance, legal/compliance, and (if applicable) EHS representation. Assign a single owner to coordinate the overall timeline even if different people own different sections.

1. Define the scope by entity and state. If you operate in multiple states or have multiple legal entities, do not run one generic audit — map out every state and entity combination, because rules and notification status differ by state.

1. Pull the baseline document set. For each entity/state combination, gather: CTC templates for every role category, a sample of signed appointment letters per category, current HR policy manual, attendance and leave system exports, PF/ESI registration certificates and recent filings, statutory registers, and (if applicable) safety committee records and facility documentation.

1. Engage your compliance consultant or labour law counsel early, not at the end. Share the current notification status question with them first — you need to know which specific rules are actually in force or expected to come into force for each of your operating states before you can meaningfully assess compliance against them.

1. Run the checklist area by area. Use a structured tracker (like the table above, expanded into a full spreadsheet) and assign a status to each line item: Compliant, Partial, or Gap. Require evidence attached to every "Compliant" rating — a status without supporting documentation is not a finding, it is an assumption.

1. Score the gaps by risk and effort. For each identified gap, estimate two things: the compliance/legal risk if left unaddressed (low/medium/high) and the effort required to fix it (quick fix vs. structural change). This scoring is what turns a long list of findings into an actionable plan.

1. Validate findings with a walkthrough, not just document review. Pick a small sample of employees across categories and trace their full record — appointment letter, attendance, leave, payslip, PF contribution — end to end. This often surfaces inconsistencies that a document-by-document review misses.

1. Present findings to leadership with a remediation plan attached, not just a list of problems. Include cost implications (especially for wage-base changes affecting PF/gratuity cost) so budgeting decisions can be made with full information.

1. Set a re-audit cadence. Given how actively state rules are still evolving, plan for at least an annual full re-audit, with lighter quarterly checks on the highest-risk areas (wage definition, appointment letters for new joiners, registers).

Prioritised Remediation Plan: Quick Fixes vs. Structural Changes

Not every gap needs the same urgency or resourcing. Splitting your remediation plan into two tracks helps you show fast progress while properly resourcing the harder work.

Quick fixes (typically achievable within weeks)

• Updating appointment letter templates to reflect current wage and leave language, then reissuing to new joiners immediately.
• Filling documentation gaps — signing letters for anyone missing one, backfilling missing register entries where legitimately possible, updating policy manual language to match current templates.
• Correcting payslip terminology and formatting to align with updated wage definitions.
• Setting up or refreshing overtime authorisation workflows.
• Re-verifying and updating PF/ESI registration details for entity or address changes.
• Displaying updated statutory notices in the workplace.

Structural changes (typically require a longer runway and cross-functional sign-off)

• Redesigning CTC structures across all employee categories to meet the wage-definition proportion expectations, including modelling the cost impact on PF, gratuity, and overall payroll budget.
• Reconfiguring payroll software/HRMS calculation engines so that statutory deductions are computed automatically on the correct wage base, rather than relying on manual adjustments.
• Establishing or reconstituting safety committees, including training committee members and setting a governance cadence.
• Building out welfare facilities that require capital investment (crèche facilities, expanded welfare amenities) where headcount thresholds require them.
• Formalising a gig/platform worker classification framework, potentially with legal review of every distinct engagement model your business uses.
• Standing orders review and re-certification, if your workforce size or operations have changed materially.

Sequencing advice

Tackle quick fixes immediately — they reduce visible risk with minimal resourcing and build momentum. In parallel, kick off structural changes with realistic timelines, because these often involve budget approval, system configuration changes, or legal drafting that cannot be rushed without introducing new errors. Track both tracks on the same remediation plan so leadership sees a complete picture rather than only the fast wins.

Documenting Compliance Efforts for Inspection-Readiness

Being compliant and being able to demonstrate compliance are related but distinct. An inspector, auditor, or even an internal stakeholder reviewing your practices needs to see evidence, not just outcomes.

Build an audit trail, not just an audit report

• Keep dated versions of every policy and template change, with a clear record of what changed and why (ideally referencing the specific compliance driver, even in general terms like "updated to align with current wage definition guidance").
• Retain sign-off records showing which internal stakeholder approved each change — this demonstrates governance, not just ad hoc adjustment.
• Maintain a running log of your compliance consultant's advice and the state notification status they confirmed at each point in time — this protects you if rules were genuinely ambiguous or evolving when you made a decision.

Prepare a compliance folder structure

Organise documentation so that, if asked, you can produce evidence within hours rather than weeks:

• Entity-and-state-wise folder for registrations, licences, and renewals.
• Policy and template version history.
• Register exports for the current and prior retention-relevant periods.
• Filing acknowledgements for returns.
• Audit tracker with status and evidence links (the table format described earlier, kept live).

Train the people who would face an inspector first

HR and admin staff at branch or site level are often the first point of contact during an inspection or audit visit. Make sure they know where documentation is stored, understand basic terminology, and know who to escalate to — a well-organised compliance file that no one on-site can locate or explain still creates a poor impression.

How HRMS/Payroll Software Helps Maintain Audit Trails

A recurring theme across every section of this checklist is the gap between what policy documents say and what payroll/attendance systems actually calculate or record. This gap is exactly where good HRMS and payroll software earns its keep.

• Centralised, version-controlled templates. Instead of appointment letters and CTC structures living in scattered spreadsheets and Word documents across different managers' laptops, a proper HRMS keeps a single current template per role category, with change history retained automatically.
• Automated wage-base calculations. Rather than manually recalculating PF, gratuity, and overtime bases every time a rule or CTC structure changes, configured payroll software applies the current wage base consistently across the entire employee population, reducing the risk of the "policy says X, payroll does Y" mismatch.
• System-generated registers. Attendance, leave, overtime, and wage registers generated directly from transactional data are inherently more consistent and reconcilable than manually maintained spreadsheets, and they are far faster to produce on demand during an inspection or audit.
• Retention and access control. Cloud-based HRMS platforms typically retain historical records automatically for the periods you configure, with access logs showing who viewed or modified records — itself a useful piece of governance evidence.
• Alerts for threshold changes. Good payroll systems can flag when an employee's compensation structure, headcount changes, or contribution base crosses a threshold that might change statutory applicability, prompting a review rather than letting the change go unnoticed.
• Audit-ready exports. Instead of manually assembling documentation before every audit or inspection, a well-configured HRMS lets you export a complete, reconciled evidence package — appointment letter, attendance history, leave ledger, and payslips — for any employee, at any point, in minutes.

This is precisely the kind of operational backbone platforms like CozyHR are built to provide: a system where your compliance decisions (once confirmed with your legal advisor) get implemented consistently, tracked with a clear history, and are always ready to produce as evidence — rather than compliance living only in policy documents that may or may not match daily practice.

FAQ

Q1: Do the labour codes apply to my business right now? This depends entirely on your state(s) of operation and the current notification status of central and state rules, which has been evolving over an extended period and varies by state. Do not assume applicability (or non-applicability) based on general news coverage — confirm the current status specifically for each state you operate in with a compliance professional before making structural changes.

Q2: We already updated our CTC structure once — do we need to redo it? Possibly. Many early adjustments were made based on incomplete or draft rules, applied inconsistently across employee categories, or implemented only prospectively for new joiners. A fresh audit of your current CTC templates against the current wage definition guidance for your state is worth doing even if you have already made changes once.

Q3: What is the "50% of CTC as basic wages" idea, and is it a fixed legal number? The general concept discussed around the new wage definition is that a significant portion — commonly referenced using an "around half" style benchmark in market discussion — of total remuneration should be classified as wages for statutory calculation purposes, rather than exclusions and allowances. The exact treatment, thresholds, and how it applies to your specific compensation components should be confirmed with your compliance advisor rather than relied upon as a fixed universal number from this article.

Q4: Do we need appointment letters for contract and gig workers too? Written documentation is expected across a much wider range of engagement types than before, including fixed-term employees and, in many cases, contract labour. The specific requirements for gig and platform worker documentation are still developing and vary by sector and state — this is a good area to get specific legal advice on for your business model.

Q5: How often should we run this compliance audit? Given how actively rules are still being notified and refined across states, an annual full audit with quarterly checks on high-risk areas (wage definition, new joiner appointment letters, registers) is a reasonable cadence for most organisations. Increase frequency if you are actively expanding into new states or scaling headcount past key thresholds.

Q6: Our safety committee requirement doesn't seem to apply to us — do we still need to do anything on occupational safety? Even establishments below factory-level thresholds typically have some baseline occupational health and working condition obligations under general shops and establishments-type rules. Confirm your correct classification and applicable baseline obligations with your consultant rather than assuming complete exemption.

Q7: What is the biggest mistake companies make in this kind of audit? Auditing policy documents in isolation instead of tracing actual practice end to end. A policy manual can say all the right things while payroll, attendance, and registers tell a different story. Always validate with a sample walkthrough of real employee records, not just a review of templates.

Q8: Can HR software alone make us compliant? No — software cannot make legal determinations about which rules apply to you or how to classify your workforce. What good HRMS/payroll software does is implement your confirmed compliance decisions consistently, maintain accurate records, and make those records easy to produce as evidence. The legal determinations still need to come from qualified counsel or a compliance consultant familiar with your current state-wise rules.

Conclusion

A genuine labour codes compliance checklist is not a one-time project you complete and file away — it is an ongoing discipline of verifying that your wage structures, contracts, working-hour records, social security registrations, safety obligations, and statutory registers reflect current rules and actual practice, not just good intentions from a year or two ago. Given how unevenly state-wise implementation has progressed, the single most important habit to build is regularly confirming current notification status with a qualified labour law professional before making structural changes, rather than relying on any general guide, including this one, as a final word.

If you are looking for a way to turn these audit findings into consistent, everyday practice — accurate wage-base calculations, centralised and version-controlled appointment letters, system-generated registers, and audit-ready records you can produce in minutes rather than weeks — CozyHR's HR and payroll platform is built to support exactly that kind of ongoing compliance discipline for Indian businesses. Explore how CozyHR can help your team keep payroll, contracts, and statutory records consistently audit-ready, so your next compliance review is a formality rather than a scramble.