Building a useful PSCS contractor coordination record

On a construction project with several contractors, the important evidence is not simply that a meeting happened. It is whether the Project Supervisor Construction Stage (PSCS) identified where work overlapped, agreed controls with the relevant contractors, communicated those controls and followed up when site conditions changed. A coordination record should enable a supervisor joining tomorrow to understand the live interfaces and decisions.

The Health and Safety Authority (HSA) guidance on the Construction Regulations 2013 describes the PSCS role in coordinating the project and contractors' duties to cooperate and provide relevant information. This page concerns evidence of actual coordination, not an overview of every PSCS duty or a replacement for the statutory construction-stage safety and health plan.

Start with the project and appointment context

Record the project, location, construction stage, PSCS appointment and current contractor packages. The HSA client guidance explains when a competent and adequately resourced PSCS appointment is required. Do not infer from a coordination spreadsheet that the appointment itself has been made correctly. Keep the written appointment and relevant plan accessible through the project's controlled documents.

Map the workfronts rather than merely listing company names. A crane lift, excavation, façade installation and materials delivery may be scheduled by separate contractors but affect the same route or exclusion zone. Note who can influence each interface, the expected dates and the party who will communicate the plan to workers. The most useful record answers “whose work might put someone else's team at risk today?”

Collect contractor information before the interface arises

Request the relevant parts of contractors' methods, plant arrangements, schedules and site-specific safety information. The HSA guidance says contractors must cooperate with the PSCS, provide site-specific information or relevant safety-statement extracts, comply with site rules and take corrective action. A generic safety statement alone will not show how a concrete pour will coexist with an electrician's access route.

Ask for the information early enough to change a sequence. If a subcontractor appears with different equipment or crew, refresh the interface review. Do not treat tender material as current without checking whether the conditions it assumed still exist. Version and date each input so the PSCS can identify the operative method.

Record the decision, not just the discussion

For each material interface, state the hazard or conflict, affected parties, agreed control, accountable owner, due time and verification method. A coordination meeting note saying “traffic discussed” does not show whether delivery vehicles will be segregated from pedestrians. A better entry names the revised route, signs and barriers, the contractor installing them, the supervisor checking them and the start time of the new arrangement.

Where a specialist must assess the control, record that dependency. The PSCS coordination role does not turn an administrator into a scaffold designer, lifting planner or electrical engineer. Keep technical approval and inspection records linked but distinct. Where an urgent hazard cannot wait for the next meeting, use the project's immediate escalation process and then document the decision.

Brief contractors and check implementation

Distribute the agreed change to contractor supervisors and workers affected by it. A meeting attendee may not be the person on the next shift. Record how the current instruction was shared, whether revised RAMS or a Safe Plan of Action is needed, and who confirmed the workfront understood it. The HSA RAMS and Safe Plan of Action guidance describes task-level planning that can carry these changes into daily work.

Follow up on site. A signed coordination minute is not proof that barriers were installed or deliveries changed. Inspect the interface when it is active, capture any deviation and reassign action. Repeated deviations may mean the sequence is unrealistic or contractors did not receive sufficient time and resources to implement the control.

Example: overlapping work at a shared access point

A roofing contractor plans a hoist beside the only route used by a fit-out contractor. The PSCS brings both supervisors together, checks the lifting arrangement and agrees timed access, an exclusion zone and an alternative route. The record identifies the lifting supervisor, the fit-out supervisor, the person checking the barrier and the briefing method. The next day, deliveries block the alternative route. The fit-out work pauses, the route is reassessed and the record is amended with the new decision.

Recording only the original meeting would hide the live failure. The coordination trail should connect the first plan, the site check, the change and the final verification.

Structure a compact evidence register

Use fields that support action: date, location, packages involved, source document version, interface, control, owner, deadline, communication, verification and closure. Link open items to the construction-stage plan or formal notices when appropriate. Avoid duplicating entire contractor methods into every meeting record; point to the controlled version. Preserve superseded decisions so a later reviewer can understand what was known at each stage.

Review the register at handover between PSCS personnel or project phases. Open restrictions, unresolved temporary works and upcoming high-risk overlaps deserve attention before completed routine items. A record that nobody uses to plan the next shift has limited operational value.

Where a contractor does not accept an agreed change, record the dispute and interim safe arrangement rather than marking the item closed. Escalate through the project's decision structure, then update every affected supervisor when the final arrangement is agreed.

The Complys Ireland construction safety page is the final-map product route for discussing current document and evidence organisation. Check the present implementation with Complys before asserting specific workflow functions. This guide does not claim that Complys performs PSCS statutory duties, validates technical designs, automatically coordinates contractors or authorises work.