Government Invited Public Feedback on Four Draft Labour Codes — Why I Responded to One Only
Four Labour Codes, One Considered Response: Why I Chose the Code on Wages
Government of India invited public feedback on
four draft labour codes. I explain why I submitted suggestions only on the Code
on Wages, and summarise my concept note on wage transparency and worker
confidence.
Recently, the Ministry of Labour and Employment,
Government of India, invited public comments and suggestions on draft rules
under four labour codes. Such consultations matter. They are among the
few formal spaces where individual citizens can place thoughtful inputs on
record before rules are finalised.
After reading through the drafts, I chose to
submit feedback on only one of the four codes. This post explains which
codes were opened for consultation, why I limited my response to a single code,
and the essence of what I submitted.
The Four Draft Labour Codes Open for Feedback
The consultation covered draft rules under the
following labour codes:
- Code
on Wages
https://www.indiacode.nic.in/handle/123456789/1526 - Industrial
Relations Code
https://www.indiacode.nic.in/handle/123456789/1530 - Code
on Social Security
https://www.indiacode.nic.in/handle/123456789/1528 - Occupational
Safety, Health and Working Conditions Code
https://www.indiacode.nic.in/handle/123456789/1529
Each of these codes addresses a distinct and
complex aspect of India’s labour ecosystem — from wages and industrial
relations to social security coverage and workplace safety. Together, they
represent a significant reorganisation of labour regulation, and each deserves
careful, specialised engagement.
Why I Chose to Respond Only to the Code on Wages
My decision to submit feedback only on the Code on Wages was
deliberate.
Wages sit at a unique intersection of employment,
trust, and financial dignity. They are where labour law meets everyday life
— shaping not only income, but also predictability, confidence, and a sense of
continuity across jobs. Unlike other aspects of labour regulation, wages follow
the worker across employers, contracts, and phases of life.
My own long-standing interest lies in safe,
transparent, and trustworthy financial systems, particularly where design
choices affect individuals rather than institutions. From that perspective, the
Code on Wages offered a narrow but meaningful space to think about how wage-related
information is experienced by workers over time.
Rather than offering broad or superficial
observations across all four codes, I felt it was more responsible to
contribute one focused idea, grounded in restraint and lived
understanding, to the area where I could add something constructive without
overreach.
The Core Idea Submitted Under the Code on Wages
The submission I sent was not a demand or a
recommendation for immediate implementation. It was a concept note — an
exploration of whether, over time, wage transparency for workers could be
strengthened without increasing employer burden or mandating
digital-only systems.
At its heart were two linked ideas.
Note: In this context, WUAN refers to a proposed Wages Universal Account Number, distinct from the existing Universal Account Number (UAN) used by the Employees' Provident Fund Organisation for provident fund accounts.
Executive Summary of the Submission
A Wages Universal Account Number
(WUAN)
The first idea was a Wages
Universal Account Number (WUAN) —
a lifelong, wage-linked identifier for workers.
The intent is continuity, not control.
Such an identifier would remain constant
throughout a worker’s career, regardless of changes in employers or modes of
wage payment.
It would be informational only, serving as
a stable reference that allows wage-related information to be viewed across
employments.
It is not a payroll system, not a tax mechanism,
and not an enforcement tool.
A Worker-View Consolidated Wage History
Linked to WUAN, the
second idea explored was a view-only wage history for workers.
This would allow individuals to see, in one place,
their periods of employment, wages received, and related components such as
bonuses or indicative gratuity information. It would not replace statutory wage
slips or employer-maintained records. Instead, it would provide workers with a
clearer, consolidated picture of their wage journey over time.
The purpose is visibility and confidence — nothing
more.
What the Submission Deliberately Does Not Attempt
Just as important as what the submission explores
is what it consciously stays away from. It does not argue for digital-only wage
payments, nor does it seek to introduce any new compliance or reporting
obligations for employers. The idea is not about payroll processing, tax
reporting, or enforcement mechanisms, and it does not dilute the flexibility
that employers require to operate across diverse contexts.
If such a concept were ever to be examined
further, it would need to rest on strong privacy protections, minimal data
collection, and clear, consent-based access — and nothing more.
A Larger Reflection
India has, in recent years, shown that it can
design large-scale systems that work best when they are voluntary,
inclusive, and trust-based.
If ever explored thoughtfully, a concept like WUAN could represent India’s contribution to
global thinking on employee transparency and ease of operations — not
through compulsion, but through clarity and trust.
Closing Note
Public consultations work best when responses are
offered with restraint, focus, and respect for complexity. This
submission was made in that spirit — as a single, well-considered contribution
to one draft code, placed carefully on record.
Whether or not the idea is taken forward, the
consultation itself is a reminder that policy improves when citizens engage thoughtfully
rather than noisily.
Further Reading
Official texts of the four labour codes are
available on the Government of India’s India Code portal:
https://www.indiacode.nic.in
The Citizen Advocate Summary
Declaring April 11 as
Safe ePay Day is a symbolic, citizen-led proposal to annually reinforce safe
digital payment behaviour, public awareness, and shared
responsibility—celebrating not just scale, but the joy of safe ePayments.
👉 Please visit movethebarrier.blogspot.com/April11
The Joy of Safe ePayments
Nayakanti Prashant – Citizen Advocate, Safe ePay Day
“Let’s make April 11 a global symbol of care — in payments, in
protection, in progress.”
🪞 Disclaimer
The only Joy is
“Joy of Safe ePayments.”
Nothing More – Nothing Less.
Author’s Note
This
reflection was developed with the assistance of an AI language model, used as a
thinking, structuring, and editorial companion. The ideas, interpretations, and
conclusions expressed here are entirely my own.

Comments
Post a Comment