Start here.
Consider replacing the part of a spreadsheet that repeatedly leaves staff with conflicting answers or commitments. Follow a recent job, find where the problem starts, and compare a small repair with a replacement using the same example. Keep the parts of the workbook that still serve a clear purpose.
- Trace one recent mistake to the point where someone lost the latest answer.
- Separate useful calculations and planning from records people depend on to act.
- Test a repair and a replacement with the same real-life exception.
Follow one job from request to invoice
Imagine a small equipment rental business. The team uses a shared workbook to plan collections and returns. A customer extends a rental by phone. The person taking the call changes the return date in the workbook, but the colleague preparing the next collection is still looking at yesterday’s printed list.
The owner could buy a rental system. First, they need to know how the old date reached the next person. If everyone uses a live list except for the printed copy, the fix might be to change how the collection list is shared. If nobody can tell which changes are confirmed, who accepted them, or whether the same item has already been promised, the business has a bigger decision.
Pick a real job that went wrong and a similar one that went well. For each handoff, write down who knew the latest answer, where they recorded it, and what the next person actually saw. Include one late change. A tidy demonstration can hide the exact moment your team needs help.
Separate the workbook from the work it supports
List the things the workbook does today. It might calculate a deposit, show what is available, remind someone to call back, and give the owner a monthly total. Those jobs do not all have to move together. A workbook might still be the right place to work out next quarter’s prices even if it stops being the place where staff confirm a booking.
Ask the person who maintains the workbook to explain a confusing row, a formula someone is afraid to touch, and a note that staff treat as a rule. In the rental example, a blank return date might mean an extension is waiting for approval. If a replacement treats that blank as an available item, copying the records alone will not carry over the business decision.
Choose the smallest change you can test
Use this example to compare three possible fixes. Before trying one, agree where staff will read the confirmed return date and who will correct it if it is wrong.
If you are comparing a product with a repaired workbook, ask both to handle the same booking, extension and cancelled collection. Watch the person who receives each update. Where do they go for the latest answer, and what tells them it is safe to act?
| Choice | What to try | What to check |
|---|---|---|
| Keep the workbook | Give collection staff one shared view of confirmed dates. | Can they spot a late change before loading the vehicle? |
| Fix one handoff | Have staff confirm an extension once and send the change to the person planning collections. | Who follows up if nobody acknowledges the change? |
| Replace the booking workflow | Try a booking tool that can show the same item across an extension and a new request. | Can staff tell which booking is confirmed and avoid promising the same item twice? |
Decide what would make the trial worth continuing
Try the change with one clear slice of work, such as bookings for one equipment category. Record what happened before the trial, using recent jobs as a baseline. During the trial, note each time someone used an old date, had to ask a colleague to confirm availability, or entered a change twice. Also record any new work the fix created.
Agree on the decision before starting. If the team can work from one agreed list and the missing handoff disappears during a representative trial, keep the simpler arrangement and check it again after a busy period. If staff still have to reconcile conflicting promises, take those examples into a software demonstration. If the trial had only routine bookings, test an extension and a cancellation before deciding.
Name the place that holds the confirmed booking during the trial. If you test a second tool, agree which entries are practice and what must be copied back before you end the trial. Without that agreement, staff can leave the test with two equally plausible answers.
Bring the evidence when you ask for help
You can start with a short note: “We can work out prices in the workbook. The problem is that an extension can be accepted after the next collection has already been planned. We need both people to see the confirmed return date before making another promise.”
Bring a blank or anonymised copy of the relevant sheet, one ordinary job and one awkward change. Ask what would stay in the workbook, who would own the new record, and how the supplier would show the change working. If a supplier suggests replacing the whole workbook, ask them which part of your example requires that move.
Write a one-job brief
Use one completed job to help staff or suppliers understand the problem.
- Start and finish
- What started the job and how did the team know it was finished?
- Latest answer
- Which information changed, who confirmed it, and where was it recorded?
- Decision
- What would a trial need to show before you change the way the whole team works?
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Can we keep using spreadsheets after buying software?
Yes. You can keep a workbook for planning or calculations while using another tool for confirmed bookings or orders. Agree which place staff should trust for each decision and how information moves between them.
Should we transfer every worksheet to the new system?
Start with what people need for active work and what they need to look up. Discuss the rest separately. Explain formulas, notes and exceptions before deciding what to transfer.
What if the spreadsheet only causes problems when we are busy?
Include a busy-day example in the trial, including a late change or an absent colleague. A quiet week may tell you whether people understand the new routine, but it may leave the original problem untested.