Introduction of Sweet Treat Reward System
Date of latest update
Type
Change
ID
R9999
Change Category
Other Industry Codes impacted
Change Path
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.
Impact Status
Alternative Change Proposals
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Date
Version 4.2.0 - 27 Mar 2027.
| Included changes | Affected REC Items | |
|---|---|---|
| R0002 | Review of Data Specification Category in REC Baseline Statement | |
| R0136 | Change to REC Schedule 22 Market Stabilisation Charge (MSC) |
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 08 Jun 2026 |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Linked to SDS Delivery
No
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.
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.
Stages Selection
Workgroup
Workgroup(s)
Review status
Reviewed - Accepted
CoMCoP 2-year Audit Cycles
Date of latest update
Type
Change
ID
R0311
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal has been implemented as part of the June 2026 REC Release.
Summary
Renewal audits under the Consolidated Metering Code of Practice (CoMCoP) are consistently delivered on a 2 year cycle and include both a desktop audit and a site audit. However, Schedule 15 currently does not explicitly define this.
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Date
26 June 2026
| Included changes | Affected REC Items | |
|---|---|---|
| R0103 | Central provision of DCC Technical Contacts for requesting test certificates |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- An update to the REC Schedule 15 - Metering Accreditation
Proposed Solution Document
Document title
R0311_Draft legal text (For Final Recommendation)
Archive
Off
Problem Statement
The current lack of explicit wording in the Metering Accreditation Schedule of both a desktop and site audits that need to be completed one year after the initial accreditation, and then every two years for renewals introduces ambiguity for future audit delivery undertaken under CoMCoP as it creates a gap between operational practice and the codified baseline. This could potentially lead to inconsistent approaches by Parties, which in turn could reduce the consistency, predictability, and effectiveness of the industry’s audit and assurance framework.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME Role
Lead Assurance Analyst
R0311 submission form
Draft legal text (On submission)
R0311 Draft legal text (For Consultation)
R0311_Change Report (Final Recommendation)_v1.1 (13 May 2026)
Company Name
-
Review status
Review required