The Handoff
Know who holds the data, instructions, access, and operating knowledge.
Revival Group / Edited field-guide edition
Ask about ownership at the beginning
A system is not truly handed over because someone sent a folder. The team needs the information, access, and practical knowledge to keep the work running.
At kickoff, ask who holds the data, who maintains the instructions, and what happens to access when the engagement ends. Discuss the transfer before it becomes urgent.
Keep an operating package
Keep the workflow map, the current instructions, a list of systems and owners, and a runbook written for the people doing the work. Record how to check outputs, handle exceptions, and return to the previous process.
Document access ownership without putting passwords or tokens in the runbook. Use your organization's approved access-management process for credentials and transfers.
Practice the handoff
Have the receiving team run an ordinary task, resolve an exception, and explain how to stop the system. Use that exercise to find gaps in the documentation.
Agree on responsibility during the transition and on the support that remains afterward. Put ownership, access, and exit expectations into the engagement terms with appropriate professional review; a checklist is not a contract.
Leave room for a better relationship
The aim is a team that understands its own operation and knows when to ask for help. Ongoing work can then be about improving the system rather than keeping essential knowledge out of reach.
Ask one question before the next build starts: what would we need to operate this ourselves? The answer should be specific enough to become a checklist, a practice session, and a named owner.
Put it into practice
Map one task with the people doing it. Use the free Floor Walk worksheet, then decide what should change.
Use the Floor Walk worksheetEdited field-guide adaptation of Shop Manual 12: The Handoff.