Introduction of Sweet Treat Reward System

Date of latest update
Type
Change
ID
R9999
Change Category
Priority
Urgent
Yes
Latest Update
Consultation issued June 29th
Summary
This proposal introduces a formalised “Sweet Treat Reward System” within the REC governance framework, whereby participants are recognised with confectionery based incentives for timely delivery, high quality submissions, and proactive engagement in the change process. The change aims to improve stakeholder participation, reduce consultation fatigue, and enhance overall delivery performance by introducing a light-touch behavioural incentive aligned to existing governance activities.
Proposer
Mark Pearce
Impact Status
Impacted Consumers
Impacted REC Documents
Implementation Date
Status Scheduled
EMAR Version 4.1.0_Live

Documents

Name Version Last updated Actions
317 bytes
Version 1.0 - 08 Jun 2026 PDF - 317 bytes
1.0 08 Jun 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Linked to SDS Delivery
No
Lead Analyst
Dave Jones
Date of Update to Priority
Solution Development
Proposed solution summary
The proposed solution is to introduce a new REC provision establishing a “Sweet Treat Reward System” (STRS), creating a light-touch, non-financial incentive mechanism linked to existing change process activities. This would require updates to REC governance documentation (e.g. Change Management schedule and supporting guidance) to define eligibility criteria, reward thresholds, and roles, with the Code Manager responsible for administering and maintaining the scheme and recording outcomes within the REC Portal. End-to-end, the solution would operate by linking stakeholder behaviours (e.g. timely consultation responses, active participation in CIG discussions, and high-quality submissions) to predefined reward triggers. The REC Portal would be enhanced to capture participation metrics, calculate eligibility, and notify participants of earned rewards via automated communications (e.g. portal notifications or email), with a monthly or milestone-based cadence. Data flows would include submission timestamps, attendance records, and qualitative assessment inputs from the Code Manager or Change Leads, which would be consolidated into a “Reward Eligibility Log” maintained within REC systems. Implementation would be led by the Code Manager, supported by the DSP for system changes and reporting capability, and overseen by REC governance bodies to ensure alignment with existing obligations and neutrality principles. The solution would not alter core decision-making processes but would overlay an engagement-focused mechanism, with clear accountability for administration, auditability of outcomes, and periodic review to ensure continued effectiveness and proportionality.
Problem Statement
The REC change process currently relies on formal obligations and voluntary participation to secure stakeholder engagement; however, this approach does not consistently drive timely, high-quality input during key stages such as consultations and working groups. As a result, participation can be delayed, inconsistent, or limited in substance, reducing the effectiveness of impact assessments and slowing overall change delivery.
In the absence of any positive reinforcement mechanisms, the process places full reliance on compliance rather than motivation, which may not fully reflect the human factors influencing engagement. This creates a persistent gap between the intended collaborative nature of the REC and the reality of stakeholder behaviour, ultimately affecting the pace and quality of change outcomes delivered to the market.
Workgroup
Workgroup(s)
Review status
Reviewed - Accepted
Schedule 5 - Change Management 3.9 – Implemented on
Loading...

Implementation of Ofgem-led code modification prioritisation within the REC

Date of latest update
Type
Change
ID
R0304
Change Category
Change Path
Urgent
No
Latest Update
This change Proposal has been approved for implementation on the date as directed by the Authority.
Summary
Ofgem has consulted on, and is progressing towards a decision on, the introduction of a harmonised code modification prioritisation framework across all industry codes, under its transitional powers in Schedule 12 to the Energy Act 2023. This Issue is being raised to provide the formal REC change vehicle through which Ofgem’s prioritisation reforms can be tracked, developed and implemented in the REC, once the Authority has published its decision and statutory modification notice.
Proposer
Ann Perry
Change report - Final Change Report

Comments deadline
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Date of Update to Priority
Solution Development
Problem Statement
In the absence of REC changes, the REC would not align with Ofgem’s harmonised approach to code modification prioritisation, creating inconsistency with other industry codes and undermining the objectives of Energy code reform.
I0304 submission form
I0304 Change Report (Proposal Plan) V1.0
New Priority Status
Company Name
-
Review status
Review required

Agile Reporting within CSS

Date of latest update
Type
Change
ID
R0224
Change Path
Priority
Urgent
No
Latest Update
18/03/2026 - An update to plan has been published for consideration at the Technical Expert Panel on 25 March 26.
Summary
As part of the impact assessment process for R0115, it was identified that it is very costly and time consuming to make reporting changes within the CSS architecture. As such, we would like to explore enabling agile reporting within the CSS ecosystem, by creating a functionality that consolidates all necessary data into a single, centralised database.
Proposer
Maxime Van Eyseren
Change report - Final Change Report
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Date of Update to Priority
Solution Development
Problem Statement
Current CSS arrangements mean that REC Changes designed to facilitate access to CSS data are more onerous that they need to be. Current arrangements are costly and have relatively long lead-times. This Issue seeks to explore changing the way that the CSS data can be accessed.
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
Proposal Form - Agile reporting within CSS
I0224 Change Report (Plan) (Approved) V1.0 21.01.25
Change Proposal Re-Plan Approved
Solution/Business Case report
R0224 update to plan 18.03.26
R0224 update to plan 19 May 2026
Company Name
-
Review status
Review required