Skip to content

Handoff Checklist

Role-transfer checklist — instantiates Role Expectation Architecture

A structured transfer list that moves a role from an outgoing holder to a successor without dropping open commitments, live context, or hard-won know-how.

A Handoff Checklist is the point-of-transfer instrument that carries a role across a change of holder intact. Its defining move is to surface and hand over the live, in-flight state of the role — the open commitments, the access and locations, and the tacit know-how that otherwise lives only in the departing holder's head. This is what distinguishes it from its continuity siblings: a rotation or deputy schedule decides who covers when, an onboarding runbook builds a newcomer's competence over weeks — but the handoff checklist is the moment-of-transfer artifact whose whole job is that nothing falls through the crack between two holders.

Example

A postdoctoral researcher is leaving a lab in two weeks and must hand an ongoing, multi-month experiment to a graduate student. Working from a handoff checklist, she transfers: the current state of each active experiment (what is running, what is stalled and why); where the reagents, protocols, and data actually live; the undocumented calibration quirk on the third instrument that everyone in the lab has learned the hard way; and the open commitments — a reviewer response due next month, a reagent order still pending. The student signs off that each item has landed.

Without the list, the most valuable things would have walked out with her — not the documented protocols, which anyone can find, but the bus-factor knowledge held in one person's head.[1] The checklist turns a risky, silent gap into an explicit transfer, so the experiment continues rather than quietly stalling for a month until the student rediscovers what the postdoc already knew.

How it works

  • Enumerate what is in flight. List the open items and commitments and their current state, so nothing live is dropped at the seam.
  • Transfer access and locations. Hand over keys, credentials, and where things are — the practical means to actually do the role.
  • Capture the tacit. Extract the precedents, quirks, and "how we actually do this" that exist only in the holder's memory, and write them down.
  • Confirm receipt. Have the successor acknowledge each item, converting a drop-off into a checked, two-sided transfer.

Tuning parameters

  • Coverage depth — skeletal (access plus open items) versus exhaustive (every precedent and quirk). Deeper is safer but costs the departing holder's time, which is often the scarcest thing at exit.
  • Tacit-capture effort — how hard the process pushes to extract head-knowledge versus settling for what is already documented. More extraction loses less, but tacit knowledge resists being written down.
  • Overlap window — a live shadowing overlap between holders versus a cold handoff. Overlap transfers tacit knowledge best; a cold handoff is cheaper and sometimes all that is available.
  • Acknowledgement — successor sign-off versus drop-and-go. Sign-off catches gaps at the seam; it adds ceremony.
  • Standardization — a role-specific bespoke list versus a generic template. Bespoke fits the role; generic is faster to produce and easier to keep.

When it helps, and when it misleads

Its strength is that it prevents the classic dropped handoff — the open item nobody picked up, the knowledge that left with the person — by making an otherwise invisible risk explicit and transferable at exactly the moment it is most exposed.

Its failure modes are inherent to a checklist. It captures the known knowns; the dangerous losses are the things the outgoing holder never thinks to mention because they do not realize those things matter. A rushed exit — or an acrimonious one — yields a hollow list filled in for form's sake. And the classic misuse is to treat it as a compliance signature: initialled and filed without any real transfer behind it. The discipline that guards against this is to build the checklist continuously rather than on the last day, favour a live overlap window so the successor can ask, and let the incoming holder drive the review rather than passively receive it.

How it implements the components

This artifact fills the point-of-transfer slice of the archetype — moving the role and its live state across a change of holder:

  • handoff_substitution_and_succession_path — it is the transfer step of the succession path: the structured move of the role from outgoing to incoming holder.
  • role_memory_and_precedent_log — it captures the outgoing holder's live working memory — open items, precedents, and tacit quirks — so that knowledge transfers rather than evaporating at exit.

It transfers the role at one moment but does not schedule who covers it or arrange standing deputies (that is Role Rotation or Deputy Schedule), nor build a newcomer up to competence over time (that is the Onboarding and Role Shadowing Runbook).

Notes

The handoff checklist and the Onboarding and Role Shadowing Runbook usually run in tandem on the same successor but do different jobs: the checklist transfers the live state of the role at the seam, while the runbook builds the successor's competence over the following weeks. A handoff that dumps context onto someone not yet ramped, with no onboarding behind it, transfers the material without transferring the ability to use it.

References

[1] The bus factor — the number of people who would have to be lost before a role or project stalls because critical knowledge lived only in their heads. A handoff checklist that captures tacit know-how, not just documents, is a direct defence against a bus factor of one. ↩