Singapore's training landscape changed in July 2026. SkillsFuture Singapore (SSG) and Workforce Singapore (WSG) merged into the Skills and Workforce Development Agency (SWDA), consolidating workforce development under a single statutory board. For training providers, the compliance requirements remain — TPGateway is still the system of record — but the transition introduces new questions about readiness, terminology, and what your TMS needs to support going forward.
This guide explains what the merger means for training providers, clarifies what "SkillsFuture TMS integration" actually requires, and walks through how a properly integrated platform handles the full data flow between your organisation and SWDA.
The SSG-to-SWDA Transition — What Changed for Training Providers
The July 2026 Merger: SSG + WSG = SWDA
The Skills and Workforce Development Agency (SWDA) now oversees both skills development (previously SSG) and workforce programmes (previously WSG). For training providers, this means dealing with one agency instead of two — but the underlying compliance infrastructure remains largely intact.
The TPGateway API — the technical backbone for submitting course data to the government — continues to operate. Training providers who were compliant under SSG remain compliant under SWDA, provided their systems stay current with any API updates associated with the transition.
What Stays the Same
TPGateway remains a key portal for relevant provider workflows. Check which course, enrolment, attendance and assessment data sets apply to your programmes.
TPQA and other quality obligations may apply to your provider type. Keep relevant submissions accurate and auditable.
Funding schemes have distinct rules and may change. Check current eligibility, calculation and submission guidance for each scheme.
The published TMS integration requirement applies to relevant funded training providers, subject to its stated exemptions.
What Training Providers Need to Update
Terminology and branding. References to "SSG" in your course materials, websites, trainee communications, and internal documentation should be updated to "SWDA" where applicable. This is not just a branding exercise — trainees and corporate clients searching for information will increasingly use "SWDA" rather than "SSG."
System configuration. Confirm with your LMS/TMS vendor that their TPGateway integration reflects any endpoint, authentication, or schema changes associated with the merger. A vendor that has not updated their integration may encounter submission errors or rejected API calls.
Staff training. Operations staff familiar with SSG processes should be briefed on any procedural changes in how SWDA handles submissions, grant approvals, or audit requests. The processes are largely the same, but portal interfaces and communication channels may differ.
What "SkillsFuture TMS Integration" Actually Means
It Is Not Just SkillsFuture Credit Tracking
When HR directors and training operations managers search for "SkillsFuture TMS," they often have a narrow picture in mind — a system that tracks whether trainees have used their SkillsFuture Credits. In practice, a true SkillsFuture-integrated TMS covers far more than credit tracking.
A connected LMS and TMS can support data exchange through applicable TPGateway APIs across relevant funded training workflows: from course creation and enrolment through attendance capture, assessment submission, grant calculation, and digital certification. SkillsFuture Credit tracking is one small part of a much larger compliance workflow.
The 4 Data Flows Your TMS Must Handle
A properly integrated TMS manages four distinct data flows with TPGateway:
| Data Flow | What It Covers | What Happens If It Fails |
|---|---|---|
| Course Runs | Schedules, sessions, modules, fees, trainer assignments | May disrupt publication or enrolment, depending on the workflow |
| Enrolments | Trainee NRIC/FIN verification, sponsorship status, grant eligibility | May cause eligibility or submission errors |
| Attendance | Digital check-in (QR/Singpass), session-level attendance records | May require reconciliation |
| Assessments | Competency outcomes, pass/fail results | May delay downstream records or funding disbursement |
Verify which flows use APIs, how errors are handled and what audit records are available under current requirements.
Common Misconceptions
“SSG-approved TMS” — Avoid treating a TMS as universally government certified. Ask which TPGateway interfaces are supported, how the integration was tested and whether it covers the data flows you need.
"We just need SkillsFuture Credit tracking" — Credit tracking is a small subset of what funded training providers need. Credit tracking alone does not cover the administrative workflows that may apply to funded training.
"Any LMS with SCORM support is sufficient" — SCORM compatibility handles e-learning content delivery. It has nothing to do with government compliance or TPGateway integration. A SCORM-compliant LMS without TPGateway integration still requires manual data entry into the government portal.
How Wizlearn's TMS Integrates with SkillsFuture / SWDA
Wizlearn combines LMS and TMS functions in one platform. Depending on configuration, this can connect learning activity and training administration without a separate LMS-to-TMS transfer. Confirm the supported TPGateway flows for your programme.
Course Run and Scheduling Sync
Wizlearn supports training administration and TPGateway integration. Ask the team to demonstrate which course-run fields and updates are supported by the integration configured for your organisation.
This matters because TPGateway requires course run data to be accurate before enrolments can be processed. A delayed or incorrect course run submission delays the entire downstream workflow.
Automated Enrolment and Grant Calculation
Enrolment and funding workflows depend on the course and configuration. Ask Wizlearn to demonstrate identity, sponsorship and grant-related data handling for your programme and current scheme rules.
Automated grant calculation eliminates the manual arithmetic that causes the most common submission errors. When a training provider miscalculates a subsidy, the result is either a rejected claim (delaying cash flow) or an overpayment that triggers a clawback during audit.
Digital Attendance with QR and Singpass Integration
Paper sign-in sheets can add transcription and reconciliation work. Wizlearn can support digital attendance workflows. Confirm the check-in method, identity verification and TPGateway synchronisation available for your deployment.
Digital attendance can reduce transcription and help maintain a traceable record. Confirm the evidence needed for your programme and any relevant quality review.
Assessment Submission and OpenCerts Certification
Assessment outcomes can be managed in the learning platform and exchanged through supported TPGateway workflows. The applicable government record and certificate processes depend on the programme.
Audit Trail and Compliance Reporting
Ask Wizlearn which integration transaction logs, errors and timestamps are available for your configuration. Ask what submission history can be exported or reviewed when preparing audit evidence.
Why a Combined LMS + TMS Matters for SkillsFuture Compliance
One Platform for Learning Delivery and Administrative Compliance
Many training providers in Singapore run two separate systems: an LMS for delivering e-learning content and a TMS for handling administrative compliance. This creates a structural problem — the data generated by learners (course completions, quiz results, attendance) lives in one system, while the data required by SWDA (enrolments, grants, submissions) lives in another.
Bridging the two requires manual data transfer: exporting from the LMS, reformatting, and importing into the TMS. Every manual step introduces error, delay, and audit risk.
A combined LMS and TMS can reduce this gap. Where configured, completion records can be made available to the relevant TMS submission workflow without a separate manual export.
Eliminating Double-Entry Between Separate Systems
Double-entry can increase reconciliation work and introduce discrepancies. Common scenarios include:
Attendance mismatch: A trainee's LMS records show they completed an online module, but the TMS attendance submission to TPGateway shows them absent because the data was not transferred.
Assessment discrepancy: A trainee passed their assessment in the LMS, but the TMS submitted a different score because the export was based on an outdated file.
Enrolment timing error: A trainee was enrolled in the LMS before their TMS account was created, leading to data mismatches in the submission.
A shared data model can reduce these reconciliation problems. The data is entered once, at the source, and flows through to SWDA without manual intervention.
Frequently Asked Questions
Is Wizlearn "SWDA approved"?
Wizlearn TMS is included in SWDA’s TPGateway conformance list. Ask for current evidence and a demonstration of the TPGateway integration relevant to your programme.
Does Wizlearn support the new SWDA requirements?
Ask Wizlearn for the current integration scope and a demonstration against your programmes. Also consult the latest SWDA and TPGateway requirements.
Can I use Wizlearn if I am not yet an RTP?
Wizlearn serves training providers and corporate organisations. Check the current organisation-registration criteria directly with SWDA; a TMS does not itself confer provider status.
What SCORM versions are supported?
Confirm the supported SCORM versions, HTML5 content formats and tracking behaviour for your content during a demonstration.
What if I already have a separate LMS and TMS?
A combined platform may reduce duplicate entry. Discuss migration scope, historic data and integration needs with Wizlearn before planning a replacement.
Discuss your training workflow
Ask for a demonstration of the relevant training workflow, from course creation to supported TPGateway submissions, configured for your operations.
Whether you are an ATO/RTP managing WSQ-funded programmes and scaling your course offerings, or a corporate training department ensuring compliance with SWDA requirements, a personalised demo will show you exactly how the platform fits your workflows.
Official references
- Ministry of Manpower — establishment of SWDA
- TPGateway — TMS integration and exemptions
- TPGateway — frequently asked questions
Scheme rules, system interfaces and product configuration can change. Confirm current requirements with the relevant agency and verify the exact integration scope for your programme.
Explore Wizlearn’s LMS and TMS or contact the team about your requirements.