On October 29, Britain’s Health and Safety Executive reported a £245,000 fine against Lunar Freezing and Cold Storage Company Limited. The fine followed an August 2025 incident in which a worker was pulled into a conveyor mechanism and seriously injured. A section of fixed guarding had been removed during maintenance about two weeks earlier and never replaced. That left a way into the machine that bypassed the interlocked gate. Maintenance staff had seen the guard missing and seen employees using the gap. The weekly inspection checklist did not cover non-electrical fixed guarding.
The HSE inspector’s conclusion was direct: checks “must cover every guard, not just the electrical ones.”
For an operations leader, that raises an uncomfortable question about inspection design. Digitizing a bad checklist gives you a faster bad checklist. Before moving inspections onto tablets, check two things. Do the questions cover the hazards? Does a failed check, or an observed problem, lead to action?
The fine makes the headline, but the management issue deserves the attention. How do you make sure a completed inspection means the equipment has been assessed against the right requirements?
What does a completed checklist prove?
Start with a distinction worth making in your next operations meeting. A completed form proves that someone submitted answers. Decide what additional evidence you need before treating those answers as permission to operate.
Consider a hypothetical maintenance form with a single question: “Guards checked?” An employee selects yes. What did the employee examine? Which guards were included? What condition would require a failed result?
HSE describes a competent inspector as someone who knows what to look at, what to look for, and what to do if they find a problem. A good checklist question carries all three. Rewrite the question around the equipment. Identify the guard or access point, define the acceptable condition, and explain what the inspector must do if it fails. Have a competent person establish the checks and the safe method for performing them.
That approach follows HSE guidance to base inspection scope on risk assessment and the manufacturer’s recommendations. The same guidance lists the presence of guarding as an example of a weekly check. This is British guidance, not a statement of requirements in every country. Still, the operational question applies anywhere: does your form reflect the machine in front of the inspector?
Do this review before purchasing software or converting a paper form. Put the checklist beside the equipment and work through it with the people who know the job. Ask them to identify anything the form leaves uncertain.
What should happen after a failed safety inspection?
For your next workflow review, follow one failed inspection from the initial observation to the decision to resume work. Use a real record from your plant, with the relevant supervisor present.
Look for three things: an explicit decision about equipment use, a named person responsible for correction, and evidence supporting closure. If the record ends with “maintenance informed,” ask for the next record. Keep following the chain until you can see who verified the outcome.
Then test a harder scenario. Suppose the problem is reported near the end of a shift. The replacement part has not arrived, and the original supervisor will be away tomorrow. What instructions reach the next crew? Who owns the unresolved issue?
These are workflow design questions. Write the answers into the operating process before configuring notifications.
The Peterhead case adds a harder variant. No inspection failed, because the checklist never asked about the guard. People saw the problem anyway, and nothing in the process turned that observation into action. Your process needs a route for hazards that fall outside the form.
HSE’s maintenance guidance calls for reporting procedures and warns against ignoring reports of unsafe equipment. A reporting channel needs an operational response behind it. An email acknowledging receipt should never be mistaken for evidence that a hazard has been corrected.
Define the response with your safety and maintenance leaders. Software should support the approved process, including escalation when a responsible person has not acted.
What should you change before digitizing inspections?
Use the following as a design review agenda, not a universal machine safety checklist. Your equipment risks and applicable requirements should determine the final controls.
- Map each check to a specific condition. Replace broad prompts with equipment-specific questions. Include an “unable to verify” response that requires review, so uncertainty cannot disappear into a pass.
- Close out work that removes safeguards. When maintenance removes a guard or disables a safety device, open a linked item. Keep it open until the safeguard is reinstated and verified by someone authorized to do so.
- Define the immediate response to failure. Specify who must be contacted and how equipment status is communicated. Keep the applicable physical safety procedures explicit; an app notification does not isolate machinery.
- Separate submission from authorization. Design the workflow so that submitting a form or completing a repair does not automatically authorize equipment use. Identify who can approve return to service and what they must verify.
- Require evidence where it supports a decision. Specify the relevant photograph, measurement, or test result. A photograph can document a visible condition, but it should not be accepted as proof of a safety function that requires testing.
- Preserve unresolved issues across shifts. Link the defect to the equipment and keep its status visible until authorized closure. Require the receiving supervisor to acknowledge responsibility when ownership changes.
- Test exceptions before rollout. Walk through an unavailable reviewer, a lost connection, and an unsuccessful repair. For disconnected work, define a direct communication method so an urgent hazard does not wait for synchronization.
Keep the form focused. HSE cautions that excessive inspection detail can encourage superficial box ticking. Ask for evidence because it informs a decision, not because another required field is easy to add.
Want a second set of eyes on your inspection workflow? Bring one of your current checklists to a 30-minute working session. We’ll walk a failed check through to return to service and show you where the handoffs break. Book an inspection workflow review.
How should you judge the digital workflow?
During a pilot, review the exceptions as closely as the completed forms. Ask a supervisor to demonstrate a failed check and show what happens next. Test whether an unresolved issue stays visible when a different person takes over.
For example, require a demonstration in which a repair attempt fails verification. The workflow should preserve that failed result and keep the issue open. Do the same exercise with a missing photograph, and with an inspector who cannot confirm the condition safely.
Mobile workflow tools, including Alpha Software’s, offer data validation, configurable alerts, and offline capture with automatic sync. Specify and test the inspection process those capabilities will support before treating the rollout as complete.
Keep the limits clear. HSE’s maintenance guidance addresses physical isolation and control of stored energy. A software status cannot perform those tasks or replace competent verification.
For the pilot review, bring an open defect to the meeting alongside the completion dashboard. Ask the team to demonstrate three things: the next required action, who owns it, and the conditions for closure. Make that demonstration part of acceptance.
Close the gap between a failed check and a safe restart
Can your team show what happens between a failed safety check and authorization to restart? If that handoff is unclear, let’s map it together. Schedule a 30-minute inspection workflow review.
Not ready to talk yet? Browse our free app templates and see how a digital inspection workflow could look in your plant.
Send this to the maintenance or EHS leader responsible for your inspection process.
Frequently asked questions
How do you improve a machine safety inspection checklist?
Have a competent person compare the questions with the equipment’s risk assessment and manufacturer instructions. Make sure every guard and safety device is covered. Define the acceptable condition and required response for each relevant check, then test the form with its users.
Does a digital inspection checklist make equipment safe?
No. Treat it as support for the safety process. Equipment still needs appropriate physical safeguards, safe working procedures, and competent people; a submitted record cannot substitute for those controls.
What should happen when an inspection finds a missing guard?
Stop use of the equipment, or prevent access to the exposed area, and follow the equipment-specific safety procedure. Notify the responsible person immediately. Record the condition and required action, and require authorized verification before return to service.
Further reading
Comment