Your scope, synchronised — and the documents that describe it under control.
Scope comes from training.gov.au rather than from a spreadsheet somebody maintains, including release history and currency status. Training and assessment strategies, unit delivery plans and the assessment register are versioned and approved alongside it.
Release history and currency come from the national register.Strategies and delivery plans are versioned and approved, so the current one is never in question.
Document control on every artefact
The problem
The training product changed. Your documents did not.
A qualification is superseded, or a unit within it is. Somewhere in your organisation there is a training and assessment strategy, a set of delivery plans and a pile of assessment tools that still reference the old release. Usually nobody finds out until validation, or until an audit.
The underlying problem is that scope is held in one place, the documents that describe delivery in another, and nothing connects them. Keeping them aligned is a manual reconciliation somebody has to remember to do.
Scope, synchronised
Straight from training.gov.au, not from a spreadsheet.
Training product data is synced from training.gov.au on a schedule, including release history and currency status. The codes, titles and release status in the platform are the ones on the national register rather than the ones somebody typed.
This is where the gap analysis gets its teeth. A training product on scope with no current strategy is not a subtle problem, but it is remarkably easy to have and not know about.
- Codes and titles from the national register
- Release history and currency status
- Documents versioned and approved
Strategies and delivery plans
Documents with versions, approvals, and a current one you can name.
Training and assessment strategies and unit delivery plans are held under document control: versioned, approved, and dated. When somebody asks which one is current, there is an answer rather than a folder.
The assessment register sits alongside them, recording the tools and methods in use for each unit — which is what makes the mapping in the validation session possible in the first place.
- Versioned and approved, with approval readiness visible before submission
- The assessment register records the tools and methods actually in use
What this replaces
One source for what you deliver.
- A scope spreadsheet somebody updates when they rememberScope synchronised from training.gov.au
- Checking training.gov.au by hand to see what has movedRelease history and currency status synced on a schedule
- Three versions of a strategy and an argument about which is currentVersioned, approved documents with one current version
- A training product on scope with no strategy, undiscoveredA gap analysis that names it, recomputed every time you open it
Traceable to the Standards
Strategies, delivery plans and the assessment register are held as controlled documents against a scope taken from the national register, which is what makes delivery defensible product by product.
Where this connects
Audit readiness
The 2025 Standards, clause by clause, with evidence against each one.
Read moreFindings that close themselves
A failed question becomes a rectification plan, a task, and a record.
Read moreAssessment validation
A stated sampling policy, eligible validators, recommendations that land.
Read more
Find out what your last audit would have looked like with a system behind it.
14 days, no credit card, and the Standards are already loaded when you sign in.