The seven steps map onto the ten lifecycle stages used across the pipeline

The track above shows a project at stage six, market consultation, which is step 05 of the Accelerator. Every project page on this site carries the same track, so a city can see exactly where it stands relative to comparable work elsewhere in Europe.

The process

What each step produces, and how each step fails.

Listing the failure modes is deliberate. Most of them are recognisable, and most of them are cheaper to avoid than to correct.

01

City Challenge

The city states the problem in its own terms. ESCA structures it into a form that policy, funding and market actors can act on.

What this step produces

  • A structured challenge statement
  • An initial instrument scan
  • A view on whether a project is the right response at all

Where it goes wrong

The city arrives with a solution it has already chosen and asks for it to be justified.

Lifecycle stages 01 Challenge Identified

02

Project Definition

Scope, beneficiaries, intervention logic and success measures. What will exist at the end, and how it will be judged.

What this step produces

  • Scope and boundaries
  • Beneficiaries and intervention logic
  • Success measures agreed before anything is built
  • An order-of-magnitude cost

Where it goes wrong

Success measures are written after the funding application, to match what was promised.

Lifecycle stages 02 Concept, 03 Feasibility

03

Funding & Investment Route

Which instrument fits, what it requires, what it excludes, and what the city has to be able to demonstrate.

What this step produces

  • Instrument selection with reasoning
  • What the instrument requires the city to evidence
  • A financing structure where grant alone is insufficient
  • A decision timetable the city can actually hold

Where it goes wrong

The instrument is chosen because a deadline is close rather than because it fits.

Lifecycle stages 04 Funding Preparation, 05 Funding Secured

04

Technical Requirements

Functional requirements, interoperability, data governance and standards, written to keep the market open.

What this step produces

  • Functional requirements
  • Interoperability and data governance conditions
  • Standards and compliance obligations
  • Requirements written to keep the market open

Where it goes wrong

Requirements are copied from a supplier document, which quietly writes the competition out.

Lifecycle stages 05 Funding Secured

05

Market Dialogue

Open, recorded, documented engagement with suppliers before specifications are fixed. Equal access, no private channels.

What this step produces

  • A published, open consultation
  • Recorded sessions and published answers
  • A revised specification with a note of what changed and why

Where it goes wrong

Dialogue happens in private meetings, which taints the procedure and can invalidate it.

Lifecycle stages 06 Market Consultation

06

Procurement Roadmap

Procedure, lots, award criteria and contract model, aligned to the funding conditions and the delivery timetable.

What this step produces

  • Procedure selection
  • Lot structure
  • Award criteria and weightings
  • A contract model matched to the funding conditions

Where it goes wrong

Lots follow the departmental structure of the administration instead of the technical structure of the work.

Lifecycle stages 07 Procurement Preparation, 08 Procurement

07

Delivery Monitoring

Indicators agreed at definition are tracked to operation, so the outcome can be evidenced rather than asserted.

What this step produces

  • Indicators tracked from definition to operation
  • A reporting rhythm that survives a change of administration
  • Evidence that can be published

Where it goes wrong

Monitoring is designed at handover, by which point the baseline is gone.

Lifecycle stages 09 Implementation, 10 Operational

Boundaries

What ESCA does, and what it never does.

ESCA does

  • Structure the challenge and define the project with the administration
  • Assess which instruments fit and what each requires
  • Help draft functional requirements that keep the market open
  • Design and convene open, recorded market dialogue
  • Advise on procedure, lots and award criteria
  • Set up monitoring that outlives the project team

ESCA does not

  • Recommend, introduce or endorse suppliers
  • Bid for the work it helped specify
  • Hold private conversations with suppliers about a live project
  • Write a specification around a product
  • Run the procurement procedure on behalf of the authority
  • Take a commission, success fee or share of contract value

Start the sequence

Accelerate a Project

Cities normally enter at step 01 with a challenge rather than a project. Entering later is possible, and common, but the earlier steps then have to be reconstructed.