Not every course lodges with NCVER: that's where findings hide

Not every course an RTO delivers reports to NCVER. A High Risk Work Licence assessment lodges with a workplace health and safety regulator. RSA and RCG lodge with Liquor & Gaming NSW. A Food Safety Supervisor certificate lodges with the NSW Food Authority. Each has its own rules about who can assess and how the result is lodged, and none of them looks like an AVETMISS submission.

Most student management software is built around one assumption: a course reports to NCVER, via AVETMISS. That assumption runs so deep it's usually invisible, until you deliver a course that doesn't fit it. Then the non-NCVER path becomes an exception you handle by hand: a spreadsheet of assessors, a folder of accreditation certificates, a notice retyped into whatever layout the regulator wants this year. And exceptions handled by hand are exactly where findings hide.

There are three things the non-NCVER courses get wrong most often, and they're the three a system should be able to catch for you.

Assessor accreditation, not just trainer currency

A High Risk Work Licence assessment can't be signed off by just any currency-compliant trainer. It has to be an assessor the regulator has accredited for that specific licence class, and the accreditation itself expires. Vocational competency isn't enough. An assessor accredited for one class isn't automatically accredited for another.

This is the check that's easiest to miss and most expensive to miss, because when an unaccredited or lapsed assessor signs off a result, nothing visibly breaks. The student gets their outcome. The cohort moves on. Nobody notices until the regulator does, and by then every result that assessor signed in the meantime is in question. It's a retrospective finding, the worst kind.

RTObase keeps a register of which licence classes each assessor is accredited for, with the expiry date attached. A satisfactory result from an assessor who isn't currently accredited for that class is blocked at the source, so an invalid assessment never makes it into a lodgement file in the first place. The answer to "can this trainer sign off this assessment" is a rule the system reads, not a date you check by hand in a folder.

The right lodgement format

Each authority wants the notice of satisfactory assessment in its own format. The eight state and territory WHS regulators, SafeWork NSW, WorkSafe Victoria, WorkSafe Queensland, and the rest, don't share a template. A generic export doesn't lodge; it bounces, or worse, it sits accepted-looking until someone reconciles it.

RTObase builds the export, the Assessment Summary or notice, in the exact format each issuing authority requires, ready for you to submit. To be straight about what that means: issuing authorities don't expose an API that lets anyone lodge on your behalf. So RTObase does the part that actually eats your time, recording the accredited assessment and building the file in the precise layout the authority expects, and leaves the final submit, through their portal, to you. We do the paperwork; you hit submit. The supported set today is a defined one: High Risk Work Licences across all eight state and territory WHS regulators, RSA and RCG via Liquor & Gaming NSW, and Food Safety Supervisor via the NSW Food Authority.

The link between the assessor and the pass, and what comes after

The third gap is the one that ties the first two together: there's usually no live link between the assessor's accreditation and the result they signed. The accreditation is in one place, the pass is in another, and nobody joins them until an auditor does.

There's also a tail most systems forget entirely. Many of these licences expire, RSA, for example, runs five years in some states. A student who let their card lapse is a student you can bring back, but only if you know the expiry date and act before it passes. RTObase tracks the licence expiry, surfaces who's due for renewal, and automates the re-engagement outreach. And when it's time to hand the student their notice, you can download it on your own RTO letterhead, branded to your organisation, ready to attach to a lodgement or pass across the counter.

Why this follows from one record

A bolt-on tool for licence courses would keep its own assessor list, its own student list, and its own assessment records, and you'd be back to reconciling three lists every time a regulator asked a question. The accreditation check would be a manual cross-reference. The expired-assessor result would slip through, because the system signing off the pass wouldn't be the system holding the accreditation date.

Because the course, the assessor, the assessment and the candidate all live on the same record in RTObase, the accreditation check is just a rule reading two fields of one record: is this assessor accredited for this class, today? The lodgement export is built from the same record the assessment was recorded against, so there's no re-keying and nothing to spell slightly differently. The renewal horizon is the same expiry date the system already knows. None of this is a separate tool bolted to the side, it's the single student record doing one more thing it was already shaped to do.

That's the whole bet we keep coming back to. An RTO's job is a loop, enrol, train, complete, lodge, renew, re-engage, and a loop is best run by one product that never loses the student at a handoff. The non-NCVER courses aren't an exception to that. They're the clearest case for it.

If that's the kind of system you'd like running your licence courses, come and have a look.