A worker finishes a course on a Tuesday morning. In most compliance suites, that completion is a row in a learning system that someone, eventually, exports and reconciles against everything else. The LMS knows the person passed. The compliance score doesn’t. The skills matrix doesn’t. The plant they’re about to operate certainly doesn’t. The training happened; the consequences are a manual job for next week.
That gap — between learning and what learning is for — is where most platforms quietly give up. They treat the LMS as a swappable module, integrated through SCORM export and a reconciliation spreadsheet. We built the opposite. The LMS lives inside the compliance schema, not connected to it. Finishing a course doesn’t notify the rest of the platform. It is an event in the rest of the platform. Here is what that actually wires together today.
The score moves before anyone touches a spreadsheet
When a course is mapped to the compliance catalogue, completing it writes a completion record straight into employee_courses and triggers a council-level compliance recalculation. No nightly job, no export, no reconciliation. The worker passes, the row lands, the score moves. A compliance officer watching a department dashboard sees the number tick up in the same breath as the certificate is issued — because the certificate and the score are reading from the same table, not two systems trying to agree.
This is the unglamorous foundation everything else stands on. If completion didn’t reach the compliance engine natively, every claim below would be a promise about a future batch run.
It materialises into the skills-gap matrix
The same completion materialises into the employee’s skills record. That matters because the skills-gap view diffs required-versus-held competencies per position — what the role demands against what the person actually holds. A finished course closes a specific cell in that matrix the moment it’s recorded. A manager doesn’t re-key a qualification into a separate competency tool; the gap analysis already knows, because it draws on the same backbone as the training matrix we built from scratch. Held competencies are a consequence of completions, not a parallel record that drifts out of sync.
A role change auto-enrols the right people
Mandatory rules don’t have to be enforced council by council. A rule authored at the peak-body level cascades down to every council beneath it and auto-enrols the matching cohort by position. The instant a worker’s role changes to one the rule targets, the system enrols them — no one runs a report, spots the gap, and chases an email. The rule is the mechanism. Change the position, and the obligation finds the person. This is the same super-tenant spine that lets one course, authored once, be distributed to many councils with tenant-isolated cross-council reads — the master-distribution pattern described in multi-tier interoperability.
A licence from the LMS physically gates the plant
This is the edge that makes the whole architecture worth defending. A high-risk-work competency, verified through the LMS, mints a licence that the PPE pre-start gate enforces directly. When an operator steps up to certify a pre-start on regulated plant, the gate checks that licence against OHS Regs reg 129. An uncertified operator is blocked — not warned, not flagged for later review, blocked. The thing they learned on Tuesday is the thing that opens the gate on Wednesday, and the absence of it is the thing that keeps the gate shut.
Most suites can’t draw that line, because the licence lives in one product and the gate lives in another, and the join is a manual export. When learning and the pre-start gate share a schema, the enforcement is structural. The full mechanism is in PPE and asset management pre-start gates.
Controlled documents read both ways
The connection runs in both directions with Document Control, too. A controlled document — a procedure, a safe work method, a policy — embeds into a course as a linked resource, so learners read the document of record rather than a stale copy pasted into slides. And Document Control reads that linkage back: it knows which courses reference a given controlled document. Revise the document, and you can see exactly which learning depends on it. The course and the document aren’t two copies kept in step by discipline; they’re one link, queryable from either side.
What this means on the ground
Five connections, wired today: the score moves, the skills matrix closes, the cohort auto-enrols, the licence gates the plant, the documents bind both ways. None of it is “the LMS notifies an integration.” All of it is one system doing one thing in five places at once, because the learning data and the compliance data are the same data.
We’re deliberately not claiming the things we haven’t built — incidents don’t auto-enrol training, SWMS sign-on doesn’t yet gate on LMS completion, benchmarking cohorts don’t carry LMS columns. The honest, defensible spine is narrower and sturdier than the marketing version: the LMS isn’t connected to the compliance platform. It’s part of it.
For the architecture underneath, read the LMS that lives in your compliance schema and the full multi-tier interoperability story. To see why this only works when learning sits in the foundation rather than bolted on top, see why learning belongs in the base.