From training.gov.au
to the names of the learners it affects

Seven stops. The first six are everything Australia's national training register can answer on its own, so they run automatically and they're free — permanently. The seventh is the one the register can't answer, and it's the only one anyone pays for: The Transition File. Here's exactly what happens at each, and where your data does and doesn't go.

The seven stops, end to end

The register changes. Constantly.CONTEXT

Training packages get updated all year. When a qualification is replaced, the old one is marked superseded on training.gov.au, Australia's national training register — but it stays on your scope, and the register also records whether the replacement is equivalent or not. It is all published — but published is not the same as watched: it is a register, not a watch on your particular scope.

The register says all of that out loud — which is why stops two to six cost nothing. It even publishes the one date the legal clock hangs on: the day a replacement was first released. What it never says is anything about the people you enrolled. That is stop seven, and it is the only one that costs.

Data involved: 100% public government register

The scope checkFREE

Type your RTO code on the homepage. We pull your live scope — not the historical entries the register publishes alongside it, which quietly inflate a naive count — cross it with national supersession status, and show you the result in seconds. No account, no email, no card.

What we record per check: the RTO code, how the check arrived (typed, a followed link, or the homepage example), and a pseudonymous hash of the IP — a one-way HMAC we cannot turn back into an address, cleared nightly once it is 90 days old. No email, no name, no account — and nothing about your scope is kept against you. The full list of what we hold is on our privacy page.

The transition clockFREE

A superseded product isn't just a flag — it starts a legal clock. Item 14 of the 2025 compliance standards (F2025L00355, in force 1 July 2025) sets it for ASQA-registered providers: one year after the replacement enters the register, the old product closes to new enrolments. That's computable from a date the register already publishes — the day the replacement was first released — so we read it off for every superseded product on your scope.

Two clocks, never one. New enrolments: a hard start date — s 14(1)(a)(i), as ASQA's published guidance reads it — and where ASQA has granted an extension, the date we show you is already the extended one. Students already enrolled: no fixed deadline; they finish, certify or transfer in a timely manner (ASQA 2025 Standards FAQs v3). We read the register and the legislation; we do not assess your compliance.

Data involved: 100% public register + the legislation

The enrolment crossFREE

Load an export from your SMS at /cross and see which named learners are sitting in superseded products. The file is parsed inside your browser — the only thing our server receives from it is training product codes, which are public data.

Learner names never leave your machine. By architecture, not by promise.

The watchFREE

Leave your RTO code and an email, and we watch your scope against the register. When something of yours is superseded — or a replacement's equivalence changes, or a new-enrolment clock starts — you get an email saying what changed and what it now points at. Not the next time somebody happens to look.

We hold your RTO code (public), your email, the name you typed if you typed one, the day you signed up and which page you came from — nothing else, and never anything about your learners. The full list is on our privacy page. Every alert carries a one-click button that deletes it all; you can also just reply and we will do it by hand.

The unit-by-unit mapFREE

Knowing that the replacement is flagged not equivalent tells you something changed. It does not tell you what. So we go one level down and read the units inside both qualifications, then sort them into the only four groups that lead to different work: units that stay put, units that are the same content under a new code, units whose content genuinely changed, and units that enter or leave.

The flag also decides how much of the paperwork lands on you. On its transitions page the regulator says that for an equivalent replacement we will automatically update your scope and will confirm these changes via email, and that for a not equivalent one you need to apply to have the training product added to your scope of registration. ASQA, How to transition — read 17 August 2026.

That distinction is the whole point. Line up the old and new unit lists and subtract, and a real Diploma of Nursing supersession reads "29 units gone, 26 new" — frightening, and wrong. Follow each of those units through its own supersession chain and 27 of the 29 turn out to be the same unit renumbered. But renumbered is not the same as unchanged: the register calls 14 of them equivalent — a code change on paper — and flags the other 13 not equivalent, which means the evidence has to be mapped again. Two units actually go. The subtraction was wrong by a mile, and the work that is left is real: it just cannot be seen without following every unit, one at a time.

Free, like everything else the register publishes. What is paid, and why.

Your learners, and the decision

Every stop above is about the qualification. This one is about your provider, and it is where the register runs out for good: it publishes what the current qualification requires, and it has no idea how far any of your people got. That sits in your student management system and nowhere else.

Then comes the part that stays manual. Where the register renumbers a unit into a new code and calls it equivalent, your student management system will not award that credit transfer by itself: someone opens each learner and records it, one unit at a time. Federation University publishes its transition procedure — fifteen steps, six or more roles — which is the only public measure of that work we have found. The Transition File works out every one of those rows and hands them to you in the order you key them — each row with the AVETMISS outcome code to key, the rows that need no keystroke marked, the register's own wording quoted where evidence must be re-mapped, and the work placement hours still to budget where the register publishes them; the keying, and the judgement, stay yours.

