Contracts for Innovation: FOAK26 (DFT Rail Innovation, 2026-27)

Contracts for Innovation: FOAK26 (DFT Rail Innovation, 2026-27)

If you are building a railway technology solution and you are looking for a contract-backed way to move from prototype to real-world validation, FOAK26 is the first major UK opportunity currently open that explicitly combines those two goals.

This is a Department for Transport-backed, Innovate UK-run competition in the First of a Kind (FOAK) series. It is part of a practical model: fund high-maturity projects, test in realistic environments, generate customer evidence, and support commercial uptake. The competition is currently open from the UKRI page as of 2026-05-18, with applications closing on 2026-06-24.

This guide is intentionally practical. It avoids generic grant templates and focuses on what this specific competition asks for based on the official UKRI and Innovation Funding Service content.

Key details (quick reference)

What FOAK26 is and why it is different from a standard grant

Most grant pages say “apply for funding”; this one says “apply for a contract.” The practical implication is important. This competition is framed as a procurement of R&D services where selected teams receive a contract and are expected to deliver a concrete solution that can be demonstrated and de-risked.

The page describes it as a competition to support “innovative suppliers” for railway market readiness. The structure is not academic-only, not purely exploratory, and not a fully general technology push. The emphasis is on:

• a mature solution,
• a defined challenge fit,
• demonstrator readiness,
• customer engagement and commercial evidence,
• and a plan that can move through field testing and trial in a railway context.

The focus is therefore different from many longer-duration research grants: it is shorter, narrower, and strongly outcome-oriented around deployment.

Unlike broad innovation competitions that often reward strong concept writing, this is explicitly an industry-linked process: rail stakeholders (for example HS2, Network Rail, TfL, DLR, and others mentioned in the challenge list) are embedded in the challenge framing.

What exactly you can apply for

FOAK26 has eight named challenges. This is not a “write any rail idea and hope it fits” competition. You must map your proposal to one or more themes, and you must do so correctly.

The eight challenge themes are:

1. Safe Concurrent High-Speed Rail Installation in Constrained Environments (Stakeholder: HS2)
2. UK Dark Skies - Drone Operations BVLOS (Stakeholder: Network Rail)
3. Improving Customer Experience in Isolated Spaces (Stakeholders: TfL, DLR, Rail North Partnership)
4. Digital Hazard Log (Stakeholders: Network Rail, Southern Renewals Enterprise)
5. Scour Risks to Structures (Stakeholder: Network Rail)
6. Structures: Rapid Behaviour Verification to Support Assessment and Intervention Decisions (Stakeholder: Network Rail)
7. Green Engineering Solutions for Earthworks Resilience and Biodiversity Net Gain (Stakeholders: Network Rail, TfL, Southern Renewals Enterprise)
8. Enhancing Rail Adhesion Through Intelligent Vegetation Management and Biodiversity-Positive Interventions (Stakeholders: TfL, Network Rail)

Your proposal must be high maturity and suitable for rail settings. The competition text expects projects that already look like practical solutions, not broad blue-sky research. The term “First of a Kind” is not marketing language here: it means your solution should be capable of a real railway demonstration and should contribute to reduced risk for later adoption.

You can select one or multiple themes, but you must submit under the correct scope. Submissions considered out of scope are not assessed, which means this is likely one of the first filters before scoring.

If your project cannot be meaningfully demonstrated in operational or construction railway contexts, or if its value proposition cannot be explained to industry users, it may fail early regardless of technical quality.

Eligibility and participation rules that change how teams should apply

The eligibility criteria are straightforward but strict in execution.

• Applicant type: organisations of any size, including international participants.
• Applicant must be able to hold the contract and lead delivery.
• Work can involve subcontractors for specialist capability, including research, technology, business, and third sector partners.
• The contract must be awarded to a single legal entity.
• The majority of project work and key deliverables must be completed by the applicant, and deliverables must be UK-based.

