ASQA Complaint Email Arrives

SPEAKER_00 0:46

Episode forty two A Learner Complaint just reached ASQA Tuesday morning. Your CEO inbox has the usual overnight mix, newsletter, internal notifications, a couple of supplier emails, and one email from ASQA. The subject line is neutral, the content is not. The email notifies you that ASQA has received a formal complaint from a name learner regarding your RTO and requests a response within a defined timeframe. Specifics of the complaint are provided. Documentation you are required to supply is listed. The time frame is short. You now have a governance event on your hands. For some of you listening, that description will feel hypothetical. For others, maybe more of you than you expect, it will feel closer to home. Because the uncomfortable truth about learner complaints reaching the regulator is that most of them involve matters the RTO was aware of internally. Somewhere in the organization, someone knew this learner was unhappy. Someone knew there had been difficulties with the program. Someone had at some point had a conversation about whether to escalate. And then, for one reason or another, it wasn't pressing, it seemed manageable. The learner had gone quiet, it would blow over, it didn't get escalated. And now it has, not to you, to the regulator. The question this episode asks is not how you respond to the complaint. That's an operational question and you have a policy for it. The question is what the arrival of that email reveals about your governance system and what you should do in the first 72 hours to make sure the answer to that question is the right one. This episode is about what happens next. What should happen next specifically? Because the response to this email over the next 72 hours will reveal whether your RTO has been operating a governance system or running on goodwill and hoping nothing reached the regulator. Let me be clear about what I am and am not covering. I am not going to walk you through the complaints handling process itself. That's a compliance operational topic. What I am going to walk you through is what the receipt of that email actually tests. Because an ASQA referred complaint is not primarily a complaints test. It is a governance test. And most RTOs don't discover that until the moment they receive one. Here is the problem this episode addresses. Most complaints handling in the RTO sector is operationally competent. Policies

Complaints Test Governance Not Process

SPEAKER_00 3:41

exist, templates exist. There is a named complaints officer. Responses are typically sent within the required time frame. Resolution is documented. From an operational standpoint, the system works. From a governance standpoint, it is usually missing something important. And you only find out what is missing when the regulator asks a question that the operational system wasn't designed to answer. The question ASQA will ask is not did you receive the complaint and respond? That is operational. The question ASQA will ask is what did governance know? When did governance know it? And what decisions did governance make? Those are very different questions. And the artifacts most RTOs have available don't answer the second set. The complaint register shows the complaint was logged. It doesn't show whether it was escalated. The response letter shows an answer was sent. It doesn't show what internal deliberation led to that answer. The resolution record shows the matter was closed. It doesn't show what governance oversight existed over the closure. If governance couldn't see the complaint while it was live, or didn't review the handling while the decisions were being made, or doesn't have a record of oversight over the resolution, then from a regulatory standpoint, governance wasn't operating on this matter. The complaint was handled, not governed. And under the 2025 standards, that distinction matters more than it used to. Let me ground this in the outcome standards briefly. The outcome standards require governing persons to exercise active oversight of the RTO's handling of feedback, complaints, and appeals. The phrase active oversight is not decorative. It means governancer must be operating, not just present in structure. The regulator can now ask whether the governance system saw this complaint at the time it was being handled. Not afterwards, at the time. Under the pre 2025

2025 Standards Demand Active Oversight

SPEAKER_00 6:05

standards, the sufficient answer was often we resolve the complaint appropriately, here is the record. The evidence of resolution was the evidence of compliance. Under the 2025 standards, that is no longer sufficient. The regulator can now ask for evidence of governance oversight that is contemporaneous, formed at the time by the governance system as the matter was being handled. This is the distinction, the eight critical drivers framework calls the difference between evidence of activity and evidence of control. Most complaints files contain evidence of activity. What the regulator tests under continuous assurance is evidence of control. Let me walk you through what should happen in the first seventy two hours after that Tuesday morning email arrives. Not the complaints handling response. The governance response. Not the full group, but the name chair or equivalent within four hours of receiving the ASQA correspondence. This notification is documented. A brief factual note, timestamped with the nature of the regulatory correspondence, the learner reference, and the required response time frame. Why does this matter?

The 72 Hour Governance Response

SPEAKER_00 7:36

