Client Duties DfS: What Singapore Developers Must Do

Safety consultant adjusting harness on scaffold

Yes. Under Singapore’s Workplace Safety and Health (Design for Safety) Regulations, developers must eliminate or reduce foreseeable design risks to as low as reasonably practicable (ALARP), and a competent Design for Safety Professional (DfSP) becomes mandatory once contract value hits SGD 10 million or more. Client duties DfS obligations don’t stop at hiring someone. The developer’s statutory core:

  • Eliminate or reduce foreseeable design risks (ALARP) before construction begins
  • Convene DfS review meetings, or formally delegate that task to a DfSP
  • Maintain an accessible, inspection-ready DfS Register
  • Ensure competence and allocate real time and budget to DfS work

The threshold that changes everything: at SGD 10 million in contract value, appointing a DfSP stops being optional and becomes a legal requirement. Below that figure, developers still carry the underlying duties, just without the mandatory appointment. Either way, delegating tasks to a DfSP never transfers legal accountability away from the developer.

Key Takeaways

Developers retain legal accountability for ALARP outcomes under the WSH (DfS) Regulations even after appointing or delegating duties to a DfSP.

Point Details
SGD 10 million trigger Projects at or above this contract value must have a competent DfSP appointed before design progresses.
ALARP is mandatory, not aspirational Eliminate foreseeable design risks first; reduce to as low as reasonably practicable only when elimination is impractical.
Delegation doesn’t shift liability Developers can delegate meeting convening and register upkeep, but legal accountability stays with them.
Register must be inspection-ready Keep timestamped meeting records, residual risks, and mitigation owners accessible to MOM inspectors on request.
MOSAIC supports full DfS compliance Com offers DfSP advisory, delegation documentation, and register templates for developers managing these duties.

Table of Contents

Developer’s Statutory Duties Under the WSH (DfS) Regulations

The Regulations do not ask developers to aspire to safety. They require it, in a specific order of preference. The developer’s obligation is to eliminate or reduce foreseeable design risks to as low as reasonably practicable, and only after elimination has been ruled out impractical does reduction become the fallback. That hierarchy matters because it dictates how design decisions get justified on paper, not just how they get made.

Risk reduction has to happen at the source, and collective protective measures take priority over anything that depends on individual behavior. A parapet wall that permanently prevents a fall beats a harness point that depends on a worker clipping in correctly every single time. A permanent access gantry for facade maintenance beats a rope-access plan that has to be re-approved every cleaning cycle.

These duties don’t end when the building tops out. The Regulations follow the asset through its whole life:

  • Construction: sequencing, temporary works, and site access risks
  • Operation: how tenants and facility staff interact with the finished building
  • Maintenance: access to roofs, risers, facades, and plant rooms without exposing technicians to fall or confined-space hazards
  • Demolition: whether future contractors can dismantle the structure without cutting through live services or unstable elements

A design that looks efficient on paper but forces a maintenance technician onto an unprotected ledge has failed the ALARP test, however elegant the floor plan looks.

When Must a DfSP Be Appointed, and What Makes One Competent?

The trigger is precise: any project with a contract value of SGD 10 million or more requires the developer to appoint a competent DfSP before design work meaningfully progresses. Below that figure, the developer’s underlying duties still apply, but the mandatory appointment does not.

Competence isn’t a matter of a business card. Look for these signals before signing anyone on:

  • Completion of the WSQ Perform Design for Safety Professionals Duties unit, which covers convening meetings, maintaining registers, and communicating hazards to designers
  • Documented track record on comparable building types
  • Professional registration relevant to their discipline, where applicable
  • Availability to engage at concept design, not bolted on after schematics are locked

Pro Tip: Appoint your DfSP before the design brief is finalized, not after. Retrofitting DfS input onto a near-complete concept design almost always costs more in rework than the professional’s fee would have cost upfront.

Timing matters as much as the credential. A DfSP appointed too late has no meaningful influence on the decisions that carry the most risk.

What Can a Developer Delegate to a DfSP, and What Stays With Them?

Delegation is permitted, and in practice it’s how most compliance actually happens. The Regulations allow the developer to hand off the tasks of convening DfS review meetings and maintaining the DfS Register to an appointed DfSP. What delegation does not do is transfer legal liability.

A written delegation record should cover, at minimum:

  1. The specific duties being delegated (meeting convening, register maintenance, or both)
  2. The scope of authority granted, including sign-off limits
  3. Reporting frequency back to the developer
  4. The date delegation takes effect and any review point

Even with a signed delegation in place, the developer remains accountable for ALARP outcomes and for ensuring the DfSP is properly resourced. Hand the DfSP these items on day one:

  • The project brief and design intent
  • A realistic project timeline with DfS milestones built in
  • Full access to architectural, structural, and M&E design documents
  • Contact details for every designer and contractor who needs to attend review meetings

Skipping this handover is the single fastest way to produce a DfS Register that looks compliant but isn’t.

How Should DfS Review Meetings Run?

DfS review meetings exist to catch hazards while they’re still cheap to fix, which is on paper, not on site. The Regulations require developers to convene meetings attended by relevant designers and contractors, a duty that can be delegated to the DfSP but still needs the developer’s oversight to confirm it’s actually happening on schedule.

“Relevant” attendees are whoever’s design decisions could introduce or remove a hazard for that phase, structural engineers early on, facade and M&E consultants as the design matures, and the main contractor once buildability questions surface.

