Cold Open And The Big Bet

SPEAKER_00 0:46

Episode thirty seven What Public VET gets right about governance timing. I want you to hold two RTOs in your head while I talk today. The first is a large public training provider, multiple campuses, a staff list in the hundreds, delivering dozens of qualifications in different regions to different industries, with different employer partners at every site. Governance meetings, quarterly reviews, a compliance function that spans several full-time roles. It looks from the outside like a bureaucracy. The second is a small private RTO, single campus, fifteen staff, three qualifications on scope. One CEO who knows every trainer by name and every learner in the current cohort. Quarterly reviews happen around the same table. The compliance function is the CEO. It looks from the outside like agility. If you had to put money on which one of these two is more likely to miss an early signal of governance drift, which one is more likely to learn late that something is going wrong? Most people would bet on the large one. Most people would be wrong. The best of our public training providers catch drift earlier than almost anyone else in the sector. Not because they have more resources, not because they're structurally superior, because at some point in their history they ran into a wall that smaller RTOs can avoid for years, and they had to design their way through it. They had to systemize. And in this episode, I want to show you exactly what that means. Why it matters more than ever under the 2025 standards and what you can take from their design choices, even if your RTO will never operate at that scale. Because the principle at the center of this episode is not about size. It's about what happens when governance can no longer run on proximity. The wall the public providers hit years ago is a wall every growing RTO hits eventually. You pass a certain scale, and the governance that used to work, the quiet conversations, the hallway check-ins, the Friday debrief stops being sufficient. And because the wall doesn't announce itself, most RTOs only notice they've crossed it when something goes wrong that they should have seen coming. The benchmark public providers worked out how to see it coming. That's the subject of this episode. The problem. Here is the problem this episode addresses. When an RTO is small, governance travels in proximity. You see the trainers, you hear the conversations in the staff room. You notice when an assessment tool has drifted because someone mentions it at lunch. You know when a cohort is struggling because the trainer tells you on Friday. That proximity feels like control. But it isn't. It's informal coordination, and that is a different thing entirely. Informal coordination works until it doesn't, and the moment it stops working is rarely the moment anyone notices. What happens is this the RTO

The Governance Visibility Gap

SPEAKER_00 4:19

grows by one campus, or one new scope edition, or one new workforce program, or one new employer partnership. Nothing dramatic. A quiet expansion. Something the leadership team handled well, by the way. The operational pieces all got stood up properly. But suddenly the people at the edge of the organization aren't in your line of sight anymore. The cohort you used to hear about on Friday is now managed by someone you see once a month. The trainer who used to flag a drifting assessment tool is now reporting to a coordinator who has five other trainers to manage. The admin who used to double check every enrollment is now one of three admins, each covering a different intake. The governance system that held together through proximity is now depending on people. And people, no matter how competent, are not a governance system. This is what I call in the book the governance visibility gap. And it doesn't only exist in big organizations, it exists in small ones that are growing. It forms the moment your governance stops operating on proximity and starts operating on reports. If those reports aren't designed properly, if they don't give you comparable signals across your sites, your cohorts, your trainers, then what you will receive at governance level is not visibility. It is reassurance. Reassurance looks like stability. But stability is not the same as governability. This is exactly where the benchmark public providers have the advantage. Not because they invented something smaller RTOs can't access, because they hit the wall first. They could never rely on proximity. They had to design visibility from day one, and the best of them have. What the frameworks say. Let me ground this in the 2025 standards for a moment, because it's the standards that make this episode urgent, not just interesting. The outcome standards don't tell you how to organize your campuses. They don't prescribe how many layers of management you should have. They don't specify reporting templates. What they do tell you, and this is the shift that makes the public provider's approach so relevant, is that governing persons must be able to assure themselves on an ongoing basis that the organization is meeting its obligations. Ongoing, continuous, not at audit, not at the board meeting, not at annual

Why 2025 Standards Raise The Bar

SPEAKER_00 7:08

