By now, most RTO’s understand that the 2025 Standards have raised the bar for LMS evidence. ASQA is no longer satisfied with policy documents and sign-in sheets. They want system-level proof.
What’s less well documented is exactly what that looks like inside your LMS. The 2026 Annual Declaration on Compliance (ADC) window closes 31 March 2026. Here’s what to check, configure, and fix before then.
1. Authenticity of Assessment Evidence
ASQA auditors conducting a performance assessment will request access to your LMS. Specifically, they will look for evidence that the person who enrolled is the person who submitted the work.
What they’ll check:
- Is there a verified identity step at the point of submission, not just at enrolment?
- Is there a declaration (digital or otherwise) confirming the work is the student’s own?
- For AI-generated or plagiarised work: does the RTO have a detection mechanism, or just a policy?
What to configure:
If you’re using aXcelerate:
- Enable the USI verification integration under Settings > Compliance > USI. Ensure it’s triggered at both enrolment and when a result is recorded, not just one or the other.
- Use the eSignature field on your assessment submission forms to capture a digital declaration. This creates a timestamped, student-linked record ASQA can inspect.
If you’re using VETtrak:
- Check that your LMS is passing the student’s USI back to VETtrak on submission events via the API, not just at enrolment sync.
- Configure submission confirmation emails to include declaration language. These serve as a secondary audit trail.
For AI detection:
- Integrate with Turnitin or GPTZero at the LMS level so scans trigger automatically on upload, not manually. If your LMS doesn’t support direct integration, use Zapier or a webhook to pipe submissions through before they’re marked as received.
- Store the detection report against the submission record, not separately. Auditors want to see it alongside the work.
2. Evidence of Participation
Standard 1.1 requires proof that training was “structured and paced.” Login timestamps alone will not satisfy this. Auditors know students can log in and walk away.
What they’ll check:
- Can you produce a per-student record showing time spent on specific learning content?
- Is there a logical gate preventing assessment access before content completion?
- Do video or interactive resources show completion, not just access?
What to configure:
SCORM tracking:
- Ensure every SCORM module in your LMS is set to report back to your LMS database. Most LMS platforms capture this but don’t surface it in standard reports. Check your reporting module specifically.
- Pull a test report on a single student and confirm time-on-task data appears at the module level, not just the course level.
Gated progression:
- Set completion rules so that assessment activities have a prerequisite status of “completed” on the preceding content module, not just “viewed.”
- In Moodle-based systems, this is under Course Settings > Completion Tracking > Restrict Access. In custom LMS builds, this needs to be enforced server-side, not just in the UI.
Video completion:
- If you use Vimeo or YouTube embeds, these do not natively report back to your LMS. Replace or supplement with a platform that can push completion events to your LMS via xAPI or SCORM.
3. VET Data Streamlining (VDS)
The transition to VDS and STARS-based reporting means ASQA can now cross-reference your self-reported data against government records in near real-time. Manual data entry between your LMS and SMS is now a visible compliance risk.
What they’ll check:
- Do unit completion dates in your LMS match what’s been reported to NCVER/STARS?
- Are there unexplained gaps or lags between a student completing a unit and it appearing in your SMS?
- Is there evidence of a reconciliation process when data doesn’t match?
What to configure:
API sync between LMS and SMS:
- If you’re on aXcelerate, their REST API supports webhook triggers on unit completion events. Configure your LMS to POST to aXcelerate’s endpoint when a result is recorded. Don’t rely on nightly batch imports.
- For VETtrak, use their API to push unit completion status changes in real time. Map your LMS competency codes directly to your VETtrak unit codes to avoid translation errors during sync.
Reconciliation dashboards:
- Build a simple dashboard (even a scheduled SQL query exported to Google Sheets works) that surfaces any student records where LMS completion status does not match SMS outcome status. Run this weekly, not at audit time.
- Log every API call and its response. If a sync fails silently, you need to know. ASQA will find the discrepancy even if you didn’t.
Audit Readiness Checklist
| Feature | What ASQA Checks |
| USI Verification | Verified at enrolment and at result recording |
| Digital Declaration | Timestamped, student-linked submission declaration |
| AI/Plagiarism Detection | Automated scan stored against submission record |
| SCORM Time Tracking | Per-module session time visible in LMS reports |
| Gated Progression | Assessment access blocked until content completed |
| Video Completion | xAPI/SCORM events, not just embed views |
| Real-Time LMS to SMS Sync | API-driven, not batch import |
| Reconciliation Process | Regular check that LMS and SMS records match |
Don’t Leave It to the Last Week
The fixes above range from a configuration change taking 30 minutes to a development engagement taking several weeks. The API integrations and custom dashboards in particular need lead time.
At Greenhat, we work with Australian RTOs to audit-proof their LMS at a technical level, from configuring aXcelerate and VETtrak integrations to building custom compliance dashboards and xAPI tracking pipelines.