PSU Union Concerns About Automation

The recognised union at a steel plant heard about the 'AI manpower optimisation' slide from a contractor WhatsApp group. By the time the CIO scheduled a briefing, the demand was already drafted: withdraw the tool, disclose the vendor, and put in writing that no post would be surrendered. The slide had been written for a board that likes efficiency adjectives. It was the wrong audience and the wrong noun.

This guide is for CIOs and unit heads who have to put an agent into a unionised PSU. It is not labour-law advice and it is not a playbook for breaking a recognised union. The only durable frame we have seen work is narrow: the agent retrieves and drafts; the employee still does the judgement; nobody's post is in the business case. If your real plan is a headcount cut, that is a separate industrial-relations file. Do not hide it inside a copilot.

PSU industrial relations are not a tech-company all-hands. Recognised unions, officers' associations, contract labour, and the standing orders sit on different legal footings. An agent that touches a workman's daily log is not the same object as an agent that drafts a Hindi file note for a section officer. Write which population you are talking to before you book the hall.

Not legal advice. Industrial Disputes Act questions, standing orders, and your recognition agreements belong with IR and counsel. This is a field guide for the conversation you should have already started.

Retrieval, not replacement

Say the sentence in the first minute: we are automating retrieval of circulars, drawings and prior files so that the person on the post spends time on the exception. Do not say we are automating the post. The second sentence is a threat even when you did not mean it as one.

Put the human signature in the architecture, not as a courtesy. If the agent can close a ticket, raise a gate pass, or recommend a charge-sheet, you have built a replacement story and the union is right to treat it as one. If the agent cannot write to the system of record, you have built a clerk. Clerks are discussable.

The India AI Governance Guidelines of November 2025 include People First as a sutra. That is not a union agreement. It is a useful citation for a management that wants to sound modern while cutting the desk. Do not use a guideline as a shield. Use a signed scope.

• Name the posts in the room. If none are proposed for surrender, write that.
• Name the contract labour question separately. Hiding a contractor cut inside an AI pilot is how you get two disputes.
• Offer the tool to the incumbent first. A copilot that only management can see is a surveillance story.
• Publish the packet: what the agent retrieved, what it drafted, what the employee signed. Opacity reads as a dossier.

Who you brief, and in what order

IR and the unit head first, so they are not reading the union's letter as their first brief. Recognised union and officers' association next, in the form your recognition agreement already uses — a meeting, a notice, a works committee, whatever is live. The vendor last, and not alone with the union unless IR is in the chair.

Do not let a young product manager explain 'augmentation' with a Silicon Valley deck. The room has heard that word before, usually just ahead of a VRS rumour. Bring the actual screen and one real circular. Show that the employee can reject the draft. Show that the rejection is not scored as failure.

What not to put in the board note

Do not put a manpower saving in the same paragraph as the pilot. If finance needs a benefit, use cycle time, file completeness, overtime on closing week, or the cost of a missed statutory filing. Those are discussable without naming a post.

Do not put a heat map of 'low-value roles'. That document will leak. It will be read as a hit list. If you have a genuine process study, keep it in the IR file under the process, not under the model.

DPDP is not a labour statute, but employee personal data in prompts — attendance exceptions, medical notes, disciplinary drafts — is still personal data. A union that asks who can see the chat is asking a lawful question. Answer it with purpose tags and access lists, not with 'the cloud is secure'.

Contract labour and the silent third party

Many PSU 'clerical' queues are already contract. An agent that shrinks that queue will be felt by a contractor, then by a union that claims the work, then by a principal-employer question nobody put in the AI file. Write the labour supply contract implication in week one or you will write it in a conciliation.

Do not ask the agent to score individual workmen. Productivity scoring of named persons is a different product and a different fight. Keep the metric on the file, not on the badge.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

If we brief the union now, they will block the pilot.

If they can block it after a leak, they can block it now. Early briefing lets you drop the stupid sentence. Surprise makes the stupid sentence the only sentence.

Other PSUs automated without this theatre.

Name one, with a union letter that says so. Anecdotes from a software park are not a steel plant. Your recognition agreement is the document, not a LinkedIn thread.

The vendor's change-management SKU will handle IR.

No. A vendor does not sit in your conciliation. IR chairs. The vendor may demo the screen. They do not interpret standing orders.

We have to show ROI to the board.

Show file cycle time, overtime, and failed statutory submissions. If the only ROI you can write is fewer people, you do not have an AI business case. You have a staffing case wearing a model.

A four-week engagement playbook

Do this before the indent, not after the banner goes up on the intranet.

1. Week 1: IR and unit head agree the one-sentence frame (retrieval, no post surrendered) and the populations in scope. Kill any manpower sentence in circulating decks.
2. Week 2: brief the recognised union and the officers' association with a live screen and a reject button. Minute the questions. Do not promise a product you have not scoped.
3. Week 3: write the access list, the DPDP purpose for employee data, and the ban on individual scoring. Show the minute to IR before it goes to IT.
4. Week 4: run a supervised week with volunteer incumbents. Publish what was retrieved and what was rejected. Only then talk about a wider rollout.

How this shows up in the file

Subject: Agent pilot — retrieval support, no change to sanctioned strength.

This pilot automates retrieval and first-draft notes. It does not close tickets, does not write to the system of record, and does not propose a reduction in sanctioned strength or a change in contract-labour numbers. Recognised unions and the officers' association were briefed on (date). Employee chats are purpose-limited and are not a supervisory dossier.

Any later staffing proposal will travel on a separate IR file. This note is not labour-law advice.

This article is informational field guidance for Indian public sector undertakings and their vendors, not legal, audit, labour, energy-regulatory, banking-regulatory or procurement advice. Confirm the live circular, DPE guideline, CVC instruction, sector regulator text, purchase manual and your counsel before you file it.

How this clears vigilance and the board

A P1 CIO/CTO in a PSU will meet CVC-shaped questions even when there is no special 'AI circular'. “PSU Union Concerns About Automation” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

A PSU pilot that surprises the recognised union is already in trouble. Talk about retrieval and file quality, not headcount. The officer still signs. The clerk still exists. OT networks stay off-limits. Navratna autonomy speeds buying; it does not waive DPDP or data classification. IREPS is not GeM. RBI-shaped rules still localise payment data.

• Classify data before the POC.
• Keep agents off OT.
• Write the board memo with residual risk.
• Engage unions on retrieval vs replacement.

Close this loop before the next CAB

Put “PSU Union Concerns About Automation” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P1 CIO/CTO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “union automation concerns PSU” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.