There's a version of this conversation that's easy to have. The Australian workforce isn't digitally ready. AI is changing everything. VET has a role to play. We need to do better.

Everyone agrees with that. It means almost nothing.

Here's the version worth having.

We are asking the VET sector to do nation-building work, preparing hundreds of thousands of Australians for a digital workplace that is moving faster than any of our institutions can track. Government understands this. To their credit, they are trying. But understanding a problem and being equipped to solve it are two different things, and right now the gap between those two states is significant and widening.The problem isn't being ignored. It's being misdiagnosed.

When digital capability comes up in VET, the instinct is to reach for curriculum. Update the units. Add a software module. Make sure learners can operate the current tools. It feels like action because it produces something measurable: a unit of competency, a training plan, a box to tick.

But here's the thing. I could teach you to use an AI assistant today. Walk you through prompting, outputs, practical applications. You'd leave reasonably capable. And in eighteen months, when that tool has changed significantly, new features, new limitations, new risks, most of that training will be largely useless. Not because you learned the wrong thing, but because we taught you what to do, when we should have taught you how to think.

Digital capability isn't software literacy. It's judgment: the ability to assess what's in front of you, understand the underlying logic well enough to adapt, and make sound decisions about tools, data, and security without someone holding your hand through every new interface. That kind of capability doesn't expire when the software updates. It compounds.

DigComp 3.0, the European digital competency framework increasingly informing practice in Australia, is built around exactly this distinction. It's not a list of software skills. It prioritises judgment over task completion and treats digital risk as a core competency, not an afterthought. I've written separately about why it represents a more accurate description of digital reality than the frameworks it replaces, and why that precision matters for everything downstream.

So why aren't we working to it? Because it requires something harder than updating a unit of competency. It requires our trainers to understand it first.

And this is where I want to be careful, because this is the part of the conversation that goes wrong quickly. The instinct could be to blame trainers. It's the wrong instinct.

 A trainer who hasn't been shown how to think about digital capability, who hasn't had their own gaps diagnosed and supported, and who is already stretched across compliance requirements, learner support, and administrative load, cannot pass on something they haven't been given. You cannot teach what you don't understand. That's not a character flaw. It's just how knowledge transfer works.

The honest question is: who is responsible for building trainer capability at this level, and are they actually doing it? In most organisations, the answer is murky at best.

 This is the structural failure. The responsibility for digital workforce readiness has been delegated downward, from government to the sector, from the sector to providers, from providers to trainers, without the diagnostic work, the support infrastructure, or the time needed to make it real. Everyone in the chain is doing their best with what they have, but in most instances, what they have isn't enough.

At TLRG, we built our platform around DigComp 3.0 because we think the gap analysis has to come first. Before you can address digital capability, whether for a learner, a trainer, or an organisation, you need to know where the gaps actually are relative to what the role or course genuinely requires. Guessing doesn't work. Neither does assuming that completing a unit of competency means the capability is there.

What that work shows us, consistently, is that the gaps are rarely where people expect them. It's usually not the obvious software stuff. It's data security awareness. It's the judgment to question AI output rather than accept it. It's a basic understanding of how digital systems work, well enough to adapt when they don't.

These are not things you can regulate into existence. You can set frameworks, and you should. You can update training packages, and that matters. But the actual transfer of capability happens in the room, between a trainer and a learner, in the context of real work. If the trainer isn't equipped, none of the rest of it lands.

The pace of change is not going to pause while we sort this out. That's not pessimism. It's just the situation we're in. Government knows it. The sector knows it.

The question is whether we're willing to be honest about where the real work needs to happen, and whether we're prepared to actually support the people we're asking to do it.

 We're trying to build a digitally capable workforce with trainers who, through no fault of their own, are often not yet digitally fluent enough themselves. That's not a criticism. It's a diagnosis.

And you can't fix what you haven't diagnosed.

If you want to understand what a better diagnostic looks like in practice, my recent article on DigComp 3.0 covers why the framework itself represents a more useful description of digital reality, and what that means for the sector.

About the Author

Matt Peachey