Driver Seven And The Viability Lag

Why Finance Reports Arrive Too Late

Late Viability Stress Shrinks Options

Mapping The Viability Lag Chain

Completion Economics As Early Warning

Three Pathways To Financial Shock

When Numbers Stop Aligning

Four Practices That Preserve Choice

Financial Stress Is Governance Timing

Next Steps And Free Scorecard

SPEAKER_00 0:46

Everyone in this sector knows the feeling. Finance sends a message, cash is tighter than expected. There is a gap between what was projected and what has actually landed in the account. It feels sudden. It almost always is experienced as sudden. And the conversation that follows with the board, with the leadership team, with the finance function tends to be organized around the question of what happened. What actually happened in almost every case I have observed is this. The conditions that produced the cash position were forming in operations for two quarters before finance made them undeniable. Completion timing had been shifting, rework was increasing, assessment throughput had slowed. Claims were moving into later periods while delivery costs had already been incurred. Each of those conditions was visible, not in the cash position, which arrived last, but in the delivery and quality signals that preceded it. The organization did not have a financial problem. It had a governance problem that expressed itself financially. And the financial expression was the last stage, the one that could not be explained away, averaged or deferred. Cash, as the book puts it, is the signal that ends debate. Today we are going to talk about driver seven, financial sustainability and growth. We are going to talk about the viability lag chain, the sequence through which operational drift moves through delivery outcomes and arrives finally and urgently as a cash position. And we are going to talk about what governance needs to see in this domain to intervene before cash ends the conversation. Welcome back to the RTO Superhero Podcast. I'm Angela Connell Richards, episode 20 of the podcast, episode 9 of the Governance Shift series. Last week we went deep on driver one, marketing and growth, and I made the case that growth is the upstream driver, that every downstream condition in an RTO inherits the intake decision. That governing growth means being able to see constraint before commitment, not after the consequences have formed. Today, we are at the other end of that chain. Driver seven, financial sustainability and growth, is where the consequences of ungoverned upstream decisions eventually express themselves as financial outcomes. It is the downstream driver. And the governance challenge in this domain is almost the inverse of driver one. It is not about seeing what is coming. It is about not being the last to know what has already happened. I want to make something clear before we start. This episode is not about financial management in the technical sense. It is not about accounting practices or cash flow modelling or working capital ratios. Those things matter and your finance team understands them. This episode is about governance visibility in the financial domain, about whether governing persons can see the economic conditions of delivery early enough that financial signals arrive as part of a picture they already understand, rather than as the first unarguable fact in a conversation they were not expecting. That is a governance question, and it is one the sector has not been asking clearly enough. Part one. Because I think it is important to name it clearly before we move to the diagnostic framework. Financial reporting in most RTOs is retrospective by design. It describes outcomes, revenue recognized, costs incurred, cash received, completions claimed. These are accurate and necessary measurements. They are also inherently backward looking. They describe what has already happened based on delivery conditions that existed weeks or months ago. The structural problem is not that financial reporting is retrospective. All financial reporting is to some degree retrospective. The problem is that in most organizations, financial reporting is the primary mechanism through which governance learns about the economics of delivery, which means governance is learning about economic conditions, completion margins, rework costs, cash sensitivity, through the lens of outcomes that have already formed, rather than through the conditions that are currently determining what those outcomes will be. In a stable environment with predictable delivery conditions, this lag is manageable. The present looks enough like the recent past that outcomes-based reporting is a reasonable proxy for current conditions. In an environment with changing cohort mix, shifting completion economics, variable workforce conditions, and higher exception rates, which is the environment most RTOs are operating in right now, outcomes-based reporting is consistently behind the conditions it purports to describe. And the gap between the financial picture and the delivery reality can be substantial and consequential for quarters before it becomes visible in the numbers. Driver seven asks governance to close that gap. Not by replacing financial reporting, but by connecting it to the delivery conditions that are currently determining what financial outcomes will be. Part two. When governance first becomes clearly aware of a financial problem through the financial reports, the available responses are typically constrained. Hiring can be frozen. Expenditure can be deferred. Investment decisions can be reversed. Scope can be reduced. All of these responses may stabilize the immediate position. They may also, and this is the compounding risk, increase quality and regulatory exposure, because the things being deferred or reduced are often the things that support delivery integrity. Reduce validation effort and you increase assessment integrity risk. Reduce professional development and you increase capability gaps. Reduce learner support and you increase withdrawal rates and rework. Reduce administration capacity and you increase evidence chain fragility. The financial response to late discovered viability stress can produce exactly the conditions that will make the next governance problem worse. Governance that sees early has a different set of options. Slower intake growth. Qualification mix adjustment channel governance. Resource reallocation while commitments can still be managed. Delivery model changes before those changes need to happen under duress. The options that exist when governance sees the economic signals while they are forming in delivery rather than after they have arrived as a cash position are materially more numerous and materially less damaging to exercise. Preserving choice means seeing early, and seeing early means connecting financial governance to delivery conditions, not waiting for financial outcomes to report delivery conditions retrospectively. Finance only governs when it preserves choice. When cash is the first signal governance receives about the economics of delivery, choice has already been removed. The organization is not deciding what to do. It is deciding what can still be done. Part three. The viability lag chain. I want to introduce the viability lag chain, the sequence through which operational drift becomes financial exposure. Understanding this chain is the most practically useful thing in this episode because it tells you exactly where to look for early financial signals, and those places are not in the financial reports. The chain has three stages. The first stage is operations, cohort mixed changes, workforce capacity tightens, assessment throughput slows, exception rates rise, support demand increases. These conditions are visible in delivery operations, in extension patterns, in assessor workload, in the gap between intended and actual assessment timelines. They are governance signals. They are not yet financial signals, but they are the conditions that will determine financial outcomes across the next one to three quarters. An organization with strong driver seven visibility is watching these conditions, specifically in their economic implications. What does a ten percent increase in the extension rate in this qualification at this volume mean for completion timing and therefore for claims timing? What does an increase in the average number of assessor hours per completion mean for margin per completion? These questions connect operational conditions to financial implications before those implications have arrived in the accounts. That connection is what early governance visibility looks like in this domain. The second stage is outcomes, completions slip, withdrawals increase, rework rises, validation identifies inconsistencies. The program that was projected to deliver a certain number of completions in a given period delivers fewer or delivers them later. These are outcome signals. They are already downstream of the operational conditions that produce them, and they typically arrive in formal reporting four to eight weeks after the conditions that cause them were first visible in delivery. At this stage, governance is watching lagging indicators. The operational decisions that will determine the next round of outcomes are already being made. Governance can intervene here and should, but the options are narrower than they were at stage one. Some commitments have hardened. Some delivery decisions have already been taken that cannot be easily reversed without further impact on the learner experience and on evidence integrity. The third stage is cash. Claims shift, revenue moves, costs were incurred earlier than receipts arrived. The financial position, which has been forming across two stages of operational and outcome drift, becomes undeniable in the cash account. This is the stage at which in most organizations the financial conversation with the board begins in earnest. It is also the stage at which options are fewest. Every week that passes between stage one and stage three is a week in which governance could have intervened with lower cost, lower disruption, and lower regulatory risk. Cash ending the debate is not a financial event, it is a governance timing event. It reflects how long the organization was operating without connecting financial governance to delivery conditions. Part four completion Economics the missing metric. I want to spend time on what I think is the single most important missing metric in RTO governance packs. Not missing because it is impossible to calculate. Missing because it is not conventionally asked for, and because the organizations that do track it tend to have significantly better early warning of financial exposure. The metric is completion economics, specifically margin per completion at qualification level tracked over time and compared against intake economics. Most RTOs track cost per lead and cost per enrollment. These are driver one metrics. They describe the economics of acquiring learners. They are useful. They are not the metrics that tell you whether the delivery model is financially sustainable at the volume and mix currently being run. Margin per completion is different. It asks for each learner who completed this qualification in this period, what was the net margin after delivery costs, support costs, assessment costs, rework, and evidence overhead? And how does that compare to the projected margin when the intake was approved? When the two numbers are close, the delivery model is performing as expected. When the actual margin per completion is materially lower than the projected margin, and this is where the signal sits, it means that the cost of delivery exceeded what was modeled. That excess cost came from somewhere. Higher support demand, more rework, longer assessment cycles, higher overhead per learner. Each of those drivers has a governance implication beyond the financial one. Tracking margin per completion over time also reveals a pattern that is otherwise invisible. The economics of the delivery model, changing gradually, driven by cohort mix changes, workforce condition changes, or assessment discipline changes that individually seem minor, but in aggregate are reshaping the financial sustainability of the qualification. The organization that tracks this metric by qualification, by channel, and by intake cohort and presents it to governing persons as part of the governance pack is doing something fundamentally different from the organization that reports revenue and overall financial position. It is connecting financial governance to delivery conditions in real time. It is making the viability lag chain visible at stage one, not stage three. This is the metric I most consistently find absent from governance packs when I work with organizations experiencing financial stress. Not because anyone decided it was unimportant, but because nobody designed the governance reporting to include it. That is a design choice, and it is a reversible one. Part five. The first is completion economics deterioration. This is the pathway we have just been discussing. Volume is strong, revenue looks healthy, but the cost of delivering completions, the support intensity, the rework rate, the assessment overhead is rising, while the revenue per completion is not. The governance pack reads well because the headline revenue number is meeting projections. The margin per completion is not, but nobody is tracking that. The signal is in the operational conditions. Extension rates rising, resubmission rates rising, support hours per learner rising, all of which are visible before they become completion economics and long before they become cash. The governance question in this pathway What is the current cost per completion by qualification? And how is it trending against the projected economics of each intake? The second pathway is concentration risk. A provider becomes reliant on a dominant qualification, a single employer relationship, a particular funding stream, or a single delivery channel. The concentration is often visible to people inside the organization. It rarely appears in governance packs as a risk that requires a governing person's decision. It persists as a known condition until an external change removes the concentration. The employer restructures, the funding settings change, the channel underperforms, and the organization must respond immediately without the ramp time that earlier visibility would have allowed. Concentration risk is the governance failure of not making a decision while one was available. The concentration was visible. The dependency was knowable. The decision to diversify or to explicitly accept the risk while managing it was never made with the formality and traceability that would have produced a defensible governance record. When the condition changes, governance is managing the consequences of a risk it observed without ever formally owning. The governance question here where is the organization's revenue, delivery capacity or learner pipeline concentrated in a way that a single external change could materially affect it? And has that concentration been explicitly considered and accepted as a governed risk? The third pathway is evidence discipline under funding review. This one sits at the intersection of financial and regulatory exposure, and it is more common than most organizations recognize until they are in it. A funder conducts a review of participation and progression data. Enrolment evidence, attendance, support records, and approvals exist across systems. They are not linked into a single coherent operating record. When a sample is tested end to end, show me the complete evidence chain for these five learners. From enrolment through completion, the organization can produce documents. What it cannot always produce is a continuous unbroken chain that connects enrolment to completion without reconstruction. Where that chain is incomplete, the financial implications are direct. Claims may be at risk, contract performance measures may be queried. Funding decisions may be deferred while the organization addresses evidence gaps. The financial exposure is not the result of poor delivery. It is the result of poor evidence discipline, which is a driver 5 and driver 8 failure that arrived in driver 7 as a financial consequence. The governance question if a funder requested an end-to-end evidence trail for a random sample of completions in the last three months, how long would it take to produce? And would the chain be contemporaneous or reconstructed? Part six. The scenario when the numbers stop aligning. Let me give you the scenario. It is a composite, but every element of it is drawn from patterns I have observed in practice. A provider has been running a strong quarter. Operations reports delivery is busy but stable. Compliance reports validation and internal checks are progressing. Finance reports that revenue is holding and dashboards are within expected ranges. The organization appears under control because each view aligns within its own frame. Over the same period, small inconsistencies have been accumulating. Assessment backlog is pushing completions into later periods. A workplace partner has Delayed sign-offs on a cohort. Learner support has recorded a rise in extensions and a slight increase in withdrawals within two specific qualifications. Each signal is interpreted locally as a capacity issue, a timing variation, a manageable cohort condition. None of these signals has been sufficient to force a governing person's decision that alters operating conditions. Each one has been absorbed into its function's operational management with a plausible explanation. Integration arrives when cash tightens. Claims are delayed because completions have shifted into a later period. But delivery costs were incurred in the period that has just closed. The gap between costs incurred and receipts anticipated is now a cash position problem. Leadership brings operations, compliance, and finance together. In that meeting for the first time, the signals connect. The assessment backlog, the partner sign off delays, the extension clusters, the completion timing, the cash gap. They are all part of the same condition. A condition that has been forming for two quarters while each function was managing its own piece of it. Nobody missed anything. Nobody acted improperly. The signals existed. The governance structure did not hold them together in a form that could have produced a decision while options still existed. The meeting is productive, actions are agreed, the position is manageable. But the choices available in that meeting are narrower than the choices that were available eight weeks earlier, before the commitments hardened and the cash gap formed. Viability became the forcing function rather than a managed condition. And the organization learned at some cost that financial governance that waits for financial outcomes is always late. Part seven. What governing the financial domain actually looks like? Let me make this concrete with four specific things that distinguish organizations where financial governance preserves choice from organizations where cash ends debate. The first is a live connection between delivery conditions and financial projections, not a monthly financial report produced from completion data. A view that connects current operational conditions, extension rates, assessment throughput, rework rates, support intensity, to projected completion timing and therefore projected cash timing. This does not require sophisticated financial modeling. It requires someone asking the question Given what we are currently seeing in delivery, how does that change the timing of our completions and claims over the next two quarters? In some organizations that question is asked routinely in the ordinary governance of driver seven. In most it is asked for the first time when cash makes the answer urgent. The second is completion economics by qualification, tracked at governance level, not in a detailed operational report. In the governance pack as a standing item, alongside revenue and cash flow. If the margin per completion in a qualification is declining over three intakes, that is a governance fact, not an operational detail. It requires a governing person's response, and it requires governance to have been watching the right metric to notice it. The third is a concentration risk register that is live and acted upon. Not a risk register that notes the concentration as amber and carries it forward each month as monitored. A register that defines specifically what conditions would require a governing person's decision about the concentration and what that decision would look like. Diversification plan contingency capacity. Explicit acceptance of the risk with a defined review trigger. Any of these is a governance response. The absence of any defined response is not monitoring. It is deferral. The fourth is an evidence discipline review that connects to financial exposure. Quarterly, not at audit time. A review of whether the evidence chain for the current delivery period would support a funding review request today. Not in preparation for a request. As a standing governance condition. The cost of discovering evidence gaps at the point of a funding review is materially higher than the cost of identifying and addressing them in ordinary operations. These four things do not require a complete redesign of the financial governance framework. They require a deliberate decision to connect financial governance to the delivery conditions that determine financial outcomes and to make that connection visible to governing persons while choices still exist. I want to end with the observation that I find most important about financial governance in this sector, and that I think the viability lag chain makes most clearly. Financial stress in RTOs is not primarily a financial problem. It is a governance timing problem that arrives as a financial problem. The conditions that produce cash sensitivity form in operations. They move through outcomes, they become undeniable in cash, and at every stage of that movement, there is a governance question that, if asked and answered, would have produced a different conversation, with more options, more time, and more capacity to respond proportionately. The organizations that experience financial stress as a surprise are not, in most cases, organizations that were poorly run or whose finance teams were inattentive. They are organizations where the connection between delivery conditions and financial implications was not built into governance as a standing real-time visibility mechanism. Where financial governance was reporting outcomes rather than tracking the conditions that produce them. That is a design problem. And it has a design solution, which is connecting the financial governance pack to delivery conditions at the level of the qualification, the channel, the cohort, and the evidence chain. Not occasionally, as standard. Next week we are moving into the benchmark section of the series, looking at what high performing Australian training organizations actually do differently in governance terms. After nine episodes of diagnosis and framework, it is time to look at what designed governance looks like when it is working. I think you will find it both instructive and genuinely encouraging. The governance shift in vocational education is out in June 2026. The Driver 7 chapter covers the viability lag chain, completion economics, concentration risk, and the evidence discipline connection in full. The free RTO governance scorecard in the show notes will show you specifically where your Driver 7 visibility currently sits. Cash is not the first signal. It is the signal that ends debate. The signals that preceded it, in operations, in outcomes, in evidence discipline, were available to governance earlier. The question is whether governance was designed to see them, or whether it was designed to wait until cash made them undeniable.