Feature Article Topic: We’re Probably Compliant’ Isn’t a Strategy 

Feature Article: Three important quality checks your RTO should make before implementing assessment tools

Most RTOs are probably compliant with many of their obligations most of the time.

The problem is that “probably” is not assurance. 

Statements such as “we haven’t had any complaints”, “our trainers know what they’re doing”, “we’ve always done it this way” or “ASQA looked at this previously and it was fine” may all be true. 

None of them, on their own, demonstrate that the underlying system is currently working as intended.

Belief is not evidence 

Compliance risk often develops quietly in the processes that drift, when key staff change or when assessment tools are amended.  

Likewise, training products are updated, delivery models evolve and third-party arrangements increase. Without deliberate review and recalibration, RTOs can find that controls which were once fit for purpose gradually weaken, creating gaps between documented systems and actual practice. 

If an RTO is not systematically looking at its own performance, it can become increasingly confident in a position that has never actually been tested. 

An absence of identified problems is not necessarily evidence that no problems exist. 

Sometimes it simply means nobody has looked closely enough.

From information to assurance 

Most RTOs already hold substantial amounts of information: 

  • internal audit findings 
  • validation outcomes 
  • complaints and feedback 
  • student file reviews 
  • assessment data 
  • trainer and assessor records 
  • continuous improvement registers 
  • third-party monitoring results. 

But collecting information is not the same as analysing it. 

A mature self-assurance system asks: What is this evidence telling us about whether our controls are actually working? 

That requires more than completing compliance activities.  

It requires connecting findings, identifying patterns, testing assumptions and escalating material risks. 

A more useful approach is: 

  1. Identify 
  1. Test 
  1. Analyse 
  1. Document 
  1. Act 
  1. Monitor 

This is how assurance is built in practice. You identify the risk or control, test what is actually happening, analyse the evidence, document the position, take proportionate action where needed, and continue monitoring to confirm the control remains effective. 

The leadership question 

RTO leaders cannot reasonably be expected to always hold absolute certainty across every compliance obligation.  

Effective governance is instead about having sufficient visibility, reliable evidence and appropriate controls to understand where risk exists and when further scrutiny or action is required. 

They do need reasonable confidence that the organisation has mechanisms to identify when practice is drifting, when controls are weakening and when intervention is required. 

That means the better governance question is not simply: 

“Are we compliant?” but “What evidence gives us confidence that our compliance controls are working today?” 

That question changes the conversation. 

It moves compliance away from reassurance and towards evidence, judgement and accountability and that is where meaningful self-assurance begins.

Other feature articles: 

From Compliance Activity to Risk Control 

Closing The Assurance Loop – What Happens After You Find A Problem? 

Evidence Is Not Assurance and Why Having the Documents Is No Longer Enough 

Can You Trust Your Own Compliance Data? 

References:  

VET Quality Framework  

National Vocational Education and Training Regulator (Outcome Standards for Registered Training Organisations) Instrument 2025  

AQSQ Practice Guide Assessment 

Leadership and Accountability Practice Guide 

Risk Management Practice Guide 

Continuous Improvement Practice Guide