What changed in each unit isn't our prose either — for each pair it grades, the register publishes an official mapping note, and the file quotes it verbatim. A real one, read from the register on 30 August 2026 — entire, with only its opening training-package version line elided, marked […]:

the register's mapping note · HLTENN003 replacing HLTEN503B“[…] Significant changes to the elements and performance criteria. New evidence requirements for assessment, including volume and frequency requirements. Minimal change to knowledge evidence.”

Where the register publishes no note for a pair, the file says so — a declared blank, never our own words dressed as the register's.

So you drop in the export you already have — an Excel file (.xlsx), a CSV, the AVETMISS NAT00120 your student system generates, or the whole AVETMISS ZIP, as-is. The column headers each system writes, and which of them we have checked, are listed below. If it is Excel, your browser reads the first sheet into a CSV on the spot — no converting by hand. If it is that NAT00120, there is nothing to strip: the national standard puts every name, date of birth, address and USI in a different file — NAT00080 and NAT00085 — and that file is not one we accept. Drop the ZIP and your browser opens only the NAT00120 inside it; the client files are never even decompressed. If it is a CSV instead, names do travel in it, and your browser strips it before anything leaves the machine: it keeps a reference, the units and the results, shows you exactly what is about to be sent, and hands you the name-to-reference map as a local file we never see. You don't have to prepare anything, and you don't have to lose track of who is who. We don't ask you to trust that we won't look at names either: the engine refuses to receive them, and a file carrying a name, an email, a date of birth or a USI is rejected outright — with the seven checks shown in order and the one it failed named, never the value. The file itself is processed in memory and never stored.

What comes back, learner by learner, is what still stands between each of them and the current qualification — a dated record of where each one stands. It is your own working, dated and fingerprinted, for whenever you need to show how the transition was handled: we are not ASQA, and nothing here approves anything. And the verdicts don't arrive as an attachment: the run opens in your account as a five-tab dashboard — overview, register changes, learners, worksheet, evidence — where each learner carries a status, Needs action to Done, moved by the dated actions you record in a log where undoing is a new entry, not an erasure. The worksheet downloads as a CSV in the same keying order, the AVETMISS outcome codes in their own column — SMS-ready. When the paper matters, the whole run prints as one dated document with the decision log inside and the full SHA-256 fingerprint of the file it measured — for a CSV or Excel drop that is the de-identified file your browser built and offered you for download before sending, not your original export; re-hash that file any day and it must match. The Transition File starts at $290 AUD a month, sized by your live scope.

Buy it outright, or talk it through first — whichever you prefer. See the three sizes and what's included · Ask before you commit.

What the file accepts

What the file accepts — the column headers, as your system writes them

Three layouts. The headers below are the ones the file reader matches, spelled the way each vendor's documentation spells them. Matching ignores case and treats spaces, underscores, hyphens and dots alike, so Unit_Code, unitCode and UNIT CODE all land as the unit code. An Excel export is read from its first sheet. Whatever else the export carries, the reduced file your browser builds travels with the reference, the unit, the result, the date and the qualification code — nothing more.

aXcelerate Report Builder export — CSV (or .xlsx)

Verified against their documentation on 29 August 2026

Learner reference
Contact ID Optional ID
Unit code
Unit Code
Result
Competency Status Outcome
Completion date
Activity End Date Actual Completion Date
Qualification optional
Qualification Code

Result values written as C (20), CNA (30) or CE (70) are read by the AVETMISS code in brackets. Enrolment Status is the course enrolment, not the unit outcome, and is not read as a result. Name, USI and trainer columns are not in the reduced file your browser sends.

Wisenet LRM Unit Enrolments export — CSV

Verified against their documentation on 29 August 2026

Learner reference
Ref Export
Unit code
Unit Code
Result
Outcome (AV) Outcome Code Outcome Code (AV)
Completion date
Unit End Date End Date
Course optional
Course Code

Outcome values are the AVETMISS numeric codes — 20, 30, 60 — and are read as such. Wisenet's Result column is the grade scale you configured (HD, D, C…), not the AVETMISS outcome. Export Outcome (AV) rather than Result, or send us your headers and we confirm the mapping before you upload.

NAT00120, or the AVETMISS ZIP the file your system already builds for NCVER

Verified against NCVER's AVETMISS 8.0 specification on 29 August 2026

No headers to match: the file is fixed-width and read by position, as the specification lays it out.

