Switching BAS Providers for SGBuildex — What to Check Before You Commit

Before the mandate hits, many contractors will need to verify whether their existing BAS vendor is SGBuildex-integrated — and act if they are not. Here is what to check, what your options are, and what a switch actually involves.

Short Answer

Check BCA's official list of SGBuildex-integrated BAS providers at go.gov.sg/integrated-bas-providers. If your vendor is on the list, confirm with them directly that the integration is live — not just in development.

If your vendor is not on the list, you have two options: switch to a provider that is already integrated, or work with your existing vendor to build the integration. Both take time — and the mandate deadline does not move.

Step 1 — Check the official list

BCA maintains a list of SGBuildex-connected Biometric Authentication System (BAS) solutions at go.gov.sg/integrated-bas-providers. This is the authoritative reference — if your vendor is not on this list, they are not currently integrated with SGBuildex.

If your vendor is on the list, that is a necessary condition but not a sufficient one. Being listed means integration exists or is in progress — it does not confirm the integration is live and tested. 

Ask your vendor directly: “Is your SGBuildex integration currently live, and which projects is it running on?”

A live pilot on an active project is a stronger signal than a listed status alone.

Step 2 — If your vendor is not integrated, understand your options

There are two paths available if your current BAS vendor is not SGBuildex-integrated:

1. Switch to an integrated provider
   1. Move to a BAS provider like Hubble that already has a live SGBuildex connection. 
   2. This is the lower-risk path for meeting the May 2026 deadline — the integration is already built and tested. The trade-off is a provider switch, with the associated setup, hardware compatibility check, and worker data import.
2. Work with your existing vendor to build integration
   1. Your current vendor builds the SGBuildex API connection. This requires User Acceptance Testing before it can go live. 
   2. The risk here is timeline — building and testing an integration takes time, and if your vendor has not started, meeting the May 2026 deadline may not be feasible.

The question to ask your existing vendor

"Have you started building the SGBuildex integration, and when will it complete User Acceptance Testing?" If they cannot give you a concrete timeline, factor that uncertainty into your planning. 

Waiting for a vendor to complete integration is a risk that the contractor carries, not the vendor.

Step 3 — Check hardware compatibility before switching

One of the most common concerns when switching BAS providers is whether existing site hardware — turnstiles, biometric scanners, facial recognition terminals — needs to be replaced. 

When switching to Hubble, existing turnstiles and biometric scanners can be retained where they are compatible with Hubble's system. 

Hardware compatibility is confirmed upfront, before you commit to the switch. For devices that are not compatible, Hubble will recommend suitable hardware.

The practical implication: get a compatibility assessment early. Hardware procurement and installation takes time, and finding out your turnstiles are incompatible a week before go-live creates a problem that cannot be resolved quickly.

1. Provide your current hardware model list
   1. Share the make and model of your existing turnstiles and biometric devices with the prospective BAS provider. Compatibility can be confirmed before you proceed.
2. Confirm compatibility in writing before committing
   1. Hardware compatibility should be confirmed before signing any agreement. Do not assume compatibility — verify it explicitly.
3. Budget time for hardware replacement if needed
   1. If any devices are not compatible, factor in procurement and installation time. This can add weeks to the onboarding timeline if not identified early.

Step 4 — Understand what happens to your existing data

When switching BAS providers, contractors often want to know what happens to their existing worker records, historical attendance data, and previously submitted ePSS data. Here is a clear breakdown of what we do at Hubble:

The practical implication: a provider switch is a clean start for attendance data, not a migration exercise. Your BCA compliance history is unaffected. Your active workers carry over. Everything else stays in your previous system for your own records.

How long does a switch take?

Switching to Hubble from another BAS provider follows the same onboarding process as a new setup. There are two parallel tracks that both need to complete before the first live SGBuildex submission:

• Hubble onboarding — hardware compatibility check, active worker import, trade mapping to BCA's streamlined 30-category list, data consent signing, and first test submission. Only 30 days for a new site.
• BCA and SGBuildex registration — a separate process that runs in parallel. Register at go.gov.sg/automated-cpd-registration and factor in BCA's processing time alongside your provider onboarding.

Starting both tracks at the same time gives you the best chance of meeting the deadline without a gap in CPD submission.

Already using Hubble for ePSS?

If you are currently using Hubble Workforce's ePSS Module, upgrading to the SGBuildex CPD Module is not a provider switch — it is a module upgrade. Your worker data, project setup and trade logic are already in the system. The process is a module activation and one-time trade re-mapping to BCA's streamlined list. ePSS continues running for your ongoing projects in parallel.

Summary — the four checks before you commit

1. Is your vendor on BCA's integrated BAS list? Check at go.gov.sg/integrated-bas-providers
2. Is their integration live or still in development? Ask for a confirmed UAT completion date if it is not yet live
3. Is your existing hardware compatible? Get this confirmed in writing before committing to a switch
4. Have you registered with BCA? Both provider onboarding and BCA registration need to run in parallel — register at go.gov.sg/automated-cpd-registration

Not sure if your hardware is compatible?

Share your current device list with us and we will confirm compatibility before you commit to anything.

Talk to Us

Related

• Automated CPD Submission from 1 May 2026 — Does It Apply to Your Project?
• Main Contractor vs Subcontractor — Who Is Responsible for CPD Submission?
• What Happens When CPD Data Is Wrong — Amending and Resubmitting via SGBuildex
• Hubble SGBuildex CPD Module — How It Works