PSCS changeover: hand over the information the next supervisor needs
A change of Project Supervisor for the Construction Stage (PSCS) can happen before the construction work is complete. The new team needs to understand the live site, not merely receive a folder titled “safety file”. Outstanding risks, contractor interfaces and information destined for the completed project's safety file should have named owners and a usable transfer record.
This guide concerns the operational handover when the PSCS changes during an Irish construction project. It does not change the statutory roles. The client appoints the PSCS where required; the Project Supervisor for the Design Process (PSDP) prepares the safety file and delivers it to the client at completion. The Health and Safety Authority (HSA) explains those distinct roles in its safety-file FAQ and client duty-holder guidance.
Clarify who is changing and when
Record the outgoing PSCS, incoming PSCS, client, PSDP, appointment dates, effective transfer time and the physical extent of the work. Confirm who coordinates the site during any overlap or gap. A new company name on the project directory is not enough if contractors still take direction from the outgoing supervisor. The client should check the appointment and competence arrangements against the applicable construction regulations; this article is not a substitute for that decision.
At the transfer meeting, identify which construction-stage safety and health plan is current and what revisions are being prepared. The HSA's construction-stage plan guidance describes the PSCS's role in developing a suitable plan before construction work begins. The incoming supervisor needs the plan, site rules and the reasons for open changes, not just a PDF without a revision history.
Transfer live controls and open actions
Prepare a concise register of the work in progress: high-risk activities, sequencing constraints, temporary works, plant interfaces, restricted areas, permits, inspections, incidents, near misses and outstanding corrective actions. For each open issue, record the hazard, interim control, responsible party, due date and next decision. Where a task has been assigned to a contractor, confirm that contractor has accepted the instruction and that the incoming PSCS knows how to check completion.
The handover should include current contractor contact details and the version of any Risk Assessment Method Statement (RAMS) or other work plan used on site. The HSA's RAMS and Safe Plan of Action guidance emphasises planning, briefing and supervision in the actual work context. A superseded method statement should be kept as history but not passed off as the current instruction.
Treat safety-file contributions as a separate stream
The completed project's safety file is intended to inform future maintenance, repair and other construction work on the structure. According to the HSA safety-file FAQ, the PSDP prepares the file and the PSCS coordinates written information from contractors that the PSDP needs. The changeover record should therefore say what safety-file information has already been sent to the PSDP, what remains with the outgoing PSCS, and what the incoming PSCS must obtain as later works are completed.
Examples may include as-built information relevant to future safety, plant manuals, service locations, maintenance requirements and details of residual risks. Do not assume every ordinary daily inspection belongs in the final safety file. Ask the PSDP what information is needed and in what form. A document register can distinguish “live construction control” from “candidate safety-file contribution” so neither stream disappears.
Prove receipt and resolve gaps
At the handover, list each controlled document with title, revision, owner, transfer location and recipient. The receiving team should check usability: can it access files, understand the location, and identify the current version? Record missing material as an action with an owner and date rather than marking the handover complete by signing a generic checklist. Sensitive personal information should be transferred only as needed and under the project's data controls.
Walk the site together where practicable. A drawing can show a temporary exclusion zone, but a physical walkthrough can reveal that access has changed. Speak to key contractors about planned work and interfaces. Confirm who will communicate new coordination arrangements to workers and subcontractors. Preserve an escalation contact for issues discovered after the outgoing PSCS has left.
Example: a phased building refurbishment
An outgoing PSCS is replaced while roof repairs and mechanical works are under way. The incoming supervisor receives the construction-stage plan, current roof access restrictions, permit status, active contractor RAMS, a list of defects awaiting repair and an index of plant information already sent to the PSDP. A joint walkthrough finds a new temporary route that is missing from the drawings. The team records the change, briefs the affected contractors and updates the plan. The remaining plant manuals are assigned to the contractor responsible for installation and scheduled for transmission to the PSDP.
The important result is not a perfect folder name. It is a clear chain from each unresolved risk or required safety-file contribution to the person who will finish it.
Evaluate the record system around the handover
A construction record system should make current plans and RAMS distinguishable from archived versions, expose open actions, and allow the relevant supervisors to find contractor and asset information. Test a simulated PSCS changeover: can a new supervisor identify the current controls and all unresolved items without asking the former team to reconstruct the history?
The mapped Irish construction safety software page provides the commercial context. The general Irish construction-regulations guide covers the wider duty-holder framework. Neither a software record nor this article appoints a PSCS, signs off a statutory file or transfers legal duties automatically.