ConSASS Gap Assessment: Map 20 Elements for MOM Filing in Singapore

Safety officer observing worksite practices

A ConSASS gap assessment must deliver a mapped, evidence-backed scorecard across all 20 elements, with Band I to III shortfalls identified and ready for MOM eServices submission. The three immediate actions are running the full 20-element checklist, assembling a documentary and on-site evidence pack, and scheduling targeted implementation checks in high-risk trades before the auditor arrives.

TL;DR:

  • Use MOM’s current checklist, scorecard, and interview sheets, then score all 20 elements; Band III requires at least 70% in both earlier bands.
  • For documentation and implementation checks, collect three samples and verify at least two meet the question’s intent; document any smaller sample and its rationale.
  • Pair records with site walks and worker interviews, since a complete document set cannot establish whether crews understand and follow procedures in practice.
  • Begin four to six weeks before the audit, allowing time to close implementation gaps, which take longer to fix than missing documents.
  • For projects of S$30 million or more, the approved auditor and company representative must submit through MOM eServices using separate SingPass accounts.
Com
Prepare for a Stronger ConSASS Assessment
MOSAIC provides construction-sector safety consultancy, including ConSASS solutions, safety audits and support with safety standards and compliance.

Explore safety services

Table of Contents

ConSASS at a glance: checklist, scorecard and who it applies to in Singapore

The Construction Safety Audit Scoring System exists to give Singapore’s building sector a single, comparable yardstick for workplace safety and health performance. Before ConSASS, worksites were assessed against inconsistent internal standards, which made it difficult for clients, insurers, and regulators to compare safety maturity across contractors on different projects. ConSASS standardizes that comparison through a structured checklist, a weighted scorecard, and interview sheets, which every approved auditor uses the same way on every covered site, creating a clear maturity profile like those detailed in The Quality Grade That Follows Your Developer’s Name: How BCA’s CONQUAS Bands Read a Track Record.

Not every project needs a ConSASS audit. The requirement is triggered by contract value: construction projects with a contract sum of S$30 million or more fall under the audit mandate, a threshold we walk through in more detail in our piece on the S$30M trigger. Occupiers and principal contractors on qualifying projects are responsible for ensuring the audit takes place and that the report reaches MOM on schedule, a point we also unpack in when ConSASS is required.

Submission itself is restricted by role. Only an approved WSH auditor and an authorized company representative can submit, and both must log in with their own SingPass credentials. The system will not accept a report without both signatures attached, which means scheduling access for both parties is a logistical step worth locking in early, not an afterthought on submission day.

Three documents sit at the center of every ConSASS exercise, and safety officers should treat them as the working set for any gap assessment:

  • The ConSASS checklist, the official question bank auditors and companies used to score each element.
  • The ConSASS scorecard, where percentage results and banding outcomes are recorded for each of the 20 elements.
  • The interview sheets, used to structure worker and supervisor interviews that verify implementation on the ground.

Downloading the current versions of these three documents directly from MOM is the first practical task in any internal gap assessment, since using an outdated checklist or scorecard template is one of the more common and avoidable reasons an internal exercise fails to match the official audit later.

ConSASS structure and scoring: 3 bands, 20 elements, and the 70% threshold

ConSASS organizes safety performance into three bands that build on each other, and understanding this progression is the single most important thing a safety officer needs before running a gap assessment. Band I measures documentation: do the policies, procedures, and risk assessments exist on paper? Band II measures implementation: is what the documents describe actually happening on site, verified through observation and worker interviews? Band III measures selected best practices, the more advanced initiatives that go beyond baseline compliance.

These three bands are applied across 20 elements covering areas such as policy and organization, risk management, permit-to-work systems, training, emergency preparedness, incident investigation, and contractor management, among others. For each element, the scorecard produces a maturity percentage rather than a simple pass or fail, giving management a profile of where the organization is strong and where it is exposed.

A 70% threshold governs progression through the bands. An element must satisfy at least 70% of the applicable questions in Band I and Band II before the audit proceeds to assess that same element at Band III. Fall short of that mark, and the auditor stops scoring that element at the higher band, which caps the maximum achievable rating regardless of how strong other elements are.

A few scoring mechanics matter for gap assessment planning:

  • Questions marked not applicable (NA) are excluded from the denominator, so they neither help nor hurt the percentage, but the auditor’s remark explaining the NA still needs to be defensible.
  • An element that fails the 70% cut at Band I is not assessed further for that element, meaning documentation gaps have an outsized effect on the overall profile.
  • The scorecard aggregates all 20 element scores into an overall maturity picture, not a single pass or fail number for the whole site.

This banding logic changed meaningfully in the most recent revision. The 2020/2021 update to ConSASS deliberately shifted weight toward implementation questions and away from paperwork, aligning the checklist more closely with ISO 45001 and reflecting a broader move across the industry: a document can describe a perfect permit-to-work system, but if workers on site cannot explain how it operates, Band II exposes that gap immediately. We cover this shift and its practical implications in more depth in ConSASS: revolutionizing Singapore construction safety.

For gap assessment purposes, this means evidence collection cannot stop at the document register. A safety officer who gathers a complete set of policies and risk assessments but skips worker interviews and site walks will produce a Band I-only picture that bears little resemblance to what the actual audit will find.

Preparing and running a ConSASS gap assessment: a step-by-step practical workflow

A gap assessment is only useful if it mirrors the structure and rigor of the real audit, which means treating your own internal team the way an external auditor would treat the site. Start by assembling a small cross-functional team: a safety officer who knows the project intimately, a site supervisor who can speak to day-to-day practice, and, where possible, someone independent enough to challenge assumptions rather than confirm them.

Before any element is scored, gather the core documentation: the safety and health policy, risk assessments for all active work activities, standard operating procedures, permit-to-work records, training and competency records, incident and near-miss logs, and emergency response plans. Having these centralized before scoring begins saves considerable time once the element-by-element work starts.

  1. Download the current checklist, scorecard, and interview sheets directly from MOM’s ConSASS resources to ensure the assessment uses the exact question set auditors will apply.
  2. Work through each of the 20 elements in sequence, scoring Band I questions first against the documents gathered, then moving to Band II only for elements that clear the 70% threshold.
  3. Conduct structured interviews with workers and supervisors using the official interview sheet format, since Band II scoring depends heavily on what people on site can demonstrate, not just what management asserts.
  4. Capture photo and video evidence for physical controls such as fall protection, housekeeping, machine guarding, and signage, labeling each file with the element and question it supports.
  5. Record discrepancies immediately rather than waiting until the end, since a gap noticed during a site walk is easier to verify and correct on the spot than to reconstruct from memory later.
  6. Compile a draft scorecard reflecting the percentages achieved per element, flagging any that fall below the 70% mark for priority attention.

Not every gap carries equal weight, and a gap assessment that treats all 20 elements as equally urgent wastes time on low-risk paperwork while leaving real hazards unaddressed. A risk-based prioritization approach works better: elements tied to fall prevention, lifting operations, confined spaces, and permit-to-work systems deserve attention first, because these are the areas where a documentation-practice mismatch carries the highest consequence for workers and the steepest penalty from auditors. Lower-risk administrative elements, such as record-keeping formats, can follow once the higher-risk gaps are closed.

Pro Tip: Run your gap assessment at least four to six weeks before the scheduled audit date, so there is enough runway to close Band II implementation gaps, which take longer to fix than a missing document.

The output of this workflow should be four concrete deliverables: an internal scorecard mirroring the official format, a structured evidence pack organized by element, an action register assigning owners and deadlines to every identified gap, and a draft report for management sign-off before the real audit is scheduled. Skipping the management sign-off step is a common misstep. Without visible leadership endorsement of the corrective action plan, closing out high-priority gaps often stalls once the initial urgency of the gap assessment fades, a pattern we discuss further in our pre-audit checklist for S$30M projects.

Preparing and running a ConSASS gap assessment: a step-by-step practical workflow — overview diagram

Evidence, sampling and common audit failures: what auditors look for on site

Evidence quality determines whether a strong-looking internal scorecard survives contact with an actual auditor, and this is where many internal gap assessments fall short. Acceptable evidence spans several formats: signed and dated documents, photographs and video with visible timestamps, training attendance records cross-referenced against site personnel lists, and interview responses recorded on the official interview sheet. Each piece of evidence should be labeled with the element number and specific question it supports, since an auditor working through 204 checklist questions has no time to hunt for context.

MOM’s own guidance sets out specific sampling expectations for documentation-review and implementation-practice (DR/IP) questions. A minimum sample size of three is recommended for most DR/IP verification questions, with a passing criterion that at least two out of three samples meet the intent of the question, a rule detailed in the ConSASS user guide. When the available sample population is smaller than three, auditors may adjust the sampling approach, but that adjustment needs to be documented with a clear auditor’s remark rather than left unexplained.

