The SPM is the organising framework through which productivity is understood, planned, governed and improved throughout a project or programme. It translates strategic intent into practical, measurable actions that every member of the value chain can act on.

The SPM does not impose an extra layer of processes. It coherently organises existing activities and information flows to make managing productivity a deliberate discipline. Most of its components will already be happening in some form. The SPM connects them all with a single question: are we delivering the right thing in the right way, with the least waste, throughout the asset’s life?

Although it is developed collaboratively, drawing on the people who understand each constraint at first hand, the SPM is owned by the client, which holds the levers (scope, procurement, governance and culture) that make it work (PAS 4010, clause 4.1.2).

And it is established early, during the need and optioneering stage, before the scope is fixed and design decisions are taken. This order is vital, as an SPM that’s introduced after those choices are made is managing consequences rather than shaping outcomes (PAS 4010, clauses 4.1 and 6.2.2).

The SPM is not a fixed document. It is revisited at each lifecycle stage and decision gate so that it stays relevant as the project develops, with detail added progressively: light at the optioneering stage, when little is fixed, and fuller as scope, design and delivery decisions are made.

PAS 4010 prescribes what an SPM must address, but not its format. In practice, a well-formed strategy will cover six elements:

1. A clear statement of productivity objectives, aligned with organisational strategy and whole-life value. This is expressed in terms of effectiveness and efficiency, supported by evidence and reference-class data where it exists (PAS 4010, clause 4.1.2).
2. An analysis of productivity drivers. These are the constraints, risks, opportunities, interdependencies and systemic factors that shape productivity. They are identified systematically at every lifecycle stage and shared with the client for inclusion in the strategy (PAS 4010, clause 4.1.1).
3. A productivity plan that applies the productivity improvement hierarchy before the scope, design or method is finalised. It sets out the actions to maximise productivity, manage constraints and realise opportunities, assigning clear roles, information requirements and decision points (PAS 4010, clause 4.1).
4. Targets and baselines. These are project-specific and programme-level, aligned with standard measures where they exist, with named individuals accountable for setting, monitoring and updating them (PAS 4010, clause 7.1).
5. Monitoring and reporting arrangements. Productivity is measured using defined data sources, reporting frequencies, ownership arrangements and dashboards. Mechanisms for early warning and escalation are required so that emerging problems can be addressed promptly (PAS 4010, clause 7.2).
6. Learning and continuous improvement. Structured reviews, feedback loops and knowledge-sharing processes help to ensure that lessons are retained and improvements are sustained beyond individual roles and projects (PAS 4010, clause 8).

These six elements are mutually reinforcing. They give strength to the SPM, which must start with a clear statement of productivity objectives from the client.

Understanding what shapes productivity on a project or programme requires analysis. This should be collaborative and grounded in evidence, drawing on the people closest to the work – designers, contractors, subcontractors and suppliers – who can usually pinpoint the areas where value is being lost.

A few questions can help to reveal the main drivers. These include:

• What’s constraining flow, sequencing or access?
• Where are the biggest losses of time, talent, knowledge or materials happening?
• Which design decisions have the most impact on buildability and efficiency?
• What systemic risks – planning, consenting, utilities, interfaces – could undermine delivery?
• Where do opportunities lie for innovation, standardisation or offsite manufacture?

A useful starting point for this analysis is the set of 11 drivers of value for money developed through the Infrastructure Client Group’s productivity workstream (see annexe A1). These capture the factors that most affect cost, productivity and value – from requirements and constraints at the front end, through design, construction and commercial choices, to the cultures and organisational frictions that shape delivery. Working through these in a workshop is a quick way to check that no significant driver has been overlooked.

A role-based approach to finding productivity opportunities, moving from client-level programme decisions down to individual site-operative tasks, can complement this analysis (see annexe A2). It identifies who is typically responsible for key productivity choices at each stage and what a productivity discussion with them might cover.

The depth of this analysis should match the project. A modest scheme may need a single half-day workshop; a major project may warrant a highly structured, cross-discipline diagnostic programme. Either way, the output is a shared view of where productivity is won and lost, which becomes the foundation for the productivity plan.

The productivity plan sets out what actions are needed to address each constraint and the opportunities to be realised. Allocating responsibility, it specifies how decisions will be made and how progress will be monitored. Good plans are: client-owned but developed collaboratively; aligned with procurement and contracting; and integrated into existing project controls rather than run as a separate exercise.

Plans will vary according to context, but they typically cover how productivity will be improved by measures such as design optimisation, collaborative planning, readiness reviews, sequencing and interface management, subcontractor engagement and error reduction. The plan is a living document: it is reviewed and updated as the project evolves and its productivity drivers are better understood, not written once and filed.

Targets focus effort and make progress visible. PAS 4010 asks members of the value chain to identify the key indicators of productivity for their work and use standard measures wherever possible, so that performance can be compared across projects and over time. They should establish baselines and set targets that are specific, measurable and time-bound (PAS 4010, clause 7.1).

PAS 4010 specifies neither what project teams should measure nor how they should measure it. This is a deliberate choice: the diversity of infrastructure projects means that no single set of metrics would fit all cases. Prescribing one would risk distorting behaviour towards what is measured rather than what matters (PAS 4010, clause 0.6).

The hope is that the industry will use this freedom to experiment with metrics, rather than converging prematurely on a prescribed set. To that end, PAS 4010 requires all members of the value chain to identify the key indicators of productivity for each project and how they intend to use them, applying standardised measures where these exist. But there is also an expectation that novel metrics will be developed and tested. This is why the requirement to establish and properly use data collection and management systems, and to share successes and failures, matters so much. A significant learning phase still lies ahead (see section 5.6).

