KNOWLEDGE-TRANSFER PLAN — YENRA
Guide: https://yenra.com/retirement-of-experienced-workers/
Purpose: transfer a priority task and demonstrate the successor's readiness.
Use for an agreed departure or other role transition. Plan from tasks and
documented continuity needs, with time reserved for both participants.
Record credential locations and access request routes, never passwords.

Transition owner / departing colleague / successor / backup:
Agreed transition date / time available / current scope:

PRIORITY TASK (repeat this block for each task)
Task and trigger; next expected occurrence:
Consequence if interrupted; difficulty of recovering knowledge:
Inputs / authoritative documents / access roles:
Normal steps and expected output:
Decision cues / common exceptions / unsafe shortcuts:
Who can approve an exception; current contact route:
Recent example case (reference only, with sensitive details protected):
Document owner, version, location, and review date:

PRACTICE AND READINESS
Observed demonstration date / notes:
Successor's explanation back / gaps found:
Supervised execution / actual evidence:
Exception rehearsal / result / changes to notes:
Access checked using successor's own account:
Tasks accepted for independent work:
Tasks still requiring review / reviewer / coverage arrangement:
Manager acceptance date and evidence:

AFTER TRANSITION
First completed case review / corrections to notes:
Unresolved gap / owner / due date:
Any agreed continuing support: scope, availability, contact, terms:

Fictional example: a supplier offers a substitute component. The successor
locates the controlled specification and routes the mismatch to the named
technical approver. Independent authority to approve substitutions is not
implied by acceptance of the ordinary ordering task.
Reference: NASA knowledge capture and transfer report, linked in the guide.