review. Continuous assurance is the phrase that frames the whole regulatory environment we are now operating in. And continuous assurance is mechanical. It requires something operational, a system that produces a governance signal from the edges of the organization, at a cadence fast enough for governing persons to act while options still exist. You cannot assure yourself continuously if your governance receives calm averages from the center while drift forms at the edge. You cannot assure yourself continuously if your campuses or your cohorts or your trainers are measuring in progress differently. So progression looks stable while backlogs quietly build. You cannot assure yourself continuously if your assessment integrity looks the same in aggregate because the underlying workflow points aren't comparable. This is why systemization is not a big organization problem. It is a 2025 standards problem, and it applies to any RTO that is measuring anything across more than one trainer. More than one cohort, more than one site. In the governance shift, I describe this as the first stabilizer at scale. Comparability. Before escalation, before thresholds, before dashboards, before any of the sophisticated governance architecture you might want to build, the first question is whether your data compares like with like. If it doesn't, everything downstream is unreliable. And here's the thing that makes this specifically a 2025 standards issue, not just a general governance issue. Under the pre-2025 standards, if you had evidence assembled for audit and you could demonstrate your compliance at the point of examination, you had largely met the test. Compliance was effectively episodic. The regulator checked in, you presented evidence, and the system moved on until the next check. That is not how the 2025 standards work. The 2025 standards formalize a shift from episodic assurance to continuous assurance, which means that compliance is no longer tested at a moment in time. It is tested at every moment. The question the regulator can now ask is not just were you compliant when we examined you? It is were you compliant when the decision was made and where is the evidence formed at the time? That second question is the one that exposes organizations running on inconsistent definitions. Because when the evidence is assembled later, when the record is reconstructed in the week before audit, the inconsistency shows. The timestamps don't line up. The decisions don't trace cleanly to data. And the story that sounded coherent inside the organization starts to sound less coherent to someone sitting on the outside. The benchmark public providers solved this long before it was legislated. They had to, because their scale made the alternative impossible. What the 2025 standards have done is make their solution the baseline expectation for the entire sector. The public VET pattern. So what have the benchmark public providers actually done? I want to walk you through the pattern because it is a pattern consistent across the best of them, regardless of whether they sit in Queensland, Victoria, New South Wales, or Western Australia. Five moves in this order. The first move is stabilizing definitions. In progress means one thing across every campus, across every qualification, across every cohort. Not a range of local interpretations. One definition. Documented. Governed. Reviewed annually at a fixed cadence, with changes

Comparability Before Dashboards

SPEAKER_00 11:37

requiring formal sign off. It sounds mundane. It is the most important governance move a scaled organization can make. Because until in progress means the same thing at the Brisbane campus and the Cairns campus, you cannot compare them. And until you can compare them, variance is invisible. Here's what this looks like in practice. I worked with a multi-site provider several years ago where the definitions audit ran into something unexpected. At one campus, in progress meant a learner had submitted at least one assessment task and was within the delivery window. At another campus, in progress, meant the learner had logged in to the LMS at least once in the current month. Same term. Completely different population of learners. The difference had been invisible for two years. It only became visible when somebody asked the question. The second move is stabilizing workflow points. Where in the delivery lifecycle is the data captured? At enrollment, at first assessment upload, at trainer sign off, at employer sign off, at the close of the competency? These decisions seem operational. They are governance decisions. Because if one campus records evidence of timeliness at trainer sign off and another campus records it at employer sign off, then the timeliness data at system level is literally not measuring the same thing. The aggregator dashboard will look stable. The underlying measurement is unstable. The third move is stabilizing escalation triggers. When a cohort moves a certain number of percentage points below tolerance, escalation isn't optional. It's automatic. It's triggered by the data, not by a human decision to report it up the chain. This is the move that removes ego and politics from escalation. Because in my experience, most of the time that bad news doesn't reach governing persons, the reason isn't technical. It's human. Someone in the middle of the organization made a judgment about whether something was worth escalating. And they got it wrong. Not maliciously, just cautiously. Systemized escalation removes that judgment from individual hands. The trigger is the variance. The response is the process. The fourth move is stabilizing rhythm. This is the one most RTOs miss. Benchmark providers don't review things when an issue arises. They review things on a rhythm, whether or not an issue has arisen. Monthly cohort calibration, quarterly scope review, biannual evidence sampling, annual definitions audit. The rhythm is what makes the governance system independent of anyone's attention span or memory. It runs

Five Systemisation Moves Public VET Uses

SPEAKER_00 14:58

