Research

White paper · ProcurementOnshore and offshore, UK and Europe

Procurement without the pauses

Winning the round starts the clock. Every week a pack waits between desks is a week the project cannot get back.

YT
Yorik Tisseau, Ignis Leadership
· about 12 minutes to read

Download the PDF

PDF · 12 pages

Download the white paper

The article on this page stays open. Add your work email to get the PDF.

At a glance

Most procurement time is lost between the gates, not inside them.

Five messages for your leadership team.

1

Winning starts the clock.

A CfD milestone, a grid offer to accept and equipment with long lead times all keep running while the team works.

2

The pauses sit between gates.

Packages redrawn, questions asked twice, offers that cannot be compared, and a lender pack rebuilt at the end.

3

Process first, data second, agents third.

Map how you procure today, fix the two biggest pauses and their causes, build one record, then add agents.

4

One record, every document.

Comparison, contract, model and lender pack read the same facts, so nothing is retyped and nothing drifts.

5

Same team, more and better work.

Agents prepare the next gate while this one is decided. Your people negotiate, allocate risk and sign.

Who this paper is for

CEOs and heads of procurement, commercial and development at renewables developers, IPPs and utilities in the UK and Europe, onshore and offshore.

01 · Why now

The clocks run while documents wait

Short answer

Once a project wins its route to market, three clocks start at once: the support contract, the grid and the supply chain. None of them pauses for a tender pack sitting in someone's inbox.

18 months

After signing a UK CfD, the generator must show spend of at least 10% of pre-commissioning costs, or the required project commitments.

90 days

To accept a GB transmission connection offer once it arrives.

Up to 4 years

To secure large power transformers. Cables take two to three years, and lead times have almost doubled since 2021.

When costs outrun the project

In July 2023 Vattenfall stopped developing Norfolk Boreas in its current form, citing cost increases of up to 40%.

In May 2025 Ørsted stopped Hornsea 4 in its current form after winning a CfD in 2024. Its chief executive pointed to "the combination of increased supply chain costs, higher interest rates and increased execution risk".

Neither was a paperwork problem. Both show how little room there is between award and investment decision.

Procurement now feeds the bid

Under the EU Net-Zero Industry Act, the ability to deliver on time is a test to qualify for renewables auctions, and resilience can be scored. Supplier evidence is no longer only for lenders. It goes into the round itself.

Onshore and offshore alike: the packages differ in size and number. Both lose the same weeks between gates.

02 · Where procurement waits

Seven gates, and the pauses between them

Short answer

Drawn as a plan, procurement is a line of gates. In practice much of the elapsed time sits in the gaps, where work waits for a decision or is redone because something upstream changed.

Figure 1

The same seven gates, run two ways

TODAY: EACH GATE WAITS FOR THE LAST ONE TO FINISHPackagestrategy1Marketsounding2Tenderout3Bids andquestions4Compareoffers5Negotiatecontract6Lendersand close1Design not frozen, so packages are redrawn2Scope rewritten for the tender documents3The same questions asked by every bidder4Offers arrive in different shapes and scopes5The model and the draft contract drift apart6Due diligence starts from a blank folderPauses and gaps: work stops, or is redone, while the next gate gets ready.WITH ONE RECORD AND AGENTS: THE NEXT GATE IS READY BEFORE THIS ONE CLOSESPackagestrategyMarketsoundingTenderoutBids andquestionsCompareoffersNegotiatecontractLendersand closeAgents prepare the next pack in parallel; people decide at each gateOne project record underneath every gateScope, packages, offers, clarifications, model inputs, contract terms and lender answers, versioned and owned
Ignis view. Today each gate waits for the last one to finish. With one record, the next pack is drafted while this gate is decided.

What stays the same

The gates, the decisions and the people who take them. Shortlist, preferred bidder, risk allocation and signature stay with your team and your board.

What changes

The next pack is drafted while this gate is decided. Nothing is retyped. A change is approved once and reaches every document that uses it.

Find your own pauses in an afternoon

Take one package you closed last year. Put the date each gate opened and closed on one line. The gaps between them are your pauses. For the two longest, ask what the team was waiting for, and whether it had to wait.

03 · Process first

First, look at what you run today

Short answer

The first step is not a tool. It is a clear look at how your team takes a package from strategy to signature, where it waits, and why.

1

Offers that are not the same offer

Each bidder prices a slightly different scope, so the cheapest offer is often the one that left most out.

FixRestate every offer onto one scope before anyone ranks it.
2

Questions asked and answered twice

Clarifications sit in email threads, and the same question comes back from each bidder.

FixOne clarification log, answered once and shared.
3

A model that is not the contract

Price, indexation and caps move in negotiation; the financial model catches up later.

FixModel and draft read the same terms, and a change needs an approval.
4

Dates that do not agree

The grid date, the CfD milestone and the supplier's programme live in three places.

FixOne date register with one owner, checked at every gate.
5

The lender pack built at the end

Due diligence starts from a blank folder, months after the evidence was first gathered.

FixBuild the pack as you go, from the record.

Start with two. Pick the two pauses that cost you most, and find the reason for each. Fix those first. The rest can wait.

Figure 2

The order that works

1Process first2Data second3Agents third
Process first. Data second. Agents third.

What do you run today? Map one package from strategy to signature. Remove steps that add nothing. Simplify what is left.

What does it run on? One record per project: scope, offers, terms, dates and evidence, versioned and owned.

Then add the agents, on the redesigned process, with named people deciding at each gate.

Revisit the real problem first

Why does a tender take as long as it does? Which steps exist because a lender or a rule needs them, and which because "we have always done it"? Is the package split right for this market? Automate a broken process and you get a faster broken process.

04 · Comparing suppliers

Compare like for like before you rank

Short answer

Ranking offers that answer different scopes is really ranking scopes. Restate every offer onto one grid first, and the real differences show up in days rather than in the final week.

Table 1

How a like-for-like grid reads

LineSupplier ASupplier BSupplier CWhat the agent raises
Scope and interfacesSameGapSameB leaves out one interface
ExclusionsSameSameAskC has not stated them
Programme against grid dateSameGapSameB misses the connection date
Price and indexationSameAskSameRestated onto one index
Delay damages and capsSameSameGapBelow your last agreed position
Warranties and availabilitySameSameGapShorter term offered
Security and creditSameExcludedSameNo parent guarantee
Resilience and supply chainSameAskSameEvidence the bid and lenders need
A framework, not a real tender. Same: matches the tender scope. Gap: differs and changes the price. Ask: unclear, goes to the clarification log. Excluded: not offered.

What agents carry

  • Read every offer and map it onto the grid.
  • Flag gaps, exclusions and dates that miss the grid.
  • Draft clarifications and log each answer once.
  • Restate prices onto one index and one scope.

What your people decide

  • Which gaps matter, and what they are worth.
  • The shortlist and the preferred bidder.
  • Where to push and where to concede.
  • Supplier relationships and the final call.

Onshore and offshore: offshore runs fewer, larger packages with long supplier lists for each; onshore runs more, smaller packages, often several projects at once. The grid works for both, and the record keeps every past offer for the next tender.

04 · Contract and lender pack

Contract and lender pack, from one record

Short answer

The comparison, the contract, the model and the lender pack describe the same project. When they read from one record, a change made in negotiation reaches all of them, with a name and a date on it.

Figure 3

One record, every document

One projectrecordyours, versionedSupplier comparisonDraft contractFinancial modelLender packBoard paperNext project
Comparison, contract, model, lender pack and the board paper read the same facts.
Table 2

What has to agree before signature

ItemComparisonContractModel and lender pack
ScopeThe restated scopeScope of worksCapex and contingency
PriceRestated priceContract price and indexationCapex and cost case
DatesProgramme against gridKey dates and delay damagesSchedule and milestone tests
RiskGaps and exclusionsCaps, warranties, securityRisk register and downside case

Approve changes, do not email them. A price, date or risk moves only with a named approval on the record. The consistency check runs before every gate.

Lenders ask the same questions. Keep every question and answer from the last close, and the next data room starts half built.

05 · Same team, more output

The same team, more output, better quality

Short answer

The aim is not fewer people. It is more packages, bidders and questions handled well by the people you have, with fewer errors reaching a lender.

Quantity

  • More packages run in parallel.
  • More bidders assessed properly, not cut early for lack of time.
  • The next gate ready on the day this one closes.

Quality

  • Every number traced to its source.
  • Model, contract and pack in step.
  • Terms won and conceded kept for the next project.
Table 3

Who does what