A particularly important operational rule: the project start date is fixed per competition conditions at 1 September 2026 and the end date must be no later than 31 March 2027. Project duration must be between 3 and 7 months, and projects must start on the first day of a month.

You do not start work before contract approval. Any costs incurred before the approved start date are not supported. This affects launch planning, especially if you are arranging pilot sites and integration partners before award.

Also, applications should include evidence and planning for an integration partner. The official guidance says the integration partner is expected, but you must not enter integration partner details in the application form itself. Practically, that means you should have them lined up early and then use internal planning and letters of intent outside the submission fields to show readiness.

Funding and cost mechanics you must design for correctly

The total programme allocation is £4.3 million. At project level, each project can go up to £210,000 (inclusive of VAT) and run up to seven months. The page also states that contracts can be awarded to up to 22 projects, though not all submitted proposals will be funded.

Because this is a contract competition, two rules are operationally critical:

• At least 50% of the contract value must be direct R&D service spend (including exploration, design, prototyping, and field testing).
• Costs and milestones drive monthly cash flow, because there are no advance payments.

Why this matters: If your project depends on high upfront spending, you need a working cashflow model that still survives the payment pattern. Milestones must be clear, SMART, and tied to deliverables. Monthly invoices must be submitted within 30 days after each monitoring period.

R&D is not a placeholder. It excludes normal commercial development actions such as production scale-up, customisation-only work, and integration-only tasks. In other words, your budget narrative must show that most spend supports genuinely developmental, demonstrable work.

VAT treatment can be a trap. You are expected to enter costs correctly from the beginning (exclusive of VAT if applicable and added by the service), because double-counting VAT is a known issue and can create ineligibility.

How the application and assessment process works

The competition has a single phase. Once you submit, your application is scored against criteria set by Innovate UK and the challenge framework, with three independent assessors and challenge-holder input. Scoring contributes to funding decisions under a portfolio approach, meaning a high-scoring project can still miss funding if the competition budget is exhausted by other award decisions.

This is a common point for applicants: quality is necessary but not sufficient when a portfolio cap exists.

What to prepare for assessment:

• Clear alignment to at least one competition challenge.
• Evidence of Rail Industry Readiness Level at or above the stated stage (the page calls out an expected readiness baseline in the rail context).
• Strong commercial potential and route-to-market.
• A feasible project plan with measurable milestones and realistic delivery.
• Realistic, value-for-money budget and clear financial logic.

The application is reviewed online through the Innovation Funding Service at a dedicated competition page. Because this is a government service environment, the page includes time-bound session behaviour and may time out; this should be handled through careful draft management and periodic saves.

Step-by-step preparation strategy (especially for this competition)

Step 1: confirm challenge fit first

Make a one-page fit sheet before writing the application: for each challenge, map a line-item problem, your technical approach, demonstration method, and intended customer outcome. If you cannot explain one in 2–3 lines, that is a likely filter failure.

Step 2: decide readiness level honestly

The challenge requires projects with high maturity. This is not a “research only” brief. You should be prepared to evidence prior testing, technical development, and implementation feasibility.

Step 3: lock project boundaries to the budget shell

Your total eligible costs must not exceed £210,000 inclusive of VAT. This is where many teams lose points through ambition creep. Keep the primary scope focused on demonstrator success, not broad roadmap expansion.

Step 4: design monthly milestones around measurable milestones

The service explicitly expects milestone-based monitoring and monthly review evidence. Your milestones should be credible in time and deliverable quality. Tie each milestone to outputs and payment timing.

Step 5: build commercial logic into technical narrative

This is not optional. The brief repeatedly asks for customer need, route to market, and de-risked implementation. Include at least one concrete customer pathway.

Step 6: line up demonstration context and customer participation

A key project deliverable is a demonstration event and trial. The page requires inviting industry customers and representatives to the trial. Plan this in writing with potential stakeholders.

Step 7: prepare post-award setup in parallel

