Keeping PRISMS variations inside the 14-day window
How Academywise turns deferrals, cancellations and other reportable changes into a register with due dates set by the database and daily countdowns.
For CRICOS providers, many changes to an overseas student’s enrolment have to be reported in PRISMS within a set period. The rule itself is simple. The hard part is spotting every reportable event across a busy admissions and student services team, and reporting it on time.
This guide explains how Academywise handles that. Always confirm your reporting obligations against the Department of Education’s PRISMS guidance and the National Code.
Every variation gets a due date, set by the database
In Academywise, each reportable change is a row in the PRISMS variation register. It records the student, the variation type and the date of the event. Supported variation types include deferral, suspension, cancellation, non-commencement, early completion, course change and attendance breach.
The due date isn’t typed in by a person. A database trigger sets it to the event date plus 14 days whenever a variation is created or its event date changes. If someone submits a different due date, it is overwritten. That makes the deadline consistent across every screen, report and export.
Deferrals queue themselves
The variations most likely to be missed are the ones that start somewhere else. When staff record a deferral for an international student, Academywise automatically queues a pending PRISMS variation linked to that deferral. Nobody has to remember to open the register.
Staff can also log a variation manually from the student’s international details card. Attendance breaches can be created directly from the ESOS attendance warning workflow.
Countdowns your team can act on
The register shows a countdown badge for every pending variation:
- Green: more than three days remaining
- Amber: three days or fewer
- Red: overdue
When a variation has been reported, staff record the PRISMS confirmation number. A variation can also be marked not required (with notes), or reopened if circumstances change. The register exports to CSV for internal reporting.
Two automated reports reinforce this: a daily PRISMS deadlines email, and a Monday ESOS risk report, both sent to the recipients you choose.
What about the PRISMS API?
Academywise includes a PRISMS API connection that can create and retrieve CoEs and send supported variations, such as non-commencement, student cessation and provider transfer, directly to PRISMS. This connection is in development. It runs in test mode until the Department of Education issues access following its cyber security assessment. In test mode, results are never written to CoE numbers or variation status, so test runs cannot pollute compliance records.
Until live access is in place, the register remains the system of record and staff record each confirmation number by hand.
Checklist for your team
- Make sure every international student is marked as international on their application.
- Record deferrals in Academywise rather than in email or spreadsheets, so variations queue automatically.
- Check the register’s amber and red badges each morning, or rely on the daily deadlines email.
- Record the PRISMS confirmation number as soon as you’ve reported.
- Use not required with a note when a change isn’t reportable, so the register stays an accurate audit trail.
This guide describes how Academywise works and is general information only. It isn't legal or compliance advice. Always confirm your obligations with the official sources linked above.