Digitising Tribal Knowledge Before It Walks Out

The night-shift group on WhatsApp contained the actual isolation sequence, three memes, a medical excuse, and a photo of a tag written in paint. A vendor offered to 'ingest collaboration tools'. That ingest would have been a DPDP incident, a safety incident, and a union incident before it was a knowledge-management success.

This guide is the how-to that sits under the retirement opinion. Tribal knowledge — the local, unwritten, often bilingual practice of a crew — can be digitised. The method is slower than a scrape and faster than a three-year DMS romance: structured interviews, photographs of the real tag, a two-person review, a signed SOP diff, and only then a retrieval agent.

Language matters. Crews mix Hindi, English and the state's working language. Capture in the language the crew uses. Do not translate everything into corporate English before review; you will lose the tag name that actually sits on the pipe. Do not promise 22 scheduled languages because one plant speaks Santali on the night shift. Promise that plant's languages, with a reviewer who has them.

Not ethnography and not a safety manual. Competent persons still walk the line.

A capture loop that fits a unit

Pick a role from the starred retirement list or a repeated near-miss. Sit the incumbent and the successor together for ninety minutes. Record with consent. Walk the plant and photograph the tags the SOP still gets wrong. Draft a diff: what the SOP says, what the crew does, what the crew should do after review. A competent person accepts, rejects or time-bounds each deviation. Only the accepted text is in-force.

The agent is allowed to retrieve the in-force text and the time-bound deviation list. It is not allowed to retrieve the raw WhatsApp or the unreviewed transcript.

Inputs, reviews, outputs. Do not skip the middle column.

Input	Review	Live output
Interview + plant walk	Incumbent, successor, competent person	SOP diff, signed
Photo of actual tag	Matches P&ID / mine plan or marked as exception	Image in the in-force pack with a caption
WhatsApp folklore	Not a source until rewritten	Nothing — or a ticket to write a procedure
Bilingual crew terms	Reviewer who has those languages	Terms kept, not prematurely translated

Tools that help, and tools that steal

Speech-to-text on an India-held box helps if the reviewer still edits. A camera with a date and a GPS off switch (mines and refineries have rules) helps. A retrieval agent that cites the signed diff helps. A foreign transcription API that keeps audio helps the vendor, not you.

Do not scrape personal chats. DPDP, basic decency, and the fact that medical excuses live there are enough reasons. If the only copy of a sequence is in a chat, ask the crew to recreate it in the interview. Paying attention is cheaper than a class-action-shaped headline.

Safety-critical versus commercial folklore

How a vendor is persuaded to replace a gasket is folklore. How a line is isolated is safety. The first can wait. The second cannot be 'good enough' in a model. If the competent person will not sign the diff, the agent does not serve the topic. Paper and a phone call remain the system.

DGMS, factory inspectors and your own safety board will not accept 'the model said' as a competent person's judgement. Do not put them in that position.

Credit and access

Name the crew on the SOP revision if they want to be named. Some will. Some will want the procedure to be anonymous so they are not called every Sunday. Ask. Credit is IR. Access to raw interviews is restricted. Supervisors get the signed SOP, not the gossip in the transcript.

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.

Interviews do not scale to 8,000 people.

You are not capturing 8,000 people. You are capturing starred roles and repeated near-misses. Scale is a later wave, like any other rollout.

The crew will perform for the recorder.

That is why the successor and the walk-down exist. Performance dies at the painted tag. The tag does not perform.

We already have a KM portal.

If it holds signed, in-force diffs, point the agent at it. If it holds 2014 PowerPoints, it is another junk drawer. Do not ingest it to be polite.

Video is richer than text.

Video of an isolation can become a second SOP that nobody updates. If you record video, it still needs a signed text that the agent cites. Video is training material for humans, not an unbounded corpus.

A four-week capture sprint on one role

One role, one unit, one signed diff. Then decide if the method deserves a programme.

1. Week 1: pick the role, get consent forms, name the successor and the competent reviewer, brief IR.
2. Week 2: interview, walk-down, photographs. Transcribe on a box you control. Redact personal medical or disciplinary asides.
3. Week 3: write the SOP diff and the time-bound deviation list. Review. Sign. File a ticket for physical tag fixes.
4. Week 4: load only the signed pack into the retrieval agent. Test ten questions from the successor. Archive the raw media with a do-not-serve flag.

How this shows up in the file

Subject: Tacit-knowledge sprint at (unit/role) — signed diffs only in the live index.

Interviews are consented and purpose-limited. Processors of audio are named. WhatsApp is not a corpus. Live retrieval is restricted to signed SOP revisions and time-bound deviations. Raw media is archived, not served. Crews are credited or anonymised as they choose.

This note is not safety advice. The competent person still signs the permit.

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'. “Digitising Tribal Knowledge Before It Walks Out” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

Tribal knowledge becomes usable when it is a versioned document with an owner. Record the person, review the exception, stamp the SOP. The agent cites the stamp. WhatsApp is not a corpus. 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 “Digitising Tribal Knowledge Before It Walks Out” 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. “tacit knowledge capture AI” 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 “Digitising Tribal Knowledge Before It Walks Out” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “tacit knowledge capture AI”: 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 “tacit knowledge capture AI” 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.

What the next file must contain

“Digitising Tribal Knowledge Before It Walks Out” earns a line in the noting only if a P1 CIO/CTO can attach proof of “tacit knowledge capture AI.” 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 “tacit knowledge capture AI.”
• 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.