Back to Blog
Blog

How do you replace a 4,000 line inspection spreadsheet with a usable workflow?

How do you replace a 4,000 line inspection spreadsheet with a usable workflow?

A spreadsheet that size usually started as a simple tracker and grew into the place where inspection scope, schedules, results and follow ups all live…

A spreadsheet that size usually started as a simple tracker and grew into the place where inspection scope, schedules, results and follow ups all live, which is why it is so hard to replace and so easy to break. Over the years people add columns, colour codes, hidden tabs and formulas that only one person fully understands, and the spreadsheet becomes the unofficial system of record for inspection work even though it was never designed to be one.

Nobody in the field can use it, so results get written down elsewhere and typed in later. Inspectors carry paper checklists or notebooks, results are transcribed at the end of a shift or the end of a week, and each transfer is a chance for a reading to be copied wrong or a failed check to be missed, while the spreadsheet itself is always a few days behind what is actually happening on site.

The way out is to split what the spreadsheet is doing into its parts: the list of what needs inspecting, the checklist for each inspection, the schedule and the record of results. Pulling those apart is mostly analysis work, going through the columns and tabs with the people who use them to work out which ones describe equipment, which ones describe what gets checked, which ones track dates and which ones hold results, and it usually reveals duplicate or abandoned sections that can be dropped.

Each of those becomes part of a workflow where inspectors get their assigned inspections on a device, fill in the checklist at the equipment and the results update the record straight away. Supervisors can see what is due, what is overdue and what has failed without waiting for someone to update a file, and failed checks can raise follow up actions directly instead of relying on someone to notice a red cell and send an email.

Interface runs inspections alongside procedures for this reason, so the field work and the record are the same thing. A practical rollout starts with one area or one equipment type, runs the new workflow in parallel with the spreadsheet for a short period so the team can compare results, and retires the spreadsheet section by section once people trust the new record, rather than trying to move all 4,000 lines in one go.