Ofgem Strategic Innovation Fund Discovery C6: UK Energy Network Innovation Discovery Grants (Open 2026)

Ofgem Strategic Innovation Fund Discovery C6: UK Energy Network Innovation Discovery Grants (Open 2026)

The Ofgem Strategic Innovation Fund (SIF) Discovery C6 competition is one of the active UK network innovation competitions for energy infrastructure teams, currently visible on the UK Research and Innovation (UKRI) opportunity index with an open status and a close date of 24 June 2026. It is delivered by Innovate UK with Ofgem support and is specifically aimed at Discovery Phase projects in five innovation challenge areas. It is designed as the first step in a multi-phase pathway (Discovery → Alpha → Beta → Deployment), rather than a single terminal grant.

Key details table

What this competition is for

This competition does not fund generic software ideas, broad academic research unrelated to energy networks, or purely internal process improvements. It is aimed at applied network innovation, where the lead applicant is a network operator and the proposal is clearly tied to one of SIF’s Discovery Phase challenge tracks:

1. Industrial and business connection acceleration
2. Faster build and maintenance
3. Instant-use domestic energy devices
4. Eliminating energy outages
5. Decentralised system balancing

The practical implication is that this is a public-utility-network innovation pathway. The competition language stresses that the innovation should ultimately show value to energy consumers, support net zero at least cost, and be capable of moving beyond Discovery into Alpha and possibly Beta/Deployment. It is also explicit that this is a competitive process, and successful Discovery projects may later move into larger stages if they prove technical and commercial traction.

For many teams, this structure is useful because it lets you test ideas quickly on a relatively contained budget before attempting longer and larger-scale demonstration funding.

Who this is best suited for

The strongest fit is usually one of these:

• Distribution or transmission network organisations (or closely coordinated teams with one as formal lead).
• Network operators with practical access to live operational contexts (e.g., outage events, maintenance planning constraints, balancing challenges, domestic energy-device use cases).
• Consortia that can credibly include at least one SME or technology specialist as a meaningful partner.
• Teams ready to deliver on a strict, short planning window (roughly five months from project start to finish for the Discovery proposal).

The page makes lead-organisation eligibility strict for Discovery C6: the lead must be one of the listed Ofgem-licensed network classes. That means many academic-only groups, pure startups, or pure-consumer-facing apps are ineligible as lead but can still contribute as partners if the lead operator submits.

From a practical standpoint, this usually means:

• A network operator lead (or NESO lead) owns accountability and receives Project Direction.
• Partners contribute expertise or resources and can be responsible for specific deliverables.
• Non-funded partners can be included and may support activities using own resources, especially useful for R&D specialists and niche research contributors.

Eligibility and constraints you can’t ignore

You should treat the eligibility criteria as screening gates, not optional preference:

• Licensing gate: Lead must be eligible network operator under Ofgem licensing categories listed by the competition.
• Collaboration gate: applications are collaborations only, with at least one additional partner.
• Scope gate: your project must align with at least one SIF Innovation Challenge.
• Phase and timing gate: Discovery phase, total request cap, and strict project dates.
• Funding mechanics gate: expected private contribution and no automatic flexibility on project start date.
• Start date gate: project start date must be on the first of the month.
• Delivery gate: Project partner responsibilities must be explicit; each collaborating entity is expected to contribute to at least one deliverable in Discovery.

The source text also states that this competition is delivered with subsidy-control considerations. In simple terms, this is often read as a constrained public support model requiring careful commercial neutrality interpretation. Teams should not assume normal grant assumptions apply. If this seems unclear, the official guidance points to legal advice and direct support contacts.

Funding model and financial rules in practice

Even though the page headline talks about up to £30 million for Discovery across challenges, the individual project-level ceiling is the operationally important number: up to £200,000 requested per Discovery project (excluding VAT). Your requested amount must match a realistic Discovery scope, not a Phase I to Phase III fantasy budget.

Two other practical budget points from the competition are frequently missed:

1. Mandatory private contribution rule: standard Discovery projects require at least 10% private contribution by default.
2. First Discovery exemption nuance: this minimum may not apply if the Discovery is only for developing an Innovation Charter.

That means every budget should answer three questions:

• What exactly are you purchasing or building in Discovery?
• What are minimum costs needed to produce measurable outputs in five months?
• Which cost items are eligible, and where does the match contribution come from?

If your budget is not internally coherent, reviewers may not get to your technical strengths.

The open page also notes that matched contributions above the minimum can improve value-for-money perception. This is a reviewer signal, not a guarantee of funding, but teams with stronger private leverage and clear cost discipline tend to profile better against value for money.

How the four-phase structure affects your strategy

The four-phase progression is central to the competition strategy:

• Discovery: short, focused phase to define the problem, prove concept plausibility, and produce outputs.
• Alpha: testing and risk reduction after Discovery success and invitation.
• Beta: larger demonstration, scale and deployment preparation.
• Deployment: integration into normal operations and broader adoption.

Because Discovery is an invitation-style early filter, your proposal should be written as the first checkpoint of a longer journey, not as a final implementation plan.

Your proposal should explicitly describe:

• Why this challenge area is the right track.
• What proof will exist at Discovery close.
• How lessons can carry into Alpha and eventually scaling.
• How your project can transition from development to measurable impact.

The competition page states that applicants enter this process with awareness that implementation of successful solutions can still face competitive procurement. In practice, this means a good Discovery should prepare you for both technical validation and future commercial transition.

Application process and required materials

The official competition is hosted in the Innovation Funding Service (IFS), and the application workflow is form-based with structured evidence requirements.

Key things you should prepare before the 24 June deadline:

1. Challenge selection: pick the correct one early; applications cannot be moved between challenges.
2. Partnership map: lead + invited Project Partners must be added in IFS with agreed roles.
3. Problem statement and outputs: include user problem, value pathway, and expected outputs by Discovery end.
4. Project timeline: date constraints are strict; start must be first of month, and complete within a five-month window.
5. Video: a short unlisted YouTube video is required; missing it is an eligibility risk.
6. Project Management Template (PMT): required in the full application section and includes planning, cost and risk worksheets.
7. Cost breakdown by partner: each partner should present a defensible share and contribution logic.

The service also asks for additional sections around TR&I, animal welfare (where applicable), export controls, and strategic alignment to the innovation challenge.

If you are invited to apply again after previous cycles, the guidance distinguishes resubmission conditions and asks for evidence of material changes. That is relevant for teams with prior SIF applications; a re-application should not be a copy/paste.

Preparation checklist before drafting

Use the first 3–4 weeks after launch to complete the following:

• Build a one-page challenge fit statement against the selected Innovation Challenge.
• Prepare partner letters confirming roles, responsibilities, and deliverable ownership.
• Draft the commercial logic and value to consumers in one paragraph and one diagram if possible.
• Identify the required 10% private contribution source and secure it in principle.
• Draft the 120-second public-facing video script and gather any required recordings.
• Check that your proposed start date is aligned with a first-of-month rule and end date before 31 January 2027.

Then build the proposal backwards from deliverables:

• Week 1: project framing + partner roster.
• Week 2: technical scope + outputs + risk sections.
• Week 3: budget + PMT + value for money narrative.
• Week 4: upload and proof-read all mandatory fields (video, contacts, compliance questions, TR&I, export control).

This timeline leaves buffer for compliance questions and internal sign-off before June close.

Common application mistakes

The most frequent reasons teams lose momentum are process mismatches, not technical quality.

• Wrong challenge selected: if your submission is out-of-scope, it is not assessed.
• Lead eligibility mismatch: applying under a non-licensed lead will likely fail early.
• Underestimating partner structure: every partner should be tied to an actual deliverable.
• Budget mismatch: mixing Discovery ask with Alpha/Beta scale thinking.
• Missing 120-second video: for this competition, media upload is part of required application mechanics.
• Ignoring contribution requirement: not demonstrating private contribution where required.
• Late compliance assumptions: assuming subsidy/state aid or governance issues can be resolved after submission.

A practical rule: if one of your partner organisations has no clear role, remove it early rather than leaving a weak placeholder.

FAQ based on common applicant confusion

Is this a one-time 2026 call only?

The posting is a named Discovery cycle with explicit open/close dates in 2026. The challenge area can still produce projects that roll into next-stage invitations in subsequent cycles.

Can a startup lead this grant?

As written, lead status for this Discovery round is tied to licensed networks and NESO. Startups can usually participate as partners, not as the sole lead.

Is the £30 million the amount each project can get?

No. The total programme allocation for Discovery phase is up to £30 million across all challenges and applications. Individual project requests are capped at £200,000.

Is there a minimum cash match?

Most Discovery projects must include at least 10% of total Project costs as private contribution, with limited exceptions for initial Innovation Charter route.

Can you reapply after being unsuccessful?

Yes in some cases, but prior projects generally need to show material changes and satisfy current challenge scope when reapplying.

How are applicants reviewed?

The published process uses independent assessors. Scores feed into funding decisions unless specific notification indicates otherwise.

Why this is a useful opportunity for 2026/2027 planning

From a 2026 timing perspective, this is a meaningful open call because it supports projects that can start in late 2026 and complete early 2027. It is particularly useful for teams that need early proof-of-concept without committing to larger-scale capex before proof and stakeholder validation.

If your network innovation idea is still high-level, Discovery C6 is often the right place to test viability. If your work is already late-stage, you may be too early in cost structure for Discovery and should align your asks to Alpha-ready evidence.

For organisations already under performance pressure (grid reliability, outage resilience, connection delays, local balancing), this competition has practical relevance because it targets the same operational pain points.

Risks and reviewer expectations

Even before scoring starts, teams should assume a reviewer will check:

• Is this a true network innovation challenge, not a side project?
• Is the project lead clearly accountable and compliant?
• Is the deliverable scope achievable in five months?
• Are costs eligible, realistic, and compliant with partnership requirements?
• Are private funds and consumer benefit rationale credible?

Applications are strongest when they connect technical scope directly to customer/system-level impact. A technically elegant concept without measurable benefit framing often stalls.

Official links and next actions

• Primary UKRI listing: https://www.ukri.org/opportunity/ofgem-strategic-innovation-fund-discovery-c6/
• Innovation Funding Service competition page: https://apply-for-innovation-funding.service.gov.uk/competition/2484/overview/770c0946-2e24-4566-bab1-2bf1c1dd2b38
• SIF contact (technical scope questions): [email protected]
• IFS support: [email protected]
• Innovate UK phone support: 0300 321 4357 (UK business hours listed on official page)

If you are preparing an application, treat this as a tight 5–6-week sprint from concept to submission, with a separate 30-day post-offer setup window if successful.