April 10, 2026By Jolyn Ng

What Happens When CPD Data Is Wrong — Amending and Resubmitting via SGBuildex

Automation moves data faster, but it doesn't make it accurate. Here is how errors can occur in CPD submission, and what you can review and correct before and after.

Short Answer
Yes — you can review and correct Construction Productivity Data (CPD) before it is submitted to BCA via SGBuildex. Hubble sends data in batches within the month, during which users have full access to review and amend both attendance records and trade assignments.
If errors are found after submission, corrections can be resubmitted to maintain accurate records.

There are two moments where errors matter

The anxiety builders expressed at BCA's webinar last week was really about two separate concerns — and the answer is different for each.

Before submission

Can we catch and fix errors first?

Yes. The batch send period gives you a review window to check attendance records and trade assignments before data goes to BCA.

After submission

Can we correct what was already sent?

Yes. Corrections can be resubmitted where errors occurred in previously submitted data.

The review window before submission is the more important of the two — catching errors before they reach BCA is always preferable to resubmitting after. It is also the point where you have the most control.

What you can review and correct before submission

Hubble transmits CPD data in batches within the month. During this period, before the batch is sent to SGBuildex, users have access to review and amend:

Attendance records — full check-in and check-out data per worker per day, including identifying incomplete records where check-out is missing
Trade assignments — the trade tagged to each worker, which feeds directly into the CPD data BCA receives. This includes updating individual worker trades mid-project without re-uploading the entire worker list or waiting till every month-end.

This review step is where site administrators can align what the system recorded with what actually happened on site — before it becomes an official record.

Where most errors actually come from

Automated submission moves data faster and removes the manual upload step. But it does not fix errors that originate at the source — the site gate. In practice, most CPD data problems are operational, not technical.

Error type	Impact on CPD data
Worker forgets to check out	Open-ended attendance record — no checkout time recorded for that day
Unregistered worker on site	Worker's attendance not captured at all — invisible to CPD record
Trade not updated after deployment change	Stale trade data in ongoing submissions until corrected; Incorrect trade data submitted to BCA — affects trade productivity visibility and measurement
Subcontractor worker not using biometric system	Attendance gap — present on site but not recorded

The accountability reality

The main contractor submits CPD data but depends on subcontractors and workers behaving correctly at the gate.

An automated system captures what actually happens — missed check-outs, inconsistent biometric scanning, workers added to site without registration. The review window exists precisely because real site conditions are not perfectly clean.

Missed check-outs — how Hubble handles them

A worker who forgets to check out leaves an open-ended attendance record — no checkout time, no way to calculate time on site for that day. Left uncorrected, this flows into the CPD submission as incomplete data.

Hubble applies an automatic end-of-day checkout for workers who have not clocked out by the end of the working day. Since workers are not permitted to remain on site after hours, a hard cutoff is enforced — closing the attendance record and preventing open-ended entries from reaching the submission.

This handles the most common exception without requiring manual intervention from the site administrator for every individual case.

Duplicate registrations

A common concern raised was whether a worker could be registered or recorded twice — creating inflated attendance data.

In Hubble, every worker is tied to a unique identity. The system does not allow the same worker to have duplicate records within the same project, so double-counted attendance does not propagate into the CPD submission.

After submission — corrections and resubmission

Where errors occur in submitted CPD data, corrections can be resubmitted to BCA to maintain accurate system records. The preferred approach remains catching and resolving issues during the review window before each batch is sent — resubmission after the fact is available, but the review step is the primary control point.

What this means for your submission workflow

Automated CPD submission removes the manual upload task. It does not remove the need for data oversight. The review window before each batch send is not a formality — it is where the main contractor exercises control over what gets reported to BCA.

A practical submission workflow looks like this:

During the month — subcontractors register any new workers; trade changes are updated as deployment shifts
Before batch send — site administrator reviews attendance records and trade assignments, resolves any flagged issues
Batch send — data transmits to BCA via SGBuildex automatically
Confirmation — Activity Log confirms the submission

The first two steps are where data quality is established. The last two are where automation does its job.