Common targets could be set against measures such as plan reliability, rework, labour utilisation, production rates, design cycle times and commissioning readiness. Annexe A3 offers some example metrics that could be of use.

Proportionality is important: targets should reflect the project’s scale, complexity and risk profile. A handful of meaningful, well-owned targets will always beat a dashboard of metrics that no one acts on.

Baseline-setting deserves particular care, because a productivity improvement is only as credible as the baseline it is claimed against. Baselines should reflect current good practice and be updated over time as the sector improves, so that today’s good performance becomes tomorrow’s starting point rather than a permanent benchmark. Where data is sparse, especially when setting a baseline for the first time, the honest course is to use the best available comparison; state your assumptions and their limitations plainly; and establish mechanisms to collect better data for next time (PAS 4010, clause 7.1.2).

Monitoring is how the SPM earns its keep. It provides a clear view of performance, supports informed decisions and enables timely interventions. Effective monitoring rests on a single source of truth for productivity data; clear ownership of collection and reporting; regular review cycles matched to the pace of the work; dashboards that highlight trends and risks rather than burying them; and mechanisms for identifying emerging problems and alerting decision-makers to them (PAS 4010, clause 7.2).

Integration is what keeps this from becoming a burden. Monitoring should run through existing project controls, using data the project already generates. The aim is not to use reporting for its own sake but to use reporting that reflects reality and prompts action.

Continuous improvement is a central requirement of PAS 4010, not an optional extra (PAS 4010, clause 8). It ensures that lessons are systematically identified, validated and shared, then embedded into later stages and future projects – the step most often skipped in this sector.

Embedding lessons into future projects will usually happen outside the project-specific SPM, but it should still be done by all members of the value chain.

The principle is to treat learning as a core project activity, allocating time to it and making someone responsible for it, rather than squeezing it into the gaps. A lesson that is identified but never re-used has cost effort and returned nothing. Effective methods include structured learning reviews, cross-project knowledge exchanges, design and delivery retrospectives, readiness reviews and thematic investigations into recurring problems.

An SPM is only as good as the behaviours that surround it. Its integrity depends on problems being raised early, constraints being reported truthfully and assumptions being challenged when they threaten productivity (PAS 4010, clauses 4.3 and 8). None of these is a matter of process; all are a matter of culture.

PAS 4010 will be most effective where there’s a culture of psychological safety. This is where anyone can tell the truth about what’s happening on a project without fear. A reporting system that punishes bad news simply teaches people to hide it. An SPM built on concealed problems is worse than none, because it offers false assurance. Creating the conditions for candour is one of the most valuable things an infrastructure client and its leaders can do – a subject returned to in section 6.

Clause 6 of PAS 4010 sets out how productivity is managed throughout a project or programme, from the first identification of a need through to operation. The principle behind it is simple and follows directly from the productivity improvement hierarchy: the earlier one acts, the more one can change.

At the start, all options are still open and the cost of making a better choice is close to zero. By the time concrete is being poured, the room for manoeuvre – and the prize – has shrunk dramatically. Managing productivity through the lifecycle means acting when there is the greatest scope to influence outcomes, which is almost always sooner than the sector instinctively thinks.

PAS 4010 divides the lifecycle into five broad stages. The boundaries are not rigid – design and consenting in particular tend to iterate rather than run in a strict sequence – but the stages are a useful way to consider where productivity is gained and lost.

This stage offers the greatest potential to influence productivity. Before the project’s scope is fixed, the client should define the outcomes in functional terms – what the asset must achieve, not what it must be – and test rigorously whether those outcomes could be achieved by differently scoped alternatives or by adapting existing assets (PAS 4010, clause 6.2.2). Reference-class forecasting and benchmarking belong here too, to set baselines that are realistic rather than optimistic and to record the evidence behind the productivity gains expected of the project.

Part of defining those outcomes is a conscious decision about the design life being sought. The intuitive answer – “build it to last” – is not always the most productive overall. Sometimes, a durable high-spec solution is clearly right; at other times, a cheaper, shorter-lived solution that’s designed to be replaced offers better whole-life value, because replacing it costs less than the upfront expense of building to last. Neither option is inherently more productive. What matters is that the client weighs the options on a whole-life basis and chooses deliberately, with the trade-offs understood and recorded (PAS 4010, clause 4.1.1).

The same discipline applies to innovation. A novel solution, or a lower-cost one, that then fails to reach the design life it was specified to meet is not a productivity gain – the remedial work it triggers will usually cost more than the initial saving. An innovative solution should therefore be assured against the design life sought, not merely against first cost. A deliberately short design life can be the most productive choice. An unplanned one rarely is.

Productivity should be built into the design. The aim is to design for flow, not only for function: to minimise complexity and over-design; to favour standardisation and modularity where they fit; and to ensure that design decisions actively support sequencing, access and constructability rather than leaving the contractor to absorb the consequences.

The single most reliable productivity move at this stage is to secure construction and supply-chain expertise early, so that buildability is shaped while the design is still fluid (PAS 4010, clause 6.3). Digital modelling can be used to simulate productivity impacts before decisions are finalised, while a clear register of design interfaces keeps unresolved coordination issues from hardening into downstream constraints.

Productivity is often lost at consent without anyone noticing, because the people securing planning permission and the people doing the building are rarely the same.

Planning submissions that omit or understate construction logistics such as requirements for materials storage and site access are likely to cause later rework and delays. Equally, stringent consent conditions on factors including working hours, traffic and noise can quietly undermine productivity.

PAS 4010 asks clients to build these realities into submissions, informed by the people who will actually do the work, and to leave enough flexibility for innovation in detailed design and method to survive contact with the conditions imposed (PAS 4010, clause 6.2.3). Engaging regulators early, rather than presenting them with a finished position, is usually more productive.