Learner reference
Client identifier pos 21–30
Unit code
Subject identifier pos 31–42
Result
Outcome identifier – national pos 72–73
Completion date
Activity end date pos 61–68, DDMMYYYY
Qualification
Program identifier pos 43–52

Outcome codes the reader understands: 20, 30, 40, 41, 51, 52, 60, 61, 70, 81, 82, 85, 90; a row carrying a code outside that list is left out, and the warning the upload returns gives you the count, names the first twelve learners affected, by their reference, and counts the rest — and if more than one row in fifty carries one, the file is refused rather than read with rows missing. Drop the whole ZIP and your browser opens the NAT00120 inside it and nothing else — NAT00080 and NAT00085, the client files that carry names, are never decompressed. A release 7.0 file is stopped with a message rather than misread. Everything else in the record, the delivery location included, stays behind.

The vendor's documentation names the field but not this exact header spelling. No header on this page has been checked against a customer export yet — we have not had one from either system in hand — so send us your headers and we confirm the mapping before you upload. VETtrak (ReadyTech) users: the NAT00120 route above is verified against NCVER's specification, not against a file VETtrak generated; its Data Insights headers are not listed because we have not checked them against an export. And if the unit code or the result column is not recognised, the upload lists the unmatched columns and asks you which one it is — before anything is sent.

Where your data goes

Where your data goes — and where it can't

The whole architecture, one picture. The wall is the point.

Your browser

  • Enrolment filelearner names, results — parsed here, never sent
  • The free crossruns on this machine from start to finish

learner namesstop here. Nothing that names a person is ever sent, and the paid engine rejects a file that carries one.

codes · opaque refs

names never cross this line

Our server

  • Code lookups + cachepublic product codes only
  • Watch listRTO code, email, three sign-up fields — never learners
  • Nightly watch cronre-reads every watched scope
public lookups

training.gov.authe national register

  • Public registerscopes · supersessions · equivalence · unit grids · mapping notes · replacement release dates

never receives: your learners

The questions people actually ask

The questions people actually ask

How do I transition students to a new qualification?
Stop new enrolments in the superseded product by its computed item 14 cut-off — one year after the replacement entered the register (F2025L00355). Learners already enrolled have no fixed deadline: they complete or transfer in a timely manner. Then measure each enrolled learner unit by unit against the replacement to see who needs gap training.
Why is so much of this free?
Because training.gov.au does that part for us. Reading it is a query and a cache — fractions of a cent per check — so charging for it would only mean fewer providers find out where they stand. That now includes the item 14 clock: the date it hangs on is one the register already publishes, so we read it off and give it away too. The line we draw is simple: anything the register and the legislation let us compute, we automate and give away. What the register never publishes is anything about your own learners, and that is the one thing we charge for.
Isn't The Transition File just the free report again, with a cover page?
Fair question, and no — they don't come from the same place. Everything the register publishes is on the free side, and that now includes the unit-by-unit map — in your panel, under each product, and summarised in the daily email. This page used to say the opposite, that the register never revealed what a qualification is made of; we were wrong, so we automated the map and moved it to the free side. What The Transition File covers is the one thing no public source holds: how far each of your own learners actually got, and what you decide to do about it. That lives in your student system and in your judgement, not in the register. And the paid side is no longer just a document: the run stays in your account as a working list with a status per learner and a dated decision log, and prints as dated evidence whenever you need it.
Can you see my students' data?
No. The free enrolment cross runs inside your browser; the only thing our server receives from it is a list of training product codes — public data. The paid engine does receive a file, so there we don't rely on trust: any file carrying a name, an email, a date of birth or anything else that identifies a learner is rejected outright, with a message naming the column. What it accepts is a reference that only means something inside your own system, and the file is processed in memory, never stored. We do not ask you to email us enrolment files, and the tools above mean you never need to: the free cross runs in your browser and the paid engine refuses anything that names a learner.
Is this affiliated with ASQA or training.gov.au?
No. We're an independent service built on the public register. We read the register and the legislation; we do not assess compliance and we don't make legal or regulatory claims on your behalf. Whether a supersession or an item 14 clock requires anything of you sits between you and your regulator.
How current is the data?
Checks read training.gov.au live, and the answer is then cached: 12 hours normally, and up to 36 in the worst case, because a stale answer is served while a fresh one is fetched. The watch re-checks subscribed RTOs in a nightly round that lands before the Australian working day; on a heavy night it works through them in rotation, oldest first, so a scope can wait a day for its turn.
Who's behind this?
One person — Jonathan, a developer building Register Radar as a new venture, in the open. More on the about page.

See it with your own scope

Ten seconds. No account, no email, no card.

Check my scope

Founding member — code FOUNDER100: first month free for the first 100 redemptions, ends 31 December. Details on pricing.