What Should a DfS Register Contain?
A DfS Register should contain the Design Risk Records, meeting minutes and residual-risk information generated through the DfS review process, kept up to date throughout design and construction and handed to the Developer in current form at project completion.
Direct answer
At minimum, a DfS Register documents what risks were identified, what was decided about them, and what remains after design measures are applied. It is a working file, not a one-time compliance form.
Core components
| Component | Purpose |
|---|---|
| Design Risk Records | Foreseeable design risks identified during reviews, with residual risk clearly indicated for each |
| Meeting minutes / review notes | Who attended, what was discussed, and what was decided at each DfS review |
| Residual-risk information | Risks not reasonably eliminable through design, with any control measures identified |
| Action tracker | Status of outstanding design-risk actions and dates of follow-up reviews |
Keeping it current
Avoid treating the Register as an administrative formality. A Register only assembled at the end of a project cannot have informed the design decisions it is meant to document.
The Register should be updated after every DfS review meeting, not compiled retrospectively before handover. Kept current, it lets the Developer, design team and Contractor check the live status of every identified design risk in one place. See our main DfS Register page → for who should have access and how the Register fits the wider review process.
Official references
- GuidanceWSH Council, Workplace Safety and Health Guidelines — Design for Safety — official source →
- RegulationWorkplace Safety and Health (Design for Safety) Regulations 2015 — Singapore Statutes Online — official source →