The productivity gains here come from reliable planning and flow.

Collaborative planning helps every discipline to commit to a schedule that everyone believes in, while readiness reviews ensure that the required information, interfaces, resources and approvals are in place before each major work stage begins.

Real-time production control catches problems before they escalate (PAS 4010, clause 6.4), while standard indicators such as percent plan complete, rework and labour utilisation give a shared view of performance. The data captured is the raw material for both intervention now and better baselines in future.

Productivity does not stop at handover. An asset’s service life is where whole-life value is realised or lost and where the gap between what was predicted and what was delivered becomes clear.

Capturing productivity data at handover, conducting structured learning reviews and feeding lessons back into future projects is what turns a single good outcome into a repeatable one.

Learning is discussed here alongside operation because an asset’s service life offers the clearest evidence of what worked well and what didn’t, but in truth learning runs across all lifecycle stages. The value comes from identifying lessons continuously and, crucially, re-applying them (PAS 4010, clause 8).

PAS 4010 assigns responsibilities to each member of the value chain in proportion to its influence over productivity (see figure 1, below, which shows which parties are covered by the specification’s requirements).

The logic is that productivity improvement is a shared endeavour: everyone contributes, but in different ways. But one requirement applies to all. Every value-chain member shall identify the productivity constraints, risks and opportunities within its scope and communicate these to the client for inclusion in the SPM at every lifecycle stage (PAS 4010, clause 4.1.1).

This is the mechanism that turns the knowledge held at the edges of a project into something the client can act on. It works only if people are confident that their input will be heard.

PAS 4010 does not mandate any procurement route or form of contract – it is a specification, not a contract. But the commercial conditions a client sets and passes on through the supply chain do much to determine whether the specification and the SPM can be followed in practice. Collaborative, outcome-aligned arrangements enable the behaviours that productivity depends on, whereas adversarial, lowest-price ones tend to discourage them.

The right procurement and contractual approach therefore sits alongside PAS 4010 rather than being prescribed by it.

Clients assume the central role in PAS 4010. They commission the work, set the scope, let the contracts, establish the governance and shape the culture. Each of these activities represents a productivity lever.

The client’s core responsibilities are to:

• Own the SPM and ensure that it is developed collaboratively with the value chain (PAS 4010, clause 4.1.2).
• Set clear productivity objectives aligned with organisational strategy and whole-life value (PAS 4010, clause 4.3.2).
• Embed productivity requirements into procurement, including expectations for collaboration, data, planning and reporting. Crucially, this needs to happen before the market is engaged, so that the SPM shapes procurement instead of chasing it (PAS 4010, clause 5.2).
• Establish governance that enables timely decisions, early escalation and transparent performance management (PAS 4010, clause 4.2.2).
• Make information available – baselines, constraints, risks and assumptions – so that others can act on it (PAS 4010, clause 6.2.1).
• Monitor performance against agreed targets and ensure that lessons are identified, shared and applied (PAS 4010, clauses 7.2.2 and 8.2).
• Create the cultural conditions, including psychological safety, that enable teams to raise concerns early, challenge assumptions constructively and innovate (PAS 4010, clause 4.3.2).

The thread running through all these responsibilities is that clients influence behaviour across the value chain more than any other party. When a client treats productivity as a genuine priority – funding it, asking about it, rewarding it in procurement – suppliers respond. When it is present in a client’s documents but absent from its discussions, suppliers notice that too. Effective leadership is not a soft add-on here; productivity depends on it.

Members of the Infrastructure Client Group (ICG) have agreed a set of Client Commitments for Productivity Improvement, to accelerate the adoption of PAS 4010 and demonstrate leadership across the sector. This initiative mirrors the one that boosted uptake of PAS 2080, where a collective commitment by major infrastructure owners created consistent expectations across the market.

ICG members have committed to:

• adopt PAS 4010 and lead visibly on productivity across their portfolios;
• embed productivity capability into procurement, so suppliers are chosen and incentivised on their contribution to productivity outcomes;
• include explicit productivity requirements, including PAS 4010 compliance, in project and programme documentation;
• assess team performance against PAS 4010 as a benchmark for governance, behaviour and delivery discipline; and
• share experience, learning and performance data to support wider adoption and benchmarking.

Each member will report annually on progress, enabling the ICG to publish a collective summary from 2027 onwards – the same annual reporting discipline that underpinned PAS 2080’s success.

Acting collectively, clients can create the conditions for consistent, measurable productivity improvement across UK infrastructure and ensure that PAS 4010 is widely adopted as an industry standard.

Designers turn a brief into a buildable, efficient solution. Their decisions influence the productivity of everything downstream. They are responsible for embedding productivity into design – buildability, standardisation, material efficiency – and for identifying and managing design interfaces, so that unresolved coordination issues do not become someone else’s constraint later (PAS 4010, clause 6.3).

PAS 4010 also asks designers in leadership roles to challenge prescriptive specifications, guidance and requirements where doing so could lead to a more productive solution, recording the basis for each challenge (PAS 4010, clause 4.3.3). Much sector waste is locked into old specifications that no one has revisited in years. Designers are often the first to see this and PAS 4010 explicitly invites them to highlight it.

Contractors lead the planning and execution of the works, converting the design into reality under real-world constraints. They are responsible for developing detailed productivity plans, coordinating subcontractors, managing interfaces and ensuring that data and reporting support good decisions.

Two duties stand out: PAS 4010 asks contractors to plan and deliver enabling works with realistic buffers rather than optimistic sequencing; and to run readiness reviews before major work stages, confirming that the technical, logistical and information prerequisites are in place first (PAS 4010, clause 6.4). The readiness review is one of the highest-return practices in the specification, particularly in a constrained-access environment where a failed start is enormously costly.

