An Excel process becomes a key-person risk when one employee is the only person who knows how to run it properly.
The problem is rarely the workbook alone. It is the unwritten knowledge around it: which source file to use, when to refresh figures, which exceptions are acceptable, who approves a change, and what to do when the numbers do not look right.
Forwarding the file is not the same as handing over the process. If a colleague cannot run the workflow without repeatedly asking the former owner for help, the handover is incomplete.
Excel remains useful for modelling, forecasting, ad-hoc analysis and flexible calculations. But where a workbook supports a repeatable operational process, such as job tracking, production planning, quotations, approvals or recurring reporting, the surrounding operating knowledge needs to be transferable.
What makes an Excel process dependent on one person?
A process can appear familiar to the team while still relying heavily on one person's memory. This becomes visible during annual leave, sickness, a role change or resignation.
Common warning signs include:
- Only one person knows which workbook, tab or source file is authoritative.
- Instructions exist only in emails, chat messages or informal conversations.
- Manual overrides are applied without a written rule for when they are needed.
- A colleague can complete routine steps but cannot handle an exception.
- Approvals happen outside the workbook and are difficult for cover staff to find.
- The process relies on personal folders, personal access or relationships with particular people.
- Nobody has tested whether the nominated backup can complete a full run independently.
These signs do not automatically mean Excel must be replaced. They do mean the business should treat the workflow as an operational continuity issue rather than a simple file-sharing issue.
For a broader way to identify whether a workbook supports an important operating process, see what makes an operational spreadsheet business-critical.
Start with continuity, not workbook documentation
A useful handover starts by answering a practical question: if the current owner were unavailable tomorrow, what would another competent colleague need in order to complete the next cycle safely?
That question keeps the focus on the process rather than on cataloguing every formula or worksheet.
For example, a monthly reconciliation may involve more than opening a workbook and pressing refresh. The person running it may need to know:
- when source data is considered complete
- which invoices or records require separate treatment
- who can approve an unresolved difference
- where previous exceptions are recorded
- which output is used by finance, operations or management
- what to do if an input is missing or late
The aim is not to turn a handover into a large transformation project. It is to make the next run repeatable by someone other than the person who developed the routine.
Practical test: a handover is working when the backup can run the process, identify an exception and follow the agreed escalation route without relying on the original owner.
Create a repeatable Excel handover pack
A handover pack should explain how the process operates, not merely where the workbook is stored.
Keep it short enough to be used, but specific enough to support cover during a real absence. A simple pack can include the following.
1. Process purpose and trigger
State what the process produces, why it matters and what starts each cycle.
For example: “Prepare the weekly job-status report once operations has confirmed the current job list.” This gives the backup a clear starting point and helps them understand the output's purpose.
2. Named roles and backup cover
Identify who normally performs the work, who can cover it and who can resolve issues outside the routine.
Avoid relying on a job title alone. Roles change, and a named backup makes the continuity expectation clearer.
| Process role | Handover question |
|---|---|
| Process owner | Who is responsible for keeping the instructions current? |
| Day-to-day operator | Who completes the routine work? |
| Backup operator | Who can run the next cycle if the operator is absent? |
| Approver | Who can confirm an exception or final output? |
| Escalation contact | Who decides what happens when the routine cannot be completed? |
3. Inputs, outputs and authoritative locations
List the inputs required, where they come from and where the final output is published or used.
This is not a general file-naming exercise. It is about helping cover staff find the correct information quickly and avoid using an old copy or an informal substitute.
Include:
- the authoritative workbook location
- the source files or systems used
- the expected timing of each input
- the final report, register or operational action produced
- the location for supporting notes or exception records
4. Routine steps
Document the normal sequence in plain language. Include the checks that matter, not every mouse click.
A usable routine might say:
- Confirm that the expected source information is available.
- Update the workbook using the agreed source.
- Check the agreed totals, statuses or exceptions.
- Record any unresolved issue.
- Obtain approval where the process requires it.
- Publish or communicate the approved output.
5. Exception rules
This is often the most important part of an Excel process handover.
The next person needs to know what is normal, what is unusual and what they are authorised to decide. Record common exceptions, the evidence required and the person who can approve a departure from the routine.
Examples may include a late supplier file, an incomplete job record, a disputed value or a missing approval. The guidance should say what to do, rather than expecting the backup to infer the answer from previous versions of the workbook.
6. Access and contact information
A handover can fail even when the instructions are good if the backup cannot access the required folders, systems or shared mailbox.
Check that access reflects the roles involved and that the backup knows where to seek help. Where permissions need to be changed, make the request before an absence rather than during a time-sensitive process run.
Test the handover before it is needed
Documentation is only useful if someone can follow it under normal working conditions.
Ask the nominated backup to complete a supervised or low-risk run using the handover pack. The original owner can observe at first, but the test should show whether the instructions stand on their own.
Use the test to answer four questions:
- Could the backup locate the right workbook and inputs?
- Could they complete the normal process without undocumented steps?
- Could they recognise and deal with a realistic exception?
- Did they know who could approve or resolve an issue?
Any gaps found during the test should be added to the pack. This is more valuable than producing extensive documentation that nobody has tried to use.
Continuity check: do not assume that a named backup is genuine cover until they have completed the process themselves.
Keep Excel where it remains suitable
Not every spreadsheet needs a new system. A controlled workbook can remain appropriate where the work is occasional, analytical or exploratory, and where the process can be understood and covered by more than one person.
For example, Excel can be a sensible choice for:
- financial modelling and forecasts
- one-off analysis
- flexible scenario work
- temporary trackers
- calculations that do not require a shared operational workflow
The priority is to remove unnecessary dependency on an individual. That may mean clearer instructions, a reliable storage location, backup access and a regular continuity test.
When a managed custom application may be the stronger continuity option
A different approach may be worth considering when the spreadsheet has become the working system for a recurring business process.
This can happen when several people need to enter, review or approve information; when the process relies on repeated exception handling; or when the business needs a clearer way to guide each role through the same workflow.
A managed custom web application can be a better fit for a stable operational process that needs structured access, defined workflow steps and an operating model that is not centred on one employee's personal workbook knowledge.
The decision should still be driven by the workflow, not by workbook size or company size. One user can have a business-critical process, and a small workbook can still create material continuity risk.
Spreadsheet Upgrade provides fully managed custom web applications for business-critical operational Excel workflows. The purpose is not to replace every spreadsheet. It is to provide a more controlled operational workflow where a file and informal knowledge are no longer sufficient.
For an overview of the managed approach, see how Spreadsheet Upgrade works.
Keep detailed replacement work separate from the handover
A handover pack should make the current process repeatable. It should not become a general migration plan unless the business has already decided that a replacement is appropriate.
If you are evaluating a move away from a business-critical workbook, use the handover material as evidence of what the replacement needs to preserve: the operating rules, exception paths, approval points, access requirements and outputs that another person must be able to complete.
For detailed guidance on defining those needs, see the operational spreadsheet replacement requirements checklist. For a separate discussion of moving records and validating a replacement workflow, see data migration best practices.
A managing director's handover checklist
Before the next absence, role change or planned handover, ask:
- Is there a named owner and a named backup for the process?
- Can the backup find the authoritative workbook, inputs and output location?
- Are the routine steps and exception rules written down?
- Can the backup obtain the access and approvals they need?
- Has someone other than the owner completed a test run?
- Does the process still suit a controlled workbook, or has it become a shared operational workflow that needs more structure?
If the answer to several of these questions is no, the immediate priority is to reduce dependency on memory and informal workarounds.
Start with a Free Fit Check
If an important Excel process depends on one person, a Free Fit Check can help assess whether the workflow is better served by tighter spreadsheet controls or a managed custom application.
The objective is straightforward: make sure a business-critical process can continue when the person who knows it best is unavailable.