At most sites we audit, Excel is the food safety software, and it was never designed to be one. Temperature logs, supplier lists, training registers, internal audit schedules and traceability sheets live in workbooks on a shared drive, site after site. It works, in the sense that a record exists, until one of five things happens: an auditor asks who changed a cell and when, a mock recall needs three workbooks reconciled, a formula breaks silently, two people edit the same file, or the person who built the spreadsheet leaves. Every one of those is an evidence failure, and every one of them appears in audit reports as a non-conformance against a system that was, on paper, complete.
Failure 1: no audit trail
A cell can be changed by anyone with the file open and nobody can tell. Auditors under FSSC 22000, BRCGS and GLOBALG.A.P. increasingly ask to see who made an entry and whether it was altered. Excel’s answer is the file’s last-modified date, which proves nothing. A food safety record needs the user, the time and the history of every change, and a spreadsheet does not provide any of them.
Failure 2: nothing is ever due
A spreadsheet is a place to write things down. It does not know that the metal detector check was due at 10:00, and it does not tell anyone at 10:15 that the cell is still empty. The gap is discovered when the sheet is reviewed, which is usually the day before the audit. Missed monitoring is one of the most common HACCP findings we raise, and Excel is structurally incapable of preventing it.
Failure 3: entry and verification are the same action
Principle 6 of HACCP is verification, and auditors check that the verifier is a different person acting at a different time. In a spreadsheet the “verified by” column is typed by whoever has the file open, often the same person who made the entry, often in a batch at month end. There is no mechanism to separate the two, so there is no evidence that verification happened at all.
Failure 4: traceability across workbooks
Receiving is one workbook, production another, dispatch a third. A mock recall means matching lot numbers typed by three different people with three different habits for spaces and dashes. The exercise takes a day and the mass balance is reconciled by adjustment. A retailer that asks for the trace in four hours gets it in six, and the next question is why.
Failure 5: the single point of failure
Every site has one person who understands the workbook. The hidden sheets, the macros, the lookup that points to a file on their own drive. When that person is on leave the system limps, and when they resign it stops. An FSMS has to outlive the people who run it, and a spreadsheet rarely does.
What auditors say about it
Auditors do not write “Excel” on a non-conformance. They write “no evidence that monitoring was carried out at the stated frequency”, “records could not be demonstrated to be protected from alteration”, “traceability exercise exceeded the four-hour requirement” and “verification activities not evidenced”. Those are the spreadsheet’s failures, recorded in the language of the standard.
What to use instead
A system where records are scheduled and alert when missed, where entries are timestamped and attributed, where verification is a separate action by a separate user, where limits force a corrective action, and where traceability is a search across one data set rather than three files. ASCloud does all of that from R3,800 per site per month for a full document FSMS, and from R499 for R638 premises. Setup loads your existing workbooks, so the spreadsheet does not have to be retyped, it has to be retired.
Retire the spreadsheet
ASC loads your existing workbooks and builds your checklists in five working days. Records with an audit trail, alerts and separate verification, from R3,800 per site per month.
Frequently asked questions
Can I still export to Excel?
Yes. Any record set or report exports to a spreadsheet for analysis. The difference is that the spreadsheet is a copy, not the record.
Our auditor has never complained about Excel. Why change?
Because the next one might, and because the findings above are raised in the language of the standard rather than by naming the tool. More importantly, a real recall is not an audit, and that is when the spreadsheet costs the most.
How long does migration take?
Five working days for a standard single site. ASC loads the documents and builds the checklists from your current workbooks.
What about Google Sheets?
Google Sheets has a version history, which solves failure 1 partially. It does not solve the other four.