because it is scheduled, not because someone noticed it was time. And the fifth move, and this is the one that separates the benchmark providers from the merely large, they treat evidence as a byproduct of governance, not as a task to complete. When definitions are stable, workflow points are stable. Escalations are triggered automatically and the rhythm is running. The evidence of what was seen and decided exists as part of the record. It doesn't need to be assembled the week before an audit. It is already there, timestamped, traceable, attached to the decisions that were made at the time they were made. This is the design that allows continuous assurance to actually operate. Five moves, definitions, workflow points, escalation triggers, rhythm, evidence as byproduct. Not one of these requires a large organization. Every one of them can be installed in an RTO with fifteen staff, three qualifications, and one campus. What they require is the design decision, the decision to stop running governance on proximity and start running it on system. Illustrative scenario. Multiple campuses. Each month, governing persons receive a stable system view. Enrollments are steady. Completions are sitting within tolerance. Validation is on track. The governance pack looks controlled. Underneath that, at individual campuses, divergence is forming. At one site, a trainer is recording in progress differently, more generously. So learners who are

Definitions Drift Example

SPEAKER_00 17:07

sitting on incomplete assessments for several weeks still appear to be progressing. The backlog builds, but the monthly data doesn't show it. At another site, a different workflow point is being used to record employer sign-off. Sign-off is captured earlier in the process at this campus than at any other. So the system view of evidence timeliness looks stronger than the reality. At a third site, a local coordinator has quietly extended the tolerance window for a particular assessment task because the employer partner was running behind on workplace opportunities. A reasonable local decision. But the monthly report still shows the cohort tracking to the original timeline. These are not compliance failures. Nobody is doing anything dishonest. They are differences in definition. Local adaptations that seemed reasonable at the time. But because the definitions are inconsistent, the system view is cross-campus comparable only on paper. Underneath, the campuses are measuring different things and being reported as if they were the same. Governance receives activity, not variance, not location, not signal. Now the turning point in the scenario. Leadership for an unrelated reason decides to run a cross-campus calibration. They sample the same cohort definition across every site, using the same workflow point and the same evidence requirement. Differences become visible immediately. What had appeared as stable performance turns out to have been, in significant part, a measurement artifact. The variance was always there. It just wasn't locatable. Once definitions are aligned, the outliers can be addressed before anyone outside the organization needs to. And here's the part worth sitting with. After the calibration, the aggregated system view looks slightly worse than it did before. A couple of metrics that were sitting inside tolerance are now visibly outside tolerance because the previous numbers were smoothed by inconsistent definitions. That is not bad news. That is the first true signal the organization has had. In fact, I'd go further. The moment the calibrated numbers look slightly worse is the moment governance actually begins. Because everything before that point was based on data that could not support a real decision. The leadership team thought they were governing, but they were interpreting noise as signal. Now they have signal. Noisy at first, but signal. And once you have signal, a number of things become possible that weren't possible before. You can locate variants by campus, by cohort, by trainer. You can build thresholds that actually mean something. You can trigger escalation on real movement rather than on rumor. You can accumulate evidence as part of the governance process rather than as a retrospective assembly job. Calibration in this scenario functions as a control mechanism, not as an audit, not as an investigation. As ordinary governance done properly. This is the pattern. At scale, the first governance asset is a shared

Escalation Triggers And Review Rhythm

SPEAKER_00 20:48

definition of reality. Everything else is downstream. What this means for smaller RTOs. Now I know what some of you are thinking. Angela, my RTO is not a multi-campus public provider. I have 15 staff, three qualifications, two trainers. Does this episode even apply to me? Yes, more than you think. Because the principle is not about size, it's about comparison. If you have more than one trainer, you need comparable measures. If you have more than one cohort, you need comparable measures. If you deliver the same qualification in two workplaces or to two cohorts or across two intakes, you need comparable measures. Otherwise you're running a small version of the same structural problem that public providers faced at scale. Your governing persons see stable aggregates while drift forms somewhere you're not looking. Four practical moves work in smaller RTOs. I'll walk you through them. One, document your definitions progression, competency, evidence timeliness, assessment sufficiency. Pick the three to five measures your governance actually pays attention to and write down exactly what each of them means. Not a policy statement, a working definition, something a new staff member could apply on day one. Two, check that your data is actually comparing like with like. Before you spend another month looking at your dashboard, ask, is this metric being captured the same way, at the same workflow point, by every trainer and every admin across every intake? If the honest answer is probably not, or Or I'm not sure, then your dashboard is not yet a governance instrument. It's a reassurance instrument. And those are not the same thing. Three, build one automatic escalation trigger. Just one to start. Pick the variance that would matter most if it formed at the edge of your organization. Late submissions, assessor backlog, completion rate drop, complaint volume, withdrawal rate, and build a trigger so that when the number crosses a threshold, escalation happens without anyone needing to decide whether it should. Four, put the calibration on a rhythm. Whatever you decide to measure, sample it on a regular cycle, every month, every quarter, pick a cadence that suits your scale, and sample it across cohorts, across trainers, across intakes. Not when something looks wrong. On a rhythm, whether or not anything looks wrong. These four moves will not make you a benchmark public provider. They will start your RTO on the same design path. And the design path is the one that matters.

