Adding a person for every block of enrolments feels like prudent operations. It's a structural risk. It buries process knowledge in individual heads, keeps manual reporting cycles alive just as the data model is being rebuilt, and draws on a labour pool that is shrinking and ageing. Growth should stop depending on hiring in proportion.
Why this lands on your desk
Three things sit with you, whatever the org chart says.
The data system. The VET Information Standard will replace AVETMISS, with RTO transition due by 1 January 2029. RTOs will need a VET data system that can collect, store and report in digital form. Data will move by API between student management systems, state and territory training authority systems and NCVER, rather than through manually extracted files. NCVER's STARS will replace the AVETMISS Validation Software. That's a systems-integration decision, and it's yours.
The interim changes. AVETMISS Release 8.1 applies from 1 January 2027. It moves ANZSCO to OSCA and adds a Specific Funding Identifier code for 'Free TAFE' activity. You have to resource that alongside normal reporting. Secondary sources suggest some transition dates were still to be confirmed, so verify the specifics with NCVER rather than assume.
Visibility for the governing body. ASQA's 2026-27 priorities include provider governance and the integrity of qualifications and competency outcomes. ASQA hasn't said this in so many words, but one provider-side commentary reads it as scrutiny of operational control, and of whether governing persons can see major risks. In most RTOs, the COO is the one who has to produce that picture.
Flat demand, tighter supply of people
NCVER reports 5.1 million students in nationally recognised VET in 2025, up just 1,585 on 2024. The domestic participation rate for ages 15-64 slipped to 26.4%. There's no rising tide. Growth is a question of share and mix.
The mix is shifting. Growth was concentrated among younger students (including those in school), regional and remote students, students with a disability and First Nations students. Full-time and female student numbers declined. VET in Schools numbers in 2025 are the highest since collection began in 2006. Steady volume with a changing cohort still adds complexity per learner, and that lands in enrolment, support and reporting before it lands anywhere else.
Now the supply side. The JSA VET Workforce Study (October 2024) found VET teacher numbers shrank 11-18% over a decade, and that Australia needs 3,800 more VET teachers over five years. The average age in the workforce is 47, against 41 for the Australian workforce. Almost half of the workforce is over 50. About 48.5% work in Teach, Train and Assess roles, and administration and operations is the next largest segment (2021 Census data).
A hiring-led plan competes for scarce people. Each retirement also walks out the door with whatever that person never wrote down.
One caveat. I haven't found authoritative data on how RTOs scale headcount against enrolments. This argument rests on the workforce, data and regulatory evidence above, not on a benchmark ratio.
What actually breaks the link between growth and hiring
RTO scalability without increasing headcount isn't about squeezing people harder. It comes down to three properties of your operation.
Make it repeatable
The 2025 Standards for RTOs took effect on 1 July 2025. The Outcome Standards cover training and assessment, VET student support, VET workforce and governance. Providers must show compliance against the Standards in effect at the time of a decision.
So a documented, repeatable process is evidence, not just efficiency. "Sam knows how we do that" is not evidence. Start with the processes where one person is the single point of failure: enrolment checks, funding eligibility, reporting submissions, assessment version control.
Make it connected
Count how many times a learner's details are keyed in. Count the spreadsheets that exist only to move data between systems. The VET Information Standard model is designed to remove the manual extraction and submission step, so any process built around that step has a limited shelf life.
The aim is simple: data captured once, at source, reusable everywhere it's needed. NCVER's guidance for RTOs on preparing for VET Information Standard reporting is a sensible place to benchmark your current setup.
Make it visible
ASQA's 2026-27 priorities cover:
- provider governance, market conduct and non-genuine operations;
- quality, sufficiency and fitness-for-purpose of training;
- integrity of qualifications and competency outcomes;
- transparency and assurance in complex and international delivery models.
A governing person shouldn't need a two-week reporting cycle to learn about a risk. Think a short, regular view of completions, assessment backlogs, complaints, third-party delivery and overdue reporting tasks, produced as a by-product of work rather than as a project.
A practical first quarter
You don't need a transformation programme to start. Try this:
- Map the person-dependent processes. Ask each team lead which tasks stop if one named person is away for a fortnight.
- Time one reporting cycle end to end. Record hours, handoffs and re-keying. That's your baseline.
- Check your Release 8.1 and VET Information Standard readiness with your system vendor. Ask for dates and API capability in writing.
- Draft a one-page governance dashboard. Agree with the CEO and board chair what they'd want to see monthly.
- Set a rule for automation. If you introduce AI or other automation into operations or assessment work, govern it with ASQA's Principles for the Responsible Use of AI in VET (covered in the August 2026 ASQA IQ) in mind.
Key takeaways
- Participation is flat (5.1 million students in 2025, up 1,585), so growth means share and mix, and a changing cohort adds complexity per learner.
- The VET workforce is shrinking and ageing, so hiring in proportion to enrolments competes for scarce people.
- AVETMISS Release 8.1 applies from 1 January 2027, and the VET Information Standard transition is due by 1 January 2029. Confirm dates with NCVER.
- Under the 2025 Standards, documented, repeatable processes are evidence of compliance, not just efficiency.
- The COO's task is to make operations repeatable, connected and visible to governing persons.
Our take
Headcount isn't the enemy. Unexamined headcount is. A hire who runs a documented, connected process adds capacity. A hire who inherits an undocumented one adds another head holding the same hidden knowledge.
Over the next two to three years, the best measure of your operations isn't how many people you've added. It's how many enrolments you could absorb before anyone had to be hired. Pick one process this week where that number is worryingly low, and write down how it really works.
FAQ
What does RTO scalability without increasing headcount actually mean?
It means growing enrolments or portfolio breadth without adding staff in proportion. That relies on documented, repeatable processes, data captured once and reused, and routine visibility for governing persons. It doesn't mean cutting roles or overloading existing staff.
When does the VET Information Standard replace AVETMISS?
NCVER indicates RTO transition to the VET Information Standard by 1 January 2029, with data exchanged via APIs. Secondary sources suggest individual transition dates and the AVETMISS cut-off were still to be confirmed, so check with NCVER and your student management system vendor.
What changes on 1 January 2027?
AVETMISS Release 8.1 applies from 1 January 2027. It moves occupation coding from ANZSCO to OSCA and adds a Specific Funding Identifier code for 'Free TAFE' activity. Confirm the details with NCVER before scheduling the work.
How do ASQA's 2026-27 priorities affect operations?
The priorities cover provider governance, market conduct and non-genuine operations; quality and fitness-for-purpose of training; integrity of qualifications and competency outcomes; and transparency in complex delivery models. One provider-side commentary reads this as closer scrutiny of operational control and board visibility of risk. That's an interpretation, not ASQA's wording.