Video summary

Industrial Relations Code 2020 – What HR & Employers Must Know | Adv. S.K. Gupta

Main summary

Key takeaways

Business

Business-relevant summary of the Industrial Relations Code (IR Code 2020) discussion (HR & Employer implications)

1) Core “protection” concept: who counts as a worker (vs employee/manager)

  • The discussion emphasizes that designation/salary alone does not determine eligibility for protections under the IR Act.
  • The key test is the “nature of duty”—i.e., the dominant nature of work.
  • Courts/judgments cited indicate that a person can be treated as a workman/worker even with managerial titles if they do not genuinely exercise managerial/disciplinary authority.

Practical implication for HR

For employees with “fancy” titles (e.g., Associate Director, VP, front-office/manager roles), HR should assess:

  • whether the person actually supervises/controls work
  • whether they can direct, discipline, issue charge-sheets, sanction leave, etc.

If authority is mostly nominal and actual work is operational/clerical, they may fall within the worker definition, making broader IR protections applicable.

Framework / test mentioned (implicit playbook)

  • Dominant test: primary nature of duties
  • Supervisory test:
    • minor supervision ≠ change of status
    • major supervision + real authority may shift the person away from “workman”
  • Burden of proof: HR should expect examination by the Labour Court around actual authority and actions taken (e.g., whether charge-sheeting/disciplinary action ever occurred).

2) GRC (Grievance Redressal Committee): mandatory in establishments with 20+ workers

  • If an establishment employs 20 or more workers, a GRC must be formed.
  • Purpose: provide an in-house first step for employee grievances on working conditions and related disputes—before escalation to conciliation/tribunals.

GRC design details (as described)

  • Strength: up to 10 members (no strict minimum; speaker references 4–10).
  • Composition: typically balanced management-side and worker-side members.
  • Chairperson: appointed from within the GRC (exact side can vary based on arrangement described).

Process timeline / SLA

  • Employee grievance filing: within 1 year from the date of incident
  • GRC decision: within 30 days
  • If not resolved within required time: employee can proceed to the conciliation officer, then further forums.

Operational requirement for HR

  • Maintain legal records/registers of grievances:
    • complaint numbers
    • certified copies of orders
  • Speaker stresses that GRC should not be a formality—hearings, documentation, and a proper order are expected.

Implementation playbook implied

Create an SOP covering:

  • grievance submission window (1 year)
  • hearing steps
  • expected decision window (30 days)
  • documentation and communication of orders to employer and employee
  • escalation path if unresolved

3) Dispute-resolution architecture changes (Industrial Tribunals / Labour Courts reorganized)

The discussion suggests the IR Code aims to simplify dispute forums:

  • conciliation continues
  • changes to labour court / national labour tribunal structure
  • court inquiry abolished; “industrial tribunal/labour court” reshuffling described

Double Bench vs Single Bench

  • Certain disputes go to a double bench (categories mentioned include interpretation of standing orders, discharge/termination disputes, illegal strike/lockout, etc.).
  • Others go through a single judge process.

Business takeaway: expected faster judgments / less confusion compared with the earlier system.

4) Fixed-term employment: a category affecting retirement/termination classification

  • The code introduces fixed-term employees.
  • The discussion claims fixed-term termination often won’t be treated as “retirement”, and some terminations tied to non-renewal/contract end are handled differently.

Employer-facing advantage (as stated)

  • Greater certainty that end-of-contract disputes may reduce (as the employee expects contract end in 1–2 years).

5) Trade unions reforms: registration + recognition + negotiating councils

Registration threshold

  • Trade union registration requires:
    • minimum 7 members (option referenced), plus a new rider:
    • membership coverage of at least 10% of workers (or 1 worker, whichever is lower—as described)
  • Goal: prevent very small unions without meaningful representation.

Union recognition

  • Employer must recognize unions under defined conditions.
  • Single-union scenario: if only one union exists, recognition is implied/automatic (speaker states 100% recognition).
  • Multi-union scenario:
    • If one union has 51%, it may become the “single” recognized union.
    • Otherwise, a Negotiating Council is formed from unions meeting representation thresholds (speaker references a >20% concept and composition logic).

Dispute routing

  • Inter-/intra-union disputes and disputes around membership/recognition are routed away from civil courts to specialized benches (speaker claims industrial tribunal double bench decides such disputes).

6) Strike/lockout rules: notice, legality, and expanded “control”

Definition evolution / strike expansion

  • The discussion indicates a change to treat mass casual leave by 50%+ employees as a strike (to reduce misuse).

Notice requirement

  • Strikes/lockouts generally must follow notice rules.
  • If demands aren’t met, strikes may proceed only after notice requirements are fulfilled (speaker highlights notice to employer and government).

Timeline logic described

  • Conciliation is time-boxed (speaker references 45 days).
  • Strike/lockout can generally occur after notice + conciliation window expires (speaker references an approximate 60 days total constraint).

