Skip to main content

Ten years of evidence

Monitoring, progress and learning

Two different things happen over a ten-year programme. You report formally to Government, and you learn locally about what actually works. Both matter, and they are not the same job.

This Hub does not replace the MHCLG digital monitoring tool. Official returns are made through the Government system by your accountable body, using the current official template. Everything here is independent UrbanCat guidance to help you be ready.

The distinction

Official monitoring and local learning

Confusing the two is the most common reason Boards end up with a pile of data nobody uses.

Official programme monitoring

Reporting to MHCLG

  • Submitted by the accountable body through the Government digital tool.
  • Fixed fields, fixed deadlines, fixed definitions.
  • Focused on spend, outputs, milestones and risk.
  • Non-negotiable — always use the latest official guidance.

Local outcomes and learning

Understanding your own place

  • Designed by the Board, for the Board and for residents.
  • Mixes numbers with resident accounts of what changed.
  • Feeds decisions about the next stage of the pipeline.
  • Voluntary — but it is what makes ten years add up to something.

Tool

Six-month monitoring readiness check

Tick what is genuinely in place today. Anything left unticked is usually what causes the last-minute scramble before a return.

0/12 monitoring habits in place

12 gaps to close before the next return

Gaps to address

  • Named lead for monitoring returns
  • Board sign-off route agreed
  • Live spend and forecast tracker with the accountable body
  • Output definitions agreed and written down
  • Baseline data captured for local outcomes
  • Project milestone log kept up to date
  • Risk register reviewed at every Board meeting
  • Evidence collected at the point of delivery
  • Open route for resident feedback on projects
  • Lessons-learned session after each project
  • Public progress summary published locally
  • Latest official return template checked this cycle

Guidance

What to get right, area by area

Nine areas that recur in every reporting cycle for the next decade.
Six-month monitoring readiness(open)

MHCLG expects regular returns through its digital monitoring tool. Being ready is mostly about routine, not paperwork sprints.

  • Agree who drafts the return, who reviews it and who signs it off before the window opens.
  • Keep a single live spend and forecast sheet with the accountable body, updated monthly.
  • Record project milestones as they happen rather than reconstructing them later.
  • Log risks and mitigations in Board papers so the narrative writes itself.
  • Check the latest official return template before you start drafting.
Annual review(open)

Once a year, step back from delivery and ask whether the plan is still the right plan.

  • Review progress against the 10-year vision, not just this year's projects.
  • Test whether local priorities have shifted since the last engagement round.
  • Review Board membership, skills gaps and succession.
  • Publish a short public summary so residents can see what changed and why.
Project progress(open)

Track each project consistently so comparisons across the portfolio are meaningful.

  • Use one status vocabulary: scoping, design, procurement, delivery, complete.
  • Name a responsible organisation and a Board sponsor for every project.
  • Record start and completion dates, and explain slippage in one sentence.
Spending and forecasts(open)

Spend profiles change. What matters is that the Board sees the change early.

  • Separate committed, contracted and actual spend.
  • Forecast to the end of the current investment plan period, not just the year.
  • Flag underspend risk to the accountable body as soon as it appears.
Programme outputs(open)

Outputs are the countable things funding delivers, and they feed official reporting.

  • Agree output definitions once, at the start, and reuse them.
  • Collect evidence at the point of delivery — photos, counts, sign-in sheets, invoices.
  • Avoid double counting where projects overlap.
Local outcomes(open)

Outcomes are what actually changes for residents. This is where a Board's own learning matters most.

  • Pick a small number of local outcome measures you can realistically sustain for ten years.
  • Capture a baseline before delivery starts.
  • Mix numbers with resident accounts — both are evidence.
Community feedback(open)

Feedback is a monitoring input, not a communications exercise.

  • Offer a permanent, low-effort way for residents to comment on projects.
  • Report back publicly on what feedback changed.
  • Watch for whose voices are missing and go to them directly.
Lessons learned(open)

Recording what did not work is the highest-value thing a Board can leave behind.

  • Hold a short lessons session after each significant project.
  • Write down the decision you would make differently.
  • Share it — another neighbourhood is about to make the same call.
Updating priorities(open)

A ten-year vision should be stable. A four-year investment plan should not be frozen.

  • Set a clear process and threshold for changing the pipeline.
  • Evidence any change with engagement or monitoring data.
  • Keep an audit trail of what changed, when and why.

The long game

Building a ten-year public record

Where Boards publish monitoring information, we attach it to the community profile so anyone can see how a neighbourhood used long-term investment.