Each meeting should produce:

  1. A list of risks identified since the last session
  2. Proposed elimination or reduction measures, ranked by the ALARP hierarchy
  3. Named action owners with real deadlines
  4. An updated entry in the DfS Register reflecting decisions made

Loose verbal agreements don’t survive an inspection. Structure the follow-up:

  • Issue minutes within a set number of working days
  • Log corrective actions with due dates, not vague intentions
  • Keep evidence trails, drawings, emails, sign-offs, in a format an inspector can review without a guided tour

What Belongs in the DfS Register, and Who Needs Access?

The DfS Register is the developer’s proof that ALARP thinking actually happened, not just that someone claimed it did. MOM guidance confirms inspectors can request this documentation at any point during a project, so treat it as a live compliance document, not year end paperwork.

A defensible register records:

  • Every DfS review meeting, with dates and attendee lists
  • Residual risks that couldn’t be eliminated, and why
  • The mitigation measures adopted instead
  • The party responsible for each mitigation
  • Timestamps for every entry and revision
  • Linked design drawings or specifications referenced in each decision

Access needs to extend beyond the developer’s desk. The DfSP, relevant designers, the main contractor’s safety team, and MOM inspectors on request all need a route into the register without waiting on someone’s approval.

Pro Tip: Use version-controlled cloud storage with a locked audit trail rather than a shared spreadsheet that anyone can silently edit. An inspector who spots inconsistent version histories will ask harder questions than one who sees a clean, timestamped record.

Locked external drive and keyboard on desk

How Do You Build DfS Into Procurement and Scheduling?

Client duties DfS compliance falls apart most often at the procurement stage, before a single drawing is reviewed. Fix that by building requirements into the paperwork itself:

  1. Write DfS attendance and register-maintenance obligations directly into appointment letters for designers and contractors
  2. Add competence evidence, WSQ completion, prior DfS project history, as a scored criterion in tender evaluation, not an afterthought
  3. Allocate specific budget and schedule time for DfS activities before the design program is finalized

Resourcing failures are a documented pattern: regulations require developers to provide sufficient time and resources for DfS duties, yet compressed programs routinely squeeze this out first.

Once contracts are signed, keep information flowing:

  • Issue a written design brief that states DfS expectations explicitly
  • Share the DfS Register with every relevant designer, not just the DfSP
  • Enforce meeting attendance as a contractual obligation, not a courtesy request

What Are the Common Pitfalls and Retained Liabilities?

Developers who assume a signed DfSP contract closes their legal exposure are wrong. Liability for ALARP outcomes stays with the developer regardless of who was hired to help, and MOM can pursue enforcement action against the developer directly when documentation falls short.

The pitfalls that trigger this most often:

  • Bringing the DfSP in after schematic design is locked, when meaningful changes cost far more
  • Treating competence checks as a formality rather than a real evaluation
  • Letting the DfS Register lag behind actual meeting activity by weeks or months
  • Assuming delegation paperwork alone satisfies the developer’s own obligations

Mitigate with structure, not good intentions: schedule internal audits at each design gate, assign someone specific to check register currency monthly, and log corrective actions the moment a gap surfaces rather than at project close.

How MOSAIC Helps Developers Put DfS Duties Into Practice

Com built a practitioner-level checklist that turns the Regulations into sequenced action:

  • Confirm whether the project crosses the SGD 10 million threshold
  • Appoint a DfSP or formalize delegation in writing
  • Establish a fixed meeting schedule tied to design milestones
  • Adopt a structured DfS Register template from day one
  • Run periodic audits against the register, not just at handover

Com’s construction safety consultancy work covers DfSP advisory support, delegation documentation, register templates built for inspection readiness, and facilitation toward WSQ competency training.

Pro Tip: Engage a DfS advisor at concept design, not at tender. Early involvement catches structural and access hazards while they still cost drawings to fix, not steel.

DfS as a Value Driver, Not a Paperwork Exercise

The conventional read on DfS treats it as a compliance tax, something bolted onto a project timeline to satisfy a regulator. That framing gets the economics backward. Risks caught at concept design cost drawings to fix. The same risks caught during construction cost rework, delay, and sometimes a stop-work order. Leadership buy-in shouldn’t come from fear of MOM enforcement. It should come from recognizing that early DfS integration is cheaper than the alternative, every time. Allocate the budget and the calendar time before the design program locks, and the register stops being a liability shield and starts being a genuine planning tool.

— Aman

Get Compliance Support From MOSAIC

Meeting every client duty under the DfS Regulations while running a live project is demanding work, and most developers don’t have a dedicated DfS specialist sitting in house. Com is built for exactly that gap: construction developers in Singapore get DfSP advisory, delegation documentation, register templates, and audit support from a team that works inside the WSH framework daily, not once a project already has a problem.

Com

The typical engagement starts with an assessment of your project’s threshold status and current DfS readiness, moves into a compliance plan mapped to your design schedule, then covers DfS meeting coordination and register maintenance through to handover. If your project is approaching or has crossed the SGD 10 million contract value mark, reach out through the Com landing page to scope a DfSP engagement before your next design milestone.

Authoritative Legislation and Practical DfS Resources

Verify every requirement against the primary text rather than secondhand summaries. Start with the Workplace Safety and Health (Design for Safety) Regulations 2015 and its supplementary provisions on meeting and register duties, then review MOM’s stakeholder responsibilities guidance for enforcement context. The sector’s DfS in buildings and structures guideline adds practical detail on meeting procedure and register format. Keep dated copies of every DfS Register entry, they’re your defense the day an inspector asks to see them.

Sources

Tags

What do you think?

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Articles