Labour Inspection Readiness: An Employer's 2026 Checklist

Labour inspection readiness is no longer a once-a-year worry that HR teams can push to the bottom of the pile. With India's four labour codes and their central rules now in force, the compliance surface has widened, the penalty bands have moved sharply upward, and the inspection model itself has changed character — from a purely punitive visit to an "inspector-cum-facilitator" model that still carries real financial consequences when records do not stack up. This guide walks HR managers, founders and payroll teams through what a modern labour inspection looks like, what documents you need on hand, how to run an internal mock inspection, and how to build a defensible compliance file that survives scrutiny.

The short version: inspections reward preparation, not eloquence. An organised employer with clean registers, reconciled challans and signed policy acknowledgements will have a very different conversation than one scrambling to reconstruct attendance data from a spreadsheet nobody owns.

A note on verification: rules, rates, thresholds and state-level notifications change frequently, and several provisions are being phased in through state rules. Treat the guidance here as a structural framework, and always confirm current requirements with the relevant central or state government notification, or with your labour law advisor, before acting.

What has actually changed about labour inspections

For decades, Indian labour enforcement ran on a large number of separate statutes, each with its own inspector, its own registers, its own returns, and its own penalty schedule. An employer could be visited by officials under the factories legislation, the shops and establishments law of the relevant state, the contract labour statute, the payment of wages framework, and more — each demanding a slightly different format of essentially the same information.

The labour codes consolidate that landscape. The practical consequences for inspection readiness are these:

Consolidated registers and returns. Instead of maintaining parallel registers in different formats, employers are expected to maintain a smaller set of combined registers covering employee particulars, wages, attendance, leave, and deductions. This is genuinely simpler — but only if you actually migrate. Employers still running legacy formats often find that their old registers omit fields the combined format requires.

A facilitation-first inspection philosophy. The codes describe the enforcement officer as an inspector-cum-facilitator, with a mandate that includes advising employers on compliance, not just catching them out. In practice this means first-time or technical lapses may attract an improvement notice and a window to correct, particularly where the employer demonstrates good faith. It does not mean lapses are free.

Web-based and randomised inspection schemes. The codes contemplate inspection schemes that allocate inspections electronically, use randomised selection, and call for electronic submission of documents. The upshot for HR: your records need to be producible in digital form, quickly, without a week of internal archaeology.

Materially higher penalties. This is the single biggest change in risk profile. Where older statutes often capped fines in the hundreds or low thousands of rupees, the codes introduce far higher floors and ceilings, with escalated consequences for repeat offences within a defined window. Non-payment or underpayment of wages, failure to maintain records, and failure to remit statutory contributions now carry consequences that a growing SMB can actually feel on its P&L.

Compounding of offences. Many offences can be compounded — settled by payment of a sum — rather than prosecuted, particularly where they are not repeat offences. This is useful, but compounding still requires you to know what went wrong and to be able to quantify the exposure.

The strategic takeaway is that inspection readiness has shifted from "keep a file in the cupboard" to "run a continuously reconciled system of record." That is precisely what an HRMS is for, and it is why so many employers moved payroll and attendance off spreadsheets in the last two years.

Who can inspect you, and under what heads

Even with consolidation, several distinct compliance heads can bring an official to your door. Understanding which head a question comes from tells you which file to open.

An inspection nominally triggered under one head very often expands. An officer asking about overtime rates will look at attendance data; attendance data that does not reconcile with the wage register invites questions about wages; wage questions lead to PF wage-base questions. This cascade is why fragmented systems are the real risk, more than any single missing document.

The core document set: what to have ready at all times

Build a single, permanently maintained "inspection pack." The goal is that any competent member of the HR team can produce it within an hour, without needing the payroll lead who happens to be on leave.

Establishment-level documents

• Certificate of incorporation, PAN and GST registration
• Shops and establishments registration or factory licence for each location, with current validity
• Registration codes for provident fund and state insurance
• Professional tax registration for each applicable state, and labour welfare fund registration where applicable
• Contract labour principal employer registration, where you engage contract workers above the threshold
• Trade licence and fire safety approvals for premises, where applicable
• Notice board content: statutory abstracts, working hours, weekly off, wage period, name of inspector where prescribed

Keep a one-page "registration index" listing every registration number, issuing authority, validity date and the internal owner. This single sheet resolves half of the opening questions in most inspections.

Employee-level records

