Key takeaways
- List the systems and decisions that only the departing developer can explain.
- Turn private knowledge into notes another person can test on a real task.
- Move repository and release ownership before removing access.
- Rehearse the handoff with one representative ticket and a named reviewer.
- Close the departure with a verified checklist, not a farewell meeting.
Map the work only one person understands
Start with a list of systems, jobs, scripts, and decisions that depend on one person. Include the undocumented parts: the manual step after a deploy, the vendor contact, the query used to check a migration, and the reason a flag still exists. Ask the departing developer to mark each item as documented, partly documented, or known only to them. The last group is the real transfer list.
Check the list against repository ownership, on-call notes, and recent pull requests rather than memory alone. Look for files changed by one person repeatedly and for alerts that only one person answers. Ask the reviewer who has covered the area before. A short list of verified gaps is more useful than a long inventory of everything the team owns.
Turn private knowledge into tested notes
A note is useful when another person can follow it and reach the same result. Ask for the command, the expected output, the common failure, and the person to contact when the failure is unfamiliar. Record where the credential or permission comes from without pasting the secret itself. The note should survive a change of laptop and a change of owner.
Test each note on a clean environment with someone who did not write it. Fix the gaps while the author is still available to answer questions. Keep the note beside the code or runbook it describes rather than in a personal document. A tested note is evidence of transfer, while a folder of untested drafts is only a promise.
Transfer ownership before access changes
Move repository, deployment, and vendor ownership to named people while the departing developer can still confirm the change. Update the ownership file, the on-call rotation, the alert routing, and the release approval list. Check that the new owner can perform the action, not just that their name appears in a document. Access removal should follow a successful transfer, not replace it.
Keep a short overlap window for questions that only appear after the first real task. Name one person who will receive those questions and set an end date for the overlap. Do not leave a shared account open as a convenience. The goal is a clean boundary with a known contact, not permanent dependence on a former contributor.
Rehearse the handoff with a real task
Choose one representative task that the new owner will perform without the departing developer. Use a real ticket with a safe scope, such as a small configuration change or a routine release check. Watch where the new owner hesitates and update the note at that point. A rehearsal exposes the difference between knowing a system and having operated it.
Ask the reviewer to record the result, the questions raised, and the remaining risk. If the task cannot be completed without the departing developer, the transfer is not finished. Schedule a second rehearsal only for the gaps that matter to production. Keep the record with the departure checklist so a later audit can see what was tested.
Prepare the receiving team
Tell the receiving team what will change before the transfer starts. Name the systems, the decisions, and the meetings that will move to them, and explain why the change is happening. Ask each receiver to reserve time for the transfer rather than absorbing it into an already full week. A handoff without protected time becomes a document nobody reads.
Identify the person who will own each area after the departure, including a backup for production issues. Confirm that the receiver has the required role and can complete the approval path. If a receiver lacks access, start that request before the transfer session so it does not become a last-day blocker. Ownership should be real before the departing developer stops answering questions, and the receiver should know which decisions they are now allowed to make.
Use a short overlap with clear boundaries
Keep the overlap focused on the verified gap list and the rehearsal task. Ask the departing developer to answer questions and review the notes, not to take on new delivery work. Set a daily window for questions so the receiver knows when to expect an answer. A long overlap with no boundary can delay the transfer and hide the remaining gaps.
Record the questions that could not be answered and assign someone to resolve them after the departure. Give the receiver authority to make routine decisions without checking with the former owner. If a production issue requires former knowledge, treat it as an incident with a named owner and a follow-up action. The overlap should reduce dependence, not formalize it.
Close the departure with a verified checklist
Close with a checklist that covers work, access, ownership, and contacts. Confirm that open tickets have new owners, that the runbook was tested, that secrets were rotated where needed, and that the vendor contact list is current. Record the date and the person who verified each item, then store the checklist beside the team runbook. A farewell message is not a control, and a verbal assurance is not evidence that the transfer happened.
Review the departure two weeks later to see whether any knowledge gap has reappeared. Ask the new owner what took longer than expected and update the notes again. If the team depends on a former contributor for routine work, treat that as an open risk with an owner. The best departure leaves the work easier to run than it was before the notice.
Questions about assessing Philippine developers
How much notice is needed for a clean handoff?
The amount depends on how much single-owner knowledge exists. Start the map as soon as notice is given, and prioritize systems that affect production or customer commitments. A short, focused transfer is better than a long tour of everything.
Should the departing developer keep access during the overlap?
Keep only the access needed to answer questions and complete the transfer. Set an end date, use a named account, and remove permissions that are no longer required. Do not preserve broad access for convenience.
What if the developer leaves without notice?
Treat the missing knowledge as an incident risk and assign an owner to reconstruct it from the repository, logs, and vendor records. Prioritize production paths and customer commitments. Record the gaps rather than assuming the system is understood.
