File format
Ten core NAT files, plus supplementary organisation and program records where applicable. Tests check field positions, record lengths, byte output and file relationships.
Inspect the layouts ↓Compliance & reporting
See the checks
behind the record.
Follow the reporting process, inspect the controls and explore the tests behind CAQA RTO OS. Start with AVETMISS, then see how admissions, assessment, privacy and governance connect.
Internal software tests demonstrate the scenarios they exercise. External validation, provider evidence and reporting acceptance are separate checks.
01 / Reporting foundations
From the learner record
to the reporting file.
The software checks how information is collected, mapped and exported. The reporting body checks the collection you actually submit.
Mandatory information
Required data gaps are reported before finalisation. A diagnostic export remains available for investigation; its existence does not make a collection ready to lodge.
Follow the checks ↓Valid classifications
Tests cover permitted values and mappings for learner demographics, delivery, funding, commencement, outcomes and completions, including release-specific choices.
Browse the tests ↓Reference information
Rules use loaded training product, scope, locality and classification data. Missing reference checks are identified and cannot silently establish readiness.
See the dependencies ↓NCVER distinguishes file-format support from optional field, classification and reference checks. National AVETMISS support does not establish state reporting acceptance. NCVER compliance criteria ↗
AVETMISS 8.0
Current collection support
The exporter and checker use the selected collection year and period. Tests cover the published sample layouts, end-to-end mappings and the captured 8.0 validation catalogue.
AVETMISS 8.1
Activity from 1 January 2027
Tests exercise OSCA occupation reporting, Free TAFE funding identifier 71 and the release-specific education-level code 315. The checker identifies a fallback when the 8.1 rule file is absent; a fallback run cannot be finalised as ready.
NCVER release information ↗VET Information Standard
A separate transition
The 94-element model, lifecycle rules and STARS workflow have local tests. Eligible existing direct-reporting RTOs may transition from 1 October 2026; STA arrangements affect timing. All RTOs must transition by 1 January 2029. External access and conformance still need to be established for this product.
Check the transition conditions ↗02 / The export in detail
Every NAT file.
Every field position.
Expand a file to inspect its implemented layout. Lengths below describe the release snapshot, in characters before the CRLF line ending.
NAT00010Training organisation448 characters +
Core VET Provider Collection file. National layout: 268 characters. Implemented full layout: 448 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Training organisation identifier | 1 | 10 | A |
| Training organisation name | 11 | 100 | A |
| Training organisation type identifier | 111 | 2 | A |
| Address first line | 113 | 50 | A |
| Address second line | 163 | 50 | A |
| Address suburb | 213 | 50 | A |
| Postcode | 263 | 4 | A |
| State identifier | 267 | 2 | A |
| Contact name STA | 269 | 60 | A |
| Telephone number STA | 329 | 20 | A |
| Facsimile number STA | 349 | 20 | A |
| Email address STA | 369 | 80 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00020Training organisation delivery location180 characters +
Core VET Provider Collection file. National layout: 180 characters. Implemented full layout: 180 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Training organisation identifier | 1 | 10 | A |
| Delivery location identifier | 11 | 10 | A |
| Delivery location name | 21 | 100 | A |
| Postcode | 121 | 4 | A |
| State identifier | 125 | 2 | A |
| Address suburb | 127 | 50 | A |
| Country identifier | 177 | 4 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00030Program130 characters +
Core VET Provider Collection file. National layout: 130 characters. Implemented full layout: 130 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Program identifier | 1 | 10 | A |
| Program name | 11 | 100 | A |
| Nominal hours | 111 | 4 | N |
| Program recognition identifier | 115 | 2 | A |
| Program level of education identifier | 117 | 3 | A |
| Program field of education identifier | 120 | 4 | A |
| Occupation identifier | 124 | 6 | A |
| Vet flag | 130 | 1 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00060Subject123 characters +
Core VET Provider Collection file. National layout: 123 characters. Implemented full layout: 123 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Subject identifier | 1 | 12 | A |
| Subject name | 13 | 100 | A |
| Subject field of education identifier | 113 | 6 | A |
| Vet flag | 119 | 1 | A |
| Nominal hours | 120 | 4 | N |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00080Client347 characters +
Core VET Provider Collection file. National layout: 327 characters. Implemented full layout: 347 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Client identifier | 1 | 10 | A |
| Name for encryption | 11 | 60 | A |
| Highest school level completed identifier | 71 | 2 | A |
| Gender | 73 | 1 | A |
| Date of birth | 74 | 8 | A |
| Postcode | 82 | 4 | A |
| Indigenous status identifier | 86 | 1 | A |
| Language identifier | 87 | 4 | A |
| Labour force status identifier | 91 | 2 | A |
| Country identifier | 93 | 4 | A |
| Disability flag | 97 | 1 | A |
| Prior educational achievement flag | 98 | 1 | A |
| At school flag | 99 | 1 | A |
| Address suburb | 100 | 50 | A |
| Unique student identifier | 150 | 10 | A |
| State identifier | 160 | 2 | A |
| Address building property name | 162 | 50 | A |
| Address flat unit details | 212 | 30 | A |
| Address street number | 242 | 15 | A |
| Address street name | 257 | 70 | A |
| Survey contact status | 327 | 1 | A |
| Statistical area level 1 identifier STA | 328 | 11 | A |
| Statistical area level 2 identifier STA | 339 | 9 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00085Client contact details557 characters +
Core VET Provider Collection file. National layout: 557 characters. Implemented full layout: 557 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Client identifier | 1 | 10 | A |
| Client title | 11 | 4 | A |
| Client first given name | 15 | 40 | A |
| Client family name | 55 | 40 | A |
| Address building property name | 95 | 50 | A |
| Address flat unit details | 145 | 30 | A |
| Address street number | 175 | 15 | A |
| Address street name | 190 | 70 | A |
| Address postal delivery box | 260 | 22 | A |
| Address suburb | 282 | 50 | A |
| Postcode | 332 | 4 | A |
| State identifier | 336 | 2 | A |
| Telephone number home | 338 | 20 | A |
| Telephone number work | 358 | 20 | A |
| Telephone number mobile | 378 | 20 | A |
| Email address | 398 | 80 | A |
| Email address alternative | 478 | 80 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00090Disability12 characters +
Core VET Provider Collection file. National layout: 12 characters. Implemented full layout: 12 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Client identifier | 1 | 10 | A |
| Disability type identifier | 11 | 2 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00100Prior educational achievement13 characters +
Core VET Provider Collection file. National layout: 13 characters. Implemented full layout: 13 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Client identifier | 1 | 10 | A |
| Prior educational achievement identifier | 11 | 3 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00120Training activity158 characters +
Core VET Provider Collection file. National layout: 111 characters. Implemented full layout: 158 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Training organisation identifier | 1 | 10 | A |
| Delivery location identifier | 11 | 10 | A |
| Client identifier | 21 | 10 | A |
| Subject identifier | 31 | 12 | A |
| Program identifier | 43 | 10 | A |
| Activity start date | 53 | 8 | D |
| Activity end date | 61 | 8 | D |
| Delivery mode identifier | 69 | 3 | A |
| Outcome identifier national | 72 | 2 | A |
| Funding source national | 74 | 2 | A |
| Commencing program identifier | 76 | 1 | A |
| Training contract identifier | 77 | 10 | A |
| Client identifier apprenticeships | 87 | 10 | A |
| Study reason identifier | 97 | 2 | A |
| Vet in schools flag | 99 | 1 | A |
| Specific funding identifier | 100 | 10 | A |
| School type identifier | 110 | 2 | A |
| Outcome identifier training organisation STA | 112 | 3 | A |
| Funding source state training authority STA | 115 | 3 | A |
| Client tuition fee STA | 118 | 5 | N |
| Fee exemption concession type identifier STA | 123 | 2 | A |
| Purchasing contract identifier STA | 125 | 12 | A |
| Purchasing contract schedule identifier STA | 137 | 3 | A |
| Hours attended STA | 140 | 4 | N |
| Associated course identifier STA | 144 | 10 | A |
| Scheduled hours STA | 154 | 4 | N |
| Predominant delivery mode STA | 158 | 1 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00130Program completed72 characters +
Core VET Provider Collection file. National layout: 39 characters. Implemented full layout: 72 characters, including applicable trailing state fields.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Training organisation identifier | 1 | 10 | A |
| Program identifier | 11 | 10 | A |
| Client identifier | 21 | 10 | A |
| Date program completed | 31 | 8 | A |
| Issued flag | 39 | 1 | A |
| Parchment issue date STA | 40 | 8 | D |
| Parchment number STA | 48 | 25 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00010ATraining organisation (supplementary)448 characters +
Supplementary file for applicable non-register organisation or program records; inclusion depends on the collection and pathway.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Training organisation identifier | 1 | 10 | A |
| Training organisation name | 11 | 100 | A |
| Training organisation type identifier | 111 | 2 | A |
| Address first line | 113 | 50 | A |
| Address second line | 163 | 50 | A |
| Address suburb | 213 | 50 | A |
| Postcode | 263 | 4 | A |
| State identifier | 267 | 2 | A |
| Contact name STA | 269 | 60 | A |
| Telephone number STA | 329 | 20 | A |
| Facsimile number STA | 349 | 20 | A |
| Email address STA | 369 | 80 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
NAT00030AProgram (supplementary)130 characters +
Supplementary file for applicable non-register organisation or program records; inclusion depends on the collection and pathway.
No header row. Text is space-filled; numeric fields are zero-filled where specified; dates use DDMMYYYY. “STA” marks a field beyond the national layout.
| Field | Position | Width | Type |
|---|---|---|---|
| Program identifier | 1 | 10 | A |
| Program name | 11 | 100 | A |
| Nominal hours | 111 | 4 | N |
| Program recognition identifier | 115 | 2 | A |
| Program level of education identifier | 117 | 3 | A |
| Program field of education identifier | 120 | 4 | A |
| Occupation identifier | 124 | 6 | A |
| Vet flag | 130 | 1 | A |
A = text, N = numeric, D = date. Reference: implemented layouts and the layout/sample/byte-output tests in test_nat_files.py.
The form shown in the public admissions tour is an excerpt. The operational enrolment-form module has separate tests for the NCVER question and privacy-notice variants. Collection specifications and enrolment resources ↗
03 / A traceable collection
Prepare. Check.
Submit with evidence.
Each stage records a different fact. A generated file, a local validation result and an external acceptance acknowledgement should remain distinguishable.
- 01
Set the scope
Select organisation, year, period, release and reporting pathway.
- 02
Generate
Build the file set; show missing information and mapping problems.
- 03
Check locally
Review preliminary findings, then run the full checks and resolve errors.
- 04
Finalise
Record the declaration and bind the validated archive to its hash.
- 05
Validate & lodge
Use the authorised NCVER or STA service for the real collection.
External service - 06
Reconcile
Retain the acknowledgement, record the outcome and handle corrections.
Why a “ready” label needs evidence
Try three tested scenarios.
These illustrations explain the finalisation controls tested in the application. They do not run AVS or validate learner data.
Finalisation blocked
Zero reported errors is not enough.
A required reference rule has not been evaluated. Load the reference information and rerun the complete validation before finalising.
Test: missing_reference_checks_cannot_be_finalised
What the 232 local rule rows do, and where they differ from AVS
The captured 8.0 catalogue supplies rule identifiers, severities and field references. Tests cover blank fields, code lists, duplicates, cross-file relationships, dates, periods, outcome consistency and loaded-reference lookups. The number of catalogue rows is not a count of independently certified regulatory obligations.
- Preliminary options can suppress or soften findings; they do not replace complete finalisation checks.
- Missing references, truncated findings, preliminary results, remaining errors and a fallback rule catalogue block finalisation, even if an old status says ready.
- Local data-quality warnings and configurable thresholds are distinct from NCVER’s quality checks. Examples include the blank-USI threshold and outcome distributions.
- Documented local interpretations include nominal-hour bands, certain postcode/locality checks and reference-dependent recognition checks. AVS can produce different findings.
- Finalisation rechecks the archive digest. A changed file set must be validated again.
See the validation, reference and audit-regression test modules below. About the actual AVS service ↗
04 / Across the system
Controls that follow
the learner’s journey.
Open an area to see its behaviour, tested scenarios and the evidence your organisation still needs to supply.
AVETMISS VET Provider Collection 8.0 / 8.1AVETMISS file generation
Fixed-width files, field positions, date and numeric formatting, CRLF endings, outcome mappings, collection periods and supplementary records.
What the tests demonstrate
Tests check byte-exact records, published sample layouts, ten-file exports, funding filters, overseas addresses, USI substitutes and release-specific codes.
What still needs evidence
Correct output format is one part of reporting. Each actual collection still needs the appropriate external validation and submission.
192 passing cases in related test files. Areas overlap; these counts must not be added together.
Mandatory data, classification and reference checksLocal AVETMISS validation
Checks blanks, codes, duplicate records, file relationships, dates, scope and reference-dependent values. Findings identify the file, field, rule and affected records.
What the tests demonstrate
Tests exercise the captured rule catalogue, broken records, preliminary options, reference lookups and readable findings. Missing reference checks, fallback rule sets and truncated runs cannot establish finalisation readiness.
What still needs evidence
The captured 8.0 catalogue has 232 rule rows. Local rule interpretations and quality warnings are documented; this is not the NCVER validator.
141 passing cases in related test files. Areas overlap; these counts must not be added together.
Prepare, review, finalise and reconcileCollections and reporting history
Collections retain the year, period, options, exports, validation summary, declaration and recorded external outcome. A reporting ledger tracks what was accepted.
What the tests demonstrate
Tests cover generation through finalisation, nil-return declarations, completion deduplication, reporting clocks and binding the validated archive to its SHA-256 digest.
What still needs evidence
Recording a submission reference in the system is different from receiving an acceptance acknowledgement from NCVER or an STA.
72 passing cases in related test files. Areas overlap; these counts must not be added together.
VET Information Standard 1.0.0VET Information Standard and STARS
The model and export support the 94-element catalogue, lifecycle events, full and changed-record batches, third-party data, corrective actions and reconciliation.
What the tests demonstrate
Tests exercise classifications, element rules, status sequences, batch construction, upload/validation/submission responses, retries, removal and reconciliation using test responses.
What still needs evidence
STARS service tests use doubles. Live integration-environment and production conformance are not established by those tests.
187 passing cases in related test files. Areas overlap; these counts must not be added together.
Contract-specific state and territory reportingState and funding pathways
Jurisdiction settings select the reporting pathway, layouts, funding rules, eligibility records, claims and submission registers.
What the tests demonstrate
Tests cover state layouts, pathway isolation, eligibility decisions, claim calculations and response handling, including supported WA submission workflows.
What still needs evidence
Coverage is configuration and contract dependent. National AVETMISS file support is not assurance of every state funding obligation or live authority acceptance.
146 passing cases in related test files. Areas overlap; these counts must not be added together.
Data Provision Requirements and National VET Data PolicyData provision responsibilities
Reporting calendars, exemptions, aggregate returns, quality-indicator summaries, cessation checklists and on-request reporting keep responsibilities visible.
What the tests demonstrate
Tests cover the workflow records, due-date calculations, declaration gates, export fields and tenant-scoped configuration.
What still needs evidence
An exemption must be granted by the relevant authority. Staff remain responsible for correct declarations, transition arrangements and actual lodgement.
47 passing cases in related test files. Areas overlap; these counts must not be added together.
Learner suitability and pre-enrolment reviewAdmissions, identity and LLND
Enquiries lead to an application, identity evidence, a course-context LLND review and a combined staff decision before enrolment and class allocation.
What the tests demonstrate
Tests cover expiring invitations, immutable bank editions, identity categories and expiry, approval gates, prefill, guardian evidence, private uploads, repeat submissions and class handover.
What still needs evidence
The public LLND bank is a demonstration bank. A real assessment bank needs trainer validation. The 100-point identity example is a configurable provider policy, not a universal AVETMISS rule.
41 passing cases in related test files. Areas overlap; these counts must not be added together.
2025 Outcome Standards: assessment and recognitionAssessment and credit decisions
Assessment records connect the decision, assessor, evidence, tool review, RPL and credit-transfer process.
What the tests demonstrate
Tests cover assessment permissions and gates, result changes, supporting evidence and the relationship between recognition and enrolment status history.
What still needs evidence
Staff must supply valid assessment evidence and apply the training product and assessment requirements. A software check cannot make the competence judgement.
81 passing cases in related test files. Areas overlap; these counts must not be added together.
2025 Outcome Standards and Credential PolicyValidation and workforce
Validation planning links training products, schedules, panel declarations, credentials and recorded outcomes. Workforce records hold currency and professional development.
What the tests demonstrate
Tests check credential and independence gates, schedule-specific conflicts, external independence where required and rechecking evidence at completion.
What still needs evidence
Policy settings such as a first-three-year target are provider choices. The system needs genuine credentials, declarations, panel decisions and policy references.
49 passing cases in related test files. Areas overlap; these counts must not be added together.
USI requirements and certification controlsUSI and credential issuance
Issuance requires current verified USI evidence or a documented permitted exemption. Changes to identity or verification can affect eligibility to issue.
What the tests demonstrate
Tests cover blocked unverified issuance, exemption evidence, identity changes, revoked results, credentials, statements of attainment and related higher-education issue routes.
What still needs evidence
The Registry service contract, approved access and integration conformance remain separate requirements. The existing placeholder is not a live Verify/Locate/Create implementation; no administrator bypass is offered.
35 passing cases in related test files. Areas overlap; these counts must not be added together.
2025 Outcome Standards: student supportStudent support and case handling
Information packs, support plans, complaints, appeals, surveys, attendance and portal change requests support the learner relationship.
What the tests demonstrate
Tests cover case records, provider-policy deadlines, support actions, survey summaries, attendance permissions and student/trainer portal access.
What still needs evidence
Published policies, support delivery, case decisions and actual communications must be maintained by the provider.
87 passing cases in related test files. Areas overlap; these counts must not be added together.
Agreements, receipts and provider fee policiesFees and financial records
Fee schedules, invoices, payments, refunds and plans connect to the learner account. Admissions checks the applicable agreement and fee prerequisites.
What the tests demonstrate
Tests cover amount calculations, invoice/receipt outputs, payment and refund workflows, exposure calculations and enrolment agreement gates.
What still needs evidence
Providers must configure the applicable fee protection and refund policy. The public demo records fictional receipts and does not collect money.
59 passing cases in related test files. Areas overlap; these counts must not be added together.
2025 Outcome and Compliance StandardsGovernance and quality records
Registers hold risks, improvements, conflicts, insurance, fit-and-proper records, marketing reviews, resources and transition actions.
What the tests demonstrate
Tests cover register operations, linked evidence, tenant scope, governance workflows and the standards coverage page.
What still needs evidence
Recorded evidence supports oversight. It does not substitute for the governing body acting on risks or satisfy every obligation automatically.
43 passing cases in related test files. Areas overlap; these counts must not be added together.
Privacy and record-handling controlsPrivacy, retention and records
Private evidence storage, retention workflows, legal holds, access/correction requests, breach records and controlled data exports support record management.
What the tests demonstrate
Tests cover encryption round trips, private document access, retention/disposal gates, de-identification, consent-related records and export scoping.
What still needs evidence
Providers determine their lawful handling, retention and notification responsibilities. Tests do not establish blanket Privacy Act compliance.
90 passing cases in related test files. Areas overlap; these counts must not be added together.
Where the provider scope makes these applicableInternational and higher education
International workflows include course progress and intervention, transfers, deferrals, agents and a PRISMS task register. Higher-education workflows include admissions, credit, awards and reporting tools.
What the tests demonstrate
Dedicated tests cover ESOS, TEQSA, higher-education admissions/analytics, HELP and TCSI workflow behaviour with synthetic or mocked data.
What still needs evidence
CRICOS, National Code, HESF, HELP and TCSI obligations depend on provider registration and activity. A task register or mock API result is not a live PRISMS/TCSI submission.
112 passing cases in related test files. Areas overlap; these counts must not be added together.
Platform assurance supporting all modulesAccess and audit controls
Roles, tenant boundaries, MFA, session controls, CSRF protections, private reporting responses and audit records protect operational work.
What the tests demonstrate
Tests include denied reporting access, cross-tenant downloads, session revocation, authentication/second-factor controls, audit-chain verification and no-store headers.
What still needs evidence
Automated tests are bounded evidence. They are not an external penetration test, security certification or guarantee that an operator has configured every control.
251 passing cases in related test files. Areas overlap; these counts must not be added together.
Backup, restore and deployment controlsRecovery and operational reliability
Recovery tooling verifies completed manifests and matching encrypted artifacts. Application readiness, jobs and release identity are observable.
What the tests demonstrate
Tests reject missing, mixed, changed and incomplete backup sets; transfer-failure tests preserve the previous good set. Migration, readiness and job retry tests cover failure paths.
What still needs evidence
Backup status, key custody, restore drills and alert delivery need current operational evidence. Code tests do not prove a future restore or notification will succeed.
76 passing cases in related test files. Areas overlap; these counts must not be added together.
Data integrity and usable operationsReference data and usability
Reference importers, structured forms, organisation-scoped lists, pagination and accessible page structure support consistent day-to-day use.
What the tests demonstrate
Tests cover reference imports, classification mappings, model constraints, route/navigation coverage, form labels, templates, contrast checks and bounded query counts.
What still needs evidence
Reference lists need authorised, current data. Automated accessibility and query-count tests do not replace user testing, a full WCAG audit or production load testing.
306 passing cases in related test files. Areas overlap; these counts must not be added together.
The 2025 Standards for RTOs include Outcome Standards, Compliance Standards and the Credential Policy. This page describes software controls supporting that work; provider compliance depends on how the requirements are met in practice.
05 / Inspect the evidence
The tests behind
the descriptions.
Search every recorded test function, including parameterised case counts and skips. Results describe the dated snapshot, not a continuously updated certification.
Run scope
Full pytest suite on Windows with SQLite, synthetic fixtures and mocked external services. Parameterised cases are counted separately. No live regulator integration result is implied.
- Tested release
- 0.4.2
- Source revision
ec74e47b47f8- Recorded cases
- 2067
- Test functions
- 1543
Passing tests show the specified inputs and assertions worked. Some service tests use mocked responses; they do not demonstrate live USI, STARS, AVS, TGA, PRISMS or TCSI connectivity. The two skipped cases are not counted as passes. This evidence does not include a fresh PostgreSQL or external penetration-test certification.
The results shown here come from a completed local run of the stated source revision. They are retained as a dated evidence snapshot; they do not represent continuous monitoring or independent certification.
Download the test-result index (CSV) ↗ Download the evidence snapshot (JSON) ↗Loading the recorded results...
06 / Requirements index
Find the requirement.
Trace the supporting work.
643 references across AVETMISS, the VET Information Standard, data provision and reporting workflows.
This index comes from the internal requirements mapping compiled in September 2026. “Implementation recorded” describes a mapping entry, not an independent compliance finding. Related test files provide area-level traceability; their passing count does not prove every obligation in that row. Some references concern provider actions or future changes.
For the current boundaries, read External checks. Rule references identify the captured catalogue without republishing NCVER’s full rule wording. Consult the current official source for the authoritative requirement.
Official references: AVETMISS specifications, VET Information Standard reporting, 2026 data provision amendments, ASQA data reporting obligations.
Loading the requirement index...
07 / Complete the picture
What needs external
or provider evidence.
These checks matter when assessing the software for your organisation. A successful demonstration or internal test run cannot supply them.
| Area | Evidence to verify |
|---|---|
| AVS / STA acceptance | Validate the intended collection through the relevant external service and retain its acknowledgement. An owner-reported historical 2025 submission is recorded in the project handover; this public test snapshot does not reproduce or independently verify that acknowledgement. |
| NCVER product register | A registration request is documented. Confirm the actual current listing separately. Registration is not NCVER endorsement or certification of every feature. |
| USI Registry | The official Developer Kit, service contract, approved access and conformance results are still required for the live integration. Local issuance gates are tested; the product is not presented here as USI-compatible registered software. USI integration requirements ↗ |
| STARS / VET Information Standard | Obtain the authorised integration-environment access and complete the required readiness scenarios, then establish production access and the provider’s transition arrangements. Mocked service success is not external acceptance. |
| Reference data and 8.1 rules | Load and maintain the relevant official reference tables. Verify the real authorised TGA import and obtain the appropriate 8.1 rules. A missing table or fallback catalogue remains visible and blocks complete finalisation. |
| State funding and other integrations | Validate each contracted reporting pathway, authority response, payment arrangement and applicable integration. Tests of selected state or higher-education workflows do not establish universal contract coverage. |
| Provider decisions | Supply approved LLND banks, current policies, real identity and eligibility evidence, staff credentials, panel declarations, assessment decisions and student agreements. Verify any NRT logo authorisation. |
| Operational assurance | Confirm production access settings, backup and restore evidence, monitoring delivery, recovery-key custody and independent security assessment appropriate to the organisation. |
Bring the requirements that matter to your RTO.
We can walk through the controls, test evidence and remaining configuration for your learner cohorts, delivery and reporting pathways.
Arrange a detailed walkthroughAVETMISS is a trademark of the National Centre for Vocational Education Research. CAQA RTO OS is not affiliated with or endorsed by NCVER. Sources and evidence reviewed 9 September 2026.