Building the Platform | Part 1 How to Write a Brief That a Platform Can Actually Answer

The brief is where platform thinking either takes off or gets derailed.

Most procurement briefs for SEND capital projects in the UK are built around a single question: what kind of building do we need? They focus on specifics like square footage, number of classrooms, site address, and completion date. These are output specs, which describe a thing. And for a long time, output specs were the right tool for the job - because every project was a separate thing. But that's not the situation now.

Local authorities, multi-academy trusts, and DfE programme managers are facing a different reality. The Schools White Paper has committed £3.7 billion to create 60,000 new specialist places. Inclusion bases are expected in every secondary school. The demand is not just a one-time thing, it's sustained and timetabled. Under those conditions, a brief that describes a building is not just insufficient, it's also counterproductive. Because it doesn't allow the market to offer what it needs to: a repeatable delivery capability.

What an Output Brief Actually Signals to the Market

When a procurement team issues a brief for a specific building on a specific site, it sends a message to the supply chain: treat this as a one-off. Manufacturers read that signal and price accordingly - they absorb design costs, tooling costs, and mobilisation costs into a single contract with no guarantee of follow-on work. Supply chains don't invest in the capacity, systems, or people that portfolio-level delivery requires, because the demand signal doesn't justify it. And then the procurement body wonders why modular construction costs more than expected, or why the programme takes longer than the technology should allow. The answer is in the brief they issued.

The Procurement Act 2023, which came into force in February 2025, gives contracting authorities more discretion about how they design and evaluate procurements. That discretion is an invitation, but most procurement teams haven't accepted it yet. So, what's the distinction that changes everything?

A portfolio-framed brief doesn't ask what building do we need, it asks: what delivery capability do we need to create, and over what programme? That's not just semantics, it's a different commercial signal to the market, and it produces different responses.

Where an output brief produces tenders for a building, an outcome brief produces proposals for a platform - a stable, repeatable system capable of delivering multiple facilities across a defined programme, with costs that reduce and quality that improves as the platform matures. The difference shows up in four specific places within the brief itself.

1. Programme horizon

An output brief specifies a single completion date. An outcome brief specifies a programme horizon - typically three to five years - within which multiple facilities will be required. This change transforms the supply chain's investment calculus. Manufacturers can commit to tooling, installers can commit to trained teams, and design effort can be amortised rather than repeated.

2. Performance requirements versus product requirements

An output brief specifies products: room sizes, material specs, structural systems. An outcome brief specifies performance: acoustic standards, sensory environment criteria, thermal comfort thresholds, adaptability over time. Performance requirements allow the platform to evolve and improve. Product requirements lock it in place.

3. Evaluation criteria

Output briefs are typically evaluated on price and programme. Outcome briefs should weight platform maturity - evidence that the supplier has a proven, repeatable system - alongside the specific project response. Cost-led procurement on frameworks with similar capital projects provides the opportunity to continually improve on unit costs, working collaboratively with the supply chain. That collaborative improvement only happens if the evaluation criteria ask for it.

4. Supply chain continuity provisions

An output brief is silent on what happens next. An outcome brief includes provisions for how the supply chain relationship will be maintained, developed, and governed across the programme. It treats the supplier relationship as infrastructure, not a transaction.

Why This Feels Difficult - and Why That Feeling Is Misleading

Procurement teams often resist outcome-based briefs for two reasons that sound practical but are, in most cases, inherited assumptions rather than genuine constraints.

The first is accountability. Output specs feel safer because they're auditable. If the brief says 450 square metres and the building delivers 450 square metres, the procurement was successful. Outcome specs require judgement - about whether the delivery capability is genuinely mature, whether the platform performs as specified, whether the supply chain relationship is structured for the long term. That judgement feels exposed. But the accountability argument has quietly reversed. In a policy environment where 60,000 specialist places are expected and delivery timelines are visible, failing to build a capable delivery system is the accountability risk. A series of one-off projects that deliver inconsistently, slowly, and at rising cost is not a defensible position. A well-governed platform programme, even if imperfect in its early phases, is.

