A spreadsheet can be perfectly familiar to its creator and confusing to everyone else. A tab called “New2”, a total with no explanation, or a weekly update that depends on memory can leave a colleague unsure where to begin.

The aim of a handover is not to turn every workbook into a large manual. It is to help another person complete the next real task with confidence, know what they should not change, and recognise when the result needs checking.

Start with the job the workbook supports

Write a short note at the beginning: what this workbook is for, who maintains it, when it is updated, and which decision or task its output supports. Include a link to the working copy rather than leaving several attachments competing for attention.

For a fictional weekly delivery tracker, the note might say: “Operations updates confirmed delivery dates each Friday. Dispatch uses the next-week view to prepare Monday’s schedule. Unconfirmed requests remain outside that view.” This tells a colleague more than “weekly report”.

The UK Government Digital Service’s spreadsheet guidance recommends clear context, meaningful names, consistent column headings and explicit versioning. These are useful starting points for a workbook that needs to make sense beyond its author.

Explain the route from input to result

Walk through a single record from the source to the final output. Where does the information come from? Which fields are entered by a person? Which values are calculated? What needs refreshing before the result is used?

Describe the expected sequence in ordinary language. For example: open the current orders export, check the reporting period, add the new rows, refresh the summary, then compare the number of orders with the source. Adapt the sequence to the actual workbook; do not add steps just because they sound thorough.

Mark the areas intended for entry and explain the calculations that would be difficult to reconstruct. Labels should carry the meaning; colour can support them but should not be the only instruction.

Agree what a useful check looks like

“Check the spreadsheet” is not an actionable handover. Name the checks that matter to its purpose. A delivery list might need a review of missing addresses and duplicate order references. A time tracker might need confirmation that the reporting dates cover the intended week.

Choose checks that a colleague can perform without knowing every formula. State what to do if a check fails: pause the handover, compare against the source, or ask the designated owner. An unusual result is a reason to investigate, not a reason to overwrite a number until it looks familiar.

Keep a small, non-sensitive example available where practical. It gives the next person a way to rehearse the steps without changing live work.

Keep the working copy easy to identify

Agree where the current workbook lives and who can edit it. Put obsolete copies out of the normal workflow, following your organisation’s retention arrangements. Do not delete records that may still be required.

If a file is shared outside the team, check what the recipient actually needs. Review the whole workbook, including hidden content and personal information, rather than assuming the visible sheet is all they will receive. Do not place passwords in the handover note; use your organisation’s approved access process.

Also explain where the source information lives. Access to a workbook is not necessarily access to the material needed to update it. Test the recipient’s access using their own account before the handover is considered complete.

Ask a colleague to perform the next update

The best review question is not “does this document make sense?” Ask the next person to complete one normal update using the instructions while you observe. Notice where they have to stop, guess or ask you a question.

Use those moments to improve the workbook or its note. Perhaps a field needs a clearer label. Perhaps a step assumes knowledge that has never been written down. Keep the instructions close to the work so that changes are easier to maintain.

A compact handover note

  • Purpose: the task or decision this workbook supports.
  • Working copy: where to find the current version.
  • Owner: who maintains it and who provides cover.
  • Update: the source, frequency and sequence.
  • Check: how to recognise a result ready for use.
  • Escalation: what to do when something does not match.

A successful handover leaves less unexplained knowledge in one person’s head. Start with the workbook your team relies on most, and test whether someone else can carry out its next update.

If the workbook sits inside a larger workflow, our guide to mapping a business process can help you see the surrounding handovers.