Evidence As A Governance Byproduct

SPEAKER_00 24:04

Let me give you an example of how small that first calibration effort can be. A CEO of a small private RTO I spoke with recently ran their first definitions audit over a single afternoon. Two trainers, one admin, the CEO, and a whiteboard. They listed out the five metrics they report to their governing persons each month. They went around the room and asked each person how they captured each one. By the end of the afternoon they had identified three metrics that were being captured inconsistently, not because anyone was doing anything wrong, but because the definitions had never been written down. Three hours of work, a significant correction to what their governance pack actually meant. That is the kind of intervention that's available to every RTO in this country, regardless of scale. And it is precisely the kind of thing public providers have done at scale, systematically for decades. Common mistakes. Three mistakes I see RTOs make when they try to apply this. The first is jumping to dashboards before definitions. I cannot tell you how many RTOs I've sat with who have invested in a beautifully designed compliance dashboard. Automated pulls from three different systems, colour coded indicators, a monthly refresh cadence, and whose underlying data is measuring inconsistent things. The dashboard looks sophisticated. The governance it supports is an illusion. Definitions come first, always. The second mistake is underestimating the political work. Standardizing definitions across campuses, trainers, cohorts or intakes means overriding local adaptations that people have been using for months, sometimes years. Those adaptations exist because someone made them work locally and they are now attached to people's professional identity. The governance move is clear. The human move is harder. If you are going to systemize, you need to do it with explicit authority from governing persons. A clear rationale and a transition pathway, not by sending an email and hoping people comply. The third mistake is treating systemization as a project. The benchmark

Scenario Where Stability Is Fake

SPEAKER_00 26:41

public providers don't systemize once and move on. They review their definitions annually. They recalibrate on a rhythm. They treat systemization as a discipline, an ongoing practice, not a one-off piece of work that gets a project plan and a completion date. If your plan for systemization has a start date and an end date, you haven't built systemization. You've built a project. Those two things do not deliver the same governance outcome. Practical steps this week. So here's what I'd like you to do this week. Take one measure. One. The one your governance relies on most heavily. Completion rate maybe. Or assessment timeliness, or withdrawal rate. Walk it back through your organization. Ask every trainer, every admin, every person who touches the data. How are you capturing this? At what point in the life cycle? Using what definition? You will be surprised by the answers. The gap between what you think you're measuring and what your organization is actually measuring is the first thing you need to see clearly before you design anything else. That is your week one project. It will take two or three hours. It will change how you look at every report you receive for the rest of the year. And once you've done it for one measure, you'll want to do it for two, then three, then a full set. The rhythm builds from there. Most of the organizations I work with who now run strong governance cadences didn't start with a big plan. They started with one measure, one afternoon, one corrected definition, the rest followed. The move isn't dramatic. The move is specific. One measure, one afternoon, this week. If what I've talked about today lands with you, if you can already name the handful of measures in your RTO where the definitions might not be quite what you thought they were, then the chapter this episode draws from will give you a great deal more. It sits in a section of the governance shift called the benchmarks, where I take five Australian training organizations and break each of them down against the same governance tests. Public providers, specialist RTOs, small private providers, different models, same governance mechanism, variants visible early, escalation non-negotiable, evidence as a byproduct of ordinary work. The governance shift launches in june 2026. It sold alongside the eight critical drivers to RTO success as the RTO governance bundle. The landing page is governance-shift.com.au Next week I'm continuing the benchmarks series. Episode thirty eight The Power of Specialization. Why narrow scope governs better than broad scope and why some of the most stable RTOs in the country are also the smallest. You'll want that one if your scope has been quietly expanding. Welcome. Reusable. Same opening every episode. Welcome to the RTO Superhero Podcast. I'm Angela Connell Richards, founder of Vivacity Coaching and Consulting, and this is the podcast for leaders of Australian registered training organizations who have decided, quietly, deliberately, that compliance is not a burden to survive. It's an operating capability to build. Every week we go into the design work that separates stable RTOs from fragile ones, governance under the 2025 standards, audit practice that isn't audit theater. The specific choices that let some providers stay calm through regulatory scrutiny while others scramble. This podcast draws on what I see working across more than 400 RTOs. Practical. If you're a CEO, a governing person, a compliance manager, or a quality lead, this is built for you. Let's get into today's episode. Episode open. Episode specific. Episode thirty seven. What public VET gets right about at governance timing. I want you to hold two RTOs in your head while I talk today. The first is a large public training provider, multiple campuses, a staff list in the hundreds, delivering dozens of qualifications in different regions to different industries with different employer partners at every site. Governance meetings, quarterly reviews, a compliance function that spans several full-time roles. It looks from the outside like a bureaucracy. The second is a small private RTO. Single campus, 15

