A Design for Safety Register is mandatory for any Singapore project that meets the threshold set under the Workplace Safety and Health (Design for Safety) Regulations 2015. Once the contract-sum threshold is met, the developer must appoint a Design for Safety Professional and open the register immediately. There is no grace period for this step. If your project qualifies and no register exists yet, that gap is a compliance exposure the moment ground is broken.
TL;DR:
- Projects with a contract sum of S$10 million or more must appoint a Design for Safety Professional and open the register immediately once the threshold is met, with no grace period.
- The overall project scope, including all work packages, is assessed to determine if the threshold applies, not just the main contract, and splitting contracts to avoid the limit invites scrutiny.
- A compliant DfS register must show detailed risk identification, mitigation rationale, responsible parties, and supporting documentation, avoiding blank rationale fields.
- The developer holds ultimate responsibility, but the DfSP, designers, and contractors must actively contribute to maintain a traceable, up-to-date, and review-ready register throughout the project.
- Regular milestone reviews, proper documentation linking, and a live, version-controlled register ensure compliance and smooth inspection outcomes.
Table of Contents
- When Does DfS Register Requirements Apply to Your Project?
- What Goes Into a Compliant DfS Register?
- Who Is Responsible for DfS Compliance on a Project?
- When Should You Appoint a DfSP, and How Often Should Reviews Happen?
- How MOSAIC Keeps a DfS Register Live and Audit-Ready
- How Do Inspectors Evaluate DfS Compliance?
- MOSAIC’s Perspective on Meeting DfS Register Requirements
- MOSAIC’s DfS Advisory and Register Setup Services
- Sources
When Does DfS Register Requirements Apply to Your Project?
The statutory trigger is a construction contract sum of S$10 million or more. Below that figure, DfS obligations do not attach automatically, though many developers voluntarily maintain a register for reputational and insurance reasons. Above it, the WSH (Design for Safety) Regulations 2015 apply regardless of building type, so developments meeting this threshold face identical obligations regardless of type.
Multi-contract developments complicate the math. Developers sometimes split works across several smaller contracts, but regulators and the WSH Council look at the aggregate scope of the development, not each contract in isolation. A project structured to dodge the threshold through fragmentation invites scrutiny rather than avoiding it.
Before you assume you are exempt, verify against these factors:
- Total contract sum across all works packages, not just the main building contract
- Whether the project falls under Planning Act approval requiring a Grant of Written Permission
- Whether renovation or addition and alteration works push a previously exempt building over the threshold
- Guidance updates published by the WSH Council on borderline cases
What Goes Into a Compliant DfS Register?
An inspection-ready register is not a running list of hazards. It is a structured record that shows how each foreseeable risk was identified, why a particular mitigation was chosen, and who owns the follow-through. The WSH Council frames the register as a working safety document that has to survive handover to whoever eventually maintains or modifies the building.
At minimum, each entry should carry:
- Risk description — the specific foreseeable hazard, tied to a location or building element
- Source of the risk — design feature, site condition, or future maintenance activity that creates it
- Mitigation or design action taken — what was changed, added, or specified to address it
- Rationale — a short explanation of why that mitigation was selected over alternatives
- Responsible party — the designer, DfSP, or contractor accountable for closing the item
- Date raised and date resolved, plus current status
- Supporting attachments — drawings, calculations, or minutes referencing the decision
Pro Tip: Never leave the rationale field blank. Auditors treat a register that lists actions without reasons as evidence the review was a paperwork exercise rather than an actual design conversation.
Acceptable evidence includes signed meeting minutes, versioned drawing sets with revision notes, and a change log that lets an auditor trace a decision from first mention to final resolution.
Who Is Responsible for DfS Compliance on a Project?
Responsibility is distributed, but the developer carries ultimate accountability. That means appointing a competent Design for Safety Professional is a legal necessity, not a courtesy to the design team.
- Developers must appoint a DfSP where the threshold applies, ensure the register is actively maintained through every design phase, and hand it over intact at project completion.
- The DfSP convenes DfS review meetings on the developer’s behalf, keeps the register current, and communicates foreseeable risks to everyone downstream, including future maintenance teams, according to WSH Council guidance.
- Designers contribute risk input at each design stage and must document how their choices respond to identified hazards.
- Contractors adopt the specified mitigations on site and flag any deviation that changes the original risk assessment.
DfSPs are typically registered professional engineers, architects, or experienced designers who have completed sector-recognized training such as the WSQ Perform Design for Safety Professionals Duties course. A developer appointing someone without that grounding is taking on risk the regulation was built to eliminate.
When Should You Appoint a DfSP, and How Often Should Reviews Happen?
Appoint the DfSP during the conceptual or planning stage, before detailed design locks in decisions that are expensive to reverse. Waiting until schematic design is finalized defeats the purpose of early-phase risk elimination that the WSH Council built the framework around.
A practical procedural checklist looks like this:
- Concept stage — appoint DfSP, open the register with a blank template, hold the first DfS review meeting.
- Schematic design — review layout and structural risks; log mitigations tied to specific drawing revisions.
- Detailed design — capture mechanical, electrical, and facade-related maintenance risks; update responsible-party fields.
- Pre-tender — verify all open items have owners; freeze the register version issued to tenderers.
- Post-tender/construction — track contractor-raised deviations and amend mitigations as needed.
- As-built/handover — reconcile the register against final drawings and hand the complete document to the building owner or facilities team.
Each review meeting should generate minutes recording attendees, decisions made, and named action owners with target dates. A cadence of one review per major design milestone, plus ad hoc sessions when a significant design change occurs, tends to keep the register current without turning it into a bureaucratic burden.
Pro Tip: Schedule the handover review as a formal milestone, not an afterthought squeezed in during practical completion. Registers assembled in the final week are where most rationale entries go missing.
How MOSAIC Keeps a DfS Register Live and Audit-Ready
A register that only gets updated when someone remembers to is already failing. MOSAIC’s practical guide treats the document as live paperwork: every entry carries a version number, a change rationale, and a named owner for the next update, not just the original one.
- Assign one document owner per project phase so updates do not fall between design and construction teams.
- Use a consistent register template across projects rather than rebuilding the format each time; a shorter, standardized template combined with disciplined minutes tends to produce better compliance outcomes than an elaborate one nobody maintains consistently.
- Maintain a folder structure that pairs each register entry with its source drawing or minute, so an auditor can trace the decision in seconds.
- Build the facilities handover pack incrementally, not as a last-minute compilation.
Pro Tip: The most common failing MOSAIC finds during pre-handover reviews is a mitigation logged with no rationale and no linked document. Fix it by requiring one sentence of “why” and one attachment reference before any entry is marked closed.
How Do Inspectors Evaluate DfS Compliance?
Inspectors are not looking for a perfect register. They are looking for a traceable one. Expect checks on completeness against the project’s actual risk profile, date-stamped evidence that reviews happened when they were supposed to, and confirmation that a proper handover record exists for the building owner.
Common findings include:
- Missing rationale entries, which read as a review conducted on paper only
- Registers frozen at design stage with no construction-phase updates
- No evidence the DfSP actually communicated risks to future maintenance personnel
- Incomplete or absent handover documentation at project closeout
If an inspector flags gaps, the fastest remediation path is assembling a compliance pack: the current register, all review minutes, drawing revision history, and a short memo explaining what has been corrected. Acting within days rather than weeks signals to regulators that the lapse was administrative, not systemic.
MOSAIC’s Perspective on Meeting DfS Register Requirements
MOSAIC has advised developers through the full arc of DfS obligations, from first appointment of a DfSP through to handover packs delivered to building owners. The pattern that separates a smooth audit from a painful one is almost always the same: teams that treat the register as a living decision log, not year-end paperwork, pass without drama. If your project is approaching the threshold or your existing register has gaps, request a register review before an inspector finds them for you.
— Aman
MOSAIC’s DfS Advisory and Register Setup Services
Getting a DfS Register audit-ready under real project pressure is a different task from reading the regulation. Com has built its Design for Safety advisory around exactly that gap: developers get a DfSP appointment process, a register template matched to their project type, and a reviewer who has seen what inspectors actually flag, rather than a generic compliance checklist bought off the shelf.
Our services map directly onto the obligations covered above: DfSP advisory and appointment support, register setup with the fields and rationale structure auditors expect, facilitation of milestone review meetings, and preparation of the handover pack for facilities teams. A typical compliance review starts with an audit of your existing register against the WSH Regulations, followed by a gap report within days rather than weeks. If your project sits near the S$10 million threshold or your register has stalled since detailed design, request an environmental and safety compliance review and get a clear picture of where you stand before your next inspection.