Sampling and evidence practices to apply during your own gap assessment:

  • Sample across trades and locations, not just the areas easiest to access, since auditors often deliberately choose less convenient sampling points.
  • Document every NA marking with a specific reason, since an unexplained NA invites scrutiny rather than avoiding it.
  • Cross-check documents against site practice for every sampled item, because a mismatch between what a permit says and what workers describe is the single most common source of Band II failure.
  • Keep an evidence log mapping each sample back to its element and question number, so the same evidence can be retrieved quickly during the live audit.

The most frequent reasons an internal gap assessment overstates readiness come down to two patterns: insufficient evidence volume for a given element, and a visible gap between what the documentation describes and what workers or supervisors can demonstrate on request. A method statement that references a rescue plan for working at height means little if the interviewed worker cannot describe how the plan is executed. Closing these gaps requires more than updating a document; it requires a short, targeted toolbox talk or refresher session, followed by a re-interview to confirm the gap has actually closed, not just been noted as closed on paper.

Running a short pre-audit checklist against these common failure points, ideally a week or two before the official audit, catches the majority of issues that would otherwise surface for the first time in front of the auditor.

MOM eServices: preparing files, SingPass roles and submission checklist

Submission happens entirely online through MOM’s eServices portal, and the process is structured around two distinct SingPass logins rather than a single shared account. The approved WSH auditor logs in under their own credentials to prepare and declare the audit content, while the company representative, typically the WSH officer or an authorized management signatory, logs in separately to confirm and co-submit the report. Both steps are required before the submission is considered complete.

The portal’s own user manual walks through the submission sequence in detail, and the broad flow looks like this:

  1. Log in with SingPass and create a new ConSASS report under the relevant workplace number.
  2. Enter workplace details, including workplace name, address, and auditor and contact information, as required by the submission page.
  3. Save the report as a draft while attachments and scorecard entries are finalized, allowing work to continue across multiple sessions.
  4. Preview the full submission before declaring it, checking that every attached file opens correctly and matches the element it is meant to support.
  5. Declare and submit, after which both the auditor and company representative receive confirmation that the report has moved out of draft status.
  6. Retrieve the acknowledgement once submitted, which serves as proof of filing for internal records and future reference.

Accepted attachment formats are specified in MOM’s own ConSASS FAQ, and working within those formats from the start avoids a late scramble to convert files. Because the portal enforces per-file size limits, it pays to prepare the evidence pack with upload constraints in mind from the outset rather than after a rejection. Compressing photo and video files before attaching them, and splitting large evidence packages into logically grouped smaller files by element, keeps each upload within limits and makes the submission easier to navigate if the auditor needs to revisit a specific section.

Pro Tip: Name every attachment with the element number and a short description before uploading, such as “Element 7 Permit to Work Sample 2,” so both the auditor and the company representative can verify the right file is attached without opening each one.

If a report is returned rather than accepted, treat the returned items as a direct map of the gaps still needing attention. Address the specific points raised, resubmit through the same portal workflow, and keep a dated record of each submission attempt alongside the corresponding acknowledgement. Archiving the final acknowledgement together with the complete evidence pack protects the organization if questions arise during a future audit cycle or a related compliance review.

How to convert internal maturity findings into the official scorecard and deal with band mapping

Once the internal gap assessment is complete, the findings need to be translated into entries that match exactly what the official scorecard and eServices portal expect. This step catches organizations that ran a thorough internal exercise but formatted results in a way that does not transfer cleanly to the submission.

MOM’s 2021 revision reduced the live scorecard structure to three bands, but during the transition period a Conversion Matrix was published specifically to map 3-band audit results onto the eServices system’s existing entry fields, as described in the announcement covering the revised checklist. Teams preparing a submission should confirm which version of the scorecard and entry format currently applies in the eServices portal and use the matrix if the system still expects legacy band fields, rather than assuming the mapping is automatic.

A handful of decision rules keep scorecard entries defensible under scrutiny:

  • Mark NA only with a specific, documented reason, since an unexplained NA reads as an unverified gap rather than a genuine exclusion.
  • Record auditor’s remarks whenever sampling produces mixed results, preserving the reasoning behind a borderline score rather than leaving the percentage to speak for itself.
  • Enter percentages exactly as calculated from the sampled questions, cross-checked against the raw checklist scores before transferring them into the scorecard template.
  • Keep every remark and percentage entry consistent with the underlying evidence file, so a reviewer can trace any scorecard line back to its supporting document or interview record.

Before final submission, run a short quality-assurance pass: cross-check a sample of scored elements against their evidence files to confirm nothing was transcribed incorrectly, confirm both the auditor and company representative have reviewed and are ready to co-sign the declaration, and verify every attachment is in an accepted format and within the portal’s file-size limits. This final check is a short step that catches the kind of transcription or formatting error that otherwise turns into a returned report and a delayed audit timeline.

