A spreadsheet handover checklist

Sending the file is the easy part. The receiver also needs to know what the workbook is for, where its data comes from, which numbers are sensitive, how to refresh it, what to do when it fails, and who can approve a change. Without that, the file is a dependency on the person who left.

Agree the scope before the handover meeting: which outputs, which period, which systems, and how much support follows. A handover with no end point becomes an informal help desk, and the receiver never gains ownership.

Freeze the version that will be handed over. Run the reconciliation, confirm the current output, and record the source data date. Remove personal data, temporary sheets, and unused links. Check that macros are signed, external references resolve, and the file opens without a repair prompt.

Archive a read-only copy of the handed-over version. Keep it separate from the working file so a later change can be compared with what was agreed. The archive is also the rollback point if the first week of use exposes a problem.

Put a cover sheet in the workbook with purpose, owner, inputs, outputs, refresh steps, dependencies, and the change log. Add a colour key if the workbook uses one, and list the named ranges and tables that carry important logic. The document should answer questions that would otherwise become messages.

Separate facts from assumptions. A source system, a refresh time, and a rate are facts with an origin; a forecast rule or an allocation method is an assumption with an owner. Mark the assumptions clearly so the next reviewer knows what to challenge.

The receiver should drive the walkthrough, not watch the sender. Ask them to refresh the data, trace one number to source, produce the output, and explain what they would do if a source file were missing. The gaps in that explanation are the real handover list.

Demonstrate a failure on purpose. Show the error message, the log, the rollback, and the person to contact. A receiver who has only seen the happy path will meet the first failure alone.

Access is more than a folder permission. List the source systems, shared mailboxes, query credentials, scheduled tasks, macro trust settings, and distribution lists the workbook depends on. Transfer each one explicitly, with the account or group that now owns it.

Name the new owner, the approver for logic changes, and the person who covers absence. Remove the previous owner's personal access only after the new owner has confirmed that the workflow runs without it. A shared account that nobody owns is a future outage.

Acceptance is a demonstration, not a signature. The receiver produces the output unaided, the totals reconcile, the failure path is understood, and the access checks pass. Record the evidence and the date.

Agree a support window and an escalation route, then close it on a stated date. Keep an issue log for the first cycles, review it with the new owner, and update the documentation when a fix changes the logic. The handover ends when the new owner can change the workbook safely, not when the file is copied.