Because from this moment, governance is on notice that a regulatory matter is live. If it ever comes up later whether governance was aware, the record shows when. This is consolidated into a single, dated, named PAC. The PAC is not the response. The PAC is the source material from which a response will be built. And the PAC itself is evidence, evidence that the RTO's systems can produce a coherent learner record on demand. Most RTOs can do this, but it takes them days instead of hours. And the time it takes is diagnostic. If it takes three days to assemble a learner record, the system that holds those records isn't governance grade. Hour 24 to 48, internal review, the CEO, the compliance manager, and the delivery lead review the consolidated pack together. They ask the specific questions the regulator is likely to ask. What was the pre-enrollment information? Did it accurately represent the program? Was the support offered to this learner equivalent to what other learners received? Were there prior signals that support was insufficient? What was recorded about the learner's progression? What interventions, if any, were offered? Why were they sufficient or insufficient? This is a governance conversation. It should happen as a governance conversation, meaning it is minute. The decisions reached, the positions taken, and the basis for them are recorded. Not as a litigation defense, as the contemporaneous record of governance actually operating. Hour forty eight to seventy two. Response preparation and governance sign off. The response to ASQA is drafted. It is reviewed by governance, specifically by someone with formal oversight authority. It is signed off by that person. The sign off is documented. The response is submitted within the ASQA timeframe, and at that point the governance record for this matter shows a clear chain. Governance was notified within four hours. Evidence was consolidated within twenty four. Governance review happened within forty eight. All of this is contemporaneous, formed as it happened. If ASQA asks what governance oversight operated during this matter, that chain is the answer. And it is credible because it was built while the matter was live, not assembled after the response went out. That is what 72 hours of governance response looks like. And the only way it works in practice is if the system supporting it has been designed in advance. You cannot design a governance response under pressure. You can only activate one that already exists. One more thing about the 72 hours. There will be pressure from people inside your organization to do things faster. To get the response out quickly, to reassure the regulator. Pressure like that is usually well intentioned and usually wrong. The goal is not the fastest response. The goal is the most defensible response within the required time frame. If the required time frame is 14 days and your governance work takes five, you have nine days for the response to be drafted carefully, reviewed properly, and submitted with confidence. Short responses that arrive in 72 hours and contradict themselves

Fast Replies Can Backfire

SPEAKER_00 12:35

in the second week are worse than thorough responses that arrive on day 10. And the regulator can tell the difference. After the initial response is submitted, there is usually a second phase, the regulator's follow-up, additional questions, requests for specific records, occasionally a site visit or a video conference. The governance discipline for the second phase is the same discipline as the first. Each interaction is treated as continuous, documented, reviewed, signed off. If the engagement stretches over months, the governance record shows a continuous trail of oversight. Not a burst of activity at the start followed by operational handling afterwards. This matters because regulatory engagements can last longer than most RTOs expect. The initial complaint may be only the start. If the regulator opens a broader inquiry, your governance record will be tested across the full engagement, not just the first 72 hours. Which brings me to the backstory prevention. How you design this so you are not scrambling when the Tuesday morning email arrives. Three design moves work. The first is the escalation architecture. You need a predefined rule that specifies what kind of complaint must be escalated to governing persons within what time frame. Not every complaint, just the ones with potential governance implications. Regulatory matters, allegations of noncompliance, matters that could affect multiple learners, matters that indicate systemic failure rather than individual dissatisfaction. Your operational complaints handling

Design The System Before Crisis

SPEAKER_00 14:31

continues as normal. The escalation architecture sits above it. When a complaint meets the escalation criteria, it moves to governance attention within a defined time frame, typically 24 hours. The record of that escalation is automatic. It does not require anyone to decide whether to escalate. The rule decides. Most RTOs don't have this architecture. Escalation happens when the CEO thinks it should, which means that when a governance level complaint arrives, it may sit with the complaints officer for days before anyone more senior sees it. And during those days, governance was not operating on that matter. The second design move is the contemporaneous governance record. Every complaint that meets the escalation criteria generates an automatic governance record, a dated timestamp note in a governance log that ASQA could retrieve and read. This is not the complaint file, this is the governance record. It says, on this date, this matter came to governance attention. On that date, governance reviewed the proposed response. On another date, governance signed off. The record is spare, it doesn't contain deliberative content, it proves oversight happened. The governance log is separate from the complaints register for a specific reason. The complaints register holds operational data. What was raised, by whom, what the response was, when it was closed. The governance log holds oversight data. What governance saw when it saw it, what decisions it took. These are different records with different purposes. The regulator can ask to see both. They are testing different things with each. The third design move is the quarterly review. Once a quarter, governing persons review the full set of complaints that met the escalation threshold in the period, not individual resolutions patterns. Are complaints clustering around a particular trainer, a particular cohort, a particular program, a particular process step? Pattern detection is the governance layer that individual complaint handling cannot provide. What this quarterly review produces is not a report of complaints. It is a governance assessment of whether the RTO's complaints handling is itself functioning well. Are the escalation criteria catching the right matters? Are responses consistent? Is the resolution cycle time within expectation? Are there any patterns that suggest a systemic issue in the program, in the delivery, in support, in a specific relationship? This is the pattern detection layer. And it is what separates operational complaints handling from governance of complaints. The operational layer responds to individual matters. The governance layer reads the individual matters as a set and asks what they tell you about the organization. Three moves Escalation Architecture Contemporaneous Governance Rord Quarterly Pattern Review. None of these replace the operational complaints process. They sit above it. They turn complaints handling into a governance system. Let me also say a few words about self-reporting, because this is where many RTOs get uncomfortable. Under the 2025 standards, there are circumstances in which an RTO is obligated to notify the regulator of its own findings or events. Material changes. Significant breaches. Events that could affect learners at scale. These are listed in the standards and in the compliance requirements, and they carry specific timeframes. The uncomfortable question a learner complaint sometimes surfaces is whether the matter the learner complained about should have been self-reported by the RTO before the learner escalated it externally.

