Retirement Wave and Institutional Knowledge Loss

Every PSU we sit in has the same corridor conversation. The superintendent who knows why that pump is piped backwards retires in March. The deputy has been on deputation. The SOP still shows the old valve tag. Someone says we should 'put him into the model'. That sentence is how you get a confident wrong isolation and a labour dispute about voice rights in the same quarter.

This is an opinion for CIOs and unit heads facing a retirement bulge. The opinion is narrow. Yes, the bulge is real in many CPSEs — a hiring freeze decade meeting a pension date. Yes, tacit knowledge walks out. No, an LLM is not a succession plan. The useful work is interviews, versioned procedures, and a retrieval agent that cites the living document. The dangerous work is a fine-tune that impersonates a named officer and cannot be cross-examined.

We will not quote a single official statistic as if it were your plant. Headcount pyramids differ across railways, banks, mines and refineries. Pull your own superannuation list for the next 24 months. That list is the programme. A national newspaper chart is not.

Not HR advice, not pension advice, not a safety case. Competent persons remain competent. Retired officers remain people with rights in their voice and their stories.

What is actually walking out

Not the gazette. The gazette stays. What walks is the exception: the vendor who always short-ships, the tag that was never updated after the 2014 revamp, the district officer who will only take a particular letter format, the reason a 'temporary' jumper is still there. That knowledge is tribal, local, and often slightly illegal in a way the next audit will hate. Recording it has a purpose beyond nostalgia: you want the next officer to know the jumper exists so they can remove it, not so they can perpetuate it.

A model that absorbs the jumper as normal will teach the jumper. That is the opposite of succession. Succession is a clean procedure plus a known deviation list with owners and end dates.

• List roles, not celebrities. 'Night shift isolation at unit 3' is a role. 'Sharma-ji's way' is a cult.
• Pull the 24-month superannuation list. Star the roles that have no deputy who has actually done the job.
• Separate safety-critical exceptions from commercial folklore. They are not the same capture project.
• Budget time with the living person, not only storage for their PDFs.

Why a ghost model is a bad idea

A fine-tune on one officer's notes will be treated by juniors as that officer. When it is wrong, nobody knows whether to call the retiree or the vendor. Accountability dies. The India AI Governance Guidelines talk about accountability as a sutra. A ghost fails it.

Voice and likeness of an employee or a retiree are not free training data. DPDP may reach recordings that identify a person. Even where it does not, consent, purpose and a deletion path are decent. Unions will ask. They should.

A retrieval agent that cites 'Interview-2026-03-12, page 4, confirmed in SOP Rev 7' is a clerk. A chat window that answers in Sharma-ji's idiom is a séance. Buy the clerk.

The industrial-relations frame

If capture is framed as 'so we can run without you', the remaining cohort will not talk. Frame it as 'so the next person does not die or get a para on your watch'. Invite the recognised union and the officers' association to the kick-off. Offer the incumbent a named credit on the procedure they help rewrite. Do not put their headcount on the AI slide. The union companion is mandatory reading here.

What to tell the board

Tell them the 24-month list, the roles with no deputy, the number of in-force SOPs that still name retired tags, and the capture plan. Do not tell them you will 'preserve institutional memory in a sovereign model'. That sentence funds a séance and a banner. It does not fund a deputy's first night shift.

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.

We have no time to rewrite SOPs.

Then you have no time for a safe agent either. The rewrite is the work. The model is optional stationery.

The retiree is willing to be on a retainer; skip capture.

Retainers die, take holidays, and forget. Capture the procedure. Keep the retainer as a human escalation, not as the only copy.

Open-weight models will just remember.

They will remember a statistical average of the internet and your junk drawer. They will not remember your jumper unless you write the jumper down — and then they may treat it as gospel. Write, version, retrieve.

This is a HR problem, not an IT problem.

It is a unit problem. HR has the list. Operations has the risk. IT has the retrieval tool. If any one of you owns it alone, it will fail in that one's style.

A four-week honesty playbook

This is not the full capture. This is how you stop lying to the board in a month.

1. Week 1: 24-month superannuation list versus roles. Star those with no deputy who has done the job. Share with the unit head and IR.
2. Week 2: pick two safety-critical roles. Interview with a successor in the room. Write one SOP revision and one deviation list with end dates.
3. Week 3: put only the signed revision into the retrieval corpus. Archive the raw interview with a do-not-serve banner.
4. Week 4: brief the union/association. Publish the frame: retrieval, not replacement; credit, not harvest. Then ask for budget for the rest of the list.

How this shows up in the file

Subject: Retirement-related knowledge — SOP revision, not a ghost model.

This unit will capture critical exceptions through interviews that produce signed procedure revisions and time-bound deviation lists. Raw recordings are archives, not live corpora. No model will impersonate a named officer. Successors are named. IR has been briefed that sanctioned strength is not the object of this paper.

This note is not HR or safety 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'. “Retirement Wave and Institutional Knowledge Loss” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

A retiring cohort is not a dataset. It is a set of people who can still refuse a wrong SOP. Record them with consent. Do not train a ghost and call it succession. 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 “Retirement Wave and Institutional Knowledge Loss” 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. “knowledge retention PSU retirement” 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 “Retirement Wave and Institutional Knowledge Loss” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “knowledge retention PSU retirement”: 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 “knowledge retention PSU retirement” 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.