A DfS coordination plan is the project document that assigns Design for Safety duties, sets meeting cadence, and names the custodian of the DfS register. The developer, or a delegated Design-for-Safety professional, must ensure the plan exists and that the first review meeting is on the calendar. The immediate action is simple: appoint an owner today and open the DfS register with its first entry.
TL;DR:
- The developer must appoint a plan owner and establish a DfS register from the start of design to ensure statutory compliance and readiness for inspection.
- Failing to produce the DfS register on request can lead to fines up to $10,000, regardless of delegated custodian roles.
- The DfS coordination plan should clearly assign roles, include a fixed review cadence, and tie review stages to project milestones using the GUIDE framework.
- The register, along with the review records, must transfer to the new owner or management entity upon disposal, with a documented handover process.
- Delegating DfS coordination services to MOSAIC guarantees professional management, maintaining an auditable, inspection-ready register throughout the project lifecycle.
Table of Contents
- Statutory duties under the WSH (Design for Safety) Regulations 2015
- Who owns what in the coordination plan
- Building the plan from scoping to handover
- Running the review and keeping the register audit-ready
- Copy-ready checklist and templates for the project file
- How MOSAIC approaches DfS coordination on the ground
- Where MOSAIC fits if you would rather delegate the coordination
- Sources
- FAQ
Statutory duties under the WSH (Design for Safety) Regulations 2015
The WSH (Design for Safety) Regulations 2015 place the core duty on the developer for qualifying projects, requiring a maintained DfS register that captures every review meeting and every residual design risk identified during design development. This obligation exists independently of who chairs the meetings, which is why the coordination plan must state ownership clearly rather than assume it.
- The developer must keep the DfS register available for inspection at all times.
- Failure to produce the register when an inspector requests it can attract a fine up to $10,000.
- Delegating custodianship to a competent Design-for-Safety professional does not remove the developer’s underlying duty to ensure the register stays current and accessible.
Public-sector projects add a procurement dimension. MOM’s harmonised WSH requirements, effective from April 2024, now weight WSH performance in tender evaluation, so a documented, well-run DfS coordination plan can carry procurement weight beyond pure compliance.
Who owns what in the coordination plan
A coordination plan that does not name individuals by role tends to fail at the first audit. Roles must be assigned in writing, with clear escalation if a person is unavailable for a scheduled review.
- The developer holds the overall statutory duty and decides whether to delegate day-to-day coordination to a Design-for-Safety professional.
- The DfSP convenes DfS review meetings, maintains the register, and reports identified risks and mitigations back to the developer, as set out in MOSAIC’s breakdown of the GUIDE process.
- Designers and contractors carry design-stage duties to eliminate or mitigate foreseeable risks and must attend scheduled reviews to report on their portion of the design.
- Registered proprietors, or the subsidiary management corporation on handover, must receive the register on disposal of the developer’s interest in the structure, as the Regulations’ published text makes clear.
Building the plan from scoping to handover
A coordination plan is built in a fixed sequence, and skipping steps tends to surface later as missing register entries or unattended reviews.
- Confirm the project meets the applicability threshold and appoint a plan owner, whether the developer directly or a delegated DfSP.
- Map every stakeholder who must attend reviews, checking that designers and contractors have the competence to identify foreseeable risks in their discipline.
- Adopt the GUIDE framework (Gather, Understand, Identify, Decide, Evaluate) and tie review stages to design milestones, commonly labeled GUIDE-1 for concept, GUIDE-2 for developed design, and GUIDE-3 for detailed design.
- Set a fixed meeting cadence, agree how decisions get recorded, and define a change-control process for design revisions raised after a review closes.
- Design the register’s fields, decide who can edit it, and lock down version control so historical entries cannot be silently altered.
- Confirm the handover route: transfer to the new owner or the subsidiary management corporation on disposal, or into facilities maintenance records if the developer retains the asset.
Pro Tip: Run the first GUIDE review at concept stage rather than waiting for detailed design; elimination options are cheaper and more available earlier in the design timeline.
Public agencies increasingly check that a bid’s design documentation is complete before it reaches technical evaluation. Tools such as ArosBid’s AI tender review can flag missing DfS documentation before submission, which matters given the tender weighting changes described above.
Running the review and keeping the register audit-ready
A DfS review meeting is a decision checkpoint, not a status update. Attendance rules should require every designer and contractor with an unresolved risk on the register to be present, or to send a delegate with authority to commit to a mitigation.
- Structure the agenda around GUIDE phases, with each item assigned an output and an owner before the meeting closes.
- Record decisions in the register during the meeting, not from memory afterward.
- Keep the register’s core fields consistent: meeting date, risk ID, description, root cause, mitigation, residual risk, owner, due date, and status.
- Restrict register edits to the custodian and log every version, since the register must remain producible on inspection.
Under the WSH (Design for Safety) Regulations 2015, an inspector can request the DfS register at any time, and its unavailability can attract a fine up to $10,000. A register that only exists as scattered meeting slides will not satisfy that request.
Copy-ready checklist and templates for the project file
A coordination plan works best as a small set of standing documents that the project team can open and use without redrafting each time.
- Project-start checklist: confirm applicability, appoint the owner or DfSP, book the first GUIDE-1 review, and open the register template before design work begins.
- Minimal meeting agenda: prior actions review, new risks raised per discipline, GUIDE-stage decision items, mitigation sign-off, next meeting date.
- Register field list: risk ID, description, root cause, mitigation, residual risk rating, owner, due date, status, sign-off.
- A sign-off table for residual risk acceptance should record who accepted the risk, on what date, and under what justification.
- A transfer log for disposal or handover should record the receiving party, transfer date, and confirmation that the full register was delivered, matching the Regulations’ transfer requirement.
How MOSAIC approaches DfS coordination on the ground
MOSAIC provides Design for Safety Professional services that cover appointment, convening GUIDE-aligned reviews, and maintaining the DfS register through the design and construction phases. Engagements typically deliver an auditable register, a documented meeting cadence, and structured support at handover or disposal, aligning project practice with the statutory record-keeping duty described above. The intent is a plan that holds up under inspection, not just one that looks complete on paper.
— Aman
Where MOSAIC fits if you would rather delegate the coordination
Building and running a DfS coordination plan in-house takes time that many project teams do not have alongside design and construction pressures. MOSAIC’s Design for Safety Professional service takes on the appointment, convenes the GUIDE-aligned reviews, and keeps the register current and ready for inspection, with structured support carried through to handover.
Get in touch through MOSAIC’s Design for Safety Professional page to discuss appointing a DfSP for your project.
Sources
- Workplace Safety and Health (Design for Safety) Regulations 2015 – Singapore Statutes Online
- Workplace Safety and Health Guidelines on Design for Safety (GUIDE) – WSH Council / TAL
- WSH requirements in public sector construction and construction-related projects – MOM
FAQ
What is a DfS coordination plan in Singapore?
It is a project document that assigns who runs Design for Safety reviews, how the DfS register is kept, and when meetings happen, satisfying the developer’s duty under the WSH (Design for Safety) Regulations 2015. It typically names an owner, a review cadence, and register custody rules from the start of design.
Who is legally responsible for the DfS register?
The developer carries the underlying statutory duty, even when a Design-for-Safety professional is delegated to convene meetings and maintain the register day to day. The register must stay available for inspection, and unavailability can attract a fine up to $10,000.
What is the GUIDE framework for DfS reviews?
GUIDE stands for Gather, Understand, Identify, Decide, and Evaluate, a review structure recommended in the WSH Guidelines on Design for Safety. Teams commonly adapt it to design milestones such as concept, developed design, and detailed design stages.
What happens to the DfS register when a building is sold?
The register must transfer to the new owner or the subsidiary management corporation when the developer disposes of its interest in the structure, as required under the Regulations. A transfer log confirming date and receiving party helps evidence that the handover was complete.
Can a consultancy like MOSAIC run our DfS coordination plan?
Yes, MOSAIC offers a Design for Safety Professional service that takes on meeting convening, register maintenance, and handover support for Singapore projects. For current pricing details, please refer to the service page.
