what should a business handover include?

what is a business handover?

A business handover is the transfer of work, responsibilities and the knowledge someone needs to carry them on. It brings together what needs doing, where the information lives, how things work and who to ask, so the next person can pick things up with confidence.

It might cover an entire role, a single project or a regular task. The useful part is capturing the context as well as the documents: the decisions already made, the loose ends and the details that usually live in someone's head.

when might you need one?

Is someone leaving? Going on maternity leave? Taking an extended holiday? Being seconded to another team or organisation?

Whether the change is temporary or permanent, someone else needs to be able to pick up the work. A clear handover gives them the information, context and practical instructions to do that.

It can also help when you're delegating work, bringing in support or growing a team that relies heavily on one person for answers.

Without one, the next person can spend valuable time piecing things together. Deadlines, unfinished work and important details are easier to miss when nobody has a clear picture of what they're taking on.

You don't have to wait until someone is leaving. Capturing the important knowledge while there's time makes it easier to share responsibilities and keep things moving when plans change.

what should it cover?

Start with what someone will need on their first day, then add the detail they'll need as they settle in. The checklist below gives you a practical starting point.

1. what the role actually looks after

List the responsibilities, including the small jobs that rarely appear in a job description. Who checks the shared inbox? Who tracks renewals? Who knows which supplier to call when something goes wrong?

For each responsibility, record:

• What needs doing and why.
• How often it happens.
• Who is taking it over.
• Who approves decisions or provides support.

Where ownership hasn't been agreed, flag it clearly. A handover document can't quietly make that decision for the business.

2. what's happening now

Give unfinished work its own list. Include the current position, the next action, the person responsible and any deadline or dependency.

“Waiting for supplier” is a start. “Quote requested on Tuesday; follow up on Friday; director needs to approve before ordering” gives the next person something they can act on.

Separate urgent issues from things that can wait. Include known problems and decisions still needed, rather than leaving someone to discover them after you've gone.

3. the dates that matter

Bring together recurring commitments and upcoming dates: renewals, reporting deadlines, scheduled meetings, servicing, reviews or project milestones.

Record what must happen before each date and where the reminder lives. Check that the next owner can see the relevant calendar or tracker. A reminder attached only to a departing person's account won't make a very dependable handover.

4. how the important jobs are done

Prioritise the processes someone will need to repeat, especially those with several steps or an easily missed detail.

A practical how-to guide usually needs:

• The starting point and expected result.
• The steps in the order they're done.
• Links to the relevant files, templates or systems.
• Checks, approvals and common exceptions.
• What to do when the usual approach doesn't work.

Use plain language and screenshots where they clarify a step. Start with the processes that are frequent, time-sensitive or difficult to reconstruct. You can build the rest gradually.

5. where the information lives

Create a short map of the important folders, records, trackers and templates. Link directly to the current versions where possible, and explain any naming conventions that aren't obvious.

Check the links using the incoming person's access. A beautifully organised list of documents they can't open is still a problem.

Keep sensitive information in its appropriate restricted location. The general handover can explain where authorised people should find it without copying private records into a widely shared document.

6. who to contact, and what they know

Include the internal colleagues, suppliers and other contacts relevant to the work. Add their role, the reason someone might contact them and any useful context.

“Printer supplier” is less helpful than knowing whether that person handles servicing, billing or equipment orders. Keep the list relevant and use business contact details where available.

7. access and permissions

Identify the systems, shared inboxes, calendars and files the incoming person needs. Record who can arrange access and whether it has been checked.

Keep passwords and recovery codes out of the handover document. Account access, ownership changes and removal of outgoing access should follow the business's agreed arrangements, with the appropriate administrator or IT provider involved.

8. the final check

Give the handover a named owner and a last-updated date. Agree who maintains it after the transition.

Then ask the receiving person to use it for a real task. Can they find the right document, follow the steps and identify the next action without the outgoing person filling in the gaps?

That is often where you discover the missing detail. Allow time for questions while the person handing over is still available.

a simple starting structure

You can begin with six headings:

1. Responsibilities and new owners.
2. Current work and next actions.
3. Key dates and recurring tasks.
4. How-to guides and templates.
5. Files, systems and relevant contacts.
6. Access checks and questions still to resolve.

Use the tools your team already understands. A clear document with well-maintained links may be enough; a more complex role may need a shared knowledge library. The structure should make the work easier to pick up.

how much detail is enough?

Write for the person receiving it. Someone who knows the business may need context and exceptions; someone completely new may need each step explained.

Put the immediate priorities first. Keep reference material easy to find, and avoid burying urgent actions halfway through a long account of everything the role has ever involved.

Some roles also have formal employment, regulatory or professional handover requirements. This checklist covers practical organisation; those requirements need the appropriate specialist input.

when nobody has time to write it

The difficulty is often gathering the information while everyone is still doing their usual job. Documents are scattered, processes have changed and the person who knows the answers has a full calendar.

Ellie has brought that kind of scattered business knowledge together into practical handbooks and how-to guides. At Over To Us, we can help capture what matters, organise it and turn it into a handover your team can use.

We agree the scope, access, finished documents and project price before starting. Business information is handled professionally and confidentially.