Show Opening And Audience Promise

SPEAKER_00 32:12

staff, three qualifications on scope. One CEO who knows every trainer by name and every learner in the current cohort. Quarterly reviews happen around the same table. The compliance function is the CEO. It looks from the outside like agility. If you had to put money on which one of these two is more likely to miss an early signal of governance drift, which one is more likely to learn late that something is going wrong? Most people would bet on the large one. Most people would be wrong. The best of our public training providers catch drift earlier than almost anyone else in the sector. Not because they have more resources, not because they're structurally superior. Because at some point in their history they ran into a wall that smaller RTOs can avoid for years, and they had to design their way through it. They had to systemize. And in this episode, I want to show you exactly what that means, why it matters more than ever under the 2025 standards, and what you can take from their design choices, even if your RTO will never operate at that scale. Because the principle at the center of this episode is not about size, it's about what happens when governance can no longer run on proximity. The wall the public providers hit years ago is a wall every growing RTO hits eventually. You pass a certain scale and the governance that used to work, the quiet conversations, the hallway check-ins, the Friday debrief stops being sufficient. And because the wall doesn't announce itself, most RTOs only notice they've crossed it when something goes wrong that they should have seen coming. The benchmark public providers worked out how to see it coming. That's the subject of this episode. The problem here is the problem this episode addresses. When an RTO is small, governance travels in proximity. You see the trainers, you hear the conversations in the staff room. You notice when an assessment tool has drifted because someone mentions it at lunch. You know when a cohort is struggling because the trainer tells you on Friday. That proximity feels like control. But it isn't. It's informal coordination. And that is a different thing entirely. Informal coordination works until it doesn't. And the moment it stops working is rarely the moment anyone notices. What happens is this the RTO grows by one campus, or one new scope edition, or one new workforce program, or one new employer partnership. Nothing dramatic. A quiet expansion. Something the leadership team handled well, by the way. The operational pieces all got stood up properly. But suddenly, the people at the edge of the organization aren't in your line of sight anymore. The cohort you used to hear about on Friday is now managed by someone you see once a month. The trainer who used to flag a drifting assessment tool is now reporting to a coordinator

Proximity Governance Breaks At Scale

SPEAKER_00 35:34

who has five other trainers to manage. The admin who used to double check every enrollment is now one of three admins, each covering a different intake. The governance system that held together through proximity is now depending on people. And people, no matter how competent, are not a governance system. This is what I call in the book the governance visibility gap. And it doesn't only exist in big organizations. It exists in small ones that are growing. It forms the moment your governance stops operating on proximity and starts operating on reports. If those reports aren't designed properly, if they don't give you comparable signals across your sites, your cohorts, your trainers, then what you will receive at governance level is not visibility. It is reassurance. Reassurance looks like stability. But stability is not the same as governability. This is exactly where the benchmark public providers have the advantage. Not because they invented something smaller RTOs can't access, because they hit the wall first. They could never rely on proximity. They had to design visibility from day one. And the best of them have. What the framework say. Let me ground this in the 2025 standards for a moment. Because it's the standards that make this episode urgent, not just interesting. The outcome standards don't tell you how to organize your campuses. They don't prescribe how many layers of management you should have. They don't specify reporting templates. What they do tell you, and this is the shift that makes the public provider's approach so relevant, is that governing persons must be able to assure themselves on an ongoing basis that the organization is meeting its obligations. Ongoing, continuous, not at audit. Not at the board meeting. Not at annual review. Continuous assurance is the phrase that frames the whole regulatory environment

Continuous Assurance Needs Mechanics

SPEAKER_00 37:50