Subcontractors and suppliers bring the specialist knowledge, labour, materials and products on which delivery depends. Their responsibilities are to provide accurate, accessible data on performance and resource use; participate in collaborative planning; and identify opportunities to improve productivity within their scope, which includes giving feedback on construction methods and materials (PAS 4010, clauses 6.5 and 7.2.5).

Where standardisation, offsite manufacture or automation would improve whole-life productivity, subcontractors and suppliers are asked to either support this or provide evidence to show why it is not viable. Early and honest specialist input is the recurring theme, but this will play out only if the contractual and cultural conditions allow it.

PAS 4010 is non-prescriptive by design. It sets out what good productivity management requires, but does not mandate any particular method, tool or approach for achieving it. This guidance takes the same stance. The approaches described below are well established in infrastructure and beyond, each with a proven record. None is required by PAS 4010, none is universally right and most work best in combination.

The point is not to adopt a method wholesale, but to pick the parts that address the specific constraints on a project and apply them on the right scale. Using a method because it is fashionable, or because someone on the team likes it, is a reliable way to add cost without adding value. It should be chosen because it attacks a real problem – that is the only good reason.

The approaches fall into a few broad families.

This is the most influential body of thought on delivery productivity. It rests on a single idea: a project is a production system whose output depends on the smoothness of its whole workflow, not the speed of any one part. Pushing every trade to go as fast as possible tends to create bottlenecks and rework. A steady, predictable flow is more productive, generating fewer defects.

Several established tools sit within this family:

• The Last Planner System and collaborative (“pull”) planning. Developed through the Lean Construction Institute, this is a way of planning in which the people who will do the work base their commitments on what resources, information and access they need, and on what will be available to them when required, rather than being dictated to by a master programme. This method highlights the real prerequisites for each activity weeks before they become constraints. It maps directly on to PAS 4010’s collaborative planning duties (PAS 4010, clause 6.4).
• Takt planning. Borrowed from manufacturing, takt sets a steady “drumbeat” – the pace at which work moves through a sequence of zones to meet the overall deadline – and calibrates each trade to that rhythm rather than to its own maximum speed. It is especially powerful for repetitive and linear works, such as renewals, mains rehabilitation or tower erection.
• Theory of constraints. Developed by Dr Eliyahu Goldratt, this holds that the throughput of any connected system is governed by its single main bottleneck, so improving anything other than that constraint does not help – and may even worsen matters. Its discipline of finding and tackling the crucial bottleneck is a practical way to focus effort. This aligns with PAS 4010’s emphasis on identifying and closely managing productivity constraints (PAS 4010, clause 6.4).
• Supply and flow control. This method focuses on getting the right resources to the right place at the right time. It pulls them to the site when they are needed, rather than pushing them there early, where they tie up cash and space.
• The seven wastes. Using the mnemonic TIMWOOD, this names seven categories of non-value-adding activity – transport, inventory, motion, waiting, overproduction, over-processing and defects – as a checklist for spotting waste. It offers a shared vocabulary for the waste-reduction principle that runs through PAS 4010, without the specification mandating this or any other method.

“Production system design” is the term increasingly used for the discipline that brings these methods together. Its purpose is to determine how work will flow before the detailed programme is produced. Practitioner texts developing these ideas for UK infrastructure include Todd Zabelle’s Built to Fail and Dr Martin Perks’ Productivity by Design, alongside the foundational literature on lean techniques and the theory of constraints.

The connection between all these approaches and PAS 4010 is consistent: they offer practical ways to meet its lifecycle delivery requirements, particularly through collaborative planning, critical-path management and readiness reviews (PAS 4010, clause 6.1).

A second family of methods addresses productivity at source – in what is designed and how it is made.

Design for manufacture and assembly (DfMA) and offsite construction. These methods move work from constrained, weather-exposed sites into controlled factory conditions, improving quality and accelerating delivery. PAS 4010 asks teams to assess these options and justify non-adoption with evidence rather than defaulting to traditional methods (PAS 4010, clause 6.1), mirroring the government’s expectation in its Construction Playbook.

Value engineering and value management. This is a structured, function-focused way of asking whether the same outcome could be delivered more productively over the whole life – changing the scope, method or material – without losing performance. This is the “switch” tier of the productivity improvement hierarchy in action (PAS 4010, clause 4.1.1). The HS2 reinforced-soil abutment case study in section 11.1 is a clear example of it.

Standardisation and design for repeatability. This is where assets and components are designed so they can be produced and installed repeatedly, enabling learning and efficiency gains over time, rather than treating every element as bespoke.

A third family of methods is concerned not with how work is done, but with how realistically it is planned and measured.

• Reference-class forecasting. This was developed from the work of Daniel Kahneman, Amos Tversky and Bent Flyvbjerg. It estimates the cost and schedule of a project by comparing it with a relevant set of similar completed projects – its reference class – countering the optimism bias that affects almost all internal estimates. The specification recognises that it can be a useful tool in establishing achievable budgets and schedules and in setting credible baselines (PAS 4010, clauses 5.2.1 and 7.1). Its value depends on the size and comparability of the reference class. Using it when a sufficiently large set of similar projects does not exist can mislead rather than illuminate. It should therefore be applied where the data genuinely supports it.
• Benchmarking and data-driven baselines. This is about using historic and peer performance data to set baselines that reflect good practice, so that claimed productivity gains are measured against a credible starting point rather than an optimistic one (PAS 4010, clause 7.1.2).

New materials, tools and delivery models can save time on a project and reduce its costs, risks and emissions – sometimes dramatically. But such innovation happens only when organisations have the right governance, information and culture to try new things safely and confidently. Without this foundation, even proven solutions can stall, because no one can see clearly enough, decide quickly enough or carry the risk comfortably enough to say yes.

This is the foundation that PAS 4010 provides. By establishing a structured, evidence-based approach to managing productivity, it removes much of the uncertainty, fragmentation and reactive decision-making that keep good ideas on the shelf. The specification does not prescribe innovation; it does not need to. It creates the conditions in which innovation becomes a normal, managed part of delivery rather than a heroic exception.

The barriers are well known to anyone who has tried to introduce something new to a live project. Decision-making is fragmented, so no one feels able to commit. It’s unclear who carries the risk, so the safe answer is no. Requirements shift and design changes arrive late, so there is never a stable base to build on. Information and assurance are inconsistent, so confidence never develops. Commercial incentives reward short-term certainty over long-term value. Constraints and opportunities are hard to spot, while specialists are engaged too late to shape the decisions that matter.

Together, these barriers create a powerful bias towards “the way we have always done it”, even when everyone in the room suspects that a better way exists. PAS 4010 addresses each of these directly.

The specification aims to overcome barriers to innovation from several directions:

• By requiring teams to analyse constraints, risks and opportunities at the outset, it creates space for alternatives – be they different materials, modularisation, offsite manufacture or new methods – to be considered before design decisions lock in inefficiency (PAS 4010, clause 4.1.1).
• By mandating collaborative development of the SPM, it brings clients, designers, contractors and suppliers together early, so specialist knowledge shapes solutions while they are still fluid (PAS 4010, clauses 4.1.2 and 4.2).
• By asking clients to define clear processes for assessing and approving more productive or innovative proposals, it removes the single most common reason why good ideas are blocked: that people feel unable to say yes to them (PAS 4010, clauses 4.1.2 and 4.2).

It also promotes innovation in other ways:

• By building innovation into existing assurance processes, it enables novel approaches to be assessed fairly in proportion to the risks they pose, rather than being treated as inherently risky simply because they are new (PAS 4010, clauses 4.2 and 5.2).
• The specification’s emphasis on baselines, targets and monitoring gives teams the evidence to evaluate an innovation objectively, rather than arguing about it on instinct (PAS 4010, clause 7).
• Its learning requirements ensure that an innovation that’s proven once can be shared and applied elsewhere, rather than reinvented each time (PAS 4010, clause 8).

PAS 4010 gives teams the assurance and evidence to adopt more productive solutions with confidence, but confidence that a given solution works is not the same as confidence that it has been introduced responsibly. For that, PAS 440 (Responsible innovation) provides a framework for anticipating and managing the wider risks and impacts of innovative products, processes and technologies before they are adopted. This is particularly useful for early-stage or disruptive innovations, where the productivity case is strong but the broader implications are less well understood. PAS 4010 itself points to it in the note to clause 4.1.1(a): value-chain members identifying and adopting innovative productivity solutions should refer to PAS 440.

PAS 4010 is agnostic about the form innovation takes; it simply makes adoption more likely. Innovation might involve trying new materials, methods, technologies, delivery models or commercial arrangements. The common thread is that the SPM gives teams a structured, evidenced way to evaluate and adopt these solutions, rather than relying on the conviction of a single champion.

Organisations can use PAS 4010 deliberately to support innovation. They can do this by:

• including innovation opportunities explicitly in the analysis of productivity drivers;
• using the SPM to create early engagement windows with suppliers, before constraints harden;
• setting productivity-linked targets that reward new methods rather than penalising the risks of trying them;
• using readiness reviews to test and refine innovative approaches before committing to them;
• applying production-based indicators to measure their impact; and
• identifying, sharing and applying lessons, so that a success in one area becomes the default elsewhere.

This shifts innovation from a gamble to a managed, evidenced process.

Infrastructure projects vary enormously by scale, complexity, risk, delivery model and regulatory setting. PAS 4010 is designed to work across that range. A small water scheme and a major rail-corridor upgrade both need to manage productivity deliberately. They differ in how much structure is proportionate to the task. The aim is never to create bureaucracy. A small project with a handful of targets, a three-page productivity plan and monthly reviews can comply with the specification. A major programme will need considerably more than that. PAS 4010 accommodates both. The guiding principle is simple: as light as possible, but as robust as necessary.

Scale is the most obvious axis of proportionality and the clearest way to see how the same requirements expand and contract.

On small projects (worth less than about £10m), a minimum viable SPM is enough. That could be a short productivity-drivers workshop, a two- to three-page productivity plan, a couple of key targets, a simple dashboard, monthly reviews and a brief log of lessons learnt.

On medium-sized projects (roughly £10m to £250m), the SPM develops into a structured analysis of constraints and opportunities; a fuller productivity plan aligned with procurement; weekly monitoring of key performance indicators; readiness reviews at the stages that matter; and formalised learning reviews.

On major projects and programmes (above about £250m), a comprehensive SPM is warranted. This means extensive productivity diagnostics; integrated governance and reporting; programme-level targets and baselines; digital dashboards and data assurance; cross-project learning systems; and active development of supply-chain capability.

These thresholds are indicative. What matters is matching the weight of the SPM to the scale, complexity and risk profile of the work in hand.

Much UK infrastructure is delivered not through discrete capital projects but through rolling maintenance and renewal programmes commissioned by clients such as Network Rail, National Highways and the major utility companies. In such cases, productivity management belongs in the core operating model rather than standalone project documents.

The proportionate approach is to establish a single SPM that sets common objectives, indicators, information requirements and learning mechanisms across the programme (PAS 4010, clause 4.1.2), while individual schemes run as repeating production cycles. Each scheme will use the same productivity-driver analysis, planning discipline, targets and monitoring, but with lighter documentation and more frequent reviews.