The second resistance is legal. Procurement teams worry that outcome-based briefs are harder to defend in the event of a challenge. In practice, the new flexibilities within the Procurement Act 2023 are designed to support more sophisticated, relationship-based procurement approaches. The legal landscape has moved, but procurement practice, in most authorities, has not yet followed. So, what's the conversation that needs to happen first? Before a portfolio-framed brief can be written, a conversation needs to happen that most capital programmes do not currently structure. It's not a conversation about buildings. It's a conversation about estate strategy - demand forecasting across a three to five year horizon, site pipeline, programme interdependencies, and the governance model that will oversee delivery across multiple facilities. Without that conversation, even the best-intentioned outcome brief will default back to project logic, because the client organisation has not yet formed a view of what it is actually trying to build at system level.

Building the Platform is a series for procurement leads in local authorities, multi-academy trusts, and DfE programme teams.

Part 2 examines why your supply chain cannot currently scale - and where the responsibility for that sits.

TSL Consult provides modular construction strategy and procurement advisory for education estates.

Modular Construction Sequencing (Part 9): Delivery Blueprint for Scalable SEND Provision - Policy Ambition to Industrialised Estate Capacity

Across Parts 1–8 of this series, we have explored the sequential conditions required for modular construction to mature from accelerated delivery into a true industrialised system.

We began with the structural pressures driving change: the rapid expansion of SEND demand, the evolving expectations of the Department for Education, net zero obligations, and the increasing need for white-labelled delivery ecosystems capable of scaling beyond individual brands.

From there, the discussion progressed through the enabling mechanics:

• sequencing discipline

• platform governance

• commercial architecture

• portfolio strategy

• capital efficiency

  
  

Each part examined one layer of the system.

Part 9 brings them together.

Because the challenge facing education estates is no longer understanding modular construction as a method.

It is deploying it as a governed, investable and repeatable delivery system capable of expanding SEND capacity at national scale.

This article sets out that blueprint.

1. Start with Demand as a Portfolio Condition

The first strategic error in SEND delivery is to treat demand as episodic.

It is not.

The 2026 Schools White Paper established a decade-scale ambition for expanding inclusive provision, specialist environments and mainstream support pathways. The pressure on local authorities and trusts is therefore structural, not temporary.

This matters because structural demand cannot be met sustainably through isolated project responses.

Each new school, unit or resource base should not begin as a standalone capital event.

Instead, demand must be modelled as a portfolio condition, where the estate requires an expandable capacity system rather than individual building solutions.

This is the first principle of scalable delivery.

2. Convert Design into Platform Logic

Part 4 and Part 5 established that sequencing and governance are what transform modular construction from faster site assembly into repeatable manufacturing.

The blueprint principle is straightforward:

Every repeatable SEND requirement should be translated into governed platform logic.

This includes:

• sensory and acoustic room typologies

• therapy and breakout modules

• structural grids

• service spines

• interface tolerances

• digital configuration rules

• 
  

The objective is not standardisation for its own sake.

It is to create stable repeatable conditions from which controlled variation can emerge.

This is how bespoke educational outcomes are achieved through industrial discipline.

3. Protect the Platform Through Procurement

Part 6 demonstrated the fragility of modular systems once they enter traditional procurement structures.

A stable platform can be technically mature and still fail commercially if every competition forces redesign.

The synthesis principle is therefore critical:

Procurement must commission platforms, not repeatedly commission projects.

This means evaluating suppliers on:

• interface governance

• production control

• RCA feedback loops

• platform maturity

• evidence of cost compression across programmes

  
  

Without this, procurement becomes the mechanism that dismantles learning.

With it, procurement becomes the structure that compounds it.

4. Operate at Portfolio Scale, Not Project Scale

Part 7 shifted the discussion from individual projects to estate strategy.

This is the point at which modular delivery becomes industrialisation.

Factories do not industrialise construction.

Portfolios do.

Because only portfolio continuity provides the demand stability needed for:

• production planning

• supply chain resilience

• design amortisation

• installation learning

• data-led optimisation

For SEND expansion, this means local authorities and trusts should move from school-by-school capital logic to rolling estate platform programmes.

The estate itself becomes the production roadmap.

5. Reframe Cost as Behaviour, Not Budget

Part 8 introduced perhaps the most important commercial shift in the entire series.

Traditional delivery asks:

What does this school cost?

Industrialised delivery asks:

Is the platform reducing programme cost over time?

This distinction changes everything.

Capital efficiency in SEND expansion does not emerge from isolated value engineering exercises.