Self Reporting And Credibility

SPEAKER_00 19:01

That is not a rhetorical question. It is one ASQA will ask, and it is one your governance record will answer, one way or another. The RTOs that handle this well have a standing quarterly review that specifically asks, are there any matters in the current quarter's activity that should have triggered self-notification under our regulatory obligations? The review produces a written answer. If the answer is no, that answer is recorded. If the answer is yes, self-notification happens then, not after the regulator asks. This is one of the more difficult governance disciplines to install, because it requires the RTO to actively hunt for matters that require unflattering disclosure. But it is precisely the discipline that separates governance as a protective system from governance as a reactive one. And it is what the 2025 Standards Environment expects. Now, the specific mistakes I see RTOs make when this kind of scenario actually hits them. The first mistake is delegation of the regulatory correspondence itself. The compliance manager is handling the ASQA response. That is an operational answer to a governance question. The CEO owns regulatory correspondence. The compliance manager may draft it. The governance record has the CEO named and accountable. If the correspondence is signed by the compliance manager without governance visibility, you have just told the regulator that governance wasn't involved. The second mistake is treating the 72 hours as an operational exercise.

Mistakes That Signal Weak Oversight

SPEAKER_00 20:54

Pulling files, assembling responses, writing letters. All of that needs to happen, but it is not the whole response. If the CEO spends three days in the weeds of the complaint itself without stepping up and activating the governance response, the governance record at the end will show one person doing a lot of work and no system operating. The third mistake is believing you can reconstruct oversight after the fact. You cannot. That instinct produces a defensive response, one that emphasizes the RTO's compliance record, minimizes the learner's concerns, and treats the complaint as a misunderstanding to be resolved rather than a matter to be examined. That tone rarely helps. ASQA already has the complaint. Their job is to assess the RTO's handling. The response they find most credible is one that acknowledges the matter substantively, describes the governance oversight that operated, provides the evidence that supports the RTO's position. And where the RTO has identified something that could have been done better, says so. That last move is often the hardest. But the RTOs that handle regulatory correspondence well are the ones that can acknowledge a weakness in their own system while demonstrating that governance has already identified and addressed it. That tone is not capitulation. It is credibility. And under the 2025 standards, credibility with the regulator is itself a governance asset. This week I want you to do something specific, not in response to a current ASQA complaint. In preparation for the one that may arrive. Look at your current complaints policy. Find the clause that says what happens when a complaint is received. Now ask yourself, is there a predefined rule about which complaints go to governance attention and within what time frame? Not a policy statement that significant complaints are escalated. A rule with criteria with a time limit. If that rule doesn't exist, write one this week. Define three or four objective criteria, matters that have potential

Write Your Escalation Rule This Week

SPEAKER_00 24:07

regulatory implications, matters that allege noncompliance, matters affecting multiple learners, matters indicating systemic failure. Put a 24-hour escalation time on it. Make it automatic, meaning not requiring human judgment in the moment. Then check that your next complaint handling cycle runs the new rule, not the policy as written six years ago. The rule you just wrote. That is the architecture that would have been operating if an ASQA complaint had arrived this morning. The Evidence Gate framework, the design that separates activity from control, sits at the heart of Driver 8 of the 8 Critical Drivers Framework. If your RTO has robust complaints handling at the operational level but has never been tested on governance. Oversight of that handling, driver 8 is the chapter that installs the missing layer. The complaint-specific architecture I've walked through today draws on driver 3, student and client engagement, which covers the full life cycle from enrolment through completion, including the feedback and complaint systems that sit within that. Between drivers three and eight, you have the operational and governance layers you need. Eight Critical Drivers to RTO Success launches in June 2026. It's sold alongside the Governance Shift as the RTO governance bundle. The landing page is governance-shift.vivacity.com.au Next week episode forty three. A different kind of scenario. A validation just surfaced an assessment problem. A cohort that has already certified. A finding that has governance implications. What happens next and why the answer is rarely the one CEOs first want to give. If you have ever sat in a post validation meeting feeling the temperature in the room shift, that is the episode to tune in for.