RTO software, explained.

RTO software is shorthand for the systems an Australian Registered Training Organisation uses to run its business and stay registered. In practice it covers four jobs: a student management system for learners and enrolments, a learning platform for online delivery and assessment, a public website that takes enrolments and payments, and the compliance and reporting layer that produces AVETMISS files and audit evidence. Some providers buy all four separately, others buy one platform that does all four.

A student management system (SMS) is the system of record for people: who is enrolled, in what, with which USI, at what price, with what outcome. A learning management system (LMS) is where training is delivered and assessed online: lessons, resources, submissions and marking. The SMS answers what a learner is entitled to, the LMS answers what they have actually done. Many RTOs run both and reconcile them by hand. In RTObase they are the same record, so lesson progress and assessment submissions sit on the enrolment itself.

Only if your student management system cannot produce AVETMISS files itself. AVETMISS is the national standard your training activity is reported in, and NCVER validates the NAT files you upload to AVS. Some providers export data and run it through a separate converter or hand it to a consultant. RTObase generates the Release 8.0 NAT file set directly from live records and validates it before you upload, and when AVS returns errors you can import its report and fix the source record. AVETMISS reporting is included on every plan.

Pricing is usually shaped one of a few ways: per active student or per enrolment, a flat monthly subscription, or a lower base price with the LMS, website, portals or reporting charged as separate modules. On top of that, many vendors charge a one-off implementation or migration fee and price support separately, so the shape of the pricing matters more than the headline number. RTObase is $0 a month on the Startup plan with a platform fee of 2% + 30c per enrolment, capped at $4 + GST, or $499 + GST a month flat on Business with no per-enrolment fees.

Ask whether it generates AVETMISS NAT files itself or expects you to use a converter, whether delivery evidence and the compliance record live in the same place, exactly what a migration moves and what you re-key, what your data export looks like if you leave, what is included versus charged as a module, and whether it suits the way you actually deliver, whether that is classroom cohorts, one-to-one bookings, fully online or international students. Ask to see each answer demonstrated rather than described.

No, though plenty of RTOs run them separately and it works. The friction shows up at the join: an enquiry or enrolment taken on the website has to reach the student record without being re-keyed, and course details have to stay identical in both places. RTObase includes a website builder with enrolment and payment on the same platform, and you can also embed enrolment into an existing site with one line of code if you would rather keep the site you have.

Ask before you sign, not after. In RTObase you can export student and enrolment records as CSV and generate AVETMISS NAT files at any time. Moving in works the same way: upload the NAT files from your current system and RTObase brings across organisation, student, program, unit, enrolment and training-activity data for you to review before you go live. Documents, notes, payment history and communications are not carried inside AVETMISS files, so plan how those move separately.

No. There is no requirement to use any particular product. The obligations are about the outcome: reporting training activity in the AVETMISS standard, keeping student records for the required retention period, and being able to show a regulator the evidence behind what you claim. Spreadsheets can satisfy that for a very small provider, but the effort grows faster than the enrolment count, and the failure usually shows up at a reporting deadline or an audit request.