It emerges when:

• design cost is amortised

• manufacturing waste reduces

• installation repetition improves productivity

• risk contingencies compress

• performance data refines future iterations

  
  

In other words, cost becomes a learning behaviour of the platform.

This is how public capital begins to compound rather than simply spend.

6. Establish the Closed Learning Loop

No industrial system matures without a feedback mechanism.

One of the recurring themes across the series has been the weakness of Root Cause Analysis when confined to project registers.

The blueprint requires a closed learning loop:

Design intent → manufacture → logistics → install → deviation → RCA → platform update

This is where SEND estate delivery moves from:

• repeated issue management

to

• controlled capability growth

• 
  

Each completed facility should improve the next.

Without this loop, the system scales inefficiency.

With it, the system scales intelligence.

The Strategic Blueprint

When the nine parts are synthesised, the delivery blueprint is clear.

Policy Layer

Structural SEND demand + White Paper ambition

Technical Layer

Sequenced modular platform + governed interfaces

Commercial Layer

Platform-protective procurement + rolling frameworks

Portfolio Layer

Estate-level capacity programming

Capital Layer

Compounding cost efficiency

Learning Layer

Closed RCA-to-platform evolution

This is the industrialised operating model.

From Faster Buildings to Faster Capacity

The central misconception in modular construction is that the prize is faster building delivery.

It is not.

The strategic value lies in faster capacity creation across public estates.

That distinction matters profoundly for SEND.

Children, families, local authorities and education leaders are not measuring success by volumetric speed.

They are measuring:

• place availability

• quality of environment

• speed to occupancy

• continuity of support

• confidence in future expansion

  
  

The delivery blueprint outlined here aligns modular construction with those outcomes.

The TSLConsult View

The modular sector does not need more isolated innovation.

It needs delivery systems that can absorb policy ambition, protect platform logic, compound capital efficiency and continuously improve estate outcomes.

That is the transition from construction to industrialisation.

And for SEND provision, it may be the only route capable of matching the scale, speed and fiscal discipline now required.

This series began with sequencing.

It concludes with system design.

Because the future of modular SEND delivery will not be determined by who can build fastest.

It will be determined by who can scale governed capacity most intelligently.

Modular Construction Sequencing (Part 8):Capital Efficiency: Industrialised SEND Delivery

How Platforms Change Cost Structures

In Part 7 of this series, we explored the shift from project delivery to portfolio strategy- and how modular platforms enable education estates to scale capacity more predictably.

But scale alone is not sufficient.

For local authorities, trusts and the Department for Education, the fundamental constraint is not simply delivery capacity.

It is capital.

The expansion of SEND provision- including the creation of tens of thousands of additional places- represents a multi-billion pound structural commitment. The question is not just how quickly capacity can be delivered, but how efficiently capital can be deployed over time.

This is where the next transformation occurs.

Because industrialised construction does not just change how buildings are delivered. It changes how capital behaves.

The Limits of Project-Based Cost Thinking

Traditional construction procurement evaluates cost on a per-project basis.

Each scheme is assessed independently:

• capital cost per m²

• total project outturn cost

• value engineering exercises at the design stage

• risk contingencies applied per scheme

This approach creates a familiar pattern.

Each project seeks to optimise its own cost position, often through late-stage adjustments or scope reduction. Lessons learned may inform future schemes, but they are rarely embedded systematically.

Cost improvement is therefore incremental and inconsistent.

More importantly, this model fails to recognise a critical reality:

When demand is structural, cost cannot be optimised at the project level.

SEND provision is not a one-off capital event. It is an ongoing requirement across multiple years, locations and cohorts.

Yet it continues to be delivered as if each facility exists in isolation.

Platforms Reframe Cost as a System

Platform-based delivery fundamentally alters this dynamic.

Instead of treating each project as a discrete cost exercise, platforms establish a repeatable production system where cost is influenced by:

• standardisation of components

• stability of design parameters

• efficiency of manufacturing processes

• continuity of supply chains

• accumulation of delivery data

In this context, cost is no longer a static number assigned at project approval.

It becomes a dynamic characteristic of the system itself.

The Four Drivers of Capital Efficiency

When modular platforms are deployed across SEND provision programmes, four distinct cost advantages begin to emerge.