we're now operating in. And continuous assurance is mechanical. It requires something operational, a system that produces a governance signal from the edges of the organization, at a cadence fast enough for governing persons to act while options still exist. You cannot assure yourself continuously if your governance receives calm averages from the center while drift forms at the edge. You cannot assure yourself continuously if your campuses or your cohorts or your trainers are measuring in progress differently. So progression looks stable while backlogs quietly build. You cannot assure yourself continuously if your assessment integrity looks the same in aggregate because the underlying workflow points aren't comparable. This is why systemization is not a big organization problem. It is a 2025 standards problem, and it applies to any RTO that is measuring anything across more than one trainer, more than one cohort, more than one site. In the governance shift, I describe this as the first stabilizer at scale. Comparability. Before escalation, before thresholds, before dashboards, before any of the sophisticated governance architecture you might want to build, the first question is whether your data compares like with like. If it doesn't, everything downstream is unreliable. And here's the thing that makes this specifically a 2025 standards issue, not just a general governance issue. Under the pre-2025 standards, if you had evidence assembled for audit and you could demonstrate your compliance at the point of examination, you had largely met the test. Compliance was effectively episodic. The regulator checked in, you presented evidence, and the system moved on until the next check. That is not how the 2025 standards work. The 2025 standards formalize a shift from episodic assurance to continuous assurance, which means that compliance is no longer tested at a moment in time. It is tested at every moment. The question the regulator can now ask is not just were you compliant when we examined you, it is were you compliant when the decision was made? And where is the evidence formed at the time? That second question is the one that exposes organizations running on inconsistent definitions. Because when the evidence is assembled later, when the record is reconstructed in the week before audit, the inconsistency shows. The timestamps don't line up, the decisions don't trace cleanly to data. And the story that sounded coherent inside the organization starts to sound less coherent to someone sitting on the outside. The benchmark public providers solved this long before it was legislated. They had to, because their scale made the alternative impossible. What the 2025 standards have done is make their solution the baseline expectation for the entire sector. The public VET pattern. So what have the benchmark public providers actually done? I want to walk you through the pattern because it is a pattern, consistent across the best of them, regardless of whether they sit in Queensland, Victoria, New South Wales, or Western Australia. Five moves in this order. The first move is stabilizing definitions. In progress means one thing across every campus, across every qualification, across every cohort, not a range of local interpretations. One definition. Documented. Governed. Reviewed annually at a fixed cadence with changes requiring formal sign-off. It sounds mundane.

The Five Moves Revisited

SPEAKER_00 42:06

It is the most important governance move a scaled organization can make. Because until in progress means the same thing at the Brisbane campus and the Cairns campus, you cannot compare them. And until you can compare them, variance is invisible. Here's what this looks like in practice. I worked with a multi-site provider several years ago where the definitions audit ran into something unexpected. At one campus, in progress meant a learner had submitted at least one assessment task and was within the delivery window. At another campus, in progress meant the learner had logged in to the LMS at least once in the current month. Same term. Completely different population of learners. The difference had been invisible for two years. It only became visible when somebody asked the question. The second move is stabilizing workflow points. Where in the delivery lifecycle is the data captured? At enrollment, at first assessment upload, at trainer sign-off, at employer sign off, at the close of the competency. These decisions seem operational. They are governance decisions. Because if one campus records evidence of timeliness at trainer sign-off and another campus records it at employer sign-off, then the timeliness data at system level is literally not measuring the same thing. The aggregated dashboard will look stable. The underlying measurement is unstable. The third move is stabilizing escalation triggers. When a cohort moves a certain number of percentage points below tolerance, escalation isn't optional. It's automatic. It's triggered by the data, not by a human decision to report it up the chain. This is the move that removes ego and politics from escalation. Because in my experience, most of the time that bad news doesn't reach governing persons. The reason isn't technical, it's human. Someone in the middle of the organization made a judgment about whether something was worth escalating. And they got it wrong. Not maliciously, just cautiously. Systemized escalation removes that judgment from individual hands. The trigger is the variance, the response is the process. The fourth move is stabilizing rhythm. This is the one most RTOs miss. Benchmark providers don't review things when an issue arises. They review things on a rhythm, whether or not an issue has arisen. Monthly cohort calibration. Quarterly scope review. Biannual Evidence Sampling. Annual Definitions Audit. The rhythm is what makes the governance system independent of anyone's attention span or memory. It runs because it is scheduled, not because someone noticed it was time. And the fifth move, and this is the one that separates the benchmark providers from the merely large, they treat evidence as a byproduct of governance, not as a task to complete. When definitions are stable, workflow points are stable, escalations are triggered automatically, and the rhythm is running. The evidence of what was seen and decided exists as part of the record. It doesn't need to be assembled the week before an audit. It is already there. Timestamped, traceable, attached to the decisions that were made at the time they were made. This is the design that allows continuous assurance to actually operate. Five moves, definitions, workflow points, escalation triggers, rhythm, evidence as byproduct. Not one of these requires a large organization. Every one of them can be installed in an RTO with fifteen staff, three qualifications, and one campus. What they require is the design decision, the decision to stop running governance on proximity and start running it on system. Illustrative scenario. Let me make this concrete. There's a scenario I work through in the governance shift that shows exactly how this breaks in practice and what happens when it gets fixed. Imagine a large public provider, multiple campuses. Each month, governing persons receive a stable system view. Enrollments are steady. Completions are sitting within tolerance. Validation is on track. The governance pack looks controlled. Underneath that, at individual campuses, divergence is forming. At one site, a trainer is recording in progress differently, more generously, so learners who are sitting on incomplete assessments for several weeks

