Tribal Knowledge Capture Log · Naga Mounika Nuguri

Document type	Log
Topic area	Tech Transfer & NPI
Level	Intermediate
Updated	September 2026

This is a ready-to-use log for capturing the undocumented operating knowledge, “tribal knowledge,” that a written batch record and method document rarely hold in full. Use it during structured knowledge-capture interviews, video review of manual steps, and shadowing or secondment periods, and disposition every entry before the engineering run’s after-action review closes. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows.

Document control header

Field	Entry
Document title	Tribal Knowledge Capture Log for `<<FILL: process / transfer>>`
Document number	`<<FILL: e.g. TKC-2026-01>>`
Linked transfer plan	`<<FILL: document number>>`
Capture period	`<<FILL: start date to engineering run date>>`
Log owner	`<<FILL: e.g. Receiving site process owner>>`

1. Purpose

This log captures operating detail surfaced through structured interviews, video review, or shadowing during a technology transfer that does not appear in the written batch record, method document, or master production instructions, so each item receives an explicit disposition rather than remaining an informal, undocumented practice known only to the individuals involved.

2. Capture methods used

Method	Used	Dates / sessions	Participants
Structured knowledge-capture interview	`<<FILL: yes/no>>`	`<<FILL>>`	`<<FILL>>`
Video documentation of manual steps	`<<FILL: yes/no>>`	`<<FILL>>`	`<<FILL>>`
Shadowing / secondment	`<<FILL: yes/no>>`	`<<FILL>>`	`<<FILL>>`

3. Captured items

#	Date captured	Method	Description of the undocumented detail	Source (role, not necessarily name)	Disposition	Disposition owner	Closure date
`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL: folded into MPI / folded into risk assessment / accepted as undocumented judgment call, training only / requires further investigation>>`	`<<FILL>>`	`<<FILL>>`

Every row needs a disposition before this log is considered closed for the capture period. “Accepted as undocumented judgment call” is a legitimate disposition only when the item is a genuine skill-based judgment that training can carry forward; it is not a default for an item nobody got around to evaluating.

4. Items requiring further investigation

# (linked to Section 3)	What remains open	Owner	Target date
`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`

5. Summary at closure

Field	Entry
Total items captured	`<<FILL>>`
Items folded into master production instructions	`<<FILL>>`
Items folded into the risk assessment	`<<FILL>>`
Items accepted as training-only judgment calls	`<<FILL>>`
Items still open at engineering run close	`<<FILL: state "none" or list, with a follow-up plan>>`

6. Approvals

Role	Name	Signature	Date
Author (Receiving site process owner)	`<<FILL>>`
Reviewer (Sending site process owner)	`<<FILL>>`
Approver (Quality Assurance)	`<<FILL>>`

Filled specimen

Extract for an example lentiviral vector CAR-T process transfer to a CDMO. Company and numbers are illustrative.

#	Date captured	Method	Description of the undocumented detail	Source	Disposition	Disposition owner	Closure date
1	Pre-engineering-run interview	Structured interview	Operator adjusts closed-system tubing weld sequence order when ambient humidity is high, to reduce weld failure rate, a practice never written into the batch record	Sending site senior operator	Folded into MPI as a conditional instruction tied to a humidity threshold	Receiving site process owner	Closed, 2 weeks before engineering run
2	Video review	Video documentation	Visual in-process check for cell clumping described in the SOP as “inspect for clumps” is, in practice, a specific tilt-and-rock motion the analyst uses to reveal clumps that aren’t visible with the vessel held still	Sending site QC analyst	Folded into MPI with a photo-referenced work instruction addition	Receiving site QC lead	Closed, 1 week before engineering run
3	Shadowing	Shadowing during sending-site batch	Sending site operators have learned to treat a specific low-magnitude pressure alarm as a nuisance alarm during a particular process step, silencing it routinely, a practice not reflected in the alarm response procedure	Sending site operator	Escalated for further investigation: alarm threshold itself may need adjustment rather than accepting routine silencing as normal	Manufacturing engineering	Open at engineering run start; see Section 4

Section 4, items requiring further investigation:

#	What remains open	Owner	Target date
3	Whether the pressure alarm threshold should be adjusted rather than routinely silenced	Manufacturing engineering	Before first qualification batch

Summary at closure: 3 items captured; 2 folded into the MPI; 0 accepted as training-only; 1 open, tracked to the target date above and reviewed again at the engineering run after-action review.

Common inspection findings this log prevents

An operator practice that materially affects the process, discovered only when a new hire performs the written procedure literally and gets a different result.
Knowledge-transfer activity that happened, interviews, shadowing, video review, with no record of what was actually learned or what was done about it.
A “tribal knowledge” risk named in the transfer risk assessment with no corresponding capture activity ever performed.
An item captured during a transfer but never dispositioned, discovered only when the same gap causes a deviation months later.

How to adapt this log

Assign one owner for this log for the whole capture period; a log with no single owner accumulates entries nobody follows up on.
Disposition every entry before the engineering run’s after-action review; an item still undispositioned at that point becomes an item for the review agenda, not something quietly left in the log.
Word the “source” column by role, not always by name, if the organization’s practice is to keep individual attribution out of a document that may be shared externally; keep an internal record of who said what where needed for follow-up.
Treat “accepted as undocumented judgment call” as a real decision requiring a stated reason, not a way to close an item without doing the work of evaluating it.