Contract labour governance means knowing who is working at your site, what terms they work under, whether they receive the payments and protections due to them, and who acts when something goes wrong. For manufacturers and exporters preparing for a buyer social audit, collecting a contractor’s documents is only the starting point. The records must agree with the company’s own records and with workers’ experience.
A contractor may submit an attendance register, a wage sheet and a payment receipt. Each document may look complete. But if the factory’s shift records show additional hours, or workers describe deductions that do not appear on their payslips, the file still needs investigation.
The practical question is whether your business can follow a worker’s journey from recruitment and deployment through attendance, payment, safety and grievance resolution, without losing accountability between departments.
What you need to know
- Maintain one current view of contractors, workers, activities and locations.
- Compare records for the same workers and reporting period.
- Check worker-level payment and contribution details where applicable, rather than relying only on aggregate receipts.
- Include contract workers in safety, worker communication and grievance arrangements.
- Assign an internal owner to every exception, with a deadline and escalation route.
- Separate legal requirements, buyer requirements and your own operating controls.
Why contract labour is a company governance issue
The contractor may recruit workers and administer payroll. Your business may control site access, production schedules, work allocation and the conditions in which those workers operate. Those responsibilities meet at the workplace. The ETI Base Code states that labour and social-security obligations should not be avoided through labour-only contracting or subcontracting arrangements. This is a buyer-standard expectation, alongside the applicable legal obligations. [1]
If procurement appoints the contractor, operations approves overtime, HR collects records and finance pays invoices, no single department automatically sees the whole picture. A wage issue can remain unresolved because each team assumes another team has checked it.
Good governance makes these handovers visible. The business needs an accountable manager, clear departmental responsibilities and an agreed method for checking contractor performance.
This is also why a social audit involves more than a document review. Sedex describes SMETA as an on-site assessment covering records, practices, workers and workplace conditions. [2] The checks below are a recommended preparation framework, rather than a fixed checklist used in every audit. The buyer, audit methodology and site circumstances determine the actual scope.
For an overview of the process, read What Happens in a SMETA Audit?.
1. Map every contractor and work location
Start with the workforce actually present, including people on night shifts, temporary assignments and support activities such as security, housekeeping, loading and maintenance.
Create a contractor register that records:
- Contractor identity and company contact.
- Activities, sites and shifts covered.
- Current worker deployment and worker categories.
- Contract period and approved scope.
- Applicable registrations, licences and their review dates.
- Internal contract owner and site supervisor.
- Recruitment intermediaries or subcontractors, where used.
Reconcile this register with site access and departmental deployment records. Ask whether any workers appear on the shop floor but are missing from the contractor list. Check whether a contractor has moved workers between locations without updating the records.
A contractor register becomes useful when someone maintains it. Decide who updates it when a worker joins, leaves, changes shift or moves to another site.
2. Check contracts and applicable requirements
A commercial agreement should explain how workforce information will be supplied and how problems will be handled. A general promise to comply with the law leaves too many operating questions unanswered.
Review whether the agreement addresses worker identification, attendance reporting, wages, overtime, applicable contributions, safety induction, grievance access and corrective actions. Define how the company obtains records, reviews exceptions and responds to missing or unreliable evidence.
Keep a site-specific legal applicability register alongside the contract. Verify the appropriate government, current rules and notifications, establishment type, workforce categories and relevant thresholds. A licence or registration should be checked for validity and scope, wherever applicable.
Current legal context: The Government of India made the four Labour Codes effective from 21 November 2025. [3] A checklist based only on the earlier labour-law framework therefore needs review. Detailed obligations should be checked against the applicable provisions, rules and notifications for the establishment concerned. This article provides a governance workflow, rather than a determination of each site’s legal obligations.
The website’s Four Labour Codes in India guide provides a related reading route. Confirm its latest review date before using it for an applicability decision.
3. Connect worker identity, employment and deployment records
Use a consistent worker reference to connect records across the company and contractor. Name spelling alone is often unreliable, particularly when several people share a name or records use different languages.
Check that the deployed worker can be traced to their employment documentation, start date, work assignment and relevant age-verification records. Verify that the terms communicated to the worker agree with the records provided by the contractor.
The ETI Base Code addresses freely chosen employment and prohibits requiring workers to lodge deposits or identity papers with their employer. [1]
Ask how recruitment takes place. Where relevant, investigate recruitment charges, deposits or restrictions on access to identity documents. Do not accept a policy statement as proof that these practices are absent.
Store identity and bank information securely. Collect what is necessary for the check, restrict access and avoid circulating full personal documents in general audit folders.
4. Reconcile attendance, hours and overtime
The ETI Base Code addresses working hours, voluntary overtime and rest periods, alongside national law and collective agreements. Its requirements should not be treated as a substitute for applicable Indian law. [1]
Compare company attendance and shift records with the contractor’s muster roll and payroll inputs for the same period.
Look for unexplained differences in days worked, overtime, weekly rest and shift changes. Review peak-production periods as well as ordinary weeks. Check who authorises extra hours and whether those hours reach payroll.
Gate records can help identify discrepancies, but time inside the premises is not automatically time worked. Breaks, transport schedules and other circumstances may explain a difference. Investigate the source records before reaching a conclusion.
If workers describe hours that are missing from the records, examine the process. A supervisor’s informal instruction may never have reached the person preparing payroll.
5. Trace wages and applicable contributions to workers
The ETI Base Code calls for understandable written information about wage terms and each pay period, and sets expectations for wages and deductions. [1]
Reconcile the wage calculation with attendance, overtime, deductions and the applicable wage requirements. Then compare the net amount with payment evidence.
Distinguish payment to the contractor from payment to workers. Settling the contractor’s invoice does not establish that each worker received the correct amount on time.
For applicable provident fund, ESI or other contribution obligations, examine the relevant worker-level details and period, alongside payment evidence. An aggregate receipt alone does not establish that every eligible deployed worker was included correctly.
Investigate failed transfers, missing entries, unexplained deductions and workers who cannot understand their wage statement. Where a payment method other than bank transfer is used, verify its legal acceptability and maintain reliable evidence of receipt.
A three-way record cross-check
This table is SVEGA’s recommended reconciliation tool, built around the workforce topics in the ETI Base Code and the records-and-practices assessment described by Sedex. It is not a published mandatory SMETA checklist. [1][2]
Use this table as a review tool. Worker conversations should be voluntary and confidential, with protection against retaliation. They help identify issues for investigation; they should never be used to coach workers for an audit.
| Check | Company record | Contractor record | Worker experience to understand |
|---|---|---|---|
| Identity and deployment | Site access and department roster | Worker register and assignment details | Actual employer, role, site and start date |
| Employment terms | Approved engagement requirements | Employment documentation | Whether terms were explained and understood |
| Working hours | Attendance, shifts and overtime approvals | Muster roll and payroll hours | Actual hours, breaks and rest days |
| Wage payment | Reviewed payroll inputs and exceptions | Wage sheet and payment evidence | Amount received, date and unexplained deductions |
| Contributions, where applicable | Coverage review and exception list | Worker-level contribution details and receipts | Access to relevant account or benefit information |
| Safety | Site induction, PPE and incident records | Training and deployment records | Training received and ability to report hazards |
| Grievance access | Channels, case ownership and closure records | Contractor complaint arrangements | Whether workers know how to raise concerns safely |
Record differences and their explanations. A mismatch is a reason to investigate, not automatic proof of misconduct.
6. Include contract workers in safety controls
The ETI Base Code calls for safe working conditions and regular, recorded safety training, including repeat training for new or reassigned workers. [1]
A safety policy means little to a worker who enters the production area before induction or receives instructions they cannot understand.
Compare deployment lists with induction and task-specific training records. Check that workers receive suitable PPE and know how to report hazards and incidents. Include contractor personnel in relevant emergency arrangements and site communications.
Review incidents involving contract workers across both company and contractor records. If each party keeps a separate incident log, establish how reports are shared, investigated and closed.
Sample short-tenure workers and recent joiners. They may leave before a monthly training session, creating a gap that an overall training percentage conceals.
7. Make grievance and POSH arrangements accessible
The UN Guiding Principles on Business and Human Rights recommend operational grievance mechanisms for people who may be adversely affected. Principles 29 and 31 address access to remedy and effectiveness criteria such as accessibility and predictability. These are international guidance, rather than a standalone Indian statutory complaint procedure. [4]
Contract workers need a practical route to raise concerns about pay, safety, treatment and working conditions. A channel that exists only in a permanent-employee handbook may not reach them.
Check awareness across shifts, languages and contractor groups. Explain who receives a complaint, how concerns are escalated and how the worker receives a response. Protect confidentiality and prohibit retaliation.
Sexual-harassment complaints require the appropriate statutory process. The POSH Act’s definition of employee expressly includes people engaged through contractors and contract workers. Businesses should therefore assess whether eligible contract workers can access the relevant arrangements, rather than treating contractor status as a reason for exclusion. [5]
Section 16 of the POSH Act restricts publication or communication of specified complaint, inquiry and identity information to the public, press and media. [5]
Keep sensitive complaint records separate from general compliance files. Management reporting can track response times and overdue actions without exposing complainants’ identities.
For a related discussion of governance and evidence, see Grievance Mechanisms Under BRSR. Its BRSR context does not mean BRSR applies directly to every unlisted manufacturer.
8. Review contractor performance and escalate exceptions
Give each finding an owner, deadline and evidence requirement. “Discussed with contractor” should not be the final status of an unresolved wage or safety issue.
Separate immediate correction from the action needed to prevent recurrence. Paying a missing amount may resolve the immediate shortfall. Fixing the payroll handover or failed-transfer review is what reduces the chance of another worker facing the same problem.
Agree an escalation route for repeated or serious concerns. Responses may include additional verification, a formal remediation plan and changes to contractor arrangements. Assess contractual and legal obligations before commercial action, and protect workers from losing wages or access to remedies during a contractor transition.
Common mismatches worth investigating
Deployment exceeds the worker register. The factory records additional workers during a busy period, but their employment and induction information is missing.
Overtime appears in one system only. Production approves extra work, while payroll receives the standard shift record.
A payment file is treated as a completed payment. Transfers were submitted, but failed transactions were never followed up.
A contribution receipt covers a different population. The receipt is current, but the worker-level details do not match the deployed workforce.
Training attendance does not establish understanding. A signature exists, but the worker cannot explain the task’s hazards or reporting route.
A grievance channel depends on the person being complained about. Workers must approach the contractor supervisor even when the concern involves that supervisor.
These are illustrative patterns, not reported SVEGA client findings. Each needs evidence-based investigation and a response proportionate to the issue.
Build a monthly contractor-governance review
Schedule the review around the payroll and contribution cycle so that completed records can be checked together. Monthly review is a recommended operating rhythm; urgent worker concerns should be addressed immediately.
- Confirm the workforce. Reconcile joiners, leavers, locations and shifts.
- Review a meaningful sample. Include recent joiners, overtime cases, different contractors and previous exceptions.
- Trace hours to payment. Check calculations, deductions, receipt and failed transactions.
- Check applicable coverage. Investigate worker-level omissions or period mismatches.
- Review safety and worker voice. Examine induction gaps, incidents and unresolved concerns.
- Agree actions. Assign ownership, dates and escalation triggers.
- Verify previous closures. Check whether the correction worked and whether the problem recurred.
Use full-population checks where the data allows it. Increase review depth when sampling identifies a wider pattern. Keep a short management record of what was reviewed, what remains open and who will act.
Frequently asked questions about contract labour governance
What is contract labour governance in a manufacturing company?
It is the system used to oversee contract workers’ deployment, employment records, hours, payments, safety and grievance access. It connects contractor responsibilities with internal ownership, evidence checks and corrective action.
Does paying the contractor’s invoice prove that workers have been paid correctly?
No. The invoice records the commercial payment to the contractor. The business still needs to examine worker-level wage calculations and reliable evidence of payment when assessing whether wages were received correctly and on time.
Which contract-worker records should be compared before a buyer social audit?
Compare worker registers, deployment lists, attendance, overtime, wage sheets, payment evidence and applicable contribution records for the same people and period. Also check training, safety and grievance arrangements against actual workforce coverage. The final audit scope depends on the buyer and methodology; Sedex confirms that SMETA scope determines the areas reviewed. [2]
Should contract workers be included in workplace grievance arrangements?
Yes, accessible worker-voice arrangements should cover the workforce present at the site. Sexual-harassment concerns must follow the applicable statutory route. Contractor status does not, by itself, exclude a person from the POSH Act’s employee definition. [5]
Who should own the contractor-governance review internally?
Assign an accountable manager with authority to coordinate action. HR, operations, procurement, finance and EHS should each own their checks. The allocation should fit the business, while avoiding gaps between commercial, payroll and site responsibilities.
Can a complete contractor file still reveal problems during an audit?
Yes. A complete file can contain inconsistent periods, missing workers or records that do not reflect actual practice. Reconciliation and confidential worker feedback help identify those gaps.
Put ownership behind the records
If preparing contractor evidence requires repeated chasing across teams, the business needs a clearer operating process. Start by identifying who owns the workforce register, who reconciles hours and payments, and who follows up unresolved concerns.
SVEGA’s Social Governance System Build helps organisations establish ownership, controls, evidence systems and review structures. If contract-worker records are a recurring source of uncertainty, discuss the gaps in your current process and the controls needed to address them.
References
[1] Ethical Trading Initiative. ETI Base Code. See clauses 1 (freely chosen employment), 3 (safety and training), 5 (wages and deductions), 6 (working hours) and 8 (employment relationships and contracting). Read the Base Code.
[2] Sedex. SMETA audit. See “How does SMETA work?” for the relationship between scope, site practices and records; see the certification FAQ for the methodology’s boundaries. Read the SMETA overview.
[3] Ministry of Labour and Employment, Government of India. Government Makes the Four Labour Codes effective to Simplify and Streamline Labour Laws. Press Information Bureau, 21 November 2025. Cited here for the commencement announcement, not as a complete statement of every site’s obligations. Read the announcement.
[4] Office of the United Nations High Commissioner for Human Rights. Guiding Principles on Business and Human Rights: Implementing the United Nations “Protect, Respect and Remedy” Framework. 2011, Principles 29 and 31. Read the Guiding Principles.
[5] Government of India. Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act, 2013. Sections 2(f) and 16. India Code. Read the Act.
References checked: 5 October 2026. SVEGA’s reconciliation table and monthly workflow are practical recommendations; they are not presented as prescribed legal formats or a mandatory audit checklist. Examples are illustrative, not reported client findings. Verify site-specific legal applicability before acting on a legal requirement.