Calibration Makes Variance Visible

SPEAKER_00 47:30

still appear to be progressing. The backlog builds, but the monthly data doesn't show it. At another site, a different workflow point is being used to record employer sign off. Sign off is captured earlier in the process at this campus than at any other. So the system view of evidence timeliness looks stronger than the reality. At a third site, a local coordinator has quietly extended the tolerance window for a particular assessment task because the employer partner was running behind on workplace opportunities. A reasonable local decision. But the monthly report still shows the cohort tracking to the original timeline. These are not compliance failures. Nobody is doing anything dishonest. They are differences in definition, local adaptations that seemed reasonable at the time. But because the definitions are inconsistent, the system view is cross-campus comparable only on paper. Underneath, the campuses are measuring different things and being reported as if they were the same. Governance receives activity, not variance, not location, not signal. Now the turning point in the scenario. Leadership, for an unrelated reason, decides to run a cross-campus calibration. They sample the same cohort definition across every site, using the same workflow point and the same evidence requirement. Differences become visible immediately. What had appeared as stable performance turns out to have been in significant part a measurement artifact. The variance was always there. It just wasn't locatable. Once definitions are aligned, the outliers can be addressed before anyone outside the organization needs to. And here's the part worth sitting with. After the calibration, the aggregated system view looks slightly worse than it did before. A couple of metrics that were sitting inside tolerance are now visibly outside tolerance because the previous numbers were smoothed by inconsistent definitions. That is not bad news. That is the first true signal the organization has had. In fact, I'd go further. The moment the calibrated numbers look slightly worse is the moment governance actually begins. Because everything before that point was based on data that could not support a real decision. The leadership team thought they were governing, but they were interpreting noise as signal. Now they have signal. Noisy at first, but signal. And once you have signal, a number of things become possible that weren't possible before. You can locate variants by campus, by cohort, by trainer. You can build thresholds that actually mean something. You can trigger escalation on real movement rather than on rumor. You can accumulate evidence as part of the governance process rather than as a retrospective assembly job. Calibration in this scenario functions as a control mechanism. Not as an audit, not as an investigation. As ordinary governance done properly. This is the pattern. At scale, the first governance asset is a shared definition of reality. Everything else is downstream. What this means for smaller RTOs. Now I know what some of you are thinking. Angela, my RTO is not a multi campus public provider. I have fifteen staff, three qualifications, two trainers. Does this episode even apply to me? Yes, more than you think. Because the principle is not about size, it's about comparison. If you have more than one trainer, you need comparable measures. If you have more than one cohort, you need comparable measures. If you deliver the same qualification in two workplaces, or to two cohorts, or across two intakes, you need comparable measures. Otherwise you are running a small version of the same structural problem

Four Moves For Small RTOs

SPEAKER_00 52:08

