What Campus does
Campus is a student management system and learning management system for Australian registered training organisations. It is built around a data-driven AVETMISS and NAT compliance engine rather than rules hardcoded into the software. If you are looking for RTO software, a VET student management system, an LMS for training providers or an AVETMISS reporting tool, Campus is the Cohiva product for that.
Campus helps RTOs report training activity to NCVER using AVETMISS-compliant NAT files, and supports the day-to-day work of enrolment, assessment and certification. The two halves, the student management system and the LMS, sit on one record of the student, so the enrolment, the learning and the reporting all draw on the same data.
Explore Campus for the full product, or read on for how it fits an RTO.
The category Campus wins
The RTO software category has a particular demand that general education tools do not meet: AVETMISS. Australian training providers have to report training activity to NCVER in a precise format, and the standard changes. A product that hardcodes those rules ages badly and leaves the provider patching around it.
Campus is built for that reality. It is RTO and VET student management software with a data-driven compliance engine, so the AVETMISS and NAT logic is configured as data rather than baked into the code. For a compliance manager preparing for audit, that is the difference between software that helps you comply and software that you have to work around.
Key capabilities
- Student management. Manage enrolments, units, assessment outcomes and certification on one student record, from first enquiry to completion.
- Learning management. Deliver and track learning alongside the student record, so progress and results stay connected to enrolment and reporting.
- AVETMISS and NAT reporting. Produce AVETMISS-compliant NAT files to report training activity to NCVER, with a compliance engine driven by data so it can keep pace with the standard.
- CRICOS and funded support. Support CRICOS and government-funded RTOs, which carry their own reporting and compliance requirements.
- Audit-ready records. Keep enrolment, assessment and reporting records structured, which supports your obligations and helps you comply when an audit comes.
Built for the Australian VET sector
Campus supports CRICOS and government-funded RTOs, which face specific reporting and compliance requirements on top of the AVETMISS standard. The compliance engine is data-driven so it can keep pace with changes to the standard, which matters in a sector where the reporting rules are revised and providers carry the obligation to report correctly.
For an RTO, the value is in not having to choose between an education platform that does not understand AVETMISS and a reporting tool that does not run teaching. Campus does both on one record, which keeps the data that feeds a NAT submission consistent with the enrolment and assessment data the provider works from every day.
Why a data-driven engine matters
The AVETMISS standard is revised, and the NAT file format carries strict rules about what each field holds and how records relate. When that logic is hardcoded, every change to the standard becomes a software change, and providers wait on a release to stay compliant. In the meantime, the temptation is to patch around the system, which is exactly where reporting errors creep in.
A data-driven engine configures the AVETMISS and NAT rules as data, so the validation and the file structure can keep pace with the standard without rebuilding the product. For a compliance manager, this means the system that produces a NAT submission reflects the current rules, and the records that feed it, enrolments, units and assessment outcomes, are the same records the RTO works from day to day. Consistent source data is what makes a submission defensible, and what helps a provider comply rather than reconcile two versions of the truth before each reporting period.
This is the practical reason RTOs look for purpose-built software rather than a general education platform: the reporting obligation is specific, ongoing, and carries real consequences if it is wrong.
Part of the Cohiva suite
Campus shares one identity and one control plane with the rest of the Cohiva products, so an RTO that also runs facilities, finance or HR can work across them on one platform. A provider that delivers training in its own venues, employs shift-based trainers, or signs training agreements can join Campus up with Complex, Culture and Sign on the same login and data layer.
One record from enquiry to certificate
A student's journey through an RTO touches many parts of the business: the first enquiry, the enrolment, the units of competency, the assessment outcomes, the certificate, and the reporting that follows. When those live in separate systems, the data has to be re-entered or reconciled at each step, and every re-entry is a chance for the record that feeds a NAT submission to drift from the record the trainer works with.
Campus keeps the student on one record across that whole journey. The enrolment, the learning, the assessment results and the reporting draw on the same data, so the figures reported to NCVER match the day-to-day record of what the student actually did. For a provider, a single consistent record is both less administrative work and a stronger position at audit time, because the source of truth is one place rather than several.
Getting started
Campus is part of the Cohiva platform, designed to meet the reporting and compliance demands of the Australian VET sector. To see capabilities and a closer look at how Campus handles AVETMISS and student management, visit campus.cohiva.app.