PSCS safety plan action register in Ireland

An Irish construction-stage safety and health plan can become inaccurate quickly if a design change, new subcontractor, revised sequence or site finding is recorded elsewhere but never reaches the plan. The Project Supervisor Construction Stage (PSCS) needs a way to turn those changes into named actions, check their effect on work and retain evidence of the updated arrangements. An action register is a management aid for that purpose. It is not itself a substitute for the construction-stage plan or for the PSCS's legal duties.

The Health and Safety Authority's guidance on creating a construction-stage safety and health plan says an appointed PSCS must develop a suitable, project-specific plan before construction work begins, keep it updated and make relevant information available to people who need it. This guide focuses on assigning and closing plan-related actions during the construction stage. It does not repeat a general overview of Ireland's Construction Regulations or present a generic action list as statutory wording.

Start from the live plan, not a detached task list

Record the current plan version, project, PSCS contact and location of the controlled copy. Each action should link to a specific plan section, drawing, RAMS, safe plan of action, permit or site rule affected. If an issue is only captured as “update safety plan,” nobody can tell which work must change or who should be briefed. Keep the source of the issue: site inspection, coordination meeting, design notification, incident learning, contractor proposal or regulator direction.

Set a triage rule. A new hazard may require stopping or restricting work now, not waiting for a weekly plan update. The competent PSCS representative and affected contractor should decide whether temporary controls, a revised sequence or a formal document amendment is needed before work continues. Record the interim decision, its owner and the time it was communicated. Do not allow an open action to appear as approval to proceed.

Give every action an accountable owner

An action register should identify the issue, affected activity and location, decision needed, person or organisation responsible, due point, dependencies, evidence required, reviewer and status. A named PSCS coordinator may own the plan update while a contractor owns a revised method statement and another party owns a design clarification. Those responsibilities are related but should not be collapsed into one “site team” task.

The PSCS should coordinate interfaces. If a temporary access route affects three contractors, agree who changes the route, who updates site information and who briefs each crew. An acknowledgement by one supervisor does not prove that every affected group received the current controls. The HSA's Safe Plan of Action and RAMS guidance describes how task planning and briefings connect with broader site coordination. A task-level Safe Plan of Action is distinct from the construction-stage plan; use cross-references rather than substituting one for the other.

Track decisions, documents and briefings separately

There are at least three milestones in a meaningful plan action: the decision on what changes, issue of the controlled update, and confirmation that affected people know the change. A register that closes after a document upload can miss the last step. Record the reviewer and version approved, superseded material withdrawn or marked, distribution list, briefing date and evidence that the right crews understood the change.

Where the change concerns a permit or isolation, update those controls through their own process. A safety plan amendment should not be treated as a permit to work. Where the change is technical or design related, obtain the appropriate competent input rather than letting an administrative action owner decide engineering adequacy. Keep a clear record of outstanding assumptions and the authority for each decision.

The HSA's Safe Plan of Action guidance stresses that supervisors brief crews and revisit the task plan if conditions change. The action register can point to that briefing and its evidence, while the actual task controls stay in the task record. Avoid copying a risk assessment into every register row, which creates conflicting versions.

Example: sequence change on a shared work face

Suppose a contractor proposes to bring plant into an area before a neighbouring trade finishes overhead work. The PSCS identifies a conflict in the existing construction sequence. The immediate action is to hold the affected movement until the parties agree separation or a revised sequence. One contractor supplies a revised method; another confirms completion of overhead work; the PSCS reviews the interface and updates the relevant plan section and site rule. The site supervisor briefs both crews and checks the agreed exclusion in the field. The register records each owner, document version and verification. It closes only when the conflicting activities are actually controlled, not simply when a meeting minute says “resolved.”

Escalate stalled or unsafe actions

Set escalation according to risk and work timing. An overdue action that affects tomorrow's work requires a different response from an editorial update with no current exposure. Identify who can restrict the activity, who decides on an alternative control and who communicates the decision to contractors. Record missed deadlines and the reason; do not silently move the due date. If the plan cannot be kept accurate or a critical interface is unresolved, the appropriate competent people must decide whether work can proceed. Software should never make that judgement automatically.

At review meetings, look for repeated causes: changes arriving late from design, plan versions circulating uncontrolled, actions assigned to a role that lacks site authority, or briefings that never reach subcontractors. Use the findings to improve the coordination process. The purpose is to keep the construction-stage plan an active management document throughout the project.

For current-product discussion, see Complys Ireland construction safety software. Verify the live product and destination claims during integration. This guide does not claim Complys creates or legally approves the statutory plan, performs a PSCS appointment, validates engineering decisions or authorises a contractor to work.