Passing a ConSASS audit means meeting Band I and Band II readiness, at least 70% of relevant questions per SHMS element, with evidence verified through document review, interviews, and physical inspection. Mandatory for worksites with contract sums of S$30 million or more, the audit rewards sites that map every checklist question to traceable evidence before the auditor arrives, confirm a SAC-accredited auditor, and assign someone to own the MOM WSH eServices submission.
TL;DR:
- Sites must ensure at least 70% of questions in Band I and II are verified with documented evidence and verified through interviews and physical checks.
- External audits are mandatory for worksites with a contract sum of S$30 million or more, conducted by SAC-accredited auditors, at least every six months during the project.
- Preparing a detailed evidence matrix that links each checklist question to specific documents, staff, and site locations greatly improves audit performance.
- Most failures occur on the site floor during the audit when controls are not explained clearly or evidence is missing, not because controls are absent.
- Continuous management discipline and a focus on fixing the weakest elements, rather than just updating manuals, lead to better long-term ConSASS readiness.
Table of Contents
- What ConSASS checks and how the scoring works
- Who must run ConSASS, how often, and who can audit
- Build an evidence matrix before the auditor walks in
- On audit day: where sites lose marks
- Submitting through MOM WSH eServices and handling returns
- Why ConSASS readiness is a system, not a checklist exercise
- How MOSAIC supports ConSASS readiness and submission
- Get your site audit-ready before the auditor arrives
- FAQ
What ConSASS checks and how the scoring works
ConSASS does not function as a simple pass or fail exercise. According to MOM’s FAQ on passing marks, the audit scores the development status of each safety and health management system element, and the current guide applies over 200 questions across three bands. Each element must clear at least 70% of questions in Band I and Band II before Band III best-practice questions even come into play.
The three bands mean distinct things on site:
- Band I covers documentation: policies, risk assessments, and procedures exist and are current.
- Band II covers implementation: workers follow those procedures, supervisors enforce them, and records prove it.
- Band III covers best practice: initiatives beyond regulatory minimums, audited only once Band I and II pass.
Auditors shade each element on the scorecard rather than issue a single pass/fail verdict, producing a maturity profile. Management should read that profile as a roadmap: the weakest element, not the overall average, tells you where the next incident is most likely to originate.
Who must run ConSASS, how often, and who can audit
Contract sum thresholds decide who is in scope. Per the MOM ConSASS submission page, worksites valued at S$10 million or more must maintain a safety and health management system, while worksites at S$30 million or more must commission external ConSASS audits, a requirement in force since August 2011. Our overview of ConSASS requirements for S$30M projects breaks down what qualifies as contract sum for mixed-scope projects.
Frequency and auditor eligibility both carry compliance weight:
- Mandatory sites need an external audit periodically during the duration of works.
- Auditors must hold current SAC accreditation as a Workplace Safety and Health Auditing Organisation, confirmed through MOM’s auditor engagement FAQ.
- Accreditation scope should match the worksite’s risk profile before you lock in a booking date.
Our checklist for occupiers facing the S$30M trigger covers how to verify accreditation status before scheduling.
Build an evidence matrix before the auditor walks in
Most sites fail not because controls are missing but because evidence cannot be produced on demand. An evidence matrix fixes that gap by assigning each checklist question a document, an interviewee, and a physical check.
- List every checklist question from the current ConSASS version and confirm which SHMS element it sits under.
- Assign a document owner for each Band I question: permit records, training logs, risk assessments, inspection reports.
- Name an interviewee for each Band II question, typically a supervisor or frontline worker who can describe the control in their own words.
- Identify the physical location an auditor would need to visit to confirm the control exists on site.
- Apply the sampling rule: the ConSASS user guide recommends a minimum sample of three records for document review and interview questions, with two of three needing to pass. When only two samples exist, the auditor checks 100% of them, so pull extra records wherever the project allows.
- Run mock interviews with the staff named in step three so answers stay consistent with the documentation.
- Walk the site before audit day and close out any corrective actions still open in your tracker.
- Confirm admin basics: checklist version in use, the named eService submitter, and the auditor’s SAC accreditation certificate on file.
Pro Tip: Keep the evidence matrix as a living document between audits, not a one-time exercise before the auditor arrives.
Our practical guide to a high ConSASS score includes sample document templates for common Band I and Band II questions.
On audit day: where sites lose marks
The gap between a document and the site floor is where most questions turn into a “No.” A supervisor who cannot explain a control in their own words signals weak Band II implementation even when the paperwork is flawless, and missing closure evidence on corrective actions is one of the most common repeat findings.
ConSASS credits a question only when document, interview, and physical observation all point to the same control. A toolbox talk record means little if the worker interviewed cannot recall it and the hazard it addressed is still unguarded on site.
Before the auditor arrives:
- Stage evidence folders by SHMS element, not by date, so retrieval is fast.
- Confirm sampled records are pulled and labeled, not scattered across shared drives.
- Have named interviewees briefed on which questions they may be asked.
- Walk the auditor to the physical control rather than describing it from the site office.
Pro Tip: Give each interviewee a one-page script of the three or four questions most likely to come their way for their area of responsibility.
For crews managing outdoor or landscaping-adjacent work, this guide to on-site safety checks offers useful cross-trade inspection habits worth adapting to a construction context.
Submitting through MOM WSH eServices and handling returns
Once the audit closes, the report has to reach MOM through the Submit a ConSASS Audit eService, which requires Singpass login and a complete package: the checklist, the scorecard, interview sheets, and the final audit report with supporting documents.
- Create the report in the eService portal and verify workplace particulars match MOM’s records.
- Attach the checklist, scorecard, and final report, saving drafts as needed while documents are finalized.
- Preview and declare the submission before it goes in, since this step is where most data mismatches surface.
- Submit and monitor status through the dashboard, which differs depending on whether the login belongs to the auditor, the WSHAO, or the occupier.
If MOM returns a report, edit the flagged sections, re-upload the amended documents, and resubmit promptly. Assign one named person to monitor the eService account so a returned report does not sit unanswered for weeks.
Why ConSASS readiness is a system, not a checklist exercise
The temptation on most sites is to treat ConSASS as a document drill: polish the manuals, print the policies, and hope the scorecard follows. That approach consistently produces sites with strong Band I paper and weak Band II implementation, because a manual that nobody on the floor has internalized earns no credit once an auditor asks a supervisor to explain it.
The more defensible position is that ConSASS readiness is a continuous management discipline, not a seasonal sprint before the auditor’s visit. Sites that treat the banded scorecard as a standing diagnostic, fixing the weakest element first rather than chasing an average, tend to show steadier improvement across audit cycles than sites that cram. Our view on using ConSASS results for continuous improvement expands on why the post-audit period matters as much as the pre-audit scramble.
— Aman
How MOSAIC supports ConSASS readiness and submission
We support project teams through the full readiness cycle rather than a single visit before audit day. Our work typically includes readiness reviews against the current checklist, building the evidence matrix element by element, running mock audits that mirror the DR, IP, and PI structure, and guiding teams through the submission process once the audit closes.
Because the banded scorecard points to specific weak elements, we prioritize corrective action where it moves the needle fastest rather than spreading effort evenly across every question. A short readiness review or mock audit, with a clear set of deliverables agreed upfront, is usually enough to surface the gaps a site needs to close before the real audit date.
Get your site audit-ready before the auditor arrives
We offer several services that map directly onto the preparation steps above:
- ConSASS support covers readiness reviews, evidence matrix development, and mock audits ahead of your scheduled assessment.
- WSH Audit and Inspection services help confirm your SHMS implementation matches your documentation before an external auditor tests it.
- EHS Advisory and Documentation builds the manuals, risk assessments, and records that form your Band I evidence base.
- Design for Safety Professional input addresses hazards at the design stage, reducing the control gaps ConSASS later audits.
If your contract sum puts you in scope for a six-monthly external audit, request a readiness assessment through our contact page and we will outline the deliverables before work begins.
FAQ
What is considered a passing mark under ConSASS?
There is no single percentage pass mark. MOM’s FAQ explains that each SHMS element needs at least 70% of its Band I and Band II questions to meet the required standard before Band III questions are even assessed.
How often does a site need a ConSASS audit?
Worksites with contract sums of S$30 million or more must commission an external ConSASS audit at least once every six months for the duration of the project, as set out on MOM’s ConSASS submission page.
Who can conduct a ConSASS audit in Singapore?
Only auditors from organizations accredited by the Singapore Accreditation Council as Workplace Safety and Health Auditing Organisations can conduct the audit, per MOM’s auditor engagement guidance. Confirm accreditation scope before scheduling.
What happens if MOM returns a submitted ConSASS report?
The named eService submitter edits the flagged sections, re-uploads the amended checklist or supporting documents, and resubmits through MOM WSH eServices. Assigning one accountable person for monitoring avoids delays in responding.
Can MOSAIC help prepare for a ConSASS audit?
Yes, our ConSASS services include readiness reviews, evidence matrix development, and mock audits structured around the current checklist’s banding and sampling rules.
