Is a spreadsheet acceptable for operator rounds?

Nothing in UK health-and-safety law names a medium. COMAH, PSSR and DSEAR care that the duty is discharged and that you can show it — not what software holds the record. A disciplined spreadsheet on a small site with one engineer can satisfy that. The questions that decide it are about properties, not products: can you produce the record, can you trust it, and does it cover the period being asked about.

What actually goes wrong with spreadsheets first?

Almost always the same thing, and it is rarely dramatic: copies. Somebody works offline, emails a version, keeps a local file over a shutdown. Within a year there are four files with overlapping months and nobody can say which one is the record. The data was never wrong — the question 'which file is authoritative?' simply stopped having an answer.

Can't you lock a spreadsheet down?

You can protect sheets, restrict editing, keep it in SharePoint with version history and get a long way. What you cannot get is a record that its own custodian cannot alter — the person with the password can always change a past cell, and an auditor knows it. That is not a criticism of Excel; it is simply not what a spreadsheet is for.

Do we have to stop using Excel?

No, and we would argue you shouldn't. Excel is excellent at analysis, one-off questions and the report your manager actually wants. What changes is where the evidence LIVES: recorded once, unalterable, attributable — and then read into Excel whenever you want. The spreadsheet stops being the record and goes back to being the tool.

How long does moving take?

The plant model and the first rounds are built in days rather than months, and the first real round has gone live within days of starting. The bigger question is usually not the software but the discipline: deciding what actually gets checked, how often, and what the limits are. Most sites find that conversation valuable in its own right.

When Excel is enough for operator rounds — and when it isn't

Excel is genuinely good, and pretending otherwise wastes your time

Every engineer reading this has built something useful in a spreadsheet in an afternoon. That is not a weakness of Excel — it is the reason it won. It costs nothing extra, everybody already knows it, it does not need a project, and it will happily do something no software vendor anticipated.

Most inspection software is sold by implying that the spreadsheet was foolish. It was not. It was the fastest correct answer available at the time, and on a lot of sites it still is.

When a spreadsheet is enough

Honestly assessed, Excel is the right answer when most of these are true:

One person, or a small stable team. The same engineer records and reviews, so nobody has to reconstruct who did what.
One place. The file lives in one location that everybody agrees on, and nothing is kept locally.
Low consequence if a cell changed. Nobody would be seriously harmed, and nothing external is decided, if a past value were altered.
Nobody outside asks for it. No auditor, insurer, regulator or customer requires the record on their terms.
Recording happens at a desk. Not one-handed, in a plant room, on a phone, in the rain.

If that describes your site, the useful advice is: keep the spreadsheet, tidy the discipline around it, and spend the money elsewhere.

Where it changes

It rarely changes because somebody decides Excel is inadequate. It changes because the plant does, and the spreadsheet is asked to do something it was never built for.

More than one person recording

Two operators on opposite shifts cannot both hold the file. So it gets copied, or it gets a tab each, or somebody types up the night shift's paper in the morning — and the record quietly becomes a transcription of a record, which is a different thing.

Somebody asks who wrote a number, and when

A cell knows its value. It does not know who typed it, at what time, standing in front of which machine, or what the limit was that morning. Those are the four things every investigation asks for, and none of them survive in a spreadsheet by default.

The file becomes the record — and files get copied

This is the failure nobody plans for and almost everybody meets. Within a year there are several files with overlapping months, all plausible, and the question "which one is the record?" has stopped having an answer. Nothing was falsified. The authority simply dissolved.

Recording moves into the plant

A phone or tablet in a boiler house, one-handed, with gloves on, sometimes with no signal. A spreadsheet can technically be opened there. Nobody who has tried it does it twice.

Somebody needs to prove nothing was edited

Not to suspect anybody — simply to answer the question. A spreadsheet cannot demonstrate that a past value was never changed, because the person holding it has always been able to change it. Auditors know this, which is why the follow-up questions get longer.

Reporting outgrows the sheet

Somebody wants a trend across two years and four plants in Power BI, refreshed automatically. The spreadsheet becomes a manual export step performed by one person, and everybody quietly depends on them remembering.

Six questions to ask of your own spreadsheet

Not a scorecard. If the answers make you uncomfortable, that is the signal — and if they do not, you have just saved yourself a purchase.

Which file is the record? If two people answer differently, you already have your answer.
Who wrote this number, and when? Not "who owns the file" — who typed the value.
What was the acceptable range that day? If limits have changed since, can you still show what applied at the time?
Can you show a value was never edited? Not that it wasn't — that it couldn't have been.
What happens when a check is missed? A blank cell and a missed check look identical.
Who reconstructs it if the owner leaves? The file survives. The knowledge of how it works often does not.

Straight talk

A blank cell is the sharpest of these. In a spreadsheet, "not done", "done and not written down", "not applicable today" and "the machine was out of service" all look exactly the same — and only one of them is a problem.

Excel keeps its job

The mistake most software makes here is trying to replace the spreadsheet entirely, and then producing something worse at the thing Excel is best at: letting a competent person ask an unanticipated question quickly.

The better split is simple. Evidence is recorded once, where it cannot be altered and every entry carries who, when, and what it was judged against. Then Excel reads it — refreshing itself from the live record rather than being re-exported by hand every Monday, with the same column names your existing sheets already use. Power BI and Fabric read exactly the same data, so a dashboard and a spreadsheet cannot disagree.

Nobody has to give up the tool they are fast in. What changes is that the spreadsheet stops being the thing that must not be lost.

Amberhold is built for the point where those six questions start to matter — and it is deliberately good at handing your data straight back to Excel, because that is where a lot of real work will always get done.

Common questions

Questions we actually get asked

Is a spreadsheet acceptable for operator rounds?: Nothing in UK health-and-safety law names a medium. COMAH, PSSR and DSEAR care that the duty is discharged and that you can show it — not what software holds the record. A disciplined spreadsheet on a small site with one engineer can satisfy that. The questions that decide it are about properties, not products: can you produce the record, can you trust it, and does it cover the period being asked about.
What actually goes wrong with spreadsheets first?: Almost always the same thing, and it is rarely dramatic: copies. Somebody works offline, emails a version, keeps a local file over a shutdown. Within a year there are four files with overlapping months and nobody can say which one is the record. The data was never wrong — the question 'which file is authoritative?' simply stopped having an answer.
Can't you lock a spreadsheet down?: You can protect sheets, restrict editing, keep it in SharePoint with version history and get a long way. What you cannot get is a record that its own custodian cannot alter — the person with the password can always change a past cell, and an auditor knows it. That is not a criticism of Excel; it is simply not what a spreadsheet is for.
Do we have to stop using Excel?: No, and we would argue you shouldn't. Excel is excellent at analysis, one-off questions and the report your manager actually wants. What changes is where the evidence LIVES: recorded once, unalterable, attributable — and then read into Excel whenever you want. The spreadsheet stops being the record and goes back to being the tool.
How long does moving take?: The plant model and the first rounds are built in days rather than months, and the first real round has gone live within days of starting. The bigger question is usually not the software but the discipline: deciding what actually gets checked, how often, and what the limits are. Most sites find that conversation valuable in its own right.

When Excel is enough — and when it isn't