When a shared spreadsheet needs a workflow

A shared spreadsheet needs a workflow when the problem is ownership, status or controlled handoffs. Replacing the file with a new application will not resolve an undefined process by itself.

Identify what the spreadsheet is doing

A spreadsheet may be a calculation tool, a shared record, a work queue or an informal approval system. Those uses have different requirements. Ask the team what would stop if the file disappeared for a day and which decisions depend on it.

Look at the changes people make around the sheet: reminder messages, copied tabs, emailed versions and private notes. Those activities often reveal the actual workflow more clearly than the visible columns. Capture them before deciding which part should move.

Use the symptom to identify the requirement

Symptom	Requirement to clarify
Several versions circulate	One authoritative record and a controlled update route.
Rows have no clear owner	Assignment and visible responsibility.
Approvals happen in chat	Recorded authority tied to a specific version of the request.
Duplicate entries appear	Stable identifiers and duplicate handling.
Formula cells are overwritten	Appropriate edit boundaries and validation.
Nobody knows what is pending	Defined states, next actions and review ownership.

Keep useful calculations where they belong

Not every spreadsheet should become a custom application. A small, well-owned analysis may work well with clearer access, validation and documentation. The decision depends on the consequence of errors, number of contributors and need for traceable actions.

Separate calculation logic from process authority. A formula can calculate a total; it does not establish permission to approve the associated purchase. If the sheet combines both, document the boundary before automating data movement.

Design a small transition

An illustrative transition could replace free-form request rows with a structured intake while leaving a reviewed export for analysis. Another could add an approval record and status view without migrating years of historical data at once.

Define what remains authoritative during the transition. Avoid allowing both the old sheet and the new system to update the same record independently. Agree the cutover, reconciliation and fallback approach so staff know where new work belongs.

Prepare a migration decision record

• The current file owner and the people who use it.
• The fields, calculations and permissions that matter.
• The handoffs and exceptions happening outside the file.
• The records that must migrate and those that can remain archived.
• The tests that prove a representative case still works.

Use anonymised structure or synthetic rows for initial discussion. A full export of customer, employee or financial records is rarely necessary to explain the workflow problem.