Practitioner insights from MOSAIC: turning a gap assessment into continuous WSH improvement

Treating ConSASS as a once-a-cycle paperwork obligation misses most of its value. We recommend running an internal gap assessment at a cadence tied to project milestones rather than waiting until an audit is imminent, typically at project kickoff, at the midpoint of major works, and again ahead of the formal MOM submission window. Findings from each cycle feed directly into management review meetings, where the action register becomes a standing agenda item rather than a document that gets filed and forgotten, a practice we discuss further in the business case for regular ConSASS audits.

We use a consistent template for evidence-pack structure across gap assessments to ensure comparability from one project to another.

  • A document index mapping every policy, procedure, and record to its corresponding element and question number.
  • A photo and video log organized by element, with timestamps and site location noted for each file.
  • An interview matrix tracking which workers and supervisors were interviewed, on what date, and against which questions.
  • A sample size log recording how many samples were drawn per DR/IP question and the outcome of each.

This structure does double duty: it speeds up the internal assessment itself, and it hands the eventual auditor a navigable evidence package rather than a loose folder of files. We cover the broader integration of this approach with wider safety management frameworks, including ISO 45001 alignment, in our 2026 guide to integrating ConSASS with DfMA and AI.

First-person perspective: why MOSAIC treats ConSASS as a safety-improvement tool, not a paperwork exercise

In our work across Singapore construction sites, the organizations that get the most out of ConSASS are the ones that stop viewing it as a compliance hurdle and start using it as a diagnostic for where their safety management system is genuinely weak. A scorecard percentage is only a number until a project leader acts on what it reveals, closes the specific gap, and checks that the fix holds under the next round of scrutiny. We built our ConSASS assessment service around that principle: a gap assessment should leave a project team with clearer priorities and genuine buy-in from management, not just a filed report. That shift in mindset is also what makes the eventual audit far less stressful, a point worth carrying into how we support submissions directly.

— Aman

How MOSAIC can help: ConSASS assessments, training and audit submission support

Running a full ConSASS gap assessment while also managing day-to-day site operations stretches most safety teams thin, and that is precisely where our services fit the tasks covered in this guide. Our ConSASS service covers the element-by-element internal assessment, evidence pack compilation, and scorecard preparation described above, while our WSH Audit and Inspection service extends that same rigor to broader site compliance checks beyond the ConSASS scope. For projects still closing design-stage hazards, our Design for Safety Professional service strengthens the upstream controls that several ConSASS elements score directly.

Com

Our typical engagement follows a straightforward flow:

  • Scoping: we confirm project size, trigger status, and audit timeline.
  • Internal gap assessment: our team runs the full 20-element review on site.
  • Evidence pack assembly: documents, photos, and interview records are organized by element.
  • Submission support: we help prepare the scorecard and eServices submission for your authorized representative.
  • Post-audit closure: outstanding actions are tracked through to resolution.

If your project is approaching the S$30 million threshold or your audit date is already on the calendar, reach out through our ConSASS service page to scope an engagement that fits your timeline.

FAQ

What is a ConSASS gap assessment?

A ConSASS gap assessment is an internal review that scores a construction site against the same 20 elements and 3 bands used in the official Construction Safety Audit Scoring System, identifying shortfalls before the formal MOM audit. It typically covers both documentation review and on-site implementation checks, mirroring the real audit’s structure.

Who needs to submit a ConSASS audit in Singapore?

Construction projects with a contract sum of S$30 million or more are required to undergo a ConSASS audit, with the report submitted by an approved WSH auditor and a company representative through MOM eServices. Both parties must log in using their own SingPass credentials to complete the submission.

What is the 70% rule in ConSASS scoring?

An element must satisfy at least 70% of the applicable questions in both Band I and Band II before it is assessed at Band III. If an element falls short at Band I, the auditor does not proceed to score that element further, which caps its overall maturity rating.

How many samples are needed for ConSASS evidence checks?

MOM guidance recommends a minimum sample size of three for documentation-review and implementation-practice questions, with a passing criterion of at least two out of three samples meeting the question’s intent. Where fewer than three samples are available, auditors may adjust the approach, but the reasoning should be documented.

Where can I get the official ConSASS checklist and scorecard?

The official checklist, scorecard, and interview sheets are published by MOM and available for download alongside the ConSASS checklist, which contains the full set of audit questions organized by element. Using the current version is essential, since outdated templates will not match the live eServices submission format.

Sources

Tags

What do you think?

Leave a Reply

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

Related Articles