This page lists the items due for release as part of the Winter 2026 Technical Update. This update will be released to the DEMO and LIVE databases on the following dates:
If you have reported a bug to HEAT Support and it has been addressed within this update, you will be notified via your HEAT Support Helpdesk ticket.
The release items are categorised in the below sections:
We are releasing this update to the LIVE database midweek on the morning of Tuesday 8th December and there may be disruptions to the system for up to 1-2 hours during and after deployment. We apologise for any inconvenience this may cause.
Please note: The following list of items are subject to change
To support members with Student data cleaning and preparation for Higher Education (HE) Tracking, we are updating the Student Higher Education Tracking tab on the database homepage.
This update will improve the layout, content and links within the tab to better align with the HE Track Snapshot criteria, making it easier for members to identify and access relevant Student records.
These improvements aim to provide clearer information about HE Tracking requirements and help members prepare their Student data more effectively.
This update applies to the Student Higher Education Tracking tab on the HEAT database homepage (members only).
There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.
To make it easier for members to manage Institutions on Activity records, we are introducing improvements to the Activity import template that allow individual Beneficiaries to be removed without affecting others linked to the same Activity.
Previously, members could only remove all registered beneficiaries from an Activity using #NULL within the ‘Beneficiary Institutions’ column on the ‘Activities’ sheet of the Activity import template.
This update introduces more flexibility when managing Activities in bulk, allowing members to selectively remove Beneficiary Institutions and their associated Student registrations while retaining those that should remain linked to the Activity.
To make it easier for members to manage Institutions on Activity records, we are introducing improvements to the Activity import template that allow individual Beneficiaries to be removed without affecting others linked to the same Activity.
Previously, members could only remove all registered beneficiaries from an Activity using #NULL within the ‘Beneficiary Institutions’ column on the ‘Activities’ sheet of the Activity import template.
This update introduces more flexibility when managing Activities in bulk, allowing members to selectively remove Beneficiary Institutions and their associated Student registrations while retaining those that should remain linked to the Activity.
This update applies to the Activity import template, specifically the Activities and Beneficiaries sheets, and affects the associated Activity and Session records within the database.
There will be no impact on Data, reports, the API, or Roles and Permissions.
Does this change affect the structure of Import and Export templates?
Yes. The Activity import template will be updated to support the selective removal of Beneficiary Institutions:
For example: Activity #12345 has four Beneficiary Institutions registered:
If Bamford Academy and Oakwood College were added in error and need to be removed, enter #NULL followed by the HEAT IDs of Maplewood Academy and Riverside School in the ‘Beneficiary Institutions’ field (e.g. #NULL, [Maplewood HEAT ID], [Riverside HEAT ID]).This will remove Bamford Academy and Oakwood College, along with their 13 associated Student registrations, from the Activity and all associated Sessions. Maplewood Academy and Riverside School will remain on the Activity, retaining their 22 registered Students.
Beneficiaries sheet: Adding the #REMOVE prefix to a Beneficiary Institution HEAT ID will remove that Institution from the Activity and all associated Sessions, along with its Students from the Activity and Session registers.
For example: Using the same Activity (#12345), if Bamford Academy (HEAT ID 27948) was added in error, enter 12345 in the ‘Activity HEAT ID’ column and #REMOVE27948 in the ‘Beneficiary Institution HEAT ID’ column on the ‘Beneficiaries’ sheet. This will remove Bamford Academy and its 5 registered Students from the Activity and associated Sessions, while retaining Maplewood Academy and its 10 registered Students.
Existing Activity import templates will continue to work following this update. However, the latest version of the template will include additional guidance on using the new #REMOVE functionality.
A new ‘HE Year 05’ option is being added to the ‘Year Group’ field on Activity records to support the monitoring of Activities involving students in their fifth year of higher education.
This will be particularly useful for members delivering programmes involving students on longer degree courses, such as Medicine, allowing these Activities to be recorded and reported on more accurately.
This update applies to the ‘Year Group’ field within Activity records on the database.
There will be no impact on data, reports, the API, or Roles and Permissions.
Does this change affect the structure of Import and Export templates?
Yes. The addition of ‘HE Year 05’ to the Year Group field will affect Activity Import and Export templates.
Following the Winter 2026 Update, members will need to download the latest Activity Import templates to ensure they are using the most up-to-date field values.
Members using custom import templates will also need to update these to reflect the new Year Group option.
If your organisation uses Activity Export templates with other software or reporting processes, you should review these to ensure they accommodate the new value.
Yes. The addition of ‘HE Year 05’ to the Year Group field will affect Activity Import and Export templates.
Following the Winter 2026 Update, members will need to download the latest Activity Import templates to ensure they are using the most up-to-date field values.
Members using custom import templates will also need to update these to reflect the new Year Group option.
If your organisation uses Activity Export templates with other software or reporting processes, you should review these to ensure they accommodate the new value.
The ‘Delivered By’ field on Activity records is being expanded to include two new options: ‘Post-Entry Practitioner’ and ‘Student Recruitment Officer’.
These additional values will allow members to more accurately identify the roles of staff involved in delivering Activities, supporting more detailed recording and reporting of Activity delivery.
This update applies to the ‘Delivered By’ field within Activity records on the database.
There will be no impact on data, reports, the API, or Roles and Permissions.
Does this change affect the structure of Import and Export templates?
Yes. The addition of ‘Post-Entry Practitioner’ and ‘Student Recruitment Officer’ to the ‘Delivered By’ field will affect Activity Import and Export templates.
Following the Winter 2026 Update, members will need to download the latest Activity Import templates to ensure they are using the most up-to-date field values.
Members using custom import templates will also need to update these to reflect the new options. If your organisation uses Activity Export templates with other software or reporting processes, you should review these to ensure they accommodate the new values.
The geographical information available within the system is being updated to align with the latest deprivation measures. This includes introducing new Lower Layer Super Output Area (LSOA) and Middle Layer Super Output Area (MSOA) 2021 codes and names, alongside updates to the existing LSOA and MSOA 2011 field labels.
These changes follow the introduction of the 2025 Indices of Deprivation measures for England and Wales in the 2026 Postcode Profiler Refresh. The legacy LSOA 2001 field will also be archived, following the previous retirement of the POLAR3 deprivation measure.
These changes will affect the Postcode Profiler Report (members only) and its underlying data, as well as the Geography tab on Student and Ambassador records within the database.
There will be no impact on data, import templates, reports, or Roles and Permissions.
Is this a breaking change that affects the API?
This update introduces a change affecting the /postcodedata and /students API endpoints.
This change will not break your API interrogation. Rather, the LSOA 2001 field will be archived and will no longer be refreshed as part of future postcode updates. We will seek to permanently remove this archived field no earlier than 12 months from this change.
New LSOA 2021 and MSOA 2021 fields will be introduced to provide members with the latest available geographical data. Members using these API endpoints should review any existing integrations or processes that rely on LSOA 2001 data and consider updating them to use the new geographical fields.
Does this change affect the structure of Import and Export templates?
The Postcode Profiler Report output will be updated to include the new LSOA and MSOA 2021 codes and names, alongside revised labels for the 2011 fields. The LSOA 2001 field will be removed.
We are introducing additional checks when bulk deleting Field List values (members only), to improve data integrity and prevent required fields from being left without a value.
Previously, deleting Field List values could result in records being left with blank values, even where the field was mandatory.
This update ensures that when deleting a value from a required Field List, members must select a replacement value before the deletion can proceed. This will help maintain data completeness and consistency across records.
This update applies to the bulk actions functionality within the Field Lists page, available to those with the required permissions in the My HEAT area of the system.
There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.
As part of this update, we have introduced several accessibility improvements to make the database more user-friendly and easier to navigate.
These changes include the introduction of a new ‘Hidden Fields’ icon to clearly indicate which fields have been hidden from view, alongside adjustments to text and background colours to improve readability and alignment with accessibility contrast guidelines.
These improvements aim to provide a clearer, more consistent and accessible experience for members using the database.
For further information on our accessibility work, please see our announcement: Completion of Accessibility Review 2026.
To improve consistency across Institution records and provide easier access to Institution profiling data, we are expanding the existing functionality that automatically copies data from closed Institutions to their single successor Institution.
Currently, this functionality applies to data within the Geography tab. This update will extend the same approach to the Attainment and Destinations tabs, ensuring that relevant data from closed Institutions is also available on their successor Institution records.
Data will only be copied where it does not already exist on the successor Institution record, ensuring that existing information is not overwritten or removed.
This update applies to the Attainment and Destinations tabs within Institution records on the database.
There will be no impact on import templates, exports, reports, the API, or Roles and Permissions.
Does this change affect any data values on the database?
Yes. Where an Institution has closed and has a single successor, existing Attainment and Destinations data from the closed Institution will automatically be copied to the successor Institution record where that data does not already exist.
Existing data on successor Institution records will not be overwritten or removed.
The ‘Activities Including Sessions’ and ‘Activities Including Sessions with Students’ exports will now include all Activities, regardless of whether they have Sessions attached.
Previously, these exports only included Activities with associated Sessions. By including Activities without Sessions, members will have a more complete view of their Activity data, supporting more accurate monitoring and reporting of engagement.
This update applies to the ‘Activities Including Sessions’ and ‘Activities Including Sessions with Students’ exports within the database.
There will be no impact on reports, the API, or Roles and Permissions.
Does this change affect the structure of Import and Export templates?
The content of the ‘Activities Including Sessions’ and ‘Activities Including Sessions with Students’ exports will be updated to include Activities without associated Sessions, which were previously excluded.
Previously, where a Student’s attendance status was ‘Unconfirmed’, the ‘Student Attended’ column would appear blank in Activity exports.
We have corrected this so that ‘Unconfirmed’ is now displayed as a value, allowing members to distinguish between unconfirmed attendance and missing information when reviewing and reporting on Student engagement.
This update applies to the ‘Student Attended’ column in the following members only exports:
There will be no impact on data, reports, the API, or Roles and Permissions.
Does this change affect the structure of Import and Export templates?
The affected exports will now display ‘Unconfirmed’ in the ‘Student Attended’ column where a Student’s attendance has not been confirmed, rather than leaving the field blank.
No changes to the export column structure or import templates have been identified.
An issue was identified on some members’ Activity records where negative Student counts could appear in the ‘Unknown’ column of the Beneficiary Institutions table.
This may have occurred when merging duplicate Student records, where a Student inherited Institution information from another record.
We have corrected the calculation to prevent these incorrect negative figures from appearing, improving the accuracy of Student participation information within Activity records.
This update applies to the ‘Unknown’ column within the Beneficiary Institutions table on Activity records in the database and Activity exports.
There will be no impact on import templates, exports, reports, the API, or Roles and Permissions.
Does this change affect any data values on the database?
Yes, this update corrects the calculation of Student counts displayed in the ‘Unknown’ column of the Beneficiary Institutions table
Members who previously encountered negative figures may notice changes to the displayed Student totals following this correction.
Following the removal of the legacy Event Info functionality from Event Programmes (members only) in the Summer 2026 Update, we are removing the associated ‘Import Event Programme Event Info’ permission from roles within the database.
As this functionality is no longer available, the permission is no longer required. This change will help streamline role configuration by removing an obsolete permission and ensuring that available role settings reflect current database functionality.
This update applies to the Roles and Permissions area within the database. The ‘Import Event Programme Event Info’ permission will be removed from both existing roles and the configuration options for new roles.
There will be no impact on data, import templates, exports, reports, or the API.
Are there any changes to Roles and Permissions?
Yes. The ‘Import Event Programme Event Info’ permission will be removed from all existing roles and will no longer be available when configuring new roles.
As the associated Event Info functionality has already been retired, this change will not affect access to currently available Event Programme features.
To improve consistency in how Student registration permissions are applied across Activities and Sessions, we are updating the permissions required to register Students through the Activity Session Beneficiary Institutions table.
Previously, users with only the ‘View Students’ permission could register Students to Activity Sessions. This update ensures that users must have either the ‘Register Students’ or ‘Edit Students’ permission to carry out this action.
This change aligns the Session registration functionality with the existing permission requirements for the main Activity Beneficiary Institutions table, ensuring a consistent approach to managing Student registrations.
This update applies to the Beneficiary Institutions table within Activity Sessions on the database.
There will be no impact on data, import templates, exports, reports, or the API.
Are there any changes to Roles and Permissions?
Yes, the existing ‘Register Students’ and ‘Edit Students’ permissions will now be enforced when registering Students through the Activity Session Beneficiary Institutions table. Users with only the ‘View Students’ permission will no longer be able to perform this action.
Existing security measures prevent users without the relevant ‘View Student Special Category Data’ or ‘View Ambassador Special Category Data’ permissions from generating exports or reports containing this information.
Whilst most users on the system cannot see exports generated by others, we have found, through permission testing, roles where an individual can access other user’s exports and reports, the system was not checking for the special category permission.
The system now checks to ensure that users can only download exports and reports containing special category data where they have the appropriate permissions, regardless of who originally generated the file.
We have also improved how permissions are applied when accessing records shared by other Institution Groups. Where your organisation shares special category data with another organisation, both the sharing arrangement and the individual user must have the appropriate permissions to access this information. These changes ensure that existing special category data permissions are consistently enforced, helping to prevent unauthorised access to sensitive information.
This update applies to the exports and reports pages with records containing Student or Ambassador special category data within the database.
The additional permission checks will apply to the following member-only exports and reports where special category data is included:
There will be no impact on data, import templates, or the API.
Are there any changes to Roles and Permissions?
Yes, the ‘View Student Special Category Data’ and ‘View Ambassador Special Category Data’ permissions will now be consistently enforced when downloading exports and reports generated by other users.
When accessing records shared by another Institution Group, both the sharing arrangement and the individual user must have the appropriate permissions to view special category information. Members may wish to review their existing role permissions and sharing arrangements to ensure that users who require access to special category data have the necessary permissions.
To make it easier for members to identify and manage duplicate Student records, we have introduced new search and filtering functionality to the Student Duplicates page.
Members can now search through scanned duplicate records and filter the results by Student HEAT ID and/or Institution. This will help members locate specific duplicates more efficiently and streamline the process of reviewing and cleaning Student data.
This update applies to the Student Duplicates page within the database.
There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.
Members can now use the NOT operator (!) when filtering Activity records (members only), allowing specific values to be excluded from search results.
This additional filtering option provides greater flexibility when searching for Activities, making it easier to narrow down results and identify relevant records.
This update applies to the filters available on the Activity search page within the database.
There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.
To improve the accuracy of Ambassador working hour calculations, we are updating how Accepted Hours are calculated for Work Opportunities to exclude unpaid breaks.
Previously, unpaid break hours were included in an Ambassador’s total Accepted Hours for the week, month and year. This update ensures that only working hours are counted, providing a more accurate reflection of the hours an Ambassador is scheduled to work.
This change will also help members manage working hour restrictions, particularly for Ambassadors with visa-related working limits, by reducing the risk of unpaid breaks incorrectly contributing towards their permitted working hours.
This update affects the Accepted Hours displayed in the Ambassador table within the Applicants tab of Work Opportunity records.
This change will not affect Timesheets or the calculation of hours recorded through Timesheets.
There will be no impact on, import templates, exports, reports, the API, or Roles and Permissions.
Does this change affect any data values on the database?
Yes. The Accepted Hours totals for Ambassadors assigned to Work Opportunities with unpaid breaks will be recalculated to exclude those breaks.
This may result in lower weekly, monthly and yearly Accepted Hours totals compared with previous values. The underlying Work Opportunity hours and unpaid break information will not be changed.
Ambassadors who are marked as unavailable, archived or out of contract will now be able to continue viewing their previously accepted Work Opportunities through the Ambassador Portal.
Although these Ambassadors will remain unable to apply for new opportunities, retaining access to their existing Work Opportunity information will allow them to review previous commitments and provide greater transparency over their accepted opportunities.
This update applies to the Work Opportunities area within the Ambassador Portal.
There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.
To make it easier for members to identify and manage financial records across different departments, we are adding an ‘Activity Department’ column to the Timesheets and Expenses tables within the database.
This update will allow members to quickly identify which department an Activity is associated with when reviewing and processing financial records. The new column will also be sortable, making it easier to organise and locate relevant information.
The new ‘Activity Department’ column will be available in the following areas of the database:
The ‘Department’ field will also be added to Timesheet and Expenses exports.
There will be no impact on data, reports, or the API, or Roles and Permissions.
Does this change affect the structure of Import and Export templates?
Yes. A new ‘Department’ column will be added to Timesheet and Expenses exports.
The Student information returned through the HEAT Activity Students API is being updated to reflect HESA’s Data Futures model.
Following previous developments to align Student and Ambassador fields with HESA Data Futures, several legacy True/False fields were replaced with new list-based fields to provide more detailed and accurate information.
This update ensures that the Activity Student API payloads reflect the new field values, supporting members in accessing consistent Student information through the HEAT API.
For further background, please refer to our previous announcement, ‘Upcoming development: Update to align Student and Ambassador field values with HESA’s Data Futures model’.
This update applies to the /activities/{ID}/students endpoint within the HEAT API.
There will be no impact on data, import templates, exports, reports, or Roles and Permissions.
Is this a breaking change that affects the API?
No. However, members should be aware of an upcoming breaking change scheduled for the Summer 2027 Update.
The Activity Student API payloads will now return values aligned with the HESA Data Futures model through the following properties:
The following legacy properties will remain available temporarily but are now deprecated:
These six deprecated properties will be permanently removed from the API as part of the Summer 2027 Update. This will introduce a breaking change for integrations that continue to rely on them.
Members using the Activity Students API should review and update their existing integrations to use the replacement properties before the Summer 2027 Update.
Members registering Students to Activities through the HEAT API will now be able to assign or update their Evaluation Group as part of the registration process.
Previously, Evaluation Group information could not be set through this API functionality. Introducing this option will provide greater flexibility when managing Student registrations and help streamline data recording for evaluation purposes.
This update applies to the following HEAT API endpoint:
There will be no impact on data, import templates, exports, reports, or Roles and Permissions.
Is this a breaking change that affects the API?
No. This is a non-breaking change that introduces additional functionality to the existing /activities/{ID}/students endpoint.
A new EvaluationGroup property will be available within the API payload, allowing members to assign or update a Student’s Evaluation Group when registering them to an Activity.
The new property is optional. Where an Evaluation Group is not specified, the Student will continue to be assigned to the ‘Participant’ Evaluation Group by default, in line with the existing functionality.
Existing API integrations will therefore continue to work without requiring any changes
An issue was identified within the HEAT API where users without the ‘View Student Special Category Fields’ permission could still retrieve special category information when accessing Student records associated with Activities.
This update corrects the permission checks to ensure that special category data is excluded from API responses where the user does not have the required permission, strengthening the protection of sensitive Student information.
This update applies to the following HEAT API endpoint:
There will be no impact on data, import templates, exports, or reports.
Are there any changes to Roles and Permissions?
Yes. This update changes how existing special category data permissions are enforced when retrieving Student information through the /activities/{id}/students endpoint.
Is this a breaking change that affects the API?
When retrieving Student information through the /activities/{id}/students endpoint, special category data will no longer be included in the API response for users without the required permission.
Members using this endpoint should review any existing integrations or processes that rely on special category data and ensure their API permissions and data handling processes are appropriate.
For those utilising the HEAT API, it is important to familiarise yourself with the following changes:
This update includes changes to how existing role permissions are applied. Please refer to the following items for further details:
Please refer to the individual update sections above for further details on how these changes may affect user access and permissions.
If you have any queries about the changes included as part of the Winter 2026 Update to the database, please get in touch and we would be happy to help.