The real benefit here is cumulative improvement. Data from each cycle refines standards, methods and sequencing, so that productivity keeps increasing across the programme and the same lessons don’t have to be rediscovered by each scheme (PAS 4010, clauses 7.1.2 and 8.2).

The sector constraint analysis in this subsection draws in part, with thanks, on Dr Martin Perks’ Productivity by Design (Black Pear Advisory).

Different sectors face fundamentally different productivity constraints. An SPM should reflect the realities of the sector it serves while preserving PAS 4010’s core requirements.

In transport, the main constraint is usually limited access to an operational network. On railways, possession windows govern everything. These cannot be extended at will, so each possession is best treated as a complete production unit planned to its full capacity, with as much preparation as possible moved offsite. On roads, limited overnight and lane-rental access windows compress productive time, while underground utility conflicts are the most common source of unforeseen cost. Comprehensive pre-design utility surveys and traffic-management planning from the optioneering stage will therefore have the most influence on productivity.

In water, the main recurring constraints are long regulatory consent timelines, the need to work on live networks and uncertainty about the condition of assets. Ground and asset investigations undertaken before the design is fixed will pay for themselves many times over. Takt-based scheduling suits the inherently linear and repetitive nature of much of the work, while early engagement with regulators can convert consent conditions from a downstream surprise into a design input. The sector’s five-yearly cycle of asset management plans also makes carrying productivity baselines forward from one period to the next essential, so that the sector can keep building on its learning rather than restarting each time.

In much of the energy sector, particularly power transmission, outage windows act like rail possessions. The biggest single constraint is usually the process of obtaining development consent orders. Running consenting, land-rights acquisitions and environmental surveys during the design process rather than after it helps to address this constraint. As the grid expands for net zero, offsite-manufactured substations offer a significant productivity improvement too.

In nuclear, the defining constraints are regulatory. The Office for Nuclear Regulation’s approval process governs design changes, methods and commissioning, with safety-critical components carrying lead times measured in years. Avoiding late design changes is more important here than it is anywhere else, because each significant alteration can trigger a safety-case review. For these reasons, project teams should plan a modular construction strategy from the outset, engage with the regulator formally at every major milestone and actively develop capacity in the supply chain.

The same logic extends to gas, telecoms and other linear systems such as flood defences and district heat networks: identify the dominant constraint, calibrate the project’s tools to it and keep working in accordance with the underlying PAS 4010 requirements. The principles are universal; their application is not.

ALBs typically operate within statutory frameworks, multi-year investment cycles and well-established assurance systems. In an ALB environment, integration is preferable to addition: PAS 4010 can be integrated into existing stage-gate processes, investment decision frameworks and regulatory reporting systems, with the SPM strengthening existing governance and assurance structures (PAS 4010, clause 4.2.1). The key throughout is alignment, not duplication – productivity management embedded in the systems an ALB already uses, not bolted on beside them.

A project’s delivery model will shape how the SPM is implemented. Under a design and build arrangement, the SPM should be integrated into design development and buildability reviews. In an alliance, it should be embedded in joint governance and shared incentives, so that productivity sits naturally within the collaborative commercial model. Under a construction management approach, the emphasis will be on engaging subcontractors in developing the SPM, since they possess much of the relevant knowledge. And in public-private partnerships and long-term concession models, the SPM should align with long-term performance outcomes, so that whole-life productivity is built directly into the commercial structure.

The following hypothetical case studies show how PAS 4010 can be applied from need through to learning. Demonstrating the specification’s proportionate use in different contexts, the first covers a major multi-project programme and the second focuses on a small scheme. They are illustrative and composite – built to show how the pieces fit together – and the productivity figures in them are indicative.

For real case studies, see section 11.

The context. A £600m programme set out to improve capacity, reliability and journey times on a 60km section of busy main line. It entailed track renewals and realignments; the replacement of signalling and interlocking systems; station upgrades; bridge strengthening; and work on drainage, power and telecoms. Running in a live operational environment during tight access windows, it involved dozens of interdependent projects and several delivery partners on a multi-year framework, all contributing to the same outcome.

The challenge. Productivity was being lost systemically rather than in any one place. Late design changes, access restrictions and inter-discipline clashes combined to keep plan reliability, measured by percent plan complete (PPC), at 48%. There was a high level of rework, particularly at the interfaces between the signalling system and other structures. The preparation of sites for work during possessions was slow; the performance of contractors varied across the programme; and lengthy assurance processes created bottlenecks at crucial moments. The task was to lift productivity across the whole corridor, not project by project.

Applying the SPM. The client established a programme-level SPM as the unifying framework, sitting above proportionate project-level strategies for each scheme (PAS 4010, clause 4.1.2). It began with a cross-programme diagnostic exercise that mapped the production system for the main types of work and identified the systemic constraints: design approvals, access planning, logistics, assurance and utilities. From that came a single set of programme-wide objectives and indicators used by every contractor, embedded into the framework agreements so that productivity was a contractual expectation rather than an aspiration (PAS 4010, clause 5.2). It also introduced a programme governance structure that required monthly productivity reviews chaired by the client’s programme sponsor.

The plan in practice. The productivity plan focused on improving coordination, reliability and readiness. All disciplines planned together, holding weekly reviews to identify emerging problems before they disrupted delivery. Readiness reviews took place before every possession to confirm that the required approvals, resources and access were secured in good time. Standard methods were used wherever possible; equipment and materials were coordinated centrally; and interfaces between disciplines were managed actively to prevent delays and rework. Progress was monitored closely during possessions so that problems could be identified and tackled quickly. Learning reviews after each possession fed directly into improvements across the wider programme (PAS 4010, clauses 6.4 and 8).