RoleAgents carryYour people keep
Head of procurementTender packs, the bidder log, the comparison gridPackage strategy, shortlist, supplier relationships
Commercial leadFirst mark-up from your last agreed termsRisk allocation and the negotiation
Finance and fundingModel updates, consistency checks, lender answersThe financing case and lender relationships
Technical leadInterface and programme checks against the grid dateDesign choices and technical sign-off
CEO and boardA board paper from the record, with the open risksThe investment decision and the signature
People keep the judgement and the relationships. Agents carry the reading, the logs and the first drafts.
06 · Inside the system

A governed system on your data, better with every project

Short answer

Ignis builds the system around your team, on your own documents and in your own environment. It keeps the record, runs the repeatable work and brings every decision to a named person.

Figure 4

People and gates

People and gatesShortlist, preferred bidder, risk allocation, sign-off. Named people decide at each gate.AI manager: plans the work, routes it to agents, checks it, brings each decision to a personAGENTSTender packPackages and scope drawnfrom the recordClarificationsLogged, routed and answeredonceComparisonEvery offer restated like for likeMark-upFirst draft from the last agreedtermsConsistencyModel, contract and packagreeDue diligenceLender questions answeredfrom the recordCONNECTORS TO THE TOOLS YOU ALREADY USETender portalFinancial modelDocument storeData roomEmail, calendarYour data and context: one record, owned by you, that improves with every projectProject facts: scope,dates, grid, consentsOffers, clarificationsand decisionsPast contracts: termswon and concededLender questions andanswersGovernanceNamed gatesAudit trailAccess rulesYourenvironment
The AI manager breaks the goal into tasks, checks the output and stops at each gate.

The AI manager

Breaks a goal such as "turbine supply to preferred bidder" into tasks, gives each to the right agent, checks the output and stops at each gate for a decision.

The record is yours

Offers, terms, dates and lender answers stay in your environment under your access rules. Each project leaves it better for the next.

What stays human

The shortlist, the preferred bidder, risk allocation, the walk-away and the signature. Supplier and lender relationships.

Each project leaves the record richer: better terms to start from, fewer questions to answer, faster gates next time.

07 · Self-check

How fast can your next package move?

Short answer

Ten yes or no questions. Tick what is true today, not what is planned.

0/10 Tick what is true today
0 to 3 Start with the process map and a date register
4 to 7 Build the comparison grid and the one record, then add agents
8 to 10 Ready to run more packages with the same team
Table 4

Work it out on your own numbers

For one projectTodayRedesignedWhat it frees
Packages in procurement this year
Days waiting between gates, in total
Senior days per supplier comparison
Lender questions answered from scratch
Fill it in for one live project. The gaps are where the next fortnight goes.
08 · Where to start

Start with your two biggest pauses

Short answer

Not with a platform. First comes a short, low-risk discovery and gap review, then a map of one package from strategy to signature: two weeks at most. The price stays open until we have seen the work.

Figure 5

From discovery to a live tender

Week 1Discovery andgap reviewWeek 2ProcessmappingWeeks 3 to 5Sprint: redesign, structurethe data, set the gatesBy day 90Pilot on a live project withyour team, then embedTwo weeks at most: fixed scope, low riskLessons go back into the record, then choose the next workflow
Start with a discovery: two weeks at most, for a clear view of where agents will help. Discovery and gap review, then process mapping.
The first weeks
Week 1Discovery and gap review

Your goals, your package plan, and the two biggest pauses in procurement, with their causes.

Week 2Process mapping

One recent package traced end to end on its own documents. What people keep, what agents carry, where the gates sit.

Weeks 3 to 5Sprint

Redesign the process, build the comparison grid and the record, and set the gates for the next live package.

By day 90Pilot

Your team runs a live tender on the new way of working, then embeds it.

Guardrails

  • Ignis advises and designs; your team decides.
  • Your data stays yours, in your environment.
  • Process before platform: tool-agnostic.

Bring one project heading for preferred bidder or financial close. We will look at where it waits today and what would change first. Talk it through with Yorik.

This paper offers a commercial view only. It is not legal, regulatory or investment advice. Market figures were checked in October 2026; contract terms and dates can change.

Get Signal in your inbox

Weekly UK and European energy market insight. If you like it, sign up and get it straight into your mailbox every week.

Got a project heading for financial close?

Let’s talk through where your procurement waits, and what would change first.

Talk it through