The compliance module
Eight subsystems. Each one is a domain service with versioned rulesets and an effective date — not a report you run at the end of the year.
01
Files 21, 25, 28 and 30 generated as fixed-length ASCII against the SAQA load specification, with an Edu.Dex validation loop in the pipeline. Validation failure blocks file release — it does not surface six months later as an audit finding. Submission calendars are automated and every submission is archived immutably.
02
One interface, an implementation per SETA, sequenced across all 21 — Services SETA, INSETA and TETA at launch. Where a SETA offers only a portal, the adapter is a human-in-the-loop preparation engine: perfect upload files, a guided checklist and evidence-of-submission capture. We automate the work; we never forge the click.
03
The 21-working-day QCTO notification clock and the three-month EISA registration clock are guards on the enrolment state machine, with escalating alerts — not calendar reminders. Statutory timestamps are immutable once written. Legacy unit-standard teach-out windows are enforced by the same mechanism.
04
Every tenant carries an accreditation registry — authority, number, scope, expiry, status. A tenant cannot enrol a learner on a qualification outside its scope. The platform does not warn about the illegal action; it makes it unavailable.
05
Readiness is computed, not asserted: portfolio completeness × mastery state × logbook hours against required × practical-simulation readiness where criteria are mapped. You find out which learners are not ready while there is still time to do something about it.
06
Per corporate client, per measurement year: Learning Programme Matrix mapping, black-participant headcounts, bursaries, disability spend with the accommodation evidence behind it, and absorption outcomes as a standing KPI — exportable in a form a verification agency can consume.
07
A purpose-scoped consent registry with section 26 special-information gates over race, disability, health-adjacent and biometric-adjacent data; data-subject-rights workflows; retention schedules per record class; an Information Officer console; a cross-border transfer register; and complete processing logs.
08
File specifications, field dictionaries, clock definitions, scorecard weights and regime templates are versioned configuration with effective dates. When a SETA changes a form, that ships as a configuration release — not a code emergency in the middle of your submission cycle.
Also specified: a defined academic-record interchange to accrediting partner institutions for higher-education cohorts. HEMIS-class statutory reporting stays with the accrediting institution — we host, deliver and assess where delegated, and export. We never impersonate an accreditor.
The artefact
The audit-pack generator is the single most important thing this platform produces. It is the demo that closes the sale, because every principal in the room has assembled one of these by hand.