• Employee master with date of joining, designation, category, department, work location, and statutory identifiers
• Appointment letters issued to every employee — the codes explicitly emphasise issuing appointment letters, and their absence is a soft target during inspection
• Signed policy acknowledgements (code of conduct, POSH, IT and data policy, leave policy)
• Identity and address proofs collected in line with your data privacy policy
• Records for employees who have exited, retained for the prescribed period

Wage and payroll records

• Wage register in the prescribed combined format for each wage period
• Payslips issued to every employee for every wage period, with the mandated components visible
• Bank transfer statements or UTR-level proof reconciling to the wage register total
• Deduction register with the basis for each deduction and evidence of employee authorisation where required
• Overtime register with hours, applicable rate and payment reference
• Bonus and gratuity computations and payment proofs
• Full and final settlement computations for exits in the review period

Statutory contribution records

• Monthly PF electronic challan-cum-return filings and paid challans, month by month, with no gaps
• State insurance contribution returns and challans
• TDS challans and quarterly returns, with Form 16 issuance evidence
• Professional tax and labour welfare fund challans and returns by state
• Reconciliation notes where the wage register total does not equal the contribution wage base, explaining exactly why

That last item is underrated. Almost every reconciliation gap has a legitimate explanation — new joiners mid-month, employees above the wage ceiling, excluded components. Writing the explanation down before you are asked converts a suspicious variance into a documented control.

Time, attendance and leave records

• Attendance register or system extract for each location and each month
• Shift rosters, including any changed rosters and the notice given
• Weekly off records demonstrating compliance with the mandated rest day
• Leave register showing opening balance, accrual, availed, encashed and closing balance per employee
• Records of any spread-over or extended hours and the corresponding compensation

Workplace and welfare records

• Safety policy and, where required, safety committee constitution and meeting minutes
• Accident and dangerous occurrence register, with reporting evidence
• Internal Committee constitution under the POSH framework, policy, awareness training records and annual report filing
• Canteen, crèche, first aid and drinking water arrangements where thresholds are met
• Grievance redressal mechanism documentation and case log

Contractor and vendor records

• Contractor agreement with clear scope, rate and compliance obligations
• Contractor licence, PF and ESI registration copies
• Monthly contractor compliance pack: wage sheets, attendance, PF and ESI challans naming the workers deployed at your site
• Your own verification note confirming you checked the contractor's remittances

Principal employer liability is where many otherwise-compliant employers get caught. If a contractor fails to remit contributions for workers deployed at your premises, the exposure can travel to you. A monthly contractor compliance checklist, signed off by a named person, is the cheapest insurance available.

Building an inspection-ready compliance calendar

Readiness is a by-product of rhythm. If your monthly and quarterly rhythm is sound, an inspection is a data extraction exercise rather than a crisis.

Monthly rhythm

1. Payroll cut-off and attendance freeze. Lock attendance by a fixed date. Late regularisations go to the next cycle, with a documented exception process.
2. Payroll processing and variance review. Compare this month's gross, headcount and statutory totals against last month. Investigate anything moving more than a set threshold.
3. Statutory remittances. Remit PF, ESI, TDS, professional tax and labour welfare fund by their due dates. Save challans to a dated folder immediately, not at quarter end.
4. Register updates. Update wage, attendance, leave, overtime and deduction registers in the combined format.
5. Contractor compliance collection. Collect and verify contractor challans and wage sheets before releasing the next invoice payment. Tie the two together contractually.
6. Exception log. Record anything unusual — a delayed payment, a missed deduction, a correction — with the cause and the fix.

Quarterly rhythm

• TDS return filing and reconciliation with payroll TDS totals
• Registration validity review: which licences expire in the next two quarters
• Policy review: any policy that references a statutory number should be re-checked against current notifications
• Internal Committee meeting and case review
• Safety committee meeting where applicable
• Sample audit: pick ten employees at random and trace them end to end (offer letter to payslip to challan)

Annual rhythm

• Annual returns under applicable codes and state rules
• POSH annual report submission
• Bonus computation and payment within the prescribed window
• Gratuity provisioning review and actuarial input where relevant
• Full compliance self-audit (covered below)
• Renewal of licences and registrations
• Record retention review: archive what must be kept, dispose of what may be disposed of under your data retention policy

How to run an internal mock inspection

A mock inspection is the highest-return compliance activity available to a small HR team. Run one twice a year. Give it four hours and a named owner who is not the person who maintains the records.

Step 1 — Set the scope. Pick one location and one three-month window. Announce the scope internally but not the sample.

