Complys IE → Construction Safety Software → Revising contractor RAMS after a task change in Ireland
Construction Safety Software

Revising contractor RAMS after a task change in Ireland

A risk assessment method statement (RAMS) is a description of a particular job and its controls. It cannot remain the operative plan when the site, equipment, sequence or hazards materially change. The practical task for an Irish construction team is to recognise the change, make the work safe, revise the method with the people who know the job, and communicate the current version before work resumes.

The Health and Safety Authority (HSA) RAMS guidance says significant changes before or after starting work should lead to stopping work until the RAMS has been updated and signed off. It gives examples involving new hazards, different systems of work, non-like-for-like plant and changed training requirements. This article concerns revision after change, not a generic RAMS template or a claim that every minor variation legally requires the same form.

Recognise the trigger at the workfront

The foreperson should compare the actual task with the version briefed to the crew. Has the agreed access route been blocked? Is an excavation deeper than expected? Is a scaffold being replaced by a mobile elevating work platform? Has another contractor moved into the area? Each can alter exposure and coordination. Record what changed, when it was observed, who identified it and which activities are affected. A vague note such as “method changed” is not enough for a competent reviewer to decide what must be redone.

Distinguish a true change from a routine step already covered by the method. A daily relocation within a planned sequence may be addressed through a task briefing or safe plan of action. If a new hazard or control is outside the RAMS, the existing approval does not safely carry it. The HSA Safe Plan of Action and RAMS resource explains how task planning and the broader method work together.

Stop or restrict the affected activity

Where the change is significant, stop the affected activity and apply interim controls. That may mean isolating a workfront, keeping people out of a lifting zone or preventing use of unsuitable access equipment. Explain to the crew what is paused and what can continue under a different, still-valid method. A blanket stop may be unnecessary if unrelated work is adequately controlled; an informal decision to carry on while someone updates a document can be unsafe.

Record the responsible supervisor, the temporary restriction and the person who can authorise resumption under site arrangements. Do not treat a digital acknowledgement as a technical approval. Specialist advice may be required for temporary works, excavations, lifting plans or electrical isolation. The site team must apply the project's actual dutyholder and competence arrangements.

Reassess the job with the contractor

The contractor doing the work should provide the operational detail: plant, sequence, crew competencies, materials, access, exclusion zones and emergency arrangements. A revised method should describe the changed condition and how the new control will work in practice. An owner can then review interfaces with other contractors and the construction-stage safety plan where relevant. The HSA construction-stage plan guidance describes project information and cooperation, but does not remove the contractor's responsibility for its own safe system.

Check whether the revised method creates a new dependency. A crane may need ground-bearing information and a lift plan. Moving from scaffold to a MEWP may change rescue arrangements and operator competence. A changed delivery route may affect pedestrians and neighbouring workfronts. The point is to resolve the actual risk, not to replace one equipment name in a document.

Agree the current version and brief the people doing the work

Record version number, date, author, reviewer, scope and reason for change. Make the old version visibly superseded. Where the RAMS requires sign-off under the project's process, capture the appropriate signatures before resumption. Keep any separate permit, inspection or technical approval attached to the task rather than implying that RAMS sign-off substitutes for it.

Brief the revised sequence to the workers and supervisors who will carry it out. Ask them to identify practical conflicts. Record attendance or a defensible acknowledgement, but do not equate a tick box with understanding. A crew coming on the next shift should see the current plan and know what changed. If a subcontractor does not receive the revision, the paper record has not controlled the interface.

Example: access method changes

A contractor planned façade work from a completed scaffold. An alteration makes that bay unavailable and the team proposes a MEWP. The foreperson stops work in the bay and records the change. The contractor assesses ground conditions, access, operator competence, rescue arrangements and neighbouring activities, then revises its method. The project team checks interfaces with deliveries and another trade, agrees the current version and briefs the workers. Work resumes only when the actual equipment and controls match the approved method and any separate inspection requirements have been met.

Simply writing “MEWP instead of scaffold” would miss the controls that make this a safe change. Equally, the revised RAMS is not a substitute for competent equipment inspection or an emergency plan.

Keep a traceable change record

Retain the original RAMS, change notice, revised version, review comments, briefings and any linked permit or inspection. A later reviewer should be able to answer: what changed, why did work pause, who assessed the new risk, what was agreed, who was told and when did activity resume? If the same change keeps recurring, review planning and procurement rather than generating repeated paperwork for a predictable condition.

The Complys Ireland construction safety page is the relevant product route for discussing how a team could organise current RAMS versions, owners and evidence. Confirm the live product workflow with Complys before describing any specific approval or notification feature. This guide does not claim that Complys writes RAMS, decides whether work is safe, legally signs off a method or automatically releases a workfront.