CRF delivery is hard. And it’s about to get harder.

CRF delivery is hard. And it’s about to get harder.

There’s a version of CRF delivery that exists on paper.

It’s clean.
Structured.
Logical.

Funding comes in.
Schemes are designed.
Support goes out.
Reporting follows.

That version isn’t what most programme leads are dealing with.

What it actually feels like

It feels like trying to build something while it’s already expected to be running.

You’re being asked to deliver from April.

But:

• funding clarity isn’t always complete
• scheme design is still evolving
• partners aren’t fully lined up
• procurement hasn’t caught up

And at the same time, the narrative outside is already moving.

There are headlines about cash support landing.
Expectations are being set.

From the outside, it looks like this is ready to go.

Inside, it doesn’t feel like that.

In two-tier areas, it’s even more complex

In some parts of the country, the structure itself adds another layer.

In Years 1 and 2 of CRF:

• district councils still receive Housing Payment allocations
• the rest of the fund sits with county and unitary authorities

That means funding, design and delivery don’t always sit in the same place.

Before anything has even launched, responsibilities are already split.

And that creates real questions:

• who owns the model?
• who controls the budget?
• how does delivery actually work across layers?

None of that is insurmountable.

But it does add friction — early.

Procurement doesn’t move at CRF speed

One of the least visible challenges is also one of the most constraining.

Procurement.

You can know what you need.
You can even agree it internally.

But actually putting the right components in place — systems, partners, delivery routes — takes time.

Time that doesn’t neatly align with policy timelines.

So you get this tension:

• the need to move quickly
• the reality that some decisions can’t move quickly

And you’re left trying to bridge that gap.

It’s not one build. It’s several.

CRF isn’t a single system.

It’s multiple things, coming together at once:

• identifying and assessing need
• making decisions that are fair and consistent
• delivering support in different ways
• working across teams, partners and organisations
• holding it all together with reporting and governance

None of these are trivial.

All of them are happening at the same time.

And the model isn’t fixed

Even as you’re building it, it’s moving.

• funding assumptions change
• delivery methods evolve
• new partners get pulled in
• edge cases appear that don’t fit what you designed

So it’s not just “build and run”.

It’s build, adjust, rework, and keep going.

This is where the pressure really sits

Not in any single decision.

But in trying to make all of it hold together.

You’re balancing:

• speed vs control
• flexibility vs consistency
• local delivery vs central oversight
• immediate need vs long-term sustainability

There isn’t a clean answer to those trade-offs.

There’s just judgement.

And timing makes it sharper

April is the start point.

But for many, that’s not when things will feel fully operational.

There’s a ramp.

A period where:

• parts are live
• parts are still being worked through
• and the system is finding its shape in real time

That’s uncomfortable.

But it’s also the reality of standing something like this up.

If it feels messy, that’s because it is

There’s a temptation to think:

“We should have this more nailed down by now.”

But CRF isn’t a neat problem.

It’s:

• multi-agency
• multi-channel
• time-pressured
• and evolving as it’s being delivered

That combination doesn’t produce clean builds.

It produces working systems that get better over time.

What actually matters

Not whether it’s perfect from day one.

But whether it can:

• hold together under pressure
• adapt as requirements change
• and deliver support without breaking

That’s a different standard.

And a more realistic one.

Where this leaves most programme leads

Not behind.

Not failing.

Just in the middle of something genuinely difficult.

Trying to:

• make the right calls early
• avoid decisions that box them in later
• and build something that will still work in six months

That’s not straightforward.

It was never going to be.

Bring it back

CRF delivery isn’t difficult because something has gone wrong.

It’s difficult because of what it is.

A system.
Under pressure.
Built in real time.

And that’s exactly why, for many authorities, it’s starting to feel like more than just a delivery challenge.