If awarded, project setup is done in the portal and you have 30 days to complete it with required documentation. Start preparing bank account readiness, documentation, and legal/admin basics early.

Common mistakes this page makes easy to avoid

1. Wrongly scoped idea submission. If your proposal is not directly within one of the eight themes, it can be rejected without full scoring.
2. Incorrect timing assumptions. Project must align to the fixed September 2026 to March 2027 window and first-of-month start.
3. Ignoring 50% R&D floor. A heavily “integration-only” or “commercial roll-out only” budget can fail eligibility.
4. Underestimating monthly cashflow. No advance payment means teams that do not model delayed payment cycles can stall delivery.
5. Unclear milestones and evidence schedule. Milestones and monitoring evidence must be realistic and clearly described.
6. VAT mis-entry. The service flags VAT handling explicitly; double counting has caused ineligibility cases in past cycles.
7. Late submission near deadline. Portal issues and document upload delays are common; early submission is a better strategy than last-minute completeness.

Application materials checklist (practical)

Although every competition interface has fields that are not fully visible in the summary page, the FOAK26 page makes several requirements clear and practical:

• Project overview matching one or more challenge themes
• Timeline with 3–7 month execution window
• Milestones with deliverables and success criteria
• Budget split that supports at least 50% direct R&D
• Commercial pathway and evidence-gathering plan
• Rail context demonstration strategy, including trial design
• Proof of team capacity and relevant expertise
• Compliance notes where needed (including any partner and sanctions considerations)

Prepare these in a single set of coherent documents and narratives so that the same factual claims are repeated consistently in every section.

After submission: what happens and what happens next

If successful, the next stage is not done; it is only started.

You will be notified by email and directed to complete project setup within a set window. You must provide required location, financial, and project information. Missing this step can lose an offer.

You also need a business account aligned with IFS details (same legal name and with clearing facilities) because invoices are paid monthly in arrears.

The contract is issued via IFS, then signed. Project start may not be earlier than the approved date. If you want a smooth start, prepare finance and legal readiness in parallel with your application.

If unsuccessful, Innovate UK provides assessor feedback on the portal. A positive score can still be non-funded due to portfolio decisions, so feedback is important for improving the next round or applying to adjacent opportunities.

Frequently asked questions for FOAK26 applicants

Is this a typical unrestricted research grant?

No. It is a Contracts for Innovation procurement competition and funding is in the form of contracts, with specific milestone and monitoring structure.

Can non-UK teams apply?

Yes. The competition explicitly allows organisations from EU, EEA, and international regions, but requires key project work and deliverables to be completed in the UK.

Can we apply for more than one challenge?

Yes, selecting more than one challenge per application is permitted, but each submission must be in scope. Submissions deemed out of scope are not assessed.

Is there room for a startup?

The applicant can be any size organisation. This means startups can be strong applicants if they can prove delivery maturity and practical rail context readiness.

When is the money paid?

There are no advance payments. Invoices are submitted monthly for completed milestones and paid in arrears.

What are the biggest practical risks for new applicants?

Timing discipline, fixed project window, and cashflow management. The second biggest issue is overbuilding the scope beyond the £210,000 cap and the 3–7 month timeline.

Who can I contact for support?

Innovate UK provides support via [email protected] and phone 0300 321 4357. They also recommend contacting support at least 15 working days before the closing date where possible.

Official links and next steps

• UKRI competition page: https://www.ukri.org/opportunity/contracts-for-innovation-foak26/
• Innovation Funding Service competition overview: https://apply-for-innovation-funding.service.gov.uk/competition/2475/overview/6fba05b0-d73b-4a33-886e-cb0950f1252a
• Contracts for Innovation overview: https://www.ukri.org/opportunity/contracts-for-innovation/

If you treat FOAK26 as a compliance test instead of a “grant form,” you gain an advantage. Good applications for this competition are not just ideas—they are demonstration plans tied to a real rail customer pathway, with disciplined scope, realistic milestones, and explicit value for money.