Safety and Health Coordinator: function during execution
The Safety and Health Coordinator is not a document manager for contractors. Their function relates to coordinating the application of preventive principles, site activities, and control measures within the applicable legal framework. A digital system should facilitate information and tracking without blurring that professional responsibility.
On projects where the figure is required, Royal Decree 1627/1997 defines the functions and role of the coordinator during design or execution as appropriate. The specific circumstances must be reviewed with current regulations and the characteristics of the project.
What information you need to coordinate
Schedule of activities, concurrent companies, method changes, incidents, reviews of the safety and health plan, and high-risk activities are pieces of context that allow anticipating interference. The value appears when that information arrives before the activity.
A coordination agenda should not be built solely from meetings. Linking each matter with front, company, date, and evidence allows preparing the review and checking later if the agreed action was carried out.
Coordination versus direct execution
Coordinating doesn't mean assuming the preventive obligations of contractors and subcontractors. Each company maintains its responsibilities. The tool should preserve who must act on each measure to prevent all tasks from ending up assigned to the coordinator by default.
This distinction also improves tracking: the coordinator can detect, require, or escalate a situation, while the operational owner executes the measure and provides evidence to verify it.
Coordination meetings and minutes
A useful meeting starts from open matters: phase changes, new companies, interference risks, overdue actions, and special work. The minutes should record decision, owner, and date, not transcribe the entire conversation.
Relating the agreement with the incident, document, or activity prevents the next meeting from starting by reconstructing what was decided and why. Closed matters can be archived while maintaining their history.
Visits, observations, and actions
During a visit, an observation should identify location, situation, risk, or requirement, owner, and agreed action. A photograph helps situate the fact, but follow-up needs a status that allows knowing if it is still open and who must intervene.
Closure requires verification proportional to the situation. On relevant matters, a message response may not be sufficient; keeping evidence of the correction makes it easier to verify that the adopted measure matches what was required.
Changes requiring special attention
Incorporation of subcontractors, overlapping activities, changes in construction method, changes in access or layout, and new equipment can alter preventive coordination. Detecting them from planning reduces dependence on informal notices.
Not all changes have the same impact. Classifying by urgency and by front helps prioritize the review without converting the system into an endless list of notifications.
Traceability without unnecessary bureaucracy
Useful traceability allows reconstructing what situation was observed, what was agreed, who should act, and when it was verified. It doesn't require documenting every conversation or creating fields that nobody uses to decide.
The more critical the matter, the higher the quality of the evidence should be. The system can facilitate that discipline, but the technical assessment of measure sufficiency corresponds to the competent person.
How Bloqbase can help
Bloqbase can bring together planning, companies, documents, incidents, checklists, and evidence so that coordination reviews start from a common view of the project.
The product doesn't replace the Safety and Health Coordinator figure or automate their decisions. Its role is to reduce information dispersion and ensure that agreed actions have an owner, date, and history.