The problem is not the warning, it is what comes after
A contractor who flags a defect once has done something important. It creates a record, and it shifts the conversation from we did not know to we were told. But a single warning, however well documented, describes the state of a system at one point in time.
Duty to warn is the specific, time-bound obligation to disclose a known defect or hazard to the party who can act on it. It is not a standing shield that protects every later decision to keep servicing the same equipment.
A contractor duty to warn safety system obligation is discharged for the fault identified, at the time it was identified. It does not extend indefinitely to cover every subsequent inspection, service visit or renewal of that same system, because each of those later events is itself a separate professional act. Every renewed inspection, every signed maintenance certificate and every system checked, no issues found report after the warning is a new representation. If the underlying defect was never resolved, each of those later sign-offs can look less like ongoing diligence and more like a contractor repeatedly certifying a system it privately knew was compromised.
How UK regulation frames contractor scope of appointment
UK regulation does not deal with gas detection maintenance contracts directly, but it is instructive on how contractor responsibility is meant to work in principle.
Under the Construction (Design and Management) Regulations 2015 (CDM 2015), a principal contractor must check that anyone it appoints has the skills, knowledge, experience and, where relevant, the organizational capability to carry out their work safely, a duty set out in HSE's guidance on principal contractor roles and responsibilities. CDM 2015 governs construction projects, not industrial plant maintenance, so it cannot be read across directly.
What it does illustrate is a general UK regulatory instinct: appointment and scope matter as much as competence, and a contractor's responsibility is judged against what it was actually appointed to do, on an ongoing basis, not against a single point-in-time assessment. Applied to a maintenance contract for a safety-critical system, that instinct suggests continuing to service a system is itself part of the contractor's scope of appointment, carrying its own duty of care each time it happens, separate from whatever was said in an earlier warning.
Where a duty to warn actually ends
The table below sets out how three common moments in a contractor relationship differ in practice.
| Moment | What it discharges | What it does not cover |
| Initial warning | The specific defect known and disclosed at that time | Any later inspection, service or system change |
| Repeated sign-off without escalation | Confirms the system was checked on that date | Does not retroactively excuse an earlier unresolved defect |
| Documented refusal to continue work | Removes the contractor from further exposure on that system | Does not protect sign-offs already given before the refusal |
For a UK organization, the practical lesson is that a contractor's duty to warn safety system obligation resets, in effect, at every subsequent visit. Relying on the fact that a warning was given years earlier, while sign-off continues uninterrupted, is not the same as having addressed the risk.
Contractor risk assessment software for UK organizations
This is where systematic contractor risk assessment earns its place, not as a compliance checkbox but as the record that shows which judgment was made, when and on what basis. Contractor risk assessment software for UK organizations that logs every inspection, warning, sign-off and escalation against a specific system creates a timeline that a single paper warning cannot. It shows whether a contractor's repeated certifications were consistent with its own earlier findings, and whether an organization acted on a warning or simply filed it.
That audit trail matters in both directions. It protects a contractor who does escalate and refuse further work when a defect is not resolved, and it exposes a pattern where a contractor kept signing off a system despite having flagged a problem with it earlier. Ideagen Workforce Safety centralizes exactly this kind of contractor record: competency and training history, hazard controls, sign-off history and site documentation in one place, so a UK organization can see the full pattern of contractor engagement with a safety-critical system, not just the one warning it happens to remember.
The regulatory picture looks different in the US
UK organizations dealing with contractors on shared or multi-employer sites in the US will find a more codified version of this same tension. US regulators apply concepts such as OSHA's multi-employer citation policy, which can hold a controlling employer liable for contractor safety failures on a shared site.
For the US regulatory picture, see Ideagen's guide to contractor safety management software for OSHA, MSHA and NFPA compliance. The underlying principle, that ongoing oversight is judged separately from a single disclosure, holds regardless of which jurisdiction's regulation formalizes it.
Treat every sign-off as a new decision
The Watson Grinding case is a US industrial accident, not a UK legal precedent, and it should be read as an illustration of a pattern rather than a rule. The pattern itself keeps recurring wherever a contractor is appointed to maintain a safety-critical system over an extended period: a warning given once becomes psychologically and administratively treated as done, while the actual risk continues to accumulate with every subsequent sign-off. UK organizations that build contractor oversight around this reality, treating each inspection and certification as its own decision rather than a formality, are the ones that catch a compromised system before repetition becomes routine.
Explore workforce safety solutions
Ensuring that your workers go home in the same condition as when they arrived. We are the leader in keeping workers safe, workplaces compliant and risks mitigated.