Value for Money Strategy and System for Productivity Management Are Not the Same Thing

Reading time: 3 minutes

Here's something that's causing real confusion in infrastructure right now. Two terms are now mandatory, or close to it. The Green Book talks about Value for Money. PAS 4010 requires a System for Productivity Management. And most people think they're the same thing.

They're not. And understanding the difference changes everything about how you structure your contracts and your teams.

Value for Money is About the Decision to Invest

Let's start here. Value for Money (VfM) is a Treasury concept. It's how government, and increasingly, regulated infrastructure, decides whether to spend money in the first place.

You're comparing options. Option A costs £200m upfront, delivers £400m in benefits over 30 years. Option B costs £150m upfront, delivers £350m in benefits. Which one is better VfM? You do the sums. You look at uncertainty. You apply discount rates. You write a business case.

That's VfM work. It's a decision tool. It's saying: "Should we do this? And if we do this, which version should we do?"

VfM is upfront. It's analytical. It lives in the business case stage. You do it once, at the beginning, when the decision is still open.

A System for Productivity Management Runs Through the Whole Life of the Asset

This is the bit most people get wrong. A System for Productivity Management doesn't start when the asset is built. It starts when you're setting requirements. It runs through design. It runs through construction. It runs through operation.

A System for Productivity Management is your governance framework for delivering your VfM strategy. It runs from requirements definition through operation. It ensures the client writes requirements that are measurable. It ensures the designer makes choices grounded in those requirements, including production system choices about build sequencing and component assembly. It ensures the constructor understands both what needs to be measurable and how the design's production logic works. It ensures the operator knows what to track.

Here's the critical bit: what you measure depends on your asset type, its operating environment, and your strategic priorities. For a highway asset, you might measure network availability and user satisfaction. For a water treatment plant, operational efficiency and water quality. For a rail depot, throughput and asset reliability. There's no universal SPM. Your System has to be grounded in what productivity means in your specific context.

Why the Confusion Costs Real Money

Some organisations do brilliant VfM cases, then hand them to designers and constructors with a conventional contract. Nobody explains that every major decision needs to be grounded in the productivity criteria from the business case. By the time the asset is built, it's hard to measure anything you promised. You've got great VfM on paper and zero ability to test it.

Others build beautiful measurement systems after the fact, but the designer didn't build in the monitoring points. You're measuring something, but not what you promised. For D&B contracts without SPM clarity, nobody measured production system performance (waste in construction, rework rates, supply chain flow) so there's no baseline to compare against.

The Green Book is saying: "Justify the decision upfront with evidence." PAS 4010 is saying: "Embed measurement and governance from requirements through operation, so everyone is aligned." They're both right. But they're asking for different things.

What Matters Now

If you're designing a System for Productivity Management right now, don't think of it as an operations tool. Think of it as the framework that runs your whole asset lifecycle decision-making, grounded in your asset's specific context.

Build it into your procurement strategy. The Public Sector Procurement Act 2023 allows you to define quality criteria that differentiate tenders around "Most Advantageous Tender" (MAT). Use this to embed your SPM framework into your tender evaluation. Ask bidders: How will you measure the productivity criteria that drive our VfM strategy? What data will you collect during design and construction to prove those criteria are being met? How will your production system choices (build sequencing, component assembly, supply chain flow) deliver the productivity outcomes we promised? What monitoring and governance will you establish in operation?

This isn't just procurement compliance. This is how you lock your VfM strategy into contract performance from tender through delivery. Design and Build teams that can articulate production system thinking aligned to your SPM framework will differentiate themselves on MAT evaluation. Those that can't will become a risk to your VfM case.

Make sure your SPM framework includes production system performance metrics. What does efficient sequencing look like for your asset type? What's the right balance of off-site manufacture versus on-site assembly in your environment? What rework and waste rates are acceptable? Build these into your requirements, make them visible in tender evaluation, and measure them during delivery.

One more thing. The Green Book tells you how to decide. PAS 4010 tells you how to embed measurement and governance from the start. The Procurement Act 2023 gives you the tool to enforce it through MAT. They're not enemies. They're sequential. Get the decision right first. Then make sure you actually get what you decided to buy.

That's the difference between strategy and execution.

If you're unclear about how to build a System for Productivity Management grounded in your asset's context, or how to embed production systems thinking into your MAT evaluation and D&B contracts, let's talk. Strategic guidance on Value for Money frameworks and Systems for Productivity Management is what we do. Reach out to Dr Martin Perks, +44 7771 865271, or find us at Black Pear Advisory, Worcester.