RTO software should carry one student record from enquiry to certificate and on to the NCVER report, with nothing re-keyed. The enquiry, the enrolment form, the USI check, the evidence, the trainer's mark, the certificate and the AVETMISS 8.0 files all come from the same record. RTO Grow does this in one system.
One record, six stages
A complete RTO system runs on one student record that every stage reads and writes. RTO Grow is built that way. The LMS, the student management and the compliance registers share the same tables, and each stage below hands the record to the next.
Enquiry
A public enquiry form, the course page's "Enquire" button and a chat widget all write into one contacts inbox. The inbox shows every person once, with a stage chip from "Lead" to "Completed" and a "Came from" column built from first-touch attribution. You can enrol a contact straight from their record.
Enrolment
The hosted apply page collects the form, the USI and the declarations. It takes a card payment through Stripe Checkout or lets the student pay later, and lands in "Applications". Staff pick a delivery location and click "Approve → Enrol". One rule stops nationally recognised training being enrolled without an enrolment form on file, with a logged override for the day a class starts tomorrow.
USI
The USI is checked against the USI Registry when the form arrives, re-checked overnight, and can be verified, found or created from the student's record. A mismatch leaves a plain-English note on the file. Nothing changes without you. A verified USI flips the enrolment to ready-to-report.
Evidence
Students answer online, on paper with a scan upload, by observation, audio, video or file upload. Multiple-choice, ordering, matching and hotspot questions score themselves on "Check my answers". Written and practical work waits for a person. Every stored answer reads in plain words on every marking surface.
Marking
Trainers mark from a queue that sorts, groups and filters by course, unit, trainer and class. Every sign-off carries a typed-name assessor declaration and a credential check. A class can be marked in one dialog. A mistaken mark can be reversed with a reason, and the audit trail keeps both.
Certificate
When the last unit is competent, the enrolment completes itself. The offering decides whether the certificate issues automatically or waits in "Documents waiting". Each certificate gets a number, a PDF with a QR code, a permanent record and an email to the student. The public verify page says "Certificate verified" or names a revocation.
Reporting
The NAT files are built to AVETMISS 8.0 from the same record and checked by RTO Grow's own validator before anything is produced. A held list shows who is waiting on a USI, a release or an import note. "Who is in this build" previews every row with its NCVER code. You upload the ZIP at AVS yourself, then record the lodgement.
Where the person stays in charge
Every AI feature proposes and a person confirms. Every outcome is signed. NCVER lodgement is a human click on the AVS website, never a silent send. Compliance is your RTO's work, and the software supports it.
Book a demo and we will walk your own courses through every stage.
Frequently asked questions
Do I still need a separate LMS, SMS or compliance tool?
No. Course content, enrolments, marking, certificates, the evidence registry and NCVER reporting live in one system and read one student record. Card payments run through Stripe and email through AWS SES in Sydney. Both run as connections, so there is no extra product for you to manage.
Does it work on a phone?
The web app is responsive and the student surface is built mobile-first. The trainer portal has a bottom tab bar on a phone. There is no native app, and RTO Grow needs an internet connection.
Can a trainer mark a whole first-aid class at once?
Yes. From the class page, "Record class results" ticks who attended, marks them competent on the class's units and takes the signed declaration. It then moves straight to "Issue certificates and cards".
Do certificates issue themselves?
They can. Set the offering to "Issue automatically" and the certificate issues once the enrolment completes and the USI and profile gates pass. Set "Ask before issuing" and it waits in "Documents waiting".
Is RTO Grow ready for AVETMISS reporting?
RTO Grow builds the NAT files to AVETMISS 8.0 and validates them with its own validator. You lodge them on NCVER's AVS. We say "built to AVETMISS 8.0" and do not claim approval by NCVER.
What about employers and third parties?
A client organisation's coordinator gets a portal with "Overview", "Our people", "Certificates" and "Renewals due". A delivery partner gets a partner portal with the sections you allow in their agreement.
Does it send SMS reminders?
No. Reminders, confirmations and certificates go by email. No SMS provider is connected.