Targets, monitoring and outcomes. Programme targets were set against baselines drawn from previous corridor upgrades. Among these were lifting PPC above 75%, cutting rework by 20%, improving access utilisation by 15% and reducing possession overruns by 40% (PAS 4010, clause 7.1). Monitoring featured daily possession reports feeding a central dashboard and weekly progress reviews involving each delivery partner, with only exceptional problems raised for intervention at senior level (PAS 4010, clause 7.2).

After 24 months, the illustrative outcomes were: PPC up from 48% to 79%, rework down by 19%, possession overruns down by 42% and access utilisation up by 17%. By this time, contractors were performing more consistently, work had become easier to plan and a markedly stronger culture of learning had developed.

The lesson. Productivity in a large programme is won at programme level, not project by project. An SPM at that level gives consistency and shared expectations. Conducting readiness reviews and avoiding late design changes offer the biggest productivity gains in a constrained-access environment, while daily production control turns a good plan into a good possession.

These case studies draw on actual projects in major UK infrastructure sectors to show productivity improvement in practice and provide evidence of it, not just illustration. Each follows a common structure, so they can be read and compared easily, and each closes by mapping back to PAS 4010 to show how the same outcome would sit within an SPM today.

HS2 Ltd

At a glance. On HS2 phase 1 main works civils contract C23, near Quainton in Buckinghamshire, the team replaced a Network Rail overbridge. The original design used fully integral reinforced-concrete abutments and wing walls on deep piles. The adopted alternative used reinforced-soil abutments (featuring polymer geogrids) and wing walls on shallow foundations. The work spanned design, value engineering and construction. HS2 was the client and a joint venture between Eiffage, Kier, Ferrovial Construction and BAM Nuttall (EKFB) was the main works contractor. Arcadis Setec COWI was the designer and specialist input came from Tensar, Coffey Geotechnics and Geofem.

The productivity challenge. The original design required 55 large-diameter reinforced-concrete piles up to 23m deep, with extensive formwork, heavy reinforcement and long curing periods. That meant long construction durations; high embodied carbon; complex sequencing and access constraints; and risks associated with installing deep foundations in Oxford clay. The team set out to reduce programme duration, complexity, cost and carbon impact while maintaining structural performance over a 120-year design life.

What was done. A collaborative value engineering exercise identified that the ground conditions allowed a shallow-foundation solution if unsuitable soils were replaced – and that a reinforced-soil system could eliminate piling. The team excavated 3.7m of unsuitable alluvial soil, replaced it with granular fill and built near-vertical reinforced-soil walls using modular blocks and geogrids, supporting the bankseat directly on the reinforced-soil structure. UK-made components and dry-laid construction eliminated curing time, formwork and reinforcement cages. Finite-element analysis was used throughout to assure performance and build confidence in a non-traditional solution. The decisive enabling factor was a collaborative culture in which the default solution could be challenged and specialist suppliers empowered to lead on the alternative design.

Outcomes. The reinforced-soil solution delivered a 66% reduction in embodied carbon (663t of CO₂e versus 2,002t of CO₂e for the original piled option) alongside a 33% cost saving and significant (unquantified) programme savings from eliminating piling, curing and formwork. Finite-element analysis confirmed acceptable settlement (28mm vertical, 13mm horizontal) and geogrid strains below 1% over the design life. Qualitatively, the team noted reduced construction risk; improved safety from removing deep excavation and heavy lifting; reduced site congestion and fewer movements of spoil and concrete; and greater use of UK-made materials.

Lessons learnt. Reinforced-soil abutments are a viable alternative to piled reinforced-concrete structures, even in major rail applications. Early engagement with specialist suppliers unlocks the largest gains. Finite-element analysis is what builds confidence in non-traditional solutions. Modular systems reduce programme risk and improve flow.

Mapping to PAS 4010. An SPM would have highlighted piling as a major productivity constraint at the optioneering stage (clause 4.1). The reinforced-soil alternative is a textbook application of the “switch” tier of the improvement hierarchy and of value engineering (clause 4.1.1). The collaborative, challenge-positive culture exemplifies the leadership requirements (clause 4.3). The early engagement of specialist suppliers reflects the specification’s procurement and design-stage duties (clauses 5 and 6.3). The carbon and cost analysis embodies the effectiveness and efficiency definitions at the heart of PAS 4010 (clause 0.2).

Karl Rourke

At a glance. Funded by the Department for Transport (DfT) under ADEPT’s Live Labs 2 programme, East Riding of Yorkshire Council led nine partner authorities in testing whether street lighting could be safely removed from high-speed corridors and “conflict zones” – roundabouts, junctions and crossroads – and replaced with passive visual guidance. The work spanned need analysis, design, delivery and live operation across 17 test sites on the A1079 and A164, alongside partner sites nationwide. Partners included Local Transport Projects (road safety and design), the University of Leeds (carbon and cost modelling) and Transoft Solutions (AI monitoring). The project received £3.24m from the DfT and about £2m of partner match funding.

The productivity challenge. Every year, the UK’s 7.2 million streetlights cost more than £1bn in energy and emit a million-plus tonnes of CO₂. The sector’s default response for a decade had been to retain the lighting but switch to LED bulbs: an “improve” choice that left the asset, and most of its whole-life cost and carbon impact, in place. This prompted the council to ask: is lighting really needed on the high-speed corridors and conflict zones that existing guidance says must be lit? Answering this question credibly meant overturning a deeply held safety assumption and producing evidence robust enough for a risk-averse sector to act on.

What was done. The project worked the productivity improvement hierarchy in order:

