Map a workflow before replacing its spreadsheet

A spreadsheet can hold a list and also quietly coordinate the work represented by that list. The distinction matters when several people depend on a row being updated at the right time.

Before replacing the file, follow one piece of work from arrival to completion. The aim is to understand the process the spreadsheet supports, including the steps currently held in conversations or someone's memory.

Start with one record

As an illustrative example, take a transport job. A row might contain a customer, collection address, delivery address, date and current stage. The actual work may also need a named owner, driver instructions, documents, a cancellation route and evidence that delivery happened.

Write down what each stage means. “Booked” might mean a customer has asked for a date, or that a driver and vehicle have been assigned. A system cannot resolve that ambiguity until the business agrees the definition.

Record the handoffs

For each change of stage, ask:

• Who can make the change?
• What information or document must exist first?
• Who needs to know afterwards?
• What happens if the next person is unavailable?
• How is an incorrect change corrected?

Include the ordinary exceptions: duplicate entries, missing details, a cancelled job and a document received after completion. These are part of the process, not unusual extras to discover after the build.

Separate the record from the view

The office, a driver and a manager may need different views of the same job. They do not necessarily need separate copies. Define the authoritative record, then decide which fields each person can see or change.

Also distinguish a calculated value from something entered by a person. If a total looks wrong, the team needs to know whether to correct an input or investigate a calculation.

Compare the smallest useful change

The next step might be a clearer shared sheet with protected fields, an established job-management product or a small internal tool. Compare the options against the workflow you have written down, including permissions, export and recovery.

If migration is needed, keep a copy of the original records and agree how the imported result will be checked. The appearance of a new dashboard is not evidence that the data moved correctly.

Use our buy, build or integrate guide for that decision, or explore the scope of a bespoke business system.