Evidence management and human self-assurance for RTOs
Compliance Evidence for education providers
Build a practical, institution-specific record of how your team reviews requirements, explains its position, and connects each response to supporting evidence.
Compliance Evidence gives RTO teams a guided workspace for confirming applicability, reviewing requirements one at a time, recording the reasoning behind a response, and linking the operational records that support it.
How Compliance Evidence helps provider teams
- Start with an institution profile that shapes the requirement areas and context shown to your team.
- Review each applicable requirement individually and record Yes, Partially, No, Not applicable, or Unsure with a short explanation.
- Link or upload supporting evidence, then carry partial, negative, or uncertain responses into gaps, corrective actions, monitoring and review work.
Provider outcomes
- Give compliance, quality, academic and delivery teams one shared place to understand what has been reviewed and what still needs attention.
- Keep evidence tied to the requirement and the institution’s own reasoning instead of treating a generic document list as proof.
- Make the next action visible without presenting response coverage as a compliance score, audit outcome, certification or regulator determination.
How it works
- Confirm the institution context: Set the provider type, jurisdictions, delivery model, cohorts, funding, privacy context and third-party arrangements that shape the workspace. The map is a starting point for human review, not a final applicability decision.
- Review requirements one at a time: Open an applicable requirement, read its detail, self-assurance question, source context and applicability explanation, then record your institution’s current position and reasoning.
- Connect evidence and follow-up: Attach or link operational records that support the response. For Partially, No or Unsure responses, continue to Gaps & Actions, Calendar & Monitoring, or Audit & Review instead of waiting for every requirement to be completed.
Common questions about Compliance Evidence
What is compliance evidence?
Compliance evidence is the institution-specific record of reviewed requirements, human responses, reasoning, supporting records and follow-up work. AQF Verify provides a structured workspace for organising that record.
Does Compliance Evidence certify compliance or replace an audit?
No. The workspace is an advisory evidence-management and human self-assurance aid. It does not certify compliance, make legal or regulatory determinations, predict an audit outcome, or replace professional advice or the institution’s own governance.
What evidence should an RTO attach?
Use current operational records that show how the relevant control or outcome works in practice, such as approved records, registers, meeting minutes, sampled files, review logs, training records, monitoring outputs or links to controlled systems. Suggestions are illustrative and context-dependent; there is no one prescribed document for every requirement.
Do teams need to complete the whole Requirements Map first?
No. Teams can work one requirement or subsection at a time. After one response is saved, they can continue to another item or move immediately to gaps, actions, monitoring and review work.