LEARN MORE ABOUT
Versions of the VET Information Standard explained
This page explains the structure used when creating versions of the VET Information Standard, including how different types of versions are reflected, and provides practical examples of the versions that may be released in the future
Versioning helps users quickly identify:
-
which iteration of the VET Information Standard they are viewing;
-
whether previous versions exist and the types of versions that have previously existed; and
-
the nature of the latest version (i.e. whether it was a national, jurisdictional or maintenance change)
Versioning explained
VET Information Standard versions include a taxonomy with both a numerical representation of the types of changes to the standard, along with four key dates that apply to each version.
Numerical representation:
As shown in the diagram below, each version will have a 3-digit version number:
National version numbers increase incrementally and never reset to 0. National numbers update only when changes to the standard are of a nature that impacts the collection and reporting of data by all providers.
Jurisdiction version numbers increase incrementally and only reset to 0 when a new national version of the VET Information Standard is released. Jurisdiction numbers update only when changes to the standard are of a nature that impacts the collection and reporting of data, and which applies to providers with a funding and/or reporting arrangement in one or more specific jurisdictions.
Maintenance version numbers increase incrementally and reset to 0 when either a new national or jurisdiction version of the VET Information Standard is released. Maintenance numbers update only when changes are made to improve useability of the standard for all providers.
Key dates:
Each version of the VET Information Standard has four key dates associated with it:
The date the version is publicly released, enabling RTOs and other sector stakeholders to begin preparation to transition to the new version, where appropriate.
The date RTOs can begin reporting against this version. Reporting against this version of the standard is not mandatory at this stage unless the effective date and the mandatory transition date are the same.
The latest date by which all RTOs must be ready to commence reporting against this version of the standard.
The date that data can no longer be submitted against that version. Where an expiry date has been set this means that a new version of the VET Information Standard exists, is in effect, and data must be submitted against the new ‘active’ version.
Important versioning considerations
As described above, not all VET Information Standard versions apply to every stakeholder.
The following will help with understanding whether, and how, specific versions might apply to your organisation.
-
The content of each new version includes all content of the previous version. This means there is a traceability and continuation of reportable data from one version to the next, unless the latest version removes or modifies specific reporting obligations from the previous version.
-
Each new version will be accompanied by sector communications outlining the specific change(s).
-
Some versions may be ‘published’ and take effect on the same day. An example of this is version 2.0.0 which was both released and became effective on 1 October 2026.
-
Some versions may be ‘published’ and become mandatory for RTOs at a predefined date. This could be for an urgent fix if something isn’t working as intended.
-
Some versions, particularly jurisdictional versions, may not apply to every state and territory. This means that RTOs will need to ensure they understand whether a new version applies to them.
-
Impacted RTOs can begin reporting against the new version any time from the effective date until the mandatory transition date.
- However, once an RTO has begun reporting against the new version they will be considered to have fully adopted the requirements of the latest version of the VET Information Standard, from the date of their transition, and no longer be able to submit data against the previous version.
-
Multiple versions may be active at the same time. This is particularly the case for jurisdictional versions. For example, if NSW implemented new jurisdiction-specific elements, a new version of the standard would be published but it would only apply to RTOs with a funding or reporting arrangement in NSW. All other RTOs would continue to report against the previous version.
-
Multiple types of changes may be included within a single version, for example where both jurisdictional and maintenance changes are included in a new version. In this instance, the highest version number (i.e. jurisdiction) will increase, and the lower version number (i.e. maintenance) will reset to 0.
Versioning scenarios
Below are four potential change scenarios to the VET Information Standard.
The table below these examples illustrates how the versioning taxonomy for each version of the VET Information Standard will work:
-
Scenario A – A typographical edit to an element definition has been made. This is a maintenance change.
-
Scenario B – New South Wales has included all their state or territory elements within the VET Information Standard. This is a jurisdiction change.
-
Scenario C – Northern Territory has included all their state or territory elements within the VET Information Standard. This is a jurisdictional change.
-
Scenario D – New national elements have been added to the VET Information Standard, and New South Wales has removed a state or territory element. This is both a national and jurisdictional change.
Current version Version 2.0.0 |
Scenario A: Version 2.0.1 |
Scenario B: Version 2.1.0 |
Scenario C: Version 2.2.0 |
Scenario D: Version 3.0.0 |
|---|---|---|---|---|
|
||||
|
||||
All RTOs without a funding / reporting arrangement remain on V2.0.1 |
||||
All NSW RTOs* remain on V2.1.0 All RTOs without a funding / reporting arrangement remain on V2.0.1 |
||||
Applies to:
AND
AND
|
* with funding and/or reporting arrangements