that public providers faced at scale. Your governing persons see stable aggregates while drift forms somewhere you're not looking. Four practical moves work in smaller RTOs. I'll walk you through them. One, document your definitions. Pick the three to five measures your governance actually pays attention to and write down exactly what each of them means. Not a policy statement, a working definition, something a new staff member could apply on day one. Two, check that your data is actually comparing like with like. Before you spend another month looking at your dashboard, ask, is this metric being captured the same way at the same workflow point by every trainer and every admin across every intake? If the honest answer is probably not, or I'm not sure, then your dashboard is not yet a governance instrument. It's a reassurance instrument, and those are not the same thing. Three, build one automatic escalation trigger. Just one to start. Pick the variance that would matter most if it formed at the edge of your organization. Late submissions, assess a backlog, completion rate drop, complaint volume, withdrawal rate, and build a trigger so that when the number crosses a threshold, escalation happens without anyone needing to decide whether it should. Four, put the calibration on a rhythm. Whatever you decide to measure, sample it on a regular cycle. Every month, every quarter, pick a cadence that suits your scale, and sample it across cohorts, across trainers, across intakes. Not when something looks wrong, on a rhythm. Whether or not anything looks wrong. These four moves will not make you a benchmark public provider. They will start your RTO on the same design path, and the design path is the one that matters. Let me give you an example of how small that first calibration effort can be. A CEO of a small private RTO I spoke with recently ran their first definitions audit over a single afternoon. Two trainers, one admin, the CEO, and a whiteboard. They listed out the five metrics they report to their governing persons each month. They went around the room and asked each person how they captured each one. By the end of the afternoon, they had identified three metrics that were being captured inconsistently, not because anyone was doing anything wrong, but because the definitions had never been written down. Three hours of work a significant correction to what their governance pack actually meant. That is the kind of intervention that's available to every RTO in this country, regardless of scale. And it is precisely the kind of thing public providers have done at scale, systematically for decades. Common mistakes. Three mistakes I see RTOs make when they try to apply this. The first is jumping to dashboards before definitions. I cannot tell you how many RTOs I've sat with who have invested in a beautifully designed compliance dashboard. Automated pulls from three different systems, colour-coded indicators, a monthly refresh cadence, and whose underlying data is measuring inconsistent things. The dashboard looks sophisticated. The governance it supports is an illusion. Definitions come first. Always. The second mistake is underestimating the political work. Standardizing

Three Mistakes That Kill Systemisation

SPEAKER_00 56:19

definitions across campuses, trainers, cohorts, or intakes means overriding local adaptations that people have been using for months, sometimes years. Those adaptations exist because someone made them work locally and they are now attached to people's professional identity. The governance move is clear, the human move is harder. If you are going to systemize, you need to do it with explicit authority from governing persons, a clear rationale, and a transition pathway, not by sending an email and hoping people comply. The third mistake is treating systemization as a project. The benchmark public providers don't systemize once and move on. They review their definitions annually. They recalibrate on a rhythm. They treat systemization as a discipline, an ongoing practice, not a one-off piece of work that gets a project plan and a completion date. If your plan for systemization has a start date and an end date, you haven't built systemization. You've built a project. Those two things do not deliver the same governance outcome. Practical steps this week. So here's what I'd like you to do this week. Take one measure, one. The one your governance relies on most heavily, completion rate maybe, or assessment timeliness, or withdrawal rate. Walk it back through your organization. Ask every trainer, every admin, every person who touches the data, how are you capturing this? At what point in the life cycle? Using what definition? You will be surprised by the answers. The gap between what you think you're measuring and what your organization is actually measuring is the first thing you need to see clearly before you design anything else. That is your week one project. It will take two or three hours. It will change how you look at every report you receive for the rest of the year. And once you've done it for one measure, you'll want to do it for two. Then three. Then a full set. The rhythm builds from there. Most of the organizations I work with

One Measure To Audit This Week

SPEAKER_00 58:44

who now run strong governance cadences didn't start with a big plan. They started with one measure, one afternoon, one corrected definition. The rest followed. The move isn't dramatic. The move is specific. One measure, one afternoon this week. Episode close plus book CTA. Episode Specific. If what I've talked about today lands with you, if you can already name the handful of measures in your RTO where the definitions might not be quite what you thought they were, then the chapter this episode draws from will give you a great deal more. It sits in a section of the governance shift called the benchmarks, where I take five Australian training organizations and break each of them down against the same governance tests. Public providers Specialist RTOs Small Private Providers Different Models, same governance mechanism, variance visible early, escalation non negotiable. Evidence as a byproduct of ordinary work.

Book Plug And Subscribe Close

SPEAKER_00 59:54

The governance shift launches in june twenty twenty six. It sold alongside the eight critical drivers to RTO success as the RTO governance bundle. The landing page is governance dash shift.vivacity.com.au Next week I'm continuing the benchmark series. Episode thirty eight The Power of Specialization Why narrow scope governs better than broad scope and why some of the most stable RTOs in the country are also the smallest. You'll want that one if your scope has been quietly expanding. Sign off. Reusable, same closing every episode. If you're not yet subscribed to this podcast, subscribe now so next week's episode lands in your feed automatically. Wednesdays every week. And if you'd like to be part of the community of RTO leaders having these conversations between episodes, join the AI in your RTO Facebook group. I'm active there every week, and it's where most of the real follow up questions get worked through. Thanks for listening. I'll see you next Wednesday.