When a spreadsheet needs a workflow

Start with the moment the work changes hands

Consider an illustrative example: a reception team records a delivery in a shared sheet. Someone adds the recipient, someone else sends an email, and a colleague later marks the parcel collected. The rows may be accurate while the process is still unclear. Was the email actually sent? Who checked the collection? What happens when the first person leaves for the day?

Write down one record's journey, from arrival to completion. For each step, name the person responsible, the information they need and what tells the next person to act. If the journey depends on remembering to tell someone, that is the first thing to examine. It does not automatically mean you need new software.

Ask five questions before changing tools

• Can a colleague tell what needs attention without asking the person who entered it?
• Does every open item have an owner and an unambiguous next step?
• Can people see only the information they need for their role?
• Can you explain who changed a record and why?
• Can the team complete a handover when someone is absent?

Answer with a recent example rather than a general impression. One missed notification might call for a clearer routine. Repeated missed notifications across different shifts suggest the routine needs stronger support. A purpose-built tool earns its place by addressing a specific failure you can describe.

Try the smallest workable improvement

Before replacing the sheet, try named owners, agreed status values and a short handover checklist. Keep one authoritative copy and document who can edit it. If these changes make the work dependable, there may be no reason to migrate yet.

If the same problems continue, create a short requirements list from the failures. For example: a recipient notification recorded against the parcel, an overdue list visible to the next shift, or an explicit check before a record can be closed. These are things you can demonstrate. A broad request for a dashboard is harder to evaluate.

Run a trial that includes the awkward cases

Use fictional records in a separate test workspace. Include a duplicate name, a person who is unavailable, a record entered incorrectly and a task that remains unfinished at shift change. Ask two colleagues to complete the process without coaching each other. The point is to see whether the tool carries the context that used to live in someone's head.

Decide what success means before the trial. You might require every open record to have a visible next step, every completed handover to show who finished it and every failed notification to be discoverable. Compare the result with your current process. Avoid treating the number of features as the result.

Plan the exit as well as the move

Ask what you can export, how attachments are handled and what happens when you stop using the service. Decide which old records need to move and which should remain in a controlled archive. Rehearse with a small sample, check it and keep the original unchanged until you have verified the transfer.

For venue teams, vFound brings lost and found, parcels, checkroom, equipment and visitors into a shared workspace. It is one of Naltyx's products. The decision to use it should still start with the work your team needs to carry through, and a trial that proves that work can be completed.

A spreadsheet is not a failure. It is often a useful starting point. Move on when you can name the missing process, show why it matters and verify that the replacement handles it better.