Think about the last time you took over a job from someone else. Maybe it was running the neighbourhood group chat, looking after a family accounts folder, or stepping into a new role at work. Chances are the first few days felt like walking into a kitchen mid-recipe: pots on, no list, and the cook has left. That feeling has a name in the working world, and the cure for it is called a handover. This friendly primer explains what a handover is, why it matters, and the handful of words you will hear when people talk about it.
So what exactly is a handover?
A handover is the moment when one person passes responsibility for something to another, together with everything needed to carry it on. The key phrase is “everything needed”. Handing over a task without the context is like handing someone a key without telling them which door it opens.
You do not need to be in a big company to benefit. A handover can be a page of notes, a ten-minute chat, or a shared document with a few headings. What matters is that the next person can pick things up without redoing work that was already done.
Why a good handover saves so much effort
When things are passed on badly, the new person spends days working out what the previous one knew. This repeated effort is easy to underestimate because it never appears on any bill. It shows up as slow starts, avoidable mistakes and quiet frustration.
A clear handover, by contrast, lets the newcomer start from where the last person stopped. They spend their first week improving things rather than rediscovering them. Everyone wins, including the person who left, because nobody calls them at ten at night with a question that a note could have answered.
There is also a human side. People who leave a job well tend to be remembered well. A thoughtful note says, without any speeches, that you respected the work and the person who inherits it. It also protects you: when questions arrive months later, the answer is already written down, and you can simply point to it with a smile instead of trying to remember what you decided and why.
Finally, handovers are not only for people leaving. They happen every time someone goes on holiday, swaps teams or hands a project to a colleague for a busy week. Treat all of those as practice runs, and the big ones will feel ordinary.
The mini-glossary
Here are the terms you will meet most often. Learn these few and you will follow almost any conversation about passing work along.
- Handover note: the short written summary the leaving person prepares. It tells the reader what was done, what is pending and where things live.
- Open thread: a job that has begun but not finished. Open threads are the riskiest part of any handover, because they are easy to forget.
- Dead end: an approach that was tried and did not work. Recording these saves the next person from repeating the experiment.
- Owner: the single person responsible for a piece of work. A good note names an owner for each open thread, and says when ownership changes.
- Master copy: the place everybody has agreed to keep the latest version of a list or document, so no one edits an outdated duplicate.
- Walk-through: a live session where the leaver shows the receiver how things work, ideally while the receiver does the typing.
- Leave-behind window: a short, agreed period after departure during which the leaver will still answer questions.
- Access list: a record of who can open what, from shared folders to accounts and subscriptions.
The four questions every note should answer
If you remember nothing else from this primer, remember these. A decent handover note can be built from four questions answered in plain words.
What is finished?
List what is complete and where the proof sits. Keep it short and honest.
What is half-done?
Explain each unfinished item: the attempt, the outcome and your suggested next step. This part is gold.
Where are things kept?
Give a simple map of folders, accounts, spare keys, passwords managers and anything else the receiver will need to find.
What should I watch out for?
Mention the quirks, upcoming deadlines and the person to ask when something looks odd.
A tiny example from everyday life
Suppose you are passing on the job of organising a monthly community clean-up. Your handover note might say: the permission letter is finished and filed with the local office; the poster design is half-done and needs a new date; the bin bags are stored in the garage of a neighbour who will lend the key; and the person who coordinates volunteers prefers a message to a phone call. Four short paragraphs, and a stranger could run the next event.
Business handovers use the same ideas
The same four questions carry over to work. If you are curious about how businesses plan their online presence before handing a project to a team, a guide on mapping out digital growth plans shows how many moving parts there are and why somebody needs to keep track of them. And for anyone new to working with an outside provider, a walk through a services roadmap for first-time clients explains what usually happens from the first conversation onward. A sensible roadmap ends with a handover, though it is easy to forget to plan that final step.
Even technical setups follow this pattern. A web site, a cloud account and a few smart tools can add up to a lot of things to hand over, a point made well in a piece on combining web, cloud and smart tools. List each one, say who owns it and note where its login lives.
What if the helper is a freelancer?
Short-term helpers deserve a special mention, because their engagements end by design. A freelancer arrives, does a defined piece of work and moves on. If you are curious where people look for DevOps freelancers, DevOps FreeLancers is a portal that lists them by country and covers short engagements where a tidy handover really pays off. Ask early what you will receive at the end: notes, locations, a walk-through. It is much easier to agree this on day one than to request it from someone who has already started their next job.
Common beginner mistakes
- Writing the note on the last day. Start earlier, while there is still time to fix gaps.
- Using shorthand only you understand. Write for a smart stranger.
- Forgetting the access list. A note without the logins is half a note.
- Hiding the failures. Dead ends are useful, and nobody will judge them.
- Skipping the walk-through. Real practice finds what writing alone misses.
Your first handover in ten minutes
You can try this right now. Pick one small thing you look after: the shared shopping list, the club newsletter, the office plant rota. Open a blank page and write the four headings. Fill each in with a few honest lines. Then give the page to a friend and ask them one question: “Could you run this tomorrow?” Wherever they hesitate, add a sentence.
That small exercise teaches more than any long article. Handovers are not about paperwork. They are about being kind to the person who comes next, who will thank you quietly each time they find exactly what they need. Keep a copy of your note somewhere safe, update it when things change, and you will never again leave anyone standing in a kitchen with the pots on and no list.