1. Design Cost Amortisation

In traditional delivery, design effort is repeated for every project.

Even where previous schemes are referenced, each new facility requires:

• architectural reconfiguration

• coordination of disciplines

• compliance checks

• value engineering cycles

A platform removes this repetition.

Core design elements are developed once and reused across multiple facilities. Site-specific adjustments remain, but the underlying system is stable.

Design cost is therefore amortised across the programme, rather than incurred repeatedly.

2. Manufacturing Efficiency

Manufacturing performance improves with repetition.

Stable platforms enable:

• optimised production sequencing

• reduced material waste

• improved quality control

• shorter cycle times

These efficiencies are not theoretical. They are measurable outcomes of operating within a controlled production environment.

However, they only emerge when the platform is protected from constant redesign- a point explored in Part 6.

Without that stability, manufacturing reverts to project-driven variability, and the efficiency gains are lost.

3. Installation Productivity

On-site installation is often treated as a variable cost.

But in platform-based delivery, installation becomes increasingly predictable.

Teams gain familiarity with:

• module interfaces

• connection details

• sequencing logic

• tolerance management

As repetition increases, installation durations shorten, and risk reduces.

This has a direct impact on:

• preliminaries

• programme duration

• disruption to operational school environments

Time, in this context, becomes a controllable cost variable.

4. Risk Reduction and Contingency Compression

Traditional construction pricing includes significant allowances for risk.

These contingencies reflect uncertainty in:

• design coordination

• site conditions

• supply chain performance

• programme integration

Platform-based systems reduce this uncertainty.

When design, manufacture and installation are governed within a stable framework, variability decreases.

Over time, this allows:

• more accurate cost forecasting

•reduced contingency allowances

• improved budget confidence

This is particularly important for public sector clients managing multi-year capital programmes.

The Misconception of "Higher Upfront Cost"

A common critique of modular construction is that it can appear more expensive on a like-for-like capital comparison.

In many cases, this observation is correct- at the project level.

But it is also incomplete.

Because it ignores the effects of:

• design reuse

• manufacturing optimisation

• programme acceleration

• reduced rework

• compounding learning

When evaluated across a portfolio, these factors often outweigh any initial cost differential.

The question, therefore, is not:

Is this project cheaper?

But:

Does this platform reduce the total cost of delivering the programme?

This is a fundamentally different evaluation.

Capital Efficiency at Portfolio Scale

When SEND provision is delivered through a platform operating across multiple sites, cost behaviour begins to change in more strategic ways.

Predictability

Cost certainty improves as variability reduces.

Repeatability

Budgets become more reliable across successive schemes.

Scalability

Additional facilities can be delivered without restarting cost optimisation from first principles.

Transparency

Data from previous projects informs future investment decisions.

These characteristics are hallmarks of industrial systems.

They are rarely achieved through isolated project delivery.

Aligning Capital with Policy Ambition

The scale of SEND expansion set out by the Department for Education requires more than funding allocation.

It requires a delivery model capable of converting capital into capacity efficiently and repeatedly.

Without this, two risks emerge:

1. Cost escalation as each project absorbs inefficiencies independently

2. Delivery lag as procurement and design cycles repeat

   
   

Platform-based delivery offers a route to mitigate both.

But only if governance (Part 5), procurement (Part 6) and portfolio strategy (Part 7) are aligned.

Capital efficiency is not created by platforms alone.

It is created by systems that allow platforms to operate effectively over time.

From Cost Control to Cost Behaviour

The final shift is conceptual.

Traditional construction focuses on cost control- managing expenditure within individual projects.

Industrialised delivery focuses on cost behaviour- shaping how costs evolve across a system.

This distinction is critical.

Because in a programme as large and sustained as SEND provision, the objective is not simply to deliver within budget.

It is to ensure that each successive investment performs better than the last.

That is the essence of capital efficiency.

The Next Step

Across this series, the argument has developed from sequencing and governance through to procurement and portfolio strategy.

Part 8 extends that logic into capital.

The conclusion is clear.

Modular construction becomes truly transformative not when it builds faster- but when it enables capital to be deployed more intelligently across time.

The final part of this series will bring these elements together into a delivery blueprint for scalable SEND provision.

Because the challenge is no longer understanding modular construction.

It is implementing it as a system.