Step 2 — Issue a document request. Ask for the same list an officer would: registrations, employee master, wage registers, attendance, leave, challans, contractor pack. Set a two-hour deadline. Note what could not be produced in time — that gap is your finding, regardless of whether the document exists somewhere.

Step 3 — Run the reconciliations. Four reconciliations catch most issues:

• Headcount in employee master versus headcount in wage register versus headcount in PF filing
• Gross wages in the wage register versus total bank debit for salary
• PF wage base versus wage register components, with excluded components listed
• Attendance days versus paid days versus leave register movement

Step 4 — Trace ten employees end to end. Deliberately include one recent joiner, one exit, one employee near the ESI wage threshold, one contract worker and one employee who worked overtime. Follow each from appointment letter through attendance, payslip, deductions, remittance and, for the exit, full and final settlement.

Step 5 — Walk the floor. Check notice board content, first aid, drinking water, emergency exits, and whether the statutory abstracts posted are current.

Step 6 — Interview two employees. Ask simple questions an officer might ask: Do you receive a payslip? Do you know your leave balance? Do you know whom to approach with a grievance? Answers reveal whether your policies exist in practice or only on paper.

Step 7 — Write findings with owners and dates. A finding without an owner and a due date is a note, not a control. Track closure in your next monthly review.

A simple mock inspection scorecard

The ten findings that come up most often

From the pattern of questions employers report, a predictable set of issues recurs. None of them is exotic. All of them are avoidable.

1. Missing or generic appointment letters. Employees hired informally in the early days often never received one. Fix by issuing letters to all current employees with a clear effective-date note, and by making letter issuance a blocking step in onboarding.

2. Attendance data that cannot be reconstructed. Biometric logs get overwritten; spreadsheets get overwritten more. Retain raw logs, not just monthly summaries.

3. Wage register in the wrong format. Legacy formats often omit fields such as the number of days worked, overtime hours, or the specific head of each deduction.

4. Overtime paid at the wrong rate or not paid at all. Particularly for employees treated internally as "exempt" without any statutory basis for that treatment.

5. Weekly off and hours breaches in operations roles. Rosters that look compliant on paper but are routinely overridden in practice, with the override invisible in the system.

6. PF wage base disputes. Splitting salary into many allowances to reduce the contribution base is a long-standing area of dispute, and the codes' wage definition narrows the room for it materially. Employers who have not restructured CTC to align basic pay with the wage definition should treat this as urgent.

7. Employees near the ESI wage threshold handled inconsistently. Mid-year crossings have specific treatment rules; ad hoc handling creates gaps.

8. Contractor compliance accepted on trust. Invoices paid without collecting challans naming deployed workers.

9. POSH committee constituted but dormant. No external member, no training records, no annual report.

10. Full and final settlements delayed beyond the prescribed timeline. Exit settlements are a favourite inspection sample because they compress every compliance question into one calculation.

What to do when an inspection actually happens

Before the officer arrives

If you receive advance notice, use it. Pull the inspection pack, confirm the reconciliations still hold, and brief the team. Designate a single point of contact — usually the HR lead — plus one backup. Nobody else should hand over documents or make statements about compliance positions.

During the visit

• Verify identity and authority. Politely record the officer's name, designation, office and the head under which the inspection is being conducted. Note the date and time of arrival.
• Keep a running log. Record every document requested and provided, with the number of pages. This protects both sides.
• Provide what is asked, no more. Answer the question asked. Do not volunteer adjacent files or speculate about other locations.
• Say "I will confirm" when you do not know. An inaccurate confident answer is far more damaging than a request for time. Commit to a specific follow-up date.
• Do not backdate anything. Ever. A missing record is a technical lapse with a defined penalty band. A fabricated record is a different category of problem entirely.
• Be cooperative and factual. The facilitation model genuinely rewards employers who engage constructively and can show a system, even an imperfect one.

After the visit

• Obtain a copy of any inspection note, observation memo or improvement notice.
• Convert every observation into a tracked action with an owner and a date.
• Respond in writing within the stated window, attaching evidence of correction where you have already fixed the issue.
• If a penalty or compounding proposal follows, take legal advice before responding, and quantify the exposure precisely from your own records.
• Run a root-cause review internally. If a record was missing, ask why the process allowed it to be missing, not merely who forgot.

Building the systems that make readiness automatic

Manual readiness decays. Every month someone leaves, a rate changes, or a location opens. Sustainable readiness comes from a small number of system properties:

