Lontra HR · Working template
Knowledge handover acceptance record
Decide whether one task package can be accepted for its stated scope and support arrangement.
Use this worksheet with a fictional example first, then adapt it to your organization’s process. Keep personal or confidential information in your authorized systems.
- Specify the task package and acceptance conditions before reviewing the evidence.
- Have the receiving colleague test the sources and access through their approved role.
- Use an approved practice case that covers a normal decision and a relevant exception.
- Record observations and unresolved dependencies separately, with a responsible owner.
- Make the acceptance decision explicit and review the package after the first suitable work cycle.
Click a cell to edit it locally. Print or save as PDF to keep your completed copy. Changes are not sent to a server.
| Readiness check | Evidence to inspect | Status and next owner |
|---|---|---|
| Task and scope | Named responsibility, next work event and accepting owner | Ready / action required / untested |
| Current source | Open the approved instruction and confirm owner and version | Evidence reference and resolution owner |
| Task card | Compare steps and decision cues with the current instruction | Conflict or missing step to resolve |
| Successor access | Open required systems and sources in the receiving role | Access gap, owner and agreed support |
| Normal practice case | Explain and attempt the approved sequence | Observed gap and retest condition |
| Exception case | Identify the stopping point and authorization route | Unresolved boundary and responsible role |
| Support after transfer | Check current contact, availability and fallback | Named support commitment |
| Acceptance and review | Record proceed, supported proceed or defer, with reason | Accepting owner and first-cycle review |
Prepared by Lontra HR Editorial · 10 November 2026 · Editorial review copy. Filled examples, where present, are fictional and demonstrate the method.