• Avoid. Each site underwent a National Highways GG 104 safety risk assessment and 10-year collision review. Lighting was removed where the evidence supported that intervention. Three roundabouts were kept lit because their geometry warranted it.
• Switch. In places where visual guidance was still needed, grid-powered lighting gave way to passive and solar alternatives: solar road studs, retroreflective signs and high-performance markings.
• Improve. Where pedestrians genuinely needed lighting, it was retained but improved through the use of footway-only columns made of 80% recycled aluminium, mounted at 3m to eliminate light spillage on to the roadway. A decision tool built with the university compared options over the whole asset life. To assess this solution’s safety performance, a bespoke thermal-imaging AI system tracked driver behaviour and near misses.

Outcomes. Over the 10-year assessment period, the designs cut CO₂ emissions by 25% against like-for-like replacements, improving to 36% with value engineering, and saved £1.24m. Three-quarters of the sites recorded reduced speeds – more than 10% lower for motorcyclists in one location – and the number of night-time collisions fell even as the wider area’s total rose. Removing carriageway lighting and providing a single lit crossing of the A1079 in the village of Hayton incentivised pedestrians to cross the road at this point after dark rather than elsewhere along that stretch. Such findings have been influential: the Institution of Lighting Professionals (ILP) is preparing technical guidance and the BSI is exploring the principles for future standards.

Lessons learnt. The largest gains came from reframing the need, not optimising the default solution. Robust evidence, including risk assessment, live monitoring and whole-life modelling, makes an “avoid” intervention credible in a risk-averse sector. The project showed that the right answer is rarely uniform – avoid wherever possible, switch if necessary and improve if there’s a compelling case. The team also learnt to base whole-life comparisons on the shortest-lived asset, revisiting the decision at each replacement point rather than fixing a 40-year case at the outset.

Mapping to PAS 4010. Reframing the need is applying “avoid” at the stage of greatest leverage (clauses 6.2.2 and 4.1). The passive and solar lighting alternatives exemplify “switch” and the low-carbon pedestrian columns exemplify “improve” (clause 4.1.1), making this a rare instance of the full hierarchy’s application in one scheme. The decision tool and its transparent treatment of uncertain baselines reflect PAS 4010’s target- and baseline-setting duties (clauses 7.1 and 7.1.2). The live AI monitoring embodies its data and measurement requirements (clause 7.2), while the cross-authority learning now informing ILP and BSI guidance exemplifies continuous improvement (clause 8). Throughout, carbon, cost and safety performance improved together – illustrating the specification’s definition of productivity as effectiveness plus efficiency (clause 0.2).

How can an organisation demonstrate conformity with PAS 4010 and say so publicly? In principle, its conformity is established by assessment against the specification’s requirements, as with any other management standard. PAS 4010 deliberately leaves the detail to established assessment practice.

This question matters because a credible conformity claim is one of the most visible ways to show leadership on productivity – and clients are increasingly using it as a differentiator in supplier selection.

This section explains the three routes to a claim, what good supporting evidence looks like and how a claim should be worded.

The precedent is PAS 2080. Collective client commitment, backed by visible certification, aided its widespread adoption. Once major clients began achieving and publicising conformity, a consistent expectation spread throughout the supply chain.

HS2 made early and prominent use of this approach: in November 2020 it became the first infrastructure owner in the UK transport sector to achieve PAS 2080 accreditation, signalling its leadership on decarbonisation and encouraging its suppliers to innovate.

A PAS 4010 conformity claim offers the same mechanism for productivity: a clear, externally recognisable statement that an organisation manages productivity to a defined standard. For infrastructure owners, it reinforces the ICG client commitments set out in section 6.1. For suppliers, it is a selling point when bidding for work.

Conformity with specifications is normally claimed via one of three routes, which differ in the degree of independent assurance they carry – and therefore in cost, effort and the confidence that others will place in the claim:

• Accredited third-party certification: via assessment routes to be developed by certification bodies accredited by the United Kingdom Accreditation Service. This will provide the highest level of independent assurance and be the strongest basis for claiming conformity.
• Independent validation: assessment by an independent party that is not formally accredited, such as a trade organisation. The assessor should be able to show that it operates to recognised standards of competence, consistency and impartiality, such as those set out in BS EN ISO/IEC 17065. This sits between the other routes in terms of the level of assurance it provides.
• Self-validation: the organisation demonstrates conformity itself, publishes supporting documentation and stands behind that. This is the most accessible route, but offers the lowest level of assurance. Stakeholders might therefore place less confidence in a self-validated claim. If it is challenged, independent verification could be required.

Whichever route is chosen, the claim should be explicit about its scope and the specific clauses to which conformity is claimed.

Two things make a claim credible: a clearly bounded scope and robust supporting evidence. The first means stating plainly whether the claim covers an organisation, a programme or a single project (overstating the scope is a quick way to lose credibility). The second means showing, clause by clause, how the specification’s requirements have been met.

For a self-validated claim in particular, the supporting documentation should set out:

• the scope of the claim;
• summary evidence against each relevant clause of PAS 4010;
• any caveats regarding gaps in, or limitations of, the available data;
• the key stakeholders and roles involved in managing productivity; and
• any planned actions for further improving productivity management.

Approaches to validating evidence and presenting conformity claims can be drawn from established assurance standards such as BS EN ISO 14064-3 and BS EN ISO 14021.

The encouraging point is that an organisation running an SPM as described in section 5 has already produced most of this evidence. The SPM’s objectives, analysis of productivity drivers, plan, targets and baselines, monitoring records and learning logs map directly on to the clauses that a claim must address.

Making a conformity claim is therefore largely a case of distilling what an effective SPM generates as a matter of course. Treating the SPM as the evidence base from the outset makes any future claim far less onerous.