Illegal strike/lockout consequences

  • The discussion claims illegal strike/lockout can enable reciprocal actions:
    • a lockout in consequence of an illegal strike may not require normal notice
    • similarly, strike after an illegal lockout may bypass notice in that scenario

Business takeaway: HR should strengthen controls around legality and track notice/conciliation timing closely.

7) Layoff / retrenchment / closure rules: permission thresholds (300-worker cutoff)

The discussion repeatedly uses a 300 “workers” threshold to distinguish when government permission is required.

Layoff

  • Defined around inability/refusal to provide employment due to operational constraints (e.g., storage/power/raw material breakdown).
  • Compensation: speaker states 50% wages compensation (with riders/conditions in exceptions).
  • Compensation may not apply in certain circumstances (per discussion, including alternative job availability within a radius; strike-related chain effects, etc.).
  • Compensation logic may vary based on size/industry conditions (speaker mentions <50 scenario in some contexts).

Retrenchment & closure

  • <300 workers: employer may proceed without prior government permission, but must follow compensation notice requirements.
  • ≥300 workers: prior permission from the appropriate government is required.

Compensation structure described

  • For <300 scenario:
    • speaker states 1 month notice + pay/wages
    • 15 days compensation per completed year
    • reskilling fund provisions mentioned
  • For ≥300 scenario:
    • permission process applies; speaker claims approvals are rare in practice (based on his experience).

Reskilling fund

  • Speaker describes an obligation tied to closure/retrenchment outcomes:
    • employer pays a fund to government (employee does not directly receive it)
    • reskilling centers mandate and timelines discussed (numeric handling noted as somewhat inconsistent in subtitles: 10 days / 15 days mentioned in different places)

Operational recommendation

Maintain an exit/rights-calculation checklist:

  • classify worker-count bucket (<300 vs ≥300)
  • document notice periods
  • calculate pay/compensation and reskilling obligations
  • prepare permission dossiers for ≥300

8) Standing Orders certification: model standing orders for 300+ worker establishments

  • For establishments with 300+ workers, standing orders must be certified (modeled on government model standing orders).
  • Existing standing orders must be:
    • aligned with Model Standing Orders, or
    • properly modified and re-certified.

Model adoption shortcut

  • Deeming certification may apply if the employer adopts the Central Government model standing order and follows the relevant application/notification steps.

Standing orders content (service conditions)

Includes:

  • appointment, joining/leaving discipline
  • shift/attendance
  • inquiry and punishment procedures, etc.
  • speaker notes government schedules include required matters (mentions “Schedule One” with 11 points).

Timing / compliance

  • Even below 300, HR may consider adopting a model-approach to manage discipline consistently (speaker also notes challenge risk depending on legal opinions).

9) Punishments/fines and “compounding” to reduce litigation risk

  • Speaker states:
    • fines range (minimum ₹20,000, maximum ₹2 lakh, plus references to other act-specific penalties)
    • competent authority may issue show-cause notice before imposing a fine
    • compounding offences may allow closure of cases with partial payment (framed as potentially reducing corruption/litigation)

10) Implementation & transitional issues (rules/circulars not fully notified yet)

  • Speaker notes uncertainty during rollout:
    • some components (especially relating to the Social Security Code) may not be fully notified.
  • Recommendation: comply in the implementation area while waiting for full rule notification elsewhere (example given around PF/ESI rules and circulars).

Key actionable recommendations distilled from the discussion

  • Worker classification audit: For every “managerial” title, verify whether the person has real disciplinary/managerial authority; otherwise treat as worker for IR applicability.
  • GRC readiness (20+ workers):
    • form the committee
    • implement an SOP
    • enforce 1-year filing and 30-day decision timelines
    • keep grievance registers and certified orders
  • Standing Orders compliance (300+ workers):
    • adopt/align with model standing orders
    • ensure schedule-listed matters are included
  • Collective action compliance: create internal controls to ensure strikes/lockouts comply with notice + conciliation timing constraints.
  • Exit planning: maintain two playbooks based on <300 vs ≥300 workers for layoff/retrenchment/closure; prepare permission packages where required.
  • Union strategy: monitor union membership thresholds and recognition/negotiating council rules to enable faster, legally compliant dispute handling.

Presenters / sources mentioned

  • Adv. S.K. Gupta (primary speaker)
  • Case/judgment references mentioned by speaker:
    • Forest is the Airtel Limited vs Raghavendra (Civil Appeal No. 5187; year references seen in subtitles)
    • Shrinivas Gadolia vs Arvind Kumar (dated 25 December, year referenced via subtitle context as 2024)
  • Other entities mentioned:
    • Airtel (example employer; “front manager” reception example)
    • Indian courts / Labour Court / Industrial Tribunal / National Industrial Tribunal
    • GRC / GRC committee (as defined in the discussed code)

Original video