CPD Trade Data for SGBuildex — Mapping, Multi-Skilled Workers, and Mid-Project Changes

BCA has streamlined the trade list from 150+ ePSS categories to 30. Here is how the one-time mapping works at setup, how multi-skilled workers are handled, and how to keep trade data accurate as deployment shifts mid-project.

Short Answer

At setup, you do a one-time mapping from your existing ePSS trade codes to BCA's new 30-category list. After that, all worker trades are assigned directly from the new list — the old ePSS codes are no longer in use.

Worker trades can be updated at any point mid-project as deployment changes. The update applies from the next submission cycle forward — it is not retroactive.

What changed with BCA's trade list under SGBuildex

Under ePSS, contractors worked with four separate Excel templates — one each for Building, Offsite, Rail, and Road works — each containing their own set of trades. Across all four, the total number of trade classifications ran to 150 or more across 7 categories. 

Registering workers correctly, especially those performing multiple functions or moving between project types, was a significant administrative burden.

Under SGBuildex, BCA has consolidated this into a single streamlined trade list of 30 categories. One list covers all project types. 

Worker registration is simpler, and the same list applies whether the project is a building, an MRT station, or a road.

The one-time trade mapping at setup

When onboarding a project for automated CPD submission via SGBuildex, contractors do a one-time exercise: mapping their existing ePSS trade classifications to the new BCA 30-category list.

This is a setup step, not an ongoing task. Once the mapping is done, all worker trade assignments in Hubble use the new list directly. There is no need to maintain a parallel set of ePSS trade codes — the mapping is done once and the system moves forward on the new list.

How Hubble handles this

Hubble maintains both your internal trade codes and the BCA SGBuildex trade codes as separate fields. This means your internal job descriptions and the BCA-required trade categories coexist in the system without conflict — your internal operations are not disrupted by the BCA classification requirement.

At setup, Hubble walks through the mapping exercise with you. The result is a configured system where worker registrations automatically carry the correct BCA trade code for submission, without requiring site administrators to manually change between internal and BCA terminology every month.

How trade data works across a project's life

Trade management is not a one-time setup task — it continues throughout the project as workers join, leave, and change roles. Here is how the three main moments work:

At setup

Initial trade mapping

Map existing trade codes to BCA's 30-category list once. Import active worker list with trade assignments. Done — this does not repeat.

Ongoing

New workers and subcontractors

Register new workers directly against the 30-category list. No ePSS code translation needed. Trade assignment is part of the registration step.

Mid-project

Deployment shifts

Update individual worker trades as roles change. No full re-upload needed — change only the specific worker or in bulk. Applies from the next submission cycle forward.

Multi-skilled workers

Construction projects involve workers who perform different roles at different stages. A worker registered as a formwork carpenter in the structural phase may move to finishing work in a later phase. With Hubble, this is handled through trade reassignment.

When a worker's deployment shifts, their trade assignment in Hubble is updated to their respective BCA category. From the next submission cycle, they are recorded under the updated trade. Previous submissions remain as they were — the change is not applied retroactively.

Trade changes are not retroactive

When you update a worker's trade in Hubble, the change takes effect from the next submission cycle — it does not alter previously submitted CPD records. This is important to understand when managing workers across project phases: the CPD record reflects the trade assigned at the time of each submission, not a historical revision.

If a worker's trade was incorrect in a previous submission, that falls under the correction and resubmission process rather than a trade update. See What happens when CPD data is wrong for how resubmission works.

The practical implication for site administrators

The trade list change is largely a one-time overhead at onboarding. Once set up, the ongoing task is smaller than what ePSS required — there is no monthly template or manual manday computation to prepare and no trade code translation to manage.

The discipline that matters on an ongoing basis is keeping trade assignments current as deployment changes. 

A worker whose trade has not been updated for three months despite moving to a different role creates a CPD record that does not reflect what actually happened on site. 

The review window before each batch send is the right moment to catch these discrepancies before they reach BCA.

Summary of what is and is not needed for trade management under SGBuildex:

One-time at setup: Map existing trade codes to BCA's 30-category list. Import active worker list.

Ongoing: Register new workers directly on the new list. Update individual trade assignments when deployment changes. Review before each submission cycle.

Not required: Monthly template preparation. ePSS code translation. Full worker list re-upload for individual changes.

Want to see how dynamic trade editing works in practice?

We'll walk you through the setup exercise and show you how trade assignments are managed across a live project.

Book a 30-Min Walkthrough

Related

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