The spreadsheet is not the villain. It just was never designed for what you are asking it to do. LOLER 1998 requires automated interval tracking, complete Schedule 1 records, a tamper-evident audit trail, and Category A defect notifications. None of those are spreadsheet features. Purpose-built LOLER inspection software is built around every one of them. Below are the seven gaps that show up, reliably, in every spreadsheet-based inspection programme.
Seven places where your spreadsheet will cost you
1
No automated alerts, examinations slip
Excel does not know that a chain sling was due for thorough examination last Tuesday. The date sits in a cell. If nobody checked that cell, the overdue examination happened silently. With a fleet of 200 or more assets across multiple sites, something will always slip. HSE does not accept "we forgot to check the spreadsheet" as a compliance defence.
2
Schedule 1 fields are routinely incomplete
LOLER 1998 Schedule 1 requires 12 specific fields on every examination report. These include the date of next examination, the competent person's name and address, and the safe working load. Most spreadsheets capture four or five fields. The rest are assumed, omitted, or held elsewhere. An incomplete Schedule 1 report is a non-compliant report, regardless of how complete the rest of the record appears.
3
Version control creates a liability
Multiple engineers. Multiple devices. The spreadsheet is emailed, edited locally, and re-uploaded. By the end of a quarter, no one can be certain which version is authoritative. During an HSE audit, you must produce the definitive record immediately. "Let me find the latest version" is not an answer that demonstrates a systematic compliance process.
4
No audit trail on any entry
Excel records no trace of who changed a cell, or when. If a value is overwritten, whether accidentally or deliberately, there is no way to know. For legally required records that may be produced as evidence in enforcement proceedings, the absence of an audit trail is a serious vulnerability. A timestamped digital system creates an immutable record by contrast.
5
Accessories get confused with parent equipment
A crane carries a 12-month examination interval. Its chains and hooks require examination every 6 months under LOLER 1998. In a spreadsheet, these are often tracked together on a single row, causing accessory intervals to be missed or the crane certificate to be conflated with its accessories. This is one of the most common gaps HSE identifies during site visits.
6
Category A defect notification gets skipped
When a competent person identifies a Category A defect, the relevant enforcing authority must be notified immediately. A spreadsheet has no mechanism to trigger this step. The notification depends entirely on the individual inspector remembering to act. In a busy inspection programme, it gets skipped, exposing both the inspection company and the duty holder.
7
Excel auto-formatting corrupts asset identifiers
This is a subtle but real risk. Serial numbers such as "07-0399" entered as text will display correctly until the file is closed and reopened. Excel then auto-formats them as dates or numbers, silently corrupting the identifier. In a LOLER asset register, a corrupted unique identifier can mean a piece of lifting equipment becomes untraceable in your records.
What an HSE inspector actually wants to see
During an enforcement visit, the inspector will name an asset and ask to see its Schedule 1 report. Not in a few minutes. Immediately. They expect every required field to be present. They expect clear evidence a competent person produced it. They expect the next examination date to be visible and not lapsed.
Where defects have been found, they check that categories were applied correctly and actions were completed. The HSE guidance on LOLER is clear: a spreadsheet summary is not a substitute for a Schedule 1 report. A spreadsheet satisfies some requirements some of the time. Purpose-built LOLER software satisfies all of them, every time.
How a spreadsheet failure becomes an enforcement case
Consider a realistic scenario. An inspection company tracks 200 assets across 30 clients on a shared Excel file. An inspector leaves. The file is updated inconsistently. A bulk copy-and-paste to add a new client corrupts examination interval values: 12-month assets now show 6-month intervals. Nobody notices for three months.
An HSE inspector visits. They ask for examination records on a specific overhead crane. It takes 40 minutes to find the paper reports. The inspector asks about three further assets. Two have lapsed examination dates because a calendar reminder was deleted when an administrator changed computers. The company cannot show a systematic compliance process. It receives an Improvement Notice.
Under LOLER 1998 Regulation 11, the duty holder is required to keep records until the next examination report is received, or for a minimum of two years for non-person-carrying equipment. A spreadsheet that cannot be reliably produced, or that contains corrupted data, fails this obligation.
Why Excel cannot give you a defensible audit trail
⚠
Critical compliance vulnerability
Excel has no audit trail. Any cell can be edited at any time with no record of who made the change or when. In a disputed enforcement case, this is the difference between a credible compliance defence and an unverifiable claim. A spreadsheet with manually entered dates cannot prove when those dates were entered.
If a compliance dispute arises, or HSE investigates following an incident, you must show that records were created at the time and were not altered afterwards. A spreadsheet with manually entered dates cannot prove when those dates were entered. A timestamped digital system logs every entry with a timestamp and user identity. Modifications are recorded too. In a disputed enforcement case, that is the difference between a credible compliance defence and an unverifiable claim.
The time your spreadsheet is quietly eating every month
80 to 100 hours/month
spreadsheet administration time for a 10-client, 500-asset portfolio; two full working weeks every month, before a single inspection is carried out
The admin burden of managing LOLER compliance in Excel grows with every asset you add. For a company with 10 clients and 50 assets each, that is 500 assets to track. Weekly due-date checks, post-examination file updates, monthly overdue reviews, client status reports: combined, they add up to roughly 80 to 100 hours of spreadsheet administration per month. Two full working weeks every month, spent maintaining a tracking system rather than carrying out inspections.
What one missed examination actually costs
A UK steel fabricator was fined GBP 13,333 plus GBP 2,527 in costs for missing thorough examinations on just two overhead cranes. No incident triggered the fine. An HSE visit found lapsed examination dates. The spreadsheet had not flagged the overdue dates. Nobody had checked the relevant cells.
The cost of adequate LOLER compliance infrastructure is a fraction of a single prosecution. Not having a proper system is not a mitigating factor in the sentencing guidelines. It is treated as evidence of negligence. That increases culpability and, with it, the fine.
Is Excel acceptable for LOLER record keeping?+
LOLER 1998 does not prescribe the format for records. It requires that examination reports contain the Schedule 1 fields and are retained. Using Excel as a scheduling tracker is not illegal. Using it as a substitute for compliant examination reports is non-compliance. The report must be produced by a competent person and contain all required data fields.
What does HSE expect for LOLER records?+
HSE expects a full Schedule 1 report for every thorough examination carried out, produced by a competent person, retained for the required period, and produced immediately on request during an enforcement visit. A spreadsheet summary is not a substitute for the Schedule 1 report.
What is the main compliance risk with spreadsheet-based LOLER tracking?+
The main risks are: missed examination dates (no automated alerts), incomplete records (Schedule 1 fields left blank), version control failures (multiple files, inconsistent data), no audit trail (changes untracked), and inability to produce records promptly during an HSE visit. Any one of these can constitute a compliance failure under LOLER 1998.
Manage your LOLER inspections digitally with Lolerflow.
30-day free trial, no credit card required.
Start your free trial →