This blog explains how the OSHW Code 2026 changes contract labour compliance for enterprises managing external workforce operations. It covers worker rights, workplace safety, welfare facilities, attendance and wage transparency, contractor governance, and principal employer responsibilities. The blog also explains how connected workforce systems help improve audit readiness, compliance visibility, and operational control across sites and vendors.
Introduction
Contract labour rights are becoming a sharper compliance priority for Indian enterprises in 2026.
For many years, contract labour compliance was treated mainly as a contractor responsibility. Enterprises collected contractor documents, checked wage files, reviewed statutory proofs, and prepared records when audits or inspections came up.
That approach is no longer enough.
The Occupational Safety, Health and Working Conditions Code, 2020, commonly referred to as the OSHW Code or OSHWC Code, brings workplace safety, health, welfare, working conditions, contractor records, wage records, and inspection readiness into a more structured compliance framework. The Government of India has also made the four Labour Codes effective from 21 November 2025, rationalising 29 existing labour laws into four codes.
For enterprises managing contract labour across factories, warehouses, logistics hubs, retail networks, infrastructure sites, and facility operations, the impact is clear.
Contract labour rights cannot be managed only through vendor declarations.
They need to be built into daily workforce operations, from onboarding and site deployment to attendance, wage calculation, welfare readiness, safety records, statutory registers, vendor billing, and audit trails.
What Changes Under the OSHW Code 2026
The OSHW Code changes the way enterprises must look at contract labour compliance.
It is not only about whether the contractor has provided documents. It is about whether the enterprise can prove that workers deployed at its sites are properly onboarded, safely deployed, accurately recorded, paid correctly, and covered by required welfare and safety controls.
The Code consolidates and simplifies earlier laws related to occupational safety, health, and working conditions, with the objective of improving transparency, worker welfare, and ease of compliance.
The key shift for enterprises
Under the OSHW Code environment, compliance becomes more operational.
Enterprises must be able to show that:
Worker records are complete and traceable.
Contractors are properly mapped to sites, work orders, and worker categories.
Attendance, wages, overtime, and deductions are recorded correctly.
Safety and medical records are connected to worker deployment.
Welfare facilities are available where applicable.
Incidents and dangerous occurrences are recorded and reported.
Registers and returns are generated from reliable workforce data.
Exceptions are tracked with ownership and closure proof.
This is why contract labour compliance is moving from document maintenance to operating control.
BlueTree’s compliance readiness framework makes this point clearly: external workforce compliance now depends on how accurately workforce data is captured, validated, approved, paid, reconciled, and retained across the complete worker lifecycle.
OSHW compliance is highly operational
For external workforce-heavy enterprises, OSHW compliance cannot sit separately from workforce management.
Worker identity, contractor mapping, deployment location, shift, attendance, working hours, medical fitness, safety training, incident history, and site conditions must be connected.
When these records sit in separate files or systems, the enterprise may only discover gaps during an inspection, audit, safety incident, or worker dispute.
That is the real change under the OSHW Code 2026: compliance proof must come from daily workforce transactions, not last-minute documentation.
What Rights Contract Labour Now Receive
Contract labour rights under the OSHW Code should be understood beyond wage payment alone.
They include workplace safety, welfare facilities, working condition protections, wage transparency, proper records, and access to compliant deployment practices.
Right to safe working conditions
Contract workers have the right to work in a safe and healthy workplace.
For enterprises, this means safety controls should apply not only to permanent employees but also to contract workers deployed on the shop floor, at warehouses, in logistics operations, at retail sites, or in facility locations.
Safety readiness should include worker eligibility, medical checks where applicable, safety training, PPE tracking, incident reporting, and site-level safety governance.
Right to welfare facilities
Contract labour should have access to applicable welfare facilities at the workplace.
This may include workplace facilities such as drinking water, washing areas, rest areas, first aid, canteen access, crèche facilities, sitting arrangements, and other facilities depending on the establishment, workforce size, and applicable rules.
For enterprises, welfare readiness should not be an afterthought. It should be part of site readiness before workers are deployed.
Right to proper working hour and rest controls
Contract labour rights also include proper control over working hours, weekly rest, and overtime.
The OSHW compliance framework places strong emphasis on working hours, rest, overtime limits, and attendance pattern visibility. BlueTree’s internal readiness model highlights that manual tracking of overtime, continuous workdays, and weekly rest creates operational risk, while system-led attendance insights and OT threshold alerts help strengthen control.
This is especially important for manufacturing, logistics, ecommerce, and facility management operations where shift extensions, urgent manpower needs, and manual approvals can create compliance exposure.
Right to transparent wage and attendance records
Contract workers should not exist only in vendor files.
Their attendance, payable days, overtime, deductions, wages, and wage slips should be traceable from approved records.
Under the statutory records framework, OSHWC requirements include worker registers, wage records, attendance, overtime, leave, dangerous occurrences, wage slips, and returns to the inspector-cum-facilitator.
For workers, this improves transparency.
For enterprises, it improves audit defensibility.
Right to safety training and eligibility-based deployment
Contract workers deployed in safety-sensitive or hazardous roles must be managed with stronger readiness checks.
This includes training records, role eligibility, medical fitness where applicable, and safety induction before deployment.
BlueTree’s OSHWC readiness model specifically identifies safety training, hazardous process eligibility, medical records, incident tracking, and equipment inspection as areas where manual processes create compliance risk.
Right to proper incident and accident records
Contract workers should be covered in incident and accident reporting workflows.
If a worker is injured, involved in a dangerous occurrence, or part of a safety incident, the record should be linked to the worker profile, contractor, site, shift, and corrective action.
Without this linkage, incident investigation becomes weak and compliance proof becomes difficult.
Right to digital and traceable worker records
The OSHW Code environment increases the importance of digital and auditable records.
A worker’s profile should ideally include identity, contractor mapping, site, role, joining date, attendance, safety readiness, statutory details, medical checks where applicable, and wage records.
This creates a single view of contract labour rights, not just scattered documentation.
What Principal Employers Must Ensure
Principal employers need to treat contract labour compliance as an ongoing operating responsibility.
The contractor may manage employment and deployment, but the principal employer must have enough visibility and controls to ensure that contract labour rights are protected at the site level.
Validate the contractor before worker deployment
No worker should be deployed under an unvalidated contractor master.
Before deployment, enterprises should confirm:
Contractor legal entity details
Statutory IDs
License or registration applicability
Work order or purchase order mapping
Site and category mapping
Contractor SPOCs and escalation owners
Worker deployment eligibility
BlueTree’s onboarding operating model recommends separate contractor master and worker master controls, with gates for WO or PO validation, statutory readiness, site readiness, dedupe checks, and audit trails.
Complete worker onboarding before site entry
Contract labour should be onboarded before they report to site.
This includes worker identity, address, photo, government ID, bank details, contractor mapping, statutory readiness, and role or site extensions such as medical fitness, police verification, or EHS induction where applicable.
BeeForce supports high-volume onboarding across sites and vendors with Aadhaar OTP checks, face match, bank validation, BGV checks, UAN and ESI creation or validation, centralized profiles, alerts, reminders, and location or contractor dashboards.
Include contract labour in workplace safety governance
Safety governance should include contract workers, not only permanent employees.
Principal employers should track:
Safety induction
Medical fitness where applicable
PPE issuance
Hazardous process eligibility
Incident records
Corrective actions
Safety committee actions
Equipment inspection records
Site-level safety exceptions
When safety records sit outside workforce data, incident proof becomes weak during audits or investigations.
Monitor working hours, weekly rest, and overtime
Working hour and overtime control is a major area of contract labour risk.
Enterprises should not rely only on supervisor memory or vendor submissions.
They need system visibility into:
Shift allocation
Attendance
Consecutive workdays
Weekly rest
Overtime approvals
Overtime thresholds
Fatigue risk
Exceptions and approvals
This is important because overtime errors impact worker safety, wage cost, statutory records, and vendor billing.
Maintain unified worker and wage records
Principal employers should ensure that contract labour data is not fragmented across contractor files, biometric systems, spreadsheets, payroll sheets, and finance records.
A connected record should include:
Worker identity
Contractor mapping
Site and department
Attendance
Shift
Overtime
Leave
Wages
Deductions
Wage slips
Safety records
Incident records
Statutory proof
Vendor billing linkage
The statutory records source identifies OSHWC registers and records such as workers’ register and wage book, wage slips, returns to inspector, accident and incident reports, medical examination register, hazardous process records, equipment inspection records, and safety committee minutes.
Track wage payment and vendor billing alignment
Contract labour rights also depend on accurate wage payment.
Principal employers should ensure that approved attendance, payable days, overtime, wage rates, deductions, statutory components, and vendor bills are aligned before invoice approval.
If vendor billing is approved before wage and statutory proof validation, the enterprise may face disputes, audit issues, or principal employer exposure.
Make exceptions visible before audit
Every exception should have an owner, reason code, SLA, escalation rule, and closure proof.
Common exceptions include:
Missing worker documents
Missing statutory IDs
Pending medical fitness
Pending safety training
Unapproved overtime
Attendance mismatch
Wage mismatch
Expired contractor records
Missing statutory proof
Pending incident closure
This is where system-led compliance creates stronger governance.
How BlueTree Can Help With Contract Labour Compliance
BlueTree helps enterprises manage contract labour compliance through BeeForce, its external workforce management platform built for contract, gig, piece-rate, and blue-collar workforce operations.
BeeForce connects the workflows that usually create contract labour risk: onboarding, attendance, shifts, overtime, wage calculation, vendor billing, PF and ESIC validation, statutory registers, contractor records, and compliance dashboards.
For OSHW Code compliance, this connected model matters because workplace safety and labour rights depend on accurate worker data.
A contract worker cannot be safely governed if the enterprise does not know who the worker is, which contractor deployed them, where they are working, whether they are site-ready, whether safety induction is complete, whether attendance is accurate, and whether wages and statutory records are aligned.
BeeForce helps enterprises strengthen contract labour compliance through:
Contractor and worker onboarding
Digital worker profiles
Identity and eligibility checks
Work order and site mapping
Contractor master validation
Statutory ID capture and validation where applicable
Medical fitness and EHS induction tracking where configured
Attendance, shift, leave, and overtime workflows
Wage and payout-ready summaries
Vendor billing linked to approved workforce data
PF and ESIC visibility
Minimum wage adherence and exception reporting
License and register tracking
Vendor-wise compliance dashboards
Audit trails across approvals and exceptions
BlueTree’s compliance control model is built around capturing data correctly, validating rules early, creating traceable approvals, ensuring accurate payments, reconciling billing, and generating registers from approved data.
What this means for enterprise teams
For CHROs, BeeForce improves visibility over contract labour governance.
For compliance teams, it reduces dependency on contractor declarations and manual document chasing.
For site teams, it improves worker readiness, attendance visibility, and safety traceability.
For finance teams, it strengthens wage and vendor billing validation before payment.
For leadership, it creates better visibility into workforce risk across sites, contractors, and worker categories.
This is the difference between manual compliance and system-led compliance.
Manual compliance records issues after they happen.
System-led compliance helps prevent gaps before they become wage disputes, safety incidents, vendor billing mismatches, or audit findings.
Conclusion
Contract labour rights under the OSHW Code 2026 are not limited to wage payment.
They include safe working conditions, welfare facilities, transparent records, working hour controls, safety readiness, incident traceability, and stronger principal employer oversight.
For enterprises, this means contract labour compliance cannot remain scattered across vendor files, spreadsheets, emails, biometric exports, safety logs, payroll sheets, and manual registers.
It needs a connected operating layer.
The organizations that manage this well will reduce wage disputes, improve worker safety, strengthen contractor accountability, and maintain stronger audit readiness across every location.
BlueTree helps enterprises achieve this through BeeForce by connecting contract labour operations, compliance, payroll, vendor governance, and workplace readiness into one workflow.
Manage External Workforce with BlueTree - Govern contract, gig, and blue collar workers across vendors, sites, and shifts.
Frequenty Asked Questions
What is the OSHW Code 2026?
What rights do contract labour workers have under the code?
What are the responsibilities of the principal employer?
Does the OSHW Code change contract labour compliance?
How does BlueTree help with contract labour management?
6 to 7 minutes
|
CLM
category
What Is External Workforce Management? Definition & Why It Matters
Read More >
7 to 8 minutes
|
CLM
category
Hidden Costs of Unmanaged Contract Labour for Indian Enterprises
Read More >
5 to 6 minutes
|
EWFM
category
Blue Collar vs White Collar: Differences for Indian Workforce
Read More >