Six transition plan templates for small business: employee departure, internal role change, leave cover with a return handback checklist, manager handover, a handover note written by the employee, and a four-tab tracking spreadsheet. Editable Word and Excel files, no email form in the way.
Someone gives notice on a Monday. By the following Friday week they are gone, and you find out over the next two months which parts of the business were living in their head. The supplier who needs chasing twice. The report that goes out on the fifth. The customer who only ever called them directly.
A transition plan is the document that gets that out of one person and into the business while you still have them. There are six templates here rather than one, because a departure, an internal promotion, a leave of absence, and a manager handover are genuinely different problems. Five download as editable Word documents and one as a four-tab spreadsheet, free, with no email form.
TL;DR
A transition plan moves responsibilities, knowledge, and relationships from one person to another during a change. A complete plan names an owner and a transfer date for every responsibility, records the state of open work, schedules contact introductions, captures what only one person knows, and closes out systems and access. Six free templates below covering departure, role change, leave cover, manager handover, a handover note, and a tracker. No signup.
What a Transition Plan Is
A transition plan is a document that sets out how responsibilities, knowledge, and relationships pass from one person to another during a change. It answers three questions in writing: who takes each piece of the work, by when, and what has to be transferred for them to actually do it.
It is worth separating from the two documents it gets confused with. An offboarding checklist covers the administrative close-out, which is one section of a transition plan rather than the whole thing. A handover note is written by the departing employee for their successor. The plan is the management document that makes sure nothing falls into the gaps between people.
How Often This Actually Happens
In June 2026, the number and rate of quits in the United States were unchanged at 3.2 million and 2.0 percent, with total separations of about 5.3 million (U.S. Bureau of Labor Statistics, JOLTS). A 2 percent monthly quit rate means that across a year, a business of twenty people should expect to run this process several times. It is a recurring operation, not an exception, which is the argument for having the document ready before you need it.
Four Kinds of Transition
The head term covers four different situations, and they are not interchangeable. What you are protecting against differs in each one, which is why there are separate templates below rather than one generic form.
Type
Trigger
Notice you get
What the plan protects
Departure
Resignation, termination, retirement, contract end
Two weeks, or none at all
Knowledge and relationships walking out permanently
Role change
Promotion or lateral move; the person stays
Usually weeks
The old work quietly following them into the new role
Leave cover
Parental, medical, military, or sabbatical leave
Often months
The handback, which is where cover arrangements fail
Manager handover
A manager or owner-operator steps out or across
Weeks to months
Decision rights and team relationships, not just tasks
The departure case is the one most templates are built for and the one where you get the least time. The other three get less attention and cause more quiet damage, particularly the internal move, where the transition is easy to skip precisely because nobody is leaving the building.
What Every Plan Includes
Eight elements, sorting into four groups. Whatever the type of transition, a plan missing any of these four groups will leak somewhere.
The header
Who is moving, and from what to what
Trigger and effective dates
Working days actually available
Who owns the plan itself
The work
Every responsibility with a name next to it
Transfer date per responsibility
Open projects with current status
Permanent or interim, stated
The people
Customers and vendors to hand over
Introductions with dates
Who to tell, and in what order
What only this person knows
The close-out
Systems, access, and equipment
Administrative and payroll items
Sign-off from both sides
A date when the transition is over
Two things get skipped more than anything else. The undocumented knowledge section is the one that requires an uncomfortable direct question and is the only reason to write the plan at all. And the closing date is what stops interim assignments from becoming permanent by default, which is how a small team ends up with the owner personally doing invoicing eight months later.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Pick by the type of transition. The tracker works alongside any of them if you would rather manage the moving parts in a spreadsheet than in a document.
Employee Departure
The common case
For a resignation, termination, retirement, or contract ending. Covers where each responsibility goes, the state of open work, relationships to transfer, what only this person knows, systems and property, the final week, and administrative close-out.
Role Transition
Internal move
For a promotion or lateral move, where the person is still here and the old work quietly follows them for months. Built around drawing an explicit line: what stops, what continues briefly, and what genuinely belongs to the new role.
Leave Cover and Handback
The one nobody writes
For parental, medical, or extended leave, where the work goes out and then has to come back. Includes what gets covered, what simply pauses, contact expectations agreed in advance, and a full return handback checklist.
Manager Transition
Decisions and relationships
For a manager or owner-operator handover. Leads with decision rights and spend limits, then the team context, in-flight initiatives, relationships, the unwritten operating rules, and a hard stop on the outgoing manager's availability.
Job Handover Note
Written by the employee
A note from the person leaving to the person taking over, not a form for the file. The recurring rhythm, what is open, where things live, the things you would say over coffee, and an honest list of what did not get finished.
Transition Tracker
Spreadsheet, four tabs
The tracking layer as an editable spreadsheet: responsibilities with transfer dates, projects with status and risk, key contacts with handover dates, and access and equipment with a done column. Pre-filled with a worked example.
If Someone Just Gave Notice
Open the departure template and the tracker together. Fill the tracker first, because listing the responsibilities is the part that takes real thinking and everything else follows from it, then use the document for the narrative sections the spreadsheet cannot hold: what only this person knows, the final week, and the sign-off. If you have more than two weeks, add the handover note and ask the departing employee to write it in their own words. It will contain things you would never have thought to ask about.
6 Free Transition Plan Templates
Download all six together as a zip file, or copy an individual template. Five are editable Word documents and one is an Excel workbook with four tabs. Fill in the brackets, delete what does not apply, and change anything that does not match how your business actually works.
Download All 6 Transition Plan Templates
Departure, role change, leave cover, manager handover, handover note, and the tracker. Five DOCX files and one XLSX, in a single zip.
Template 1: Employee Departure Transition Plan
The common case. Where each responsibility goes with a transfer date, the state of open work, relationships to hand over, what only this person knows, systems and property, the final week, and administrative close-out.
Employee Departure Transition Plan
TRANSITION PLAN: EMPLOYEE DEPARTURE
[Company Name]
Employee:
Role: Department: [ ]
Manager:
Reason: [resignation / termination / retirement / end of contract]
Notice given: [MM/DD/YYYY] Last day: [MM/DD/YYYY]
Working days remaining: [ ]
Plan owner: Date written: [MM/DD/YYYY]
1. WHERE THE WORK GOES
Every responsibility needs a name next to it before the last day. Interim is
fine. Unassigned is not, because unassigned means it lands on whoever notices
it failing, usually three weeks later.
Responsibility | Goes to | Transfers on | Permanent?
[ ] | [name] | [MM/DD] | [Y / interim]
[ ] | [name] | [MM/DD] | [ ]
[ ] | [name] | [MM/DD] | [ ]
[ ] | [name] | [MM/DD] | [ ]
[ ] | [name] | [MM/DD] | [ ]
[ ] | [name] | [MM/DD] | [ ]
Anything with no name next to it by [date]:
2. OPEN WORK AND ITS STATE
For each active project, the status a successor needs to pick it up cold.
Project: [ ]
Where it stands: [ ]
What happens next, and by when: [ ]
Who else is involved: [ ]
Where the files live: [ ]
The thing that will surprise the next person: [ ]
Project: [ ]
Where it stands: [ ]
What happens next, and by when: [ ]
Who else is involved: [ ]
Where the files live: [ ]
The thing that will surprise the next person: [ ]
3. RELATIONSHIPS AND CONTACTS
Customer, vendor, or partner | Who they call now | Introduced by | Date
[ ] | [name] | [ ] | [MM/DD]
[ ] | [name] | [ ] | [MM/DD]
[ ] | [name] | [ ] | [MM/DD]
Notify externally: [who needs to hear this from you before they hear it
elsewhere, and what you are going to say]
4. WHAT ONLY THIS PERSON KNOWS
The recurring tasks, workarounds, passwords-in-a-head, supplier quirks, and
undocumented steps that exist nowhere else. Ask directly: "what would break if
you were unreachable for a month?" The answer to that question is this section.
Access removal timing: [same day as the last day, and earlier for financial
systems if the departure is involuntary]
6. THE FINAL WEEK
Day | What happens
[ ] | [Handover session with successor]
[ ] | [Customer or vendor introductions]
[ ] | [Documentation review, gaps closed]
[ ] | [Exit conversation]
[ ] | [Equipment returned, access removed, final pay confirmed]
7. ADMINISTRATIVE CLOSE-OUT
•[ ] Final paycheck timing confirmed against state rules
•[ ] Unused paid time off handled per policy and state law
•[ ] Benefits end date communicated, continuation notice sent if required
•[ ] Retirement plan and any outstanding reimbursements addressed
•[ ] Personnel records retained per federal and state requirements
•[ ] Exit conversation held and recorded
8. SIGN-OFF
Employee: Date:
Manager: Date:
Successor or interim owner: Date:
DISCLAIMER: This is a sample template for general information only and is not
legal advice. Final pay timing, paid time off payout, benefit continuation, and
record retention are set by federal and state law and vary considerably. Confirm
the rules for your state before use.
Template 2: Role Transition Plan
For a promotion or lateral move where the person is still here. Built around an explicit line: what stops on a date, what continues briefly, and what genuinely belongs to the new role, plus a 30-60-90 ramp.
Role Transition Plan (Internal Move)
TRANSITION PLAN: INTERNAL ROLE CHANGE
[Company Name]
Employee:
Moving from: [current role] To: [new role]
Effective: [MM/DD/YYYY] Overlap period: [ ] weeks
Current manager: [ ] New manager: [ ]
Plan owner: Date: [MM/DD/YYYY]
An internal move has a problem a departure does not: the person is still here.
Which means the old work quietly follows them for months unless somebody draws
a line. This plan draws the line.
1. THE LINE
Stops doing on [MM/DD]:
•[ ]
•[ ]
•[ ]
Keeps doing until [MM/DD], then stops:
•[ ]
•[ ]
Keeps permanently, because it genuinely belongs to the new role:
•[ ]
Who to ask instead, once the line is drawn: [name]
2. WHERE THE OLD WORK GOES
Responsibility | Goes to | Transfers on | Trained on
For parental, medical, or extended leave. Covers what gets covered, what simply pauses, contact expectations agreed in advance, and the return handback checklist that most templates leave out entirely.
Leave-of-Absence Cover Plan and Handback
TRANSITION PLAN: LEAVE COVER AND RETURN
[Company Name]
Employee: Role: [ ]
Type of leave: [parental / medical / military / sabbatical / other]
Most transition plan templates stop at the departure. Leave cover is the harder
version, because the work goes out and then has to come back, and the coming
back is where it usually falls apart: access was removed, projects moved on,
and nobody re-briefed anyone.
1. WHAT GETS COVERED
Responsibility | Covered by | From | Until | Notes
[ ] | [name] | [MM/DD] | [MM/DD] | [ ]
[ ] | [name] | [MM/DD] | [MM/DD] | [ ]
[ ] | [name] | [MM/DD] | [MM/DD] | [ ]
2. WHAT GETS PAUSED
Not everything needs covering. Say plainly what simply stops until they return,
so the covering person is not quietly carrying it.
•[ ] pauses until return
•[ ] pauses until return
3. HANDOVER BEFORE THE LEAVE
•[ ] Covering person shadows the work for [ ] days before the start date
•[ ] Open projects documented with current status
•[ ] Key contacts introduced to the covering person
•[ ] Recurring deadlines listed with dates
•[ ] Temporary access granted, with an end date attached
•[ ] Team and customers told who to contact and until when
4. CONTACT DURING LEAVE
Agree this in advance and in writing, because the default is a stream of
"quick questions" that nobody intended to send.
Contact expectation: [none / emergencies only, defined as: ]
Who decides what counts as an emergency: [name]
How to reach them, if at all: [ ]
5. RETURN HANDBACK CHECKLIST
The section nobody writes and everybody needs.
Before the return date:
•[ ] Access and permissions restored
•[ ] Equipment ready and working
•[ ] Schedule confirmed, including any phased or reduced start
•[ ] Team told the return date
Week one back:
•[ ] Written brief on what changed: people, tools, customers, priorities
•[ ] Covering person walks through what happened and what is open
•[ ] Projects formally handed back with a date on each
•[ ] Temporary access for the covering person removed
•[ ] Check-in at the end of week one
Ramp:
Week 1: [reduced load / observation / full]
Week 2 to 4: [ ]
Fully back by: [MM/DD]
6. LEGAL NOTES
•Federal family and medical leave protections apply to employers of a certain
size; smaller employers are often outside them, but state and local leave
laws may still apply and are frequently broader.
•Where leave is job-protected, the employee generally returns to the same or
an equivalent position. Do not let a cover arrangement quietly become
permanent.
•Keep medical information separate from the personnel file.
•Confirm your obligations before writing the plan, not after.
7. SIGN-OFF
Employee: Date:
Manager: Date:
Covering person: Date:
DISCLAIMER: This is a sample template for general information only and is not
legal advice. Leave entitlements, job restoration rights, and notice
requirements are set by federal, state, and local law, depend on employer size,
and change over time. Confirm current requirements before use.
Template 4: Manager Transition Plan
For a manager or owner-operator handover. Leads with decision rights and spend limits, then team context, in-flight initiatives, the unwritten operating rules, and a hard stop on the outgoing manager's availability.
Manager Transition Plan
TRANSITION PLAN: MANAGER OR OWNER-OPERATOR
[Company Name]
Outgoing: Role: [ ]
Incoming:
Transition window: [MM/DD] to [MM/DD]
Team size affected: [ ]
Plan owner: Date: [MM/DD/YYYY]
A manager transition moves three things at once: the tasks, the decisions, and
the relationships. Most plans cover the first and lose the other two, which is
why the team can feel leaderless for a quarter after a clean-looking handover.
1. DECISION RIGHTS
The part that matters most and gets written down least. Say who decides what,
and from when.
Decision | Now decided by | From [MM/DD] | Spend limit
[Hiring for the team] | [ ] | [ ] | [ ]
[Approving time off] | [ ] | [ ] | [ ]
[Purchases and vendors] | [ ] | [ ] | $[ ]
[Schedule and coverage] | [ ] | [ ] | [ ]
[Escalations from customers] | [ ] | [ ] | [ ]
[Pay and performance decisions] | [ ] | [ ] | [ ]
2. THE TEAM
For each direct report: where they stand, what they are working on, what they
have been promised, and anything the incoming manager should not learn by
accident in month two.
Name: [ ]
Currently focused on: [ ]
Commitments made to them: [ ]
Review or raise due: [MM/DD]
Context worth knowing: [ ]
Name: [ ]
Currently focused on: [ ]
Commitments made to them: [ ]
Review or raise due: [MM/DD]
Context worth knowing: [ ]
3. IN FLIGHT
Initiative | Stage | Next milestone | Who else depends on it
[ ] | [ ] | [MM/DD] | [ ]
[ ] | [ ] | [MM/DD] | [ ]
4. RELATIONSHIPS TO TRANSFER
Person or account | Relationship history | Handover meeting | Done
[ ] | [ ] | [MM/DD] | [ ]
[ ] | [ ] | [MM/DD] | [ ]
5. HOW THINGS ACTUALLY RUN HERE
[The unwritten operating rules: which meetings matter, how the busy season
works, which customer always calls on Friday, what the team expects that was
never a policy. This section is the difference between a successor who is
technically in charge and one the team follows.]
6. THE ANNOUNCEMENT
Told first, in person: [ ]
Told next: [ ]
Told at the same time as everyone: [ ]
Customers and vendors told by: [MM/DD]
Message: [ ]
7. AFTER THE HANDOVER
Outgoing manager available until: [MM/DD], for [ ] hours per week, for
[questions only / named open items]
Hard stop on that availability: [MM/DD]
Check-in at 30 days: [MM/DD] At 90 days: [MM/DD]
8. SIGN-OFF
Outgoing: Date:
Incoming: Date:
Owner or executive: Date:
DISCLAIMER: This is a sample template for general information only and is not
legal advice.
Template 5: Job Handover Note
Written by the person leaving, for the person taking over. The recurring rhythm, what is open, where things live, the things you would say over coffee, and an honest list of what did not get finished.
Job Handover Note (Written by the Employee)
HANDOVER NOTE
From: Role: [ ]
To:
Last day: [MM/DD/YYYY]
Written: [MM/DD/YYYY]
Written by the person leaving, for the person taking over. Not a form for the
file; a note to a colleague. Assume they know nothing about your job and are
reading this on their second day while three people wait for answers.
WHAT THIS JOB ACTUALLY IS
[Two or three sentences describing the role as it is really performed, not as
the job description says. What the week revolves around. What you spend the
most time on that nobody expects.]
THE RECURRING RHYTHM
Every day: [ ]
Every week, on [day]: [ ]
Every month, by [date]: [ ]
Quarterly or seasonal: [ ]
If you miss one of these, here is what breaks and when you will notice: [ ]
WHAT IS OPEN RIGHT NOW
[Item]
Status: [ ]
Next action and deadline: [ ]
Who to talk to: [ ]
Files: [ ]
[Item]
Status: [ ]
Next action and deadline: [ ]
Who to talk to: [ ]
Files: [ ]
PEOPLE
Name | What they need from you | How they prefer to be reached | Worth knowing
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
WHERE THINGS LIVE
[System or file]: [where, and how to get in]
[System or file]: [where, and how to get in]
[The folder that is badly named but has everything in it]: [ ]
THINGS I WOULD TELL YOU OVER COFFEE
[The workarounds, the process that looks wrong but exists for a reason, the
supplier who needs chasing twice, the report nobody reads. This is the most
valuable section in the document and it will feel like the least professional
one. Write it anyway.]
•[ ]
•[ ]
•[ ]
WHAT I DID NOT FINISH
[Be honest here. An unfinished thing you name is a task. An unfinished thing
you hide is a surprise, and it will land on this person with your name on it.]
•[ ]
•[ ]
REACH ME AT
[Optional and entirely your choice. If you offer it, put a limit on it so it
does not become an unpaid second job.]
Contact: [ ] Available until: [MM/DD]
DISCLAIMER: This is a sample template for general information only and is not
legal advice. Do not include passwords or confidential customer data in this
document; transfer credentials through your password manager instead.
Template 6: Transition Tracker (Spreadsheet)
Four tabs: responsibilities with transfer dates and a permanent-or-interim column, projects with status and risk, key contacts with introduction dates, and access and equipment with a done column. Pre-filled with a worked example you can clear.
Transition Tracker
A
B
C
D
E
F
G
H
1
Responsibility
Frequency
Current owner
Goes to
Transfer date
Permanent or interim
Trained
Notes
2
Weekly customer invoicing
Weekly
A. Rivera
M. Chen
2026-09-04
Interim
Yes
Runs Thursdays, before 3pm cutoff
3
Supplier order approvals
Daily
A. Rivera
M. Chen
2026-09-01
Permanent
Yes
Approval limit raised to $2,500
4
Month-end close checklist
Monthly
A. Rivera
Owner
2026-09-30
Interim
No
Needs one full cycle side by side
5
Scheduling and shift coverage
Weekly
A. Rivera
D. Okafor
2026-08-28
Permanent
Yes
6
Vendor contract renewals
Quarterly
A. Rivera
Owner
2026-09-30
Interim
No
Two renewals due in Q4
7
New hire paperwork
Ad hoc
A. Rivera
D. Okafor
2026-09-01
Permanent
No
Walk through once before last day
8
9
10
11
How to Build One in Two Weeks
Two weeks is what you usually get, and the person is still doing their job during them. So the plan has to be built in the order that survives running out of time.
Inventory the work first
Sit with the person and list everything they do in a normal month, including the recurring tasks nobody else has ever touched. You cannot assign work you have not named.
Rank it, then assign it
Sort by what costs money or loses a customer when it fails. Put a name and a date next to every item at the top of that list, and mark whether it is permanent or interim.
Tell people in the right order
The team, then customers and vendors, with a named replacement contact. A transition nobody announced is a transition that did not happen operationally.
Close it out and date it
Sign off both sides, remove access on schedule, and set a review date to check whether the interim assignments are still working or have quietly become permanent.
The ranking step is the one people skip, and it is what makes a two-week transition survivable. You are not going to transfer everything. Sorting by consequence means that when day nine arrives and half the list is untouched, the half still standing is the half that does not matter much. Skipping the ranking means you find out which half mattered in November.
One more thing worth building into the timeline: the introductions. Handing a customer over in a forwarded email after the last day is not a handover, it is a notification. A five-minute call with both people on it, before the departure, is the difference between a relationship that transfers and one that quietly goes looking elsewhere.
Leave Cover and the Handback
Leave cover is the transition type that gets the most notice and the least planning, because months of warning make it feel like there is time. Then the leave starts, the cover holds, and the failure arrives on the return date: access was removed, projects moved on without a record, and nobody briefed anyone.
The leave template above is built around that return. It separates what gets covered from what simply pauses, which stops the covering person quietly absorbing a second job. It puts the contact expectation in writing before the leave starts, because the default is a steady stream of quick questions nobody intended to send. And it ends with a handback checklist covering access restored, a written brief on what changed, projects formally handed back with a date on each, and temporary access removed.
Federal Leave Law May Not Cover You, and That Changes Nothing Operationally
Federal family and medical leave protections generally apply to private employers with 50 or more employees, and an employee must also have worked at least 12 months, have at least 1,250 hours of service, and work at a location with at least 50 employees within 75 miles (U.S. Department of Labor, Fact Sheet #28). Most businesses in the range this page is written for sit outside that. State and local leave laws are frequently broader and catch far smaller employers, so check yours. Either way the operational problem is identical: the work has to go somewhere and then come back. This is general information, not legal advice.
Where leave is job-protected, the employee generally returns to the same or an equivalent position, which is worth remembering when a cover arrangement starts working well.
Without an HR Department
Every transition plan template written for a large company assumes a documented process, a named successor, and a quarter to run it. At fifteen people you have none of those. Three things go wrong, and they are the same three every time.
One person is the only one who knows how something works
At twelve people this is not a risk, it is the normal state. Someone has been quietly running a process for three years and it exists nowhere except in their habits. The transition plan is the only moment you are ever going to get that out of their head, and you get about two weeks. Ask the direct version of the question: what breaks if you are unreachable for a month?
Two weeks of notice, and one of them is already booked
A large company plans a transition over a quarter. You have ten working days, and the person is also finishing their actual job. So do not attempt a complete knowledge transfer. Rank the work by what costs money or loses a customer when it fails, cover the top of that list properly, and accept that the rest gets figured out. A partial plan executed beats a thorough one abandoned on day three.
The work has no obvious place to land
In a small team there is often no second person who does anything like this job, so responsibilities get split awkwardly or land on the owner by default. That is survivable if it is deliberate and written down with a review date. It is not survivable when it happens silently, because six weeks later nobody remembers who agreed to take the invoicing and it has not been done since.
The practical answer is smaller than it looks. One document, ten working days, the top of the ranked list handled properly, and a review date. If the same knowledge keeps turning out to live in one head, that is a knowledge management problem worth fixing between departures rather than during one.
Plan vs Handover Note vs Checklist
Three documents get used interchangeably, and then somebody produces a checklist and calls the transition covered. They do different work.
Document
Written by
Covers
Ends when
Transition plan
The employer or manager
Who takes which work, by when, plus contacts and close-out
The transition date you set
Handover note
The departing employee
How the job is really done, what is open, what nobody documented
The last day
Offboarding checklist
Whoever runs admin
Final pay, benefits, equipment, access, records
The administrative close-out
You want all three for a departure, and they are not much work together because each covers what the others cannot see. The plan handles the gaps between people, the note carries the knowledge, and the offboarding checklist handles the administration.
Sign, Store, and Close It Out
The templates work on their own, printed and filled in. What tends not to work is what happens after: the plan lives in the manager's downloads folder, the interim assignments never get reviewed, and access removal happens whenever somebody remembers.
Three habits fix most of it. Sign it, so both sides have agreed to the same list rather than a shared impression of it. Put a closing date on the transition and actually check it, because that is when you find out which interim arrangements have become permanent without a conversation. And run access removal on the written schedule, with financial systems handled on the last day rather than after it.
That is the part FirstHR handles: the transition plan attaches to the employee profile alongside the rest of their record, sign-off comes back e-signed with a dated record, and the tasks in the plan become assigned items with owners and due dates rather than lines in a document nobody reopens. FirstHR is an onboarding and HR platform, not a payroll provider and not a law firm, so it does not issue final pay, calculate leave entitlements, or advise on state requirements. Applicant tracking is coming soon to FirstHR.
Key Takeaways
A transition plan moves responsibilities, knowledge, and relationships; an offboarding checklist only covers the administrative close-out.
Four transition types need different plans: departure, internal role change, leave cover, and manager handover.
Every responsibility needs a name and a transfer date next to it, marked permanent or interim. Unassigned means it lands on whoever notices it failing.
With two weeks of notice, rank the work by what costs money or loses a customer when it fails, and cover the top of that list properly.
Ask the direct question about undocumented knowledge: what breaks if you are unreachable for a month?
Leave cover fails on the return, not during the leave, which is why the handback checklist matters more than the cover plan.
Put a closing date on the transition, or interim assignments become permanent without anyone agreeing to it.
Frequently Asked Questions
What is a transition plan template?
A transition plan template is a reusable document for moving responsibilities, knowledge, and relationships from one person to another during a change. That change might be a departure, an internal role move, a period of leave, or a manager handover. A complete plan covers four things: the header saying who is moving and by when, the work itself with a named owner and a transfer date against every responsibility, the people including customers and vendors who need introducing, and the close-out covering systems, access, equipment, and sign-off. The template supplies that structure so you fill in specifics rather than deciding the shape while someone is working their notice.
What should a transition plan include?
Eight things. Who is transitioning, from what to what, and the dates. Every responsibility with a name and a transfer date next to it, marked permanent or interim. Open projects with their current status, the next action, and the deadline. Key contacts with a new point of contact and an introduction date. The undocumented knowledge that exists only in one person's head. Systems, access, equipment, and property with a removal or return date. Administrative close-out including final pay, benefits, and record retention. And sign-off from both sides plus a date when the transition is formally over. The two most often skipped are the undocumented knowledge and the closing date, and both cause problems weeks later.
How do you write a transition plan for a departing employee?
Start by inventorying the work rather than assigning it, because you cannot hand off what nobody has named. Sit with the person and list everything they do in a normal month, including the recurring tasks nobody else has touched. Then rank that list by what costs money or loses a customer when it fails, and put a name and a date against everything at the top. Ask the direct question about undocumented knowledge: what breaks if you are unreachable for a month? Schedule customer and vendor introductions rather than sending an email. Then handle systems and access on a written schedule, hold the exit conversation, and get both sides to sign. Two weeks is usually all you get, so cover the top of the list properly and accept that the rest gets figured out.
How long should a transition period be?
Two weeks is the common notice period in the United States and is usually what you actually get, though nothing federal requires it. That is roughly ten working days, and the departing person is still doing their job during them, so treat the time as scarce. For a manager or owner-operator handover, four to eight weeks with a defined overlap works better because decisions and relationships transfer more slowly than tasks. For leave cover, start the handover at least two weeks before the leave begins and plan a ramp on the return rather than a hard restart. Whatever window you have, put a closing date on the plan, because a transition with no end date turns interim arrangements into permanent ones nobody agreed to.
What is the difference between a transition plan and a handover note?
A transition plan is written by the employer and covers the whole change: who takes which responsibility, on what date, plus systems, access, contacts, and administrative close-out. It is a management document and it gets signed and filed. A handover note is written by the departing employee for whoever takes over, and it is a note to a colleague rather than a form for the file. It covers the recurring rhythm of the job, what is currently open, where things live, and the workarounds nobody documented. You want both. The plan makes sure nothing falls through the gaps between people, and the note carries the knowledge that no plan structure will surface on its own.
Do you need a transition plan for an internal promotion?
Yes, and it is the case people most often skip because the person is not actually leaving. That is exactly the problem: the old work quietly follows them for months, because colleagues keep asking the person who has always answered, and the new role never gets their full attention. A role transition plan draws an explicit line: what stops on a date, what continues briefly and then stops, and what genuinely belongs to the new role. It also names where the old work goes, states whether a backfill is happening, and announces the change in writing to the team and to any customers affected. Add a check at day 30 asking whether anything is still landing on them.
Are these transition plan templates free to download?
Yes. All six download free with no email form and no account: five as editable Word documents and one as an Excel spreadsheet with four tabs. Downloading all six at once gives you a single zip file containing each of them separately. That is worth checking elsewhere, because several of the widely-linked transition plan templates require a free account to use the template inside the vendor's own app, and template libraries often put the more complete versions behind an upgrade. Free also does not mean finished: fill in the brackets, delete what does not apply, and change anything that does not match how your business actually runs.
Who should own the transition plan?
One named person, and it should not be the person leaving. The departing employee is a contributor to the plan, often the most important one, but they have an end date and no ability to chase anything after it. At a small business the owner is the natural plan owner for a departure or a manager handover, and the receiving manager works well for an internal role move. Whoever it is, their name goes at the top of the document, they hold the deadline for unassigned items, and they run the close-out. A plan with no owner is a list of good intentions, and the reliable way to spot one is that every responsibility has a suggested destination and nothing has a date.
