The Workplace Safety and Health (Design for Safety) Regulations 2015 govern how developers, designers and contractors identify and reduce design-related risks before construction begins in Singapore. They apply chiefly to projects where a developer engages in construction work valued at $10 million or more under a development falling within the Planning Act, and the Regulations took operative effect on August 1, 2016. Teams on a qualifying project must convene design for safety (DfS) review meetings, appoint competent designers and contractors to attend them and begin maintaining a DfS Register from the earliest design stage.
TL;DR:
- Projects qualifying under the regulations must involve a construction contract of at least $10 million, a developer acting in a business capacity, and development under the Planning Act.
- The primary responsibility for maintaining an accurate and up-to-date DfS Register rests with the developer, even if a DfS Professional is appointed to facilitate the process.
- Regular DfS reviews are required at concept, detailed, and pre-construction stages, with additional reviews whenever design or risk profiles change significantly.
- Failing to produce or keep the DfS Register available on request can result in fines of up to $10,000 and other penalties depending on the breach.
- Delegating DfS duties to a professional does not transfer ultimate accountability, which remains with the developer to ensure compliance and safety.
Table of Contents
- What the WSH (DfS) Regulations require: scope, thresholds and key definitions
- Statutory duties: what developers, designers and contractors must do
- The DfS review process (GUIDE): stage-by-stage practical guide
- DfS Register: what to record, how to maintain it and lifecycle responsibilities
- Stage-by-stage compliance checklist and templates
- Delegation, common implementation failures and practitioner remedies
- Enforcement, typical inspector checks and penalties for non-compliance
- Aman’s practical perspective on implementing DfS on Singapore projects
- How Aman Engineering Consultancy can help with DfS compliance
- FAQ
- Sources
What the WSH (DfS) Regulations require: scope, thresholds and key definitions
The Workplace Safety and Health (Design for Safety) Regulations 2015 were made under section 65 of the Workplace Safety and Health Act and came into operation on August 1, 2016, establishing a statutory requirement to manage design risk before construction work starts. We treat this operative date as the dividing line for transitional projects: where a designer was appointed before August 1, 2016, that project generally falls outside the Regulations even if construction continues past that date, according to the applicability provisions set out in the statute.
For new projects, three conditions normally have to be met together before the Regulations apply:
- The construction work is undertaken by a developer acting in the course of business, not a private individual building for personal occupation.
- The contract sum for the construction work is at least $10 million, as stated in the Regulations’ applicability provisions.
- The project constitutes development under section 3(1) of the Planning Act, which covers most new building and redevelopment works requiring planning permission.
A separate rule applies to modifications. When a structure already has an existing DfS Register, a later modification to that structure that constitutes development under the Planning Act falls within the Regulations regardless of the contract sum, meaning a retrofit on a registered building can still trigger full DfS obligations. This modification rule catches many addition and alteration projects that project teams assume are too small to matter.
A project qualifies under the Regulations when it combines a commercial developer, a construction contract sum of at least $10 million, and development status under the Planning Act, or when it modifies a structure that already carries a DfS Register, as set out in the Workplace Safety and Health (Design for Safety) Regulations 2015. That single threshold decision shapes every procurement and design decision that follows.
In practice, a 40-story mixed-use tower built by a property developer with a $300 million construction contract clearly qualifies on every count. A homeowner building a single landed house for personal use, even at a high contract value, typically falls outside the Regulations because the “course of business” test is not met. A warehouse extension valued at $8 million by a logistics developer sits below the contract sum threshold and would not qualify unless it modifies a structure that already carries a DfS Register.
Statutory duties: what developers, designers and contractors must do
The Regulations assign distinct, non-interchangeable duties to three parties, and each duty has to be discharged by the party named in the statute even when day-to-day coordination is handled by a consultant.
Developers bear the primary obligation. We read the supplementary duties provisions as requiring developers to convene DfS review meetings, eliminate or reduce foreseeable design risks as far as reasonably practicable, and identify any residual risks together with the controls needed to manage them. The developer also has to ensure appointed designers and contractors attend these meetings and that the resulting decisions get recorded.
Designers carry a parallel technical duty. They have to prepare designs that eliminate foreseeable safety risks where practicable, propose design modifications when a risk cannot be eliminated outright, and pass on risk information to contractors and future maintenance teams so residual hazards are not rediscovered the hard way during construction or operation.
Contractors complete the triangle. Their duties include reporting foreseeable risks they identify once construction planning begins, ensuring the workers and supervisors they deploy are competent to manage the risks flagged in the design, and attending DfS review meetings when design decisions affect how the work will be carried out on site.
Key duties by party, in summary:
- Developer: convenes reviews, eliminates or reduces risk, maintains the Register, retains ultimate accountability.
- Designer: proposes safer design alternatives, documents residual risk, communicates hazard information forward.
- Contractor: flags construction-stage risks, confirms worker competence, participates in scheduled reviews.
- DfS Professional (where appointed): facilitates the review process and record-keeping on the developer’s behalf.
Delegation is permitted but limited. A developer may appoint a Design for Safety Professional, sometimes called a Risk Management Facilitator, to convene meetings, chase documentation and keep the Register current. What cannot be delegated is the developer’s underlying accountability: if the Register is incomplete or a review never happens, the developer remains the party answerable to the authorities, not the DfS Professional acting on its behalf. This distinction can often be blurred, so it deserves explicit mention in appointment letters and consultancy briefs: a DfS Professional manages the process, the developer owns the outcome. Our Design for Safety (DfS) / Risk Management Facilitator (RMF) service is built around that division of labor.
The DfS review process (GUIDE): stage-by-stage practical guide
The Workplace Safety and Health Council frames the review process around a structured sequence commonly referred to as GUIDE, standing for Plan, review design, Record decisions, Communicate residual risks, Monitor actions and Handover the register. This structure, described in the WSH Guidelines on Design for Safety, gives project teams a repeatable framework rather than a one-off compliance exercise.
- Plan the review by scheduling it against key design milestones and circulating the agenda, drawings and any known hazard list in advance.
- Review design collaboratively, with designers walking attendees through the elements that carry foreseeable risk and proposing modifications where elimination is not practicable.
- Record decisions in writing immediately, capturing what was changed, what was accepted as residual risk and who agreed to each point.
- Communicate residual risks to the contractors, future maintenance personnel and, where relevant, the facilities team who will inherit the structure.
- Monitor actions arising from the review until each one is closed out, not merely noted.
- Handover register contents to the next stage of the project, and ultimately to the building owner, so the record travels with the structure rather than staying with one consultant’s files.
Reviews should run at concept design, detailed design and pre-construction stages at minimum, and the Regulations’ practical logic calls for an additional review whenever the design, construction method, site access or risk profile changes materially after the last session. A facade system swapped late in design, for instance, warrants its own review rather than a retrospective note in the existing record.
Attendance matters as much as timing. A useful review brings together the developer’s representative, the lead designer, the main contractor’s safety coordinator and, where appointed, the DfS Professional facilitating the session. Each attendee should arrive with something concrete: designers with updated drawings and a list of risks they have already tried to design out, contractors with method statements for the activities under discussion, and the facilitator with the action tracker from the previous meeting.
Pro Tip: Close every DfS review with a dated action list naming an owner for each item, not just a summary of what was discussed; unowned actions are the most common reason registers go stale.
The expected outputs of each review are Design Risk Records documenting hazards and controls, signed minutes, and an action tracker showing outstanding items and their deadlines. These three documents feed directly into the DfS Register, and a review that produces discussion but no Design Risk Record has not satisfied the statutory intent even if attendance was full.
DfS Register: what to record, how to maintain it and lifecycle responsibilities
The DfS Register is the single document regulators and inspectors will ask to see first, and its contents are specified with some precision in the Workplace Safety and Health (Design for Safety) Regulations 2015. The Register must contain records of every DfS review meeting held and a record of every residual design risk that could not be eliminated, kept current as the project proceeds rather than compiled retroactively at handover.
A compliant Register typically holds:
- Design Risk Records identifying each hazard, the design response and any residual risk left after mitigation.
- Minutes of every DfS review meeting, including attendance and the decisions reached.
- A log of residual risks together with the controls in place to manage them during construction and later occupation.
- An action tracker showing items raised, owners assigned and closure dates.
The Register must be kept up to date, remain accessible to appointed designers and contractors, and be available for inspection by registered workplace inspectors, under the Workplace Safety and Health (Design for Safety) Regulations 2015. That accessibility requirement means a Register locked in one consultant’s personal files does not meet the standard, even if its contents are accurate.
The Register’s life does not end at completion. For structures still standing, the record should stay with the building to support future maintenance and, eventually, demolition planning, since the residual risks identified at design stage often remain relevant decades later. Where ownership changes, the Register should transfer with the asset, including to a subsidiary management corporation taking over a strata-titled development, so the next owner inherits the hazard knowledge rather than starting from zero.
Access needs to extend beyond the developer’s own team. Designers and contractors working on later alterations need to see what residual risks were accepted at original design stage, and inspectors need a route to review the record without delay. We recommend keeping the Register in an electronic format with version control, paired with a short handover checklist confirming which party holds the current copy at each project milestone. Our Risk Assessment Registers guidance covers the practical mechanics of keeping a live register current across a multi-year project.
Stage-by-stage compliance checklist and templates
Translating the statute into a working checklist keeps compliance from becoming a last-minute scramble before a Building and Construction Authority or Ministry of Manpower audit.
- Concept design: hold the first DfS review, open the Register, document early site and buildability hazards.
- Detailed design: run a focused review on structural, facade and mechanical and electrical risk, update Design Risk Records as drawings firm up.
- Pre-construction: confirm the main contractor’s safety coordinator has reviewed the Register, close outstanding design-stage actions before work starts on site.
- Construction: re-run a review whenever method, sequencing or access changes, log new residual risks as they emerge.
- Handover: compile the full Register, hand it to the building owner or management corporation with a signed transfer record.
- Post-handover: retain the Register for the life of the structure, update it if later alteration works trigger a further review.
Documents worth keeping at every stage include signed meeting minutes, Design Risk Records, evidence of designer and contractor competence, and a running action log showing closure dates rather than open-ended promises.
A usable Design Risk Record needs, at minimum:
- A description of the hazard and the building element it relates to.
- The design response taken, and whether the risk was eliminated or only reduced.
- Any residual risk remaining, with the control measure assigned to manage it.
- The date, attendees and the person accountable for follow-up.
Quick remediation when a record is found incomplete usually means reconvening the relevant designer and developer representative, documenting the missing decision retroactively with a clear note that it was added after the fact, and closing the gap before the next scheduled review rather than waiting for the next audit to surface it.
When project scope or contract sum changes mid-project, for instance a value engineering exercise that pushes the contract sum past $10 million, the Register should be opened or, if already open, reviewed against the revised scope at the next available DfS meeting rather than at project close. Our Design for Safety Requirements guide walks through how a scope change mid-project typically affects an existing compliance plan.
Delegation, common implementation failures and practitioner remedies
Appointing a Design for Safety Professional is sound practice, but it works only when the developer treats the appointment as support rather than substitution. A DfS Professional can run meetings, draft minutes and chase outstanding actions; the developer still has to ensure those meetings happen on schedule and that the Register reflects reality rather than a tidied-up summary.
The implementation failures we see most often on Singapore projects follow a short, repeatable list:
- Starting DfS reviews only after detailed design is locked, which leaves little room to design risks out rather than accept them.
- Treating the Register as a paperwork exercise produced for a single audit rather than a living record updated continuously.
- Letting the Register go incomplete when a designer or contractor changes partway through the project.
- Skipping competence checks on site supervisors, which weakens the contractor’s statutory duty to ensure capable personnel manage the risks flagged in design.
The remedies are procedural rather than technical. Early contractor involvement, even before the main contract is awarded, lets construction-stage risks surface while the design can still absorb changes cheaply. Procurement clauses that name DfS participation as a contractual obligation, not a courtesy, keep attendance from slipping once a project enters a busy construction phase. Linking the Register to a building information model, so Design Risk Records sit against specific model elements, reduces the chance a residual risk gets lost between design handover and facilities management.
Pro Tip: Write DfS attendance and Register upkeep into the contractor’s scope of work at tender stage; an obligation buried in a safety plan appendix gets treated as optional far more often than one written into the contract itself.
Enforcement, typical inspector checks and penalties for non-compliance
Registered workplace inspectors can request the DfS Register at any point in a project’s life, and failing to make it available on request is itself an offence. Under the WSH Guidelines on Design for Safety, failing to keep or produce the DfS Register on request can attract a fine of up to $10,000 upon conviction, with other contraventions under the Regulations carrying their own fine and imprisonment ceilings depending on the nature of the breach.
An inspection typically focuses on a short set of documents:
- The current DfS Register, including Design Risk Records and meeting minutes.
- Evidence that reviews were held at the stages the project’s risk profile demanded, not just once at the start.
- Proof of designer and contractor competence relevant to the risks on record.
- An audit trail showing open actions were closed, not left pending indefinitely.
We recommend an internal audit of the Register every few months during active construction, checked against the latest drawings and method statements, so any gap surfaces internally before an inspector finds it first. Where a gap is found, the fastest remediation is to reconvene the relevant parties, document the missing decision honestly, and close it before the next scheduled review.
Aman’s practical perspective on implementing DfS on Singapore projects
Industry leadership has been explicit that DfS exists to prevent harm upstream, with the Design for Safety Implementation Focus Group Discussion emphasizing that identifying hazards at the planning and design stage avoids far costlier rectification once construction is underway. We think the industry still underrates how much of DfS success depends on the Register being treated as a working document rather than a compliance artifact produced once and filed away.
Our view, formed across statutory submission work on Singapore projects, is that the developers who get the most value from DfS are the ones who ask their DfS Professional for a short verbal update between formal reviews rather than waiting for the next scheduled meeting to learn that a risk was never closed out. Regulators are also pushing for clearer boundaries around what a DfS Professional can decide alone and what still needs the developer’s sign-off, and that clarity benefits everyone once it is written into the appointment from day one.
— Aman
How Aman Engineering Consultancy can help with DfS compliance
We support developers, main contractors and building owners through every stage the Regulations and WSH Guidelines describe, from convening the first concept-stage DfS review through to compiling the Register at handover. Our Design for Safety Professional (DfSP) / Risk Management Facilitator (RMF) Works service covers the facilitation role the statute allows a developer to delegate, while our statutory submission team handles the related approvals that run alongside DfS obligations, including coordination with the Building and Construction Authority, Ministry of Manpower, Urban Redevelopment Authority and Singapore Civil Defence Force where a project’s scope requires it.
Where a Register needs to connect to building information modeling for a cleaner handover to facilities management, our 3D BIM team links Design Risk Records to specific model elements rather than leaving them as a standalone document.
If your project is approaching the $10 million contract sum threshold or involves modifying a structure that already carries a DfS Register, visit Aman Engineering Consultancy to discuss how we can facilitate your DfS reviews and keep your Register audit-ready from the first design meeting.
FAQ
What triggers the DfS Regulations on a Singapore project?
The Regulations generally apply when a developer acting in the course of business undertakes construction work with a contract sum of at least $10 million that qualifies as development under the Planning Act. A separate rule also brings in modifications to a structure that already has an existing DfS Register, regardless of the contract sum, as set out in the Regulations’ applicability provisions.
Who is responsible for maintaining the DfS Register?
The developer holds primary responsibility for ensuring the Register exists and stays current, even where day-to-day upkeep is delegated to a DfS Professional. Designers and contractors must have access to it and contribute the records of risks and decisions reached during DfS reviews.
What happens if a developer fails to keep or produce the DfS Register?
Failing to keep or make the Register available for inspection on request is an offence, and the WSH Guidelines note fines of up to $10,000 upon conviction for this specific failure. Other contraventions under the Regulations carry separate fine and imprisonment ceilings depending on the breach.
How often do DfS reviews need to be held?
Reviews should be held at concept design, detailed design and pre-construction stages at minimum, with an additional review whenever the design, construction method, site access or risk profile changes materially. There is no fixed calendar interval; the trigger is a meaningful change in risk, not a set number of months.
Can a developer delegate DfS duties entirely to a consultant?
A developer can appoint a Design for Safety Professional to convene meetings and maintain records, but the underlying statutory accountability stays with the developer. If a review is missed or the Register falls behind, it is the developer, not the appointed professional, who remains answerable to the authorities.
Sources
- Workplace Safety and Health (Design for Safety) Regulations 2015 – Singapore Statutes Online
- Workplace Safety and Health Guidelines on Design for Safety (Revised guidance document)
- Speech by Mr Tan Swee Yiow at the Design for Safety Implementation Focus Group Discussion