HR and Transfer Policy Queries: An Agent Case

Transfer season in a pan-India CPSE is a rumour mill with letterheads. Someone forwards a 2019 circular. Someone else swears the director (HR) promised an exemption. A well-meaning chatbot trained on a zip of mixed PDFs will pick a sentence from the wrong year and ruin someone's Monday, or worse, their posting.

This case is a composite HR-policy agent: leave, LTC, transfer, deputation FAQs. It is not an e-HRMS replacement. It is not a competent authority. It is a librarian with a date stamp.

Personal data here is obvious — employees, families, medical grounds, caste certificates in some exemption files. On-prem, purpose-limited, no Aadhaar in traces. The usual sentences, now in an HR corridor.

What the composite CPSE did

HR nominated a circular librarian. Every live circular got a unique ID, a supersession field, and a hash. Withdrawn circulars stayed in a dark collection for audit, not for answers.

The UI showed the circular number and date above the prose. If two circulars could apply, it showed both and refused to pick. If the question was when will I be transferred, it refused and pointed at the application form.

Managers could not use the agent to generate a transfer order. That stayed in the HRMS with the existing delegation.

Stale law is the bug, not tone

Employees will forgive a stiff sentence. They will not forgive a wrong entitlement. The acceptance test is: plant a withdrawn circular and a live one with similar titles; the agent must not cite the withdrawn one as current.

When HR issues a new circular, the librarian updates the register the same day. If the register is stale, the agent must show a banner: corpus last certified on date D. No banner, no production.

What not to answer

• Individual vacancy rumours.
• Medical-ground outcomes.
• Whether a named colleague will be moved.
• How to draft a grievance that accuses a superior — point at the grievance path instead.
• Anything that needs the employee's raw service book in the prompt.

[Union](/blog/psu-union-concerns-about-automation)s and trust

Show the union the circular register and the refusal list before go-live. A surprise bot that interprets a settlement will be treated as management by other means.

If a settlement and a circular disagree, the agent shows both and stops. Interpretation is HR and counsel, in writing.

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.

We will connect service books so it can be personal

Then you have a new data class, a new fiduciary map, and a new way to leak a career. Default to circulars only.

Employees want a decision, not a PDF

They want a decision from a competent officer. Give them the form and the live rule. Do not role-play the officer.

Hindi and regional languages are mandatory

Then certify the circulars you actually have in those languages. Do not let the model invent a translation of a legal circular without HR signing the translation.

This is too small to be agentic

Small and correct beats agentic and wrong. If you later add a draft application, keep the accept in HRMS.

Four weeks with a circular librarian

1. Week 1: inventory circulars. Mark live, superseded, withdrawn. Assign the librarian.
2. Week 2: build citation-first answers on a dark collection. Plant the stale-circular test.
3. Week 3: run a closed beta with one plant's HR desk, not with all employees. Log refusals.
4. Week 4: union briefing, banner rule, no-outcome standing order. Then open a wider read-only channel.

How this shows up in the file

Subject: HR policy retrieval agent — circulars only.

The agent may retrieve live, librarian-certified circulars and show supersession. It shall not issue transfers, exemptions, or individual outcomes. Withdrawn circulars shall not be cited as current. A corpus-certification date shall be visible.

Employee service books shall not be pasted into prompts. This note is an internal aid. It is not legal advice.

Transfer season is a load test

Queries spike when orders are rumoured. That is when a stale circular does the most damage. Staff the librarian through that fortnight. If HR cannot certify, take the transfer topic down. A 503 is kinder than a wrong posting rumour with a letterhead tone.

Prcept AI will not connect service books in year one. We will show supersession and refuse outcomes. If the union has not seen the register, we will not open the channel.

What HR must staff that the GPU cannot

The librarian is not a metaphor. Someone in HR must own the register the way someone owns the gazette file. When they go on leave in transfer fortnight, an understudy must be able to mark a circular withdrawn before lunch. If that post is additional charge with no understudy, take the agent down when they travel. A live bot with a dead librarian is how 2019 returns.

Medical-ground files, caste certificates used for some exemptions, and family details in LTC claims are not circulars. They are personal data with a purpose that is not 'the chatbot was curious'. Keep them in HRMS. If an employee pastes them into the chat, the intake filter should refuse and point at the counter. Log the refusal. Do not log the paste.

Managers will ask for a team view: who is eligible to move. That is a new workflow with a new paper, a new access list, and a new way to leak a career. Year one does not include it. Say so in the standing order so a plant HR does not 'just connect the roster' in October.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation, engineering or board advice. Confirm against the live Gazette, GFR, GeM term, CVC instruction, CERT-In direction, UIDAI regulation, DPE guideline, DPDP text, departmental charter, plant safety 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'. “HR and Transfer Policy Queries: An Agent Case” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

Employees will ask the bot because they do not trust the last forwarded PDF. Your job is to serve the live circular and refuse to order anyone anywhere. 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 “HR and Transfer Policy Queries: An Agent Case” 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. “HR policy chatbot PSU” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “HR and Transfer Policy Queries: An Agent Case” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “HR policy chatbot PSU”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “HR policy chatbot PSU” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

One more artefact before you close the file

Add a one-page owner map: who runs this after the vendor leaves, who can stop it, and where the logs live. If those three names are missing, the project is still a demo.

Date the page. File it next to the contract. That is the difference between a blog you read and a control you can audit.

What the next file must contain

“HR and Transfer Policy Queries: An Agent Case” earns a line in the noting only if a P1 CIO/CTO can attach proof of “HR policy chatbot PSU.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “HR policy chatbot PSU.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.