Financial year planning has recently closed for many Australian businesses. Budgets and headcounts are locked; project pipelines are signed off, and you likely have new targets in place for growth, delivery, and infrastructure programs.
But there might be a question that wasn't asked during budget reviews:
Is the capability there to deliver it all?
That's the planning gap we want to explore in this article: why capability decisions need to happen before delivery pressure builds, which roles are most exposed when planning starts late, and how earlier conversations can reduce risk before projects are already under strain.
For project directors and engineering managers, delivery risk often starts before a vacancy, an overstretched engineer, or a missing specialist. It starts when capability planning is not treated with the same priority as budgets, procurement, scheduling, and sequencing.
When we speak with engineering and infrastructure leaders, the pattern is consistent; many organisations don't have the resourcing problem they think they do. It's a planning problem.
That distinction matters.
A resourcing problem is when a project slows because the right person is not available when needed. It's the visible gap.
A planning problem is often the cause: the capability decision that should have happened three, six, or twelve months earlier.
The earlier a gap is identified, the easier it is to close. There's a wider talent pool, more timing control, and less pressure. Left too late, the same issue becomes more urgent, costly, and difficult to solve.
In infrastructure delivery, capability planning is both a people issue and a delivery risk.
That delivery risk is harder to absorb as demand for engineering and infrastructure capability in Australia keeps rising.
The scale of the challenge is clear:
As you finalise delivery plans, this is important to keep in mind. The market pressure affecting the national pipeline will also shape local project teams. If capability planning waits until mobilisation, you will be competing for scarce skills at the exact moment everyone else is looking.
We can all view the figures above as both a warning and an opportunity.
They are a warning because experienced engineering capability is already tight, and pressure is unlikely to ease in the short-term.
The opportunity is there for organisations that move early. They're better placed to protect timelines, manage cost, and capture the pipeline ahead.
That's why the timing of the capability conversation matters as much as the capability itself.
Too often, workforce planning starts once a project is moving, and the gap is obvious. By then, there are fewer specialists, shorter windows, higher rates, and more pressure on the existing team.
In practice, that means mapping critical roles against the delivery timeline, identifying where internal teams are already stretched, deciding which gaps need permanent hires or interim expertise, and starting those conversations before procurement and mobilisation compress the available options.
The alternative is to treat capability planning as part of delivery planning from the beginning.
That means thinking about:
When that happens early, capability can be brought in to support delivery, not just rescue it.
Within broader demand for engineering talent, one layer matters most: experienced specialists who can operate with independence, judgement, and delivery focus.
Of course, every level matters in your business. Senior leaders set direction, while graduates and junior engineers build future capability. But the mid-career layer often carries the delivery load.
This is the layer that runs day-to-day work, coordinates teams, solves practical technical problems, supports junior staff, and keeps projects moving without constant oversight.
For many infrastructure and engineering programs, this can include roles such as:
These roles are not always the most visible, but they often determine whether delivery stays on track.
A systems engineer keeps requirements, interfaces, assurance, and integration aligned. A project controls specialist gives early visibility of cost, schedule, and performance risk. An asset manager protects whole-of-life value. A project engineer turns the plan into progress on the ground. A contracts manager keeps obligations, variations and commercial risk under control.
When these roles are missing, overloaded, or brought in too late, pressure spreads into schedules, decisions, quality, reporting, governance, and morale.
These gaps are hard to close reactively because the value of these specialists is technical knowledge, context, judgement, relationships, and the ability to keep work moving through complexity.
That kind of capability needs to be planned early; in the same way you would plan any critical resource in short supply.
Keep in mind that if similar projects start at the same time, competition for skilled resources intensifies. Planning early helps your organisation secure the capability it needs without potentially losing competitive advantage.
Ahhh, the magic question. Let's look at an example.
Consider a project with funding approved in July, procurement scheduled for September, and delivery ramping up in November. On paper, the plan is sound. The budget is approved, milestones are set, and the delivery team knows what needs to happen.
The capability plan is less mature.
The project needs an experienced project engineer, a project controls specialist, and systems engineering support. The need is acknowledged but not treated as urgent because peak delivery pressure is still months away.
By October, the gaps are obvious.
The team is stretched, reporting is reactive, interfaces are harder to manage, and decisions take longer because technical support is inconsistent.
At that point, the issue looks like a resourcing problem, but really, the capability decision needed to happen months earlier.
In a situation like this, you may still close the gap, but you have fewer choices. People may be committed elsewhere; mobilisation must happen quickly, costs are harder to control, and new support lands already under pressure with less time to understand the context.
This is the difference between bringing capability in to plan and bringing capability in to do the urgent things.
The biggest takeaway we can give you here is that the companies that stay ahead of the pipeline are the ones who start conversations about capability before the pressure hits.
For some, that will mean a permanent hire. For others, it will mean bringing in experienced specialists who can integrate quickly, carry delivery load from day one, and leave the team stronger than they found it.
Embedded Expertise works in that space, and we can help engineering and infrastructure leaders spot capability gaps early (we know what to keep an eye on), before the gap becomes a resourcing problem.
In an upcoming article, we'll look at why capability gaps might not all be solved with the same answer, and the questions that can help you determine the best approach.