Most safety suites treat the LMS as a swappable module. You buy the compliance platform, and learning is a separately-integrated box you bolt on later — connected, if at all, through SCORM export and a manual reconciliation step where someone copies completion dates from one system into another. The login is shared. The meaning isn’t.
We spent this series describing a learning platform that doesn’t work that way, because it can’t. The LMS lives inside the compliance schema — the same database, the same row-level security, the same tenant boundary. That single fact changes what learning is allowed to do, and it ends up changing how the product is priced.
The capstone edge: one author, many councils
The deepest version of this is super-tenant master distribution. A peak body — a state association, a shared-services group, a parent organisation — authors a course once. That course is then distributed to many member councils, each of which sees it inside their own tenant, scored against their own positions, completed by their own people.
What makes this hard isn’t the copying. It’s the boundaries. Cross-council reads stay tenant-isolated: a member council never sees another council’s completions, even though they share the master course. The peak body controls the copyright-licence mode — whether members can adapt the content, must use it verbatim, or hold a time-bound licence to it. One course, authored once, governed centrally, consumed locally, with the tenant wall intact the whole way down. You cannot retrofit that onto an LMS that joins councils together at runtime. It has to be in the schema.
Skills, not just certificates
The other half of the capstone is competency intelligence. A completion in our LMS doesn’t just stamp a date — it materialises into an employee skills record. A skills-gap view then diffs required-versus-held competencies for each position: this electrician needs five tickets, holds four, is short one. That’s not a report you assemble at audit time from a pile of PDFs. It’s a live read of where the workforce actually stands against what each role demands.
Because the gap is computed from the same matrix that drives the compliance score, the two never disagree. The skills view and the audit pack are looking at one source of truth.
Six edges, not six integrations
This series walked through six places where finishing a course changes something downstream — and every one is wired into the schema, not connected over a wire:
- Completion to live recalc. An LMS course mapped to the compliance catalogue writes a completion into the employee record and triggers a council compliance recalculation. The score moves on its own.
- Completion to skills. That completion materialises into a competency record the gap view reads.
- Mandatory-rule cascade. A rule authored at the peak-body level flows down to councils and auto-enrols the matching cohort by position.
- Document Control, both ways. A controlled document embeds into a course as a linked resource, and Document Control reads that linkage back.
- PPE pre-start enforcement. A high-risk-work licence minted from an LMS-verified competency is enforced by the PPE pre-start gate under OHS Regs reg 129 — an uncertified operator is blocked from the task, not just flagged.
- Master distribution. The capstone above.
No two of those are an export and a reconciliation. They’re foreign keys.
Why this makes learning a base tier
Here’s the pricing thesis, stated plainly. An add-on is something you can skip without breaking the thing you bought. You can run our compliance platform without benchmarking, without working groups, without the provider directory — those are genuinely separable, and they’re genuinely add-ons.
You cannot run compliance without learning, because learning is how compliance changes. If completion drives the score, gates the high-risk task, and cascades down from a peak body, then carving the LMS out as a $25 menu item would mean selling a compliance engine with its primary input amputated. The integration isn’t a feature of the LMS. The LMS is half the compliance system.
So the shape changed. There’s a lean Compliance base for councils who want the matrix, the scoring, and the audit pack. And there’s a Compliance + Learning base where the two are one system — completion to recalc to skills to pre-start, all of it live. Learning isn’t a line on the add-on menu above it. It’s the other half of the floor you’re standing on.
We’re not pricing this against anyone else’s catalogue. The case is integration and the value it creates, not a comparison. When the LMS lives in the compliance schema instead of beside it, “what does the LMS cost” stops being the right question — the right question is what it’s worth to have a workforce whose competence is computed, not collated.
For the architectural spine, see the LMS that lives in your compliance schema and when finishing a course changes what’s allowed on site. For why we price platforms as more-or-less of one system rather than a federation of products, see one platform, sold in pieces. To see the shape for yourself, head to /pricing.