In childcare capital works governance, delays are rarely caused by what is happening on site. More often, they begin in approval rooms, where decisions are nearly made but not quite carried through. What looks like diligence on paper can quietly shift entire construction programmes off track.
There’s a moment that shows up in almost every capital programme.
Not on site. Not in a progress report. Not even in a risk register.
It happens in a meeting room.
A design decision is presented. It has been worked through. It is not perfect, but it is ready. The team is aligned. The programme is moving.
And then someone asks for more information.
Not because the decision is wrong. Not because there is a clear risk.
But because it feels safer to wait.
No one challenges it. The meeting moves on. The decision is deferred.
On paper, nothing has gone wrong.
In reality, the programme has just shifted.
The part nobody writes down
In childcare capital works, delays are rarely framed as governance failures.
They are framed as design development. Or stakeholder alignment. Or due diligence.
All reasonable. All defensible.
But if you track what actually happens over time, a different pattern starts to emerge.
The longest delays rarely come from contractors.
They come from decisions that were almost made.
Why this keeps happening
To be fair, most approval structures are built with good intent.
Boards and committees are there to protect the organisation. To ensure capital is spent responsibly. To reduce risk.
And in high-stakes environments like childcare, that responsibility is real.
No one wants to approve the wrong design. No one wants to be accountable for a decision that creates long-term operational issues.
So the instinct is to slow down.
Ask another question. Request another option. Wait for more certainty.
From a governance perspective, it looks like diligence.
From a delivery perspective, it starts to look like drift.
What it quietly creates
The issue is not the request for more information.
The issue is the absence of a decision mandate.
When a group is responsible for approving but not accountable for programme impact, decisions lose urgency.
And when decisions lose urgency, the programme absorbs the cost.
It shows up in small ways first.
Consultants rework drawings that were already resolved.
Procurement timelines stretch because documentation is not locked in.
Contractors begin pricing uncertainty rather than scope.
Then it compounds.
A two-week delay becomes four. Four becomes eight.
By the time it is visible, it is already embedded in the programme.
No one can point to a single failure.
But everyone feels the pressure.
What I’ve noticed over time
The projects that move well are not the ones with fewer risks.
They are the ones where decisions are made at the right level, at the right time, with a clear understanding of consequences.
In practice, this tends to show up as a very different governance behaviour.
Approvers are not asking, “Do we have perfect information?”
They are asking, “What happens if we don’t decide today?”
That shift sounds small. It changes everything.
Because now, indecision is not neutral.
It has a cost.
The part that often gets missed
Most programmes track cost, time, and risk.
Very few track decision latency.
There is no line item that says: “Cost of waiting for approval.”
So it becomes invisible.
And what is invisible is very hard to challenge.
This is where decision intelligence tools are starting to shift the dynamic.
When programme dashboards begin to show the real-time impact of delayed decisions, something changes.
A deferred approval is no longer just a governance action.
It becomes a measurable programme event.
A week of indecision is no longer abstract. It is a number.
And once it becomes a number, it becomes harder to ignore.
A question worth sitting with
If every approval delay in your programme had a visible cost attached to it, updated in real time, would the same decisions still be deferred?
Or would the conversation in that meeting room start to sound very different?