VETtrak Virtual Assistant: a VA who keeps your RTO's student data clean, claimable and migration-ready

Nobody searches “vettrak virtual assistant” because things are going well. You search it the week a NAT file bounces back with 200 validation errors and the claim window closes on Friday, or the week your one admin resigns and you realise she was the only person who knew where the enrolment wizard hides the funding fields. VETtrak has been running Australian RTOs for more than twenty years, and in most small and mid-size training organisations it is run, in turn, by exactly one person. This page is about making that person someone you pay $12-17 an hour instead of you at 10pm.

The daily rhythm a VA runs in your VETtrak

Morning starts with the enrolment queue. Whatever came in overnight, web forms, employer bookings, phone enrolments scribbled on paper, gets entered properly: the Client Wizard checked against existing records first so you don’t create your fourth copy of the same apprentice, the USI verified against the registry before the student ever sits in a classroom, pre-training review and LLN evidence attached to the client record, and the funding fields set right at the point of entry. That last one is the quiet money-saver. Funding source, purchasing contract, ANZSCO code, study reason: every one of those left blank or guessed at enrolment becomes a validation error at export, months later, when the student is long gone and nobody remembers the answer.

Then results. Trainer marksheets, assessment summaries and portal submissions get translated into recorded unit outcomes on each enrolment, with the correct national outcome codes: 20 for competency achieved, 30 for not achieved, 40 for withdrawn, 51 where RPL was granted. The trainer or assessor made the judgement; your VA records it, with activity start and end dates that will survive AVETMISS validation rather than trip it. Done weekly, this is twenty minutes of tidy data entry. Done quarterly in a panic, it is the reason your completion data never matches your delivery.

Occurrences and the waitlist get a weekly pass. When you confirm dates for the next intake, the VA sets up the new occurrence, moves the waitlisted students across, and sends the confirmation merge the same day, because VETtrak’s waitlist does not contact anyone on its own. Class lists stay current, no-shows get followed up, and finished occurrences get closed off properly instead of lingering half-open in the database forever.

Money runs alongside all of it. Fee-for-service and employer invoices are raised from the enrolment in VETtrak’s finance area, payments recorded as they arrive, and the outstanding list worked on a chasing cadence you sign off once. RTOs leak revenue in a very specific place: the gap between “student enrolled” and “invoice raised”. A VA who raises the invoice the day the enrolment is entered closes that gap permanently.

And then the big rhythm, the one this page really exists for: AVETMISS. Ahead of every state reporting window, your VA runs VETtrak’s AVETMISS export and works the error list. Missing USIs get chased with the student. Invalid postcodes get corrected. Blank outcome identifiers get filled from the marksheet record. Date clashes between the NAT00120 training activity and the enrolment get reconciled. The export gets re-run until it comes back clean, and it comes back clean days before the deadline, not at 4:55pm on the last day. If you report into a state funding contract, this single habit is worth more than everything else on this page combined, because late or dirty claims are money you delivered training for and did not get paid for.

The honest bit

Three things worth saying plainly before you hire anyone.

First, VETtrak will not fix its own data. Validation happens at export, not at entry, so an error made in March surfaces in June, and the product’s twenty-year desktop lineage shows: some workflows are genuinely quick once you know them, and some involve more clicks than any modern system would tolerate. A VA does not change that. What a VA changes is that the person doing those clicks costs $12-17 an hour and does them every day instead of in quarterly catch-up binges.

Second, the waitlist and the comms are manual. The waitlist is a list; it holds names and does nothing with them until a human moves them. The merge templates are Word documents that produce good letters and emails from live data, but they need someone to run them and someone to maintain them when course codes change. Neither is automation, and no VA can pretend otherwise. They can just be someone else’s job.

Third, and this is the 2026 reality: VETtrak’s owner, ReadyTech, launched Ready Student in 2025 and is migrating VETtrak and JR Plus customers onto it in stages. VETtrak is not switching off tomorrow, but the direction is set, and if you’re a VETtrak RTO you are, one way or another, mid-transition. That cuts both ways. It would be a strange time to hire a full-time employee whose entire skill is a platform being retired. It is a very sensible time to put 10-15 flexible hours a week into keeping the current system running while cleaning the data that will move: duplicate clients merged, abandoned occurrences closed, inconsistent programme codes standardised. Whatever is in your VETtrak on migration day is what lands in Ready Student. A VA makes sure that’s a dataset, not sediment.

What stays with you

RTOs are regulated organisations, and the line between admin and compliance judgement has to be drawn in writing before anyone gets a login.

Assessment judgements stay with your trainers and assessors, full stop. The VA records the outcome a qualified assessor determined; they never decide competency, never adjust an outcome code to make a claim work, and never mark anything. RPL and credit transfer decisions are yours. Funding eligibility calls, which contract a student sits under, whether they qualify, what you claim, are yours, and any AVETMISS fix that would change what’s being claimed gets flagged to you rather than made. Certificate and statement-of-attainment issuance is yours: the VA can prepare the award records and the merge documents, but the authorisation to issue sits with the person your registration says it sits with. And the actual lodgement of claims and AVETMISS submissions to your state training authority happens under your sign-off, every time.

VETtrak’s own security model backs the paperwork. Roles are configured in the Security Manager with feature-level permissions, so the VA’s role covers clients, enrolments, results, reporting and finance tasks, and simply does not include user administration or the things you’ve kept back. It’s a permission, not a promise.

What it costs and where to start

VETtrak admin sits on DotVA’s admin tier: $12-17 AUD an hour excluding GST, and most RTO placements run 10-15 hours a week, which lands around $500-1,100 a month. Placement takes 7-10 business days, and the first 5-7 days are supervised inside your VETtrak, starting on enrolment entry and results before anyone goes near an AVETMISS export solo. There’s a $500 refundable deposit credited to your first month, a 30-day recalibrate-or-replace guarantee if the match isn’t right, and no lock-in beyond 14 days notice. Jenn takes every discovery call herself, and after 87+ Australian placements since 2024 she will tell you straight if your volume doesn’t justify it yet.

If you want the wider training-sector picture, the education page covers how RTOs and course providers use VAs beyond the SMS. The data entry page shows how we scope high-accuracy records work, and the VA cost guide has the full pricing breakdown with on-cost comparisons against hiring locally. Otherwise, book a discovery call and bring your last NAT file error report. It makes for a very short conversation about whether this is worth doing.