A single employee master. One source for joining date, category, location, wage structure and statutory identifiers. Every downstream register derives from it. When HR, payroll and finance each keep a list, they diverge within a quarter.

Attendance captured at source and locked. Biometric, geofenced mobile punch, or supervisor-marked — the mechanism matters less than the fact that it is captured daily, retained in raw form, and frozen at cut-off with an auditable regularisation trail.

Payroll that generates statutory outputs directly. If the PF wage base is computed in a separate spreadsheet from the payroll run, the two will disagree eventually. Statutory computation belongs inside the payroll engine, driven by the same component configuration.

Registers generated, not typed. The combined registers should be a report, not a document someone maintains by hand. This is the single largest saving in inspection preparation time.

Document vault with retention rules. Appointment letters, policy acknowledgements, challans and settlement statements stored against the employee record, retrievable by employee or by month.

A compliance calendar with alerts. Due dates for remittances, returns, licence renewals and committee meetings, with escalation when a task slips.

Role-based access and an audit trail. Who changed a salary, when, and with whose approval. This is both a control and, increasingly, a data protection requirement.

This is the practical argument for consolidating HR, attendance and payroll into one system rather than three. It is not about features; it is about the fact that reconciliation failures live in the gaps between systems.

A 30-day readiness sprint

If you are starting from a weak base, do not attempt everything. Run a focused month.

Week 1 — Inventory. Build the registration index. List every location, every registration, every validity date and every owner. Identify what is missing or expired.

Week 2 — Records. Confirm appointment letters exist for all current employees. Generate wage, attendance and leave registers in the combined format for the last three months. Note format gaps.

Week 3 — Reconciliation. Run the four reconciliations. Document every variance with an explanation. Fix what can be fixed immediately; log the rest with a plan.

Week 4 — Mock inspection and closure plan. Run the mock inspection using the scorecard above. Produce a prioritised remediation plan with owners and dates, and put the recurring calendar items into your system.

At the end of the sprint you will not be perfect. You will, however, know exactly where you stand — which is the difference between managed risk and unknown risk.

Special situations worth planning for

Multiple states, one payroll team. Professional tax, labour welfare fund, shops and establishments rules, and public holiday lists all vary by state. Maintain a state matrix and review it annually. Assume nothing transfers across state lines.

Rapid headcount growth. Thresholds matter. Crossing a headcount threshold can trigger new obligations — committees, facilities, registrations, returns. Add a threshold check to your monthly headcount review so you discover the crossing before an officer does.

Remote and distributed employees. An employee working from a state where you have no registration can raise questions about which establishment they belong to and which state levies apply. Document your position and take advice; do not leave it undefined.

Acquisitions and entity restructuring. Transferred employees bring continuity-of-service questions that affect gratuity, leave balances and PF transfers. Reconcile these at the point of transfer, not years later at exit.

Seasonal and contract-heavy operations. The compliance load sits disproportionately with contractors. Build the contractor pack into your procurement process so compliance evidence is a condition of payment.

Quantifying your exposure before someone else does

Boards and founders respond to numbers, not to compliance adjectives. Translating your findings into a rough exposure estimate is what unlocks budget for remediation.

Build a simple risk register with five columns: the lapse, the affected population, the period, the estimated financial consequence, and the confidence level. For a wage-related lapse, the financial consequence usually has two parts — the arrears actually owed to employees, plus the statutory consequence of the lapse itself. For a record-keeping lapse, it is the statutory consequence alone. For a contribution lapse, it is the shortfall, plus interest and damages for the delay period, plus the statutory consequence.

Worked illustration, using placeholder numbers you should replace with your own:

Two disciplines make this register useful. First, size the population precisely rather than guessing — "22 operations staff" is actionable, "some people in ops" is not. Second, separate what you owe employees from what you may owe the state. The first is almost always the larger number, and it is also the one you should fix immediately regardless of inspection risk, because it is simply money owed to people who earned it.

Where the exposure is significant or the legal position is genuinely arguable, get an opinion before you self-correct. Voluntary correction is usually viewed favourably, but the sequencing, the disclosure and the treatment of prior periods benefit from advice.

Who owns what: a simple RACI for compliance

Diffuse ownership is the root cause of most inspection findings. Everyone assumed someone else had it. A one-page ownership map fixes more problems than a policy document.

Three rules make a RACI stick. Name individuals, not departments. Review it whenever someone in it leaves. And make each accountable person sign off a short monthly attestation — a single line confirming the month's activities were completed — because an attestation trail is itself strong evidence of a functioning compliance system.

Communicating with employees during and after an inspection

An inspection is visible. People notice officials on the floor, and rumour fills silence quickly. A short, calm internal note prevents speculation: confirm that a routine statutory inspection is taking place, that the company is cooperating, that employees may be asked routine questions and should answer honestly, and whom to contact with concerns.

Never coach employees on what to say. Beyond being wrong, it is transparent, and it converts a records question into a credibility question. If an employee gives an answer that reveals a genuine gap — they do not receive payslips, say, or do not know their leave balance — treat that as the most valuable finding of the day. It tells you a control exists on paper but not in the employee's experience, which is exactly the gap inspections are designed to surface.

Afterwards, close the loop briefly. Employees who see that a compliance question led to a visible fix are considerably more likely to raise the next one internally rather than externally.

Frequently asked questions

Do I get advance notice of a labour inspection? Sometimes, but not always. Some inspections are scheduled and communicated; others follow a complaint or a randomised allocation and arrive without notice. Because you cannot rely on notice, the working assumption should be that your records must be producible on any given working day.

Can an inspector demand documents in physical form only? The codes contemplate electronic inspection schemes and electronic submission of records, and digitally maintained registers are generally acceptable where the rules permit. That said, practice varies by state and by head of compliance, so keep the ability to print a clean, signed copy of any register on short notice, and confirm the current position for your state.

What happens if a record is genuinely missing? Say so, in writing, and explain the cause and the remediation. Missing records typically fall into a defined penalty or compounding band. Attempting to recreate a record after the fact converts a manageable technical lapse into a much more serious credibility problem.

Are the penalties really that much higher under the codes? The penalty structure has been substantially revised upward compared with the older statutes, with higher floors, higher ceilings and escalated treatment for repeat offences within a defined period. The exact figures depend on the offence and the applicable code, so verify the current schedule against the relevant code and rules rather than relying on any summary — including this one.

Does a first-time technical lapse always attract a penalty? Not necessarily. The facilitation model allows for improvement notices and correction windows in appropriate cases, particularly for non-wilful and non-repeat lapses. The determination is discretionary, which is precisely why demonstrable good faith — an existing calendar, an audit trail, prior self-identified corrections — matters so much.

Am I liable for my contractor's non-compliance? Principal employer liability is a real and long-standing feature of Indian labour law, particularly for contract labour deployed at your premises. In practice, if a contractor fails to pay wages or remit contributions, the obligation can devolve to the principal employer. Collect and verify contractor compliance evidence monthly, and link it to invoice release.

How long should I retain HR and payroll records? Retention periods vary by record type and by the applicable rule, and they generally run for several years beyond the employment relationship. Build a written retention schedule by record type, retain digitally where permitted, and align it with your data protection obligations so that you neither destroy too early nor hoard personal data indefinitely.

Should a 20-person company worry about this at all? Yes, though proportionately. Many obligations are threshold-based, so a small company's list is shorter — but wage payment, appointment letters, payslips, statutory remittances where applicable, POSH obligations and basic registers apply widely. The cost of getting these right at twenty employees is trivial; the cost of retrofitting them at two hundred is not.

Can I compound an offence instead of facing prosecution? Many offences are compoundable, typically where they are not repeat offences within the specified period. Compounding involves paying a prescribed sum and is usually preferable to prosecution, but it requires accurate quantification of the underlying lapse. Take professional advice before initiating it.

Conclusion: readiness is a system, not an event

The employers who handle inspections calmly are rarely the ones with the biggest compliance teams. They are the ones whose everyday operating rhythm produces the evidence an officer wants, as a by-product of running payroll properly. Attendance is captured daily and frozen. Payroll generates the registers. Challans are filed to a dated folder the moment they are paid. Contractor evidence is a condition of payment. A named person owns each due date.

That rhythm is entirely achievable for a company of thirty people, and entirely unachievable in spreadsheets at three hundred. The transition point usually arrives sooner than founders expect — often around the time a second location or a second state enters the picture.

If your registers are still assembled by hand each month, start with the mock inspection in this guide. It takes an afternoon and it will tell you, precisely and unsentimentally, where your exposure sits.

CozyHR brings employee records, attendance, leave and payroll into one system, so statutory registers, payslips and contribution reports come out of the same data your team already maintains — and your inspection pack is a download rather than a project. If you would like to see what that looks like for your organisation, take CozyHR for a spin.