Skip to Content
Technical Update

Winter 2026 Update

10 November 2026

There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.

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:

  • Activities sheet: Using #NULL in the Beneficiary Institutions field will now remove only those Institutions omitted from the updated list, along with their associated Student registrations on the Activity and Sessions. Beneficiary Institutions retained in the list will keep their registered Students.

For example: Activity #12345 has four Beneficiary Institutions registered:

  • Maplewood Academy (10 registered Students)
  • Bamford Academy (5 registered Students)
  • Oakwood Academy (8 registered Students)
  • Riverside Academy (12 registered Students)

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.

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.

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.

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.

There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.

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.

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.

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.

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.

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.

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.

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.

 

There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.

There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.

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.

There will be no impact on data, import templates, exports, reports, the API, or Roles and Permissions.

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.

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:

  • YoungCarerType
  • PartTimeType
  • EstrangedType
  • ServiceChildrenType
  • DependantType
  • CareLeaverType

The following legacy properties will remain available temporarily but are now deprecated:

  • IsEstranged
  • HasDependents
  • IsPartTime
  • IsYoungCarer
  • IsServiceChildren
  • IsCareLeaver

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.

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

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: