Release 6.7 - 20th January 2026

Turnitin - Enterprise

We are pleased to launch our integration with Turnitin Similarity. This integration enables trainers to check Learner's work for plagiarism within the Bud platform, streamlining and simplifying the process with fewer manual steps required.  

To make use of this integration, you will need to already have a Turnitin License. If you already do, then please speak to your Customer Success manager to get this enabled.

For more information, please see the following articles:

 

OTJH in Programme Build

We have updated the text on the "Activities" tab of the Programme Build so that the latest January OTJH values are now displayed alongside the previous values for Apprenticeship Standards.

The example below shows a standard with OTJH values in January 2026, August 2025, and before August 2025.

OTJH activities.png

 

Bug Fixes

In this release we have fixed the following bugs:

  • Employer contact cannot register as a learner - where a user is already registered as an employer contact and then invited to be a learner, some users were not seeing the role picker to switch between user types.
  • Cannot edit the ILR for OST learners that have been transferred to another trainer
  • Learners registered with more than one provider cannot add OTJH in submissions - the provider's OTJH configuration settings related to the Bulk OTJH feature switch will now be correctly applied.
  • OST learners registered with more than one provider cannot access their application
  • Saving ILR overrides - unable to save changes after removing a section in the ILR. Following a previous fix, this has been extended to all Learner, Employer, and Learning Delivery sections of the ILR.
  • ILR field LLDD returning a value of -1
  • Incorrect character limit Vs error message on return to learning comments field - There was a discrepancy between the number of characters it was possible to enter into the “return to learning” comments field (500) compared to the indicated maximum (4000). These have now been aligned and it is now possible to enter 4000 characters as indicated.
  • Returning from a break can update the wrong ILR year during cross-over - It has been observed that during the crossover period, if a learner returns from a BIL with a date returned to learning >= 01/08/202x, the ILR year that ended on 31/07/202x is being updated with the new practical period end date. This behaviour has now been corrected, and the previous academic year’s dates will not get updated.  
  • Learner Prior Attainment - Previously when exporting an ILR from Bud, a learner could only have 1 prior attainment record in the ILR which may lead to errors when a learner progressed onto a higher level apprenticeship within the same ILR academic year. This has now been amended to allow a collection of prior attainment records to be exported into the ILR XML where applicable for that academic year. Where more than one prior attainment record is applicable to an academic year, the ILR will reflect multiple entries in the example format shown below:  
     
    <PriorAttain> 
          <PriorLevel>4</PriorLevel> 
          <DateLevelApp>2023-03-21</DateLevelApp> 
        </PriorAttain> 
        <PriorAttain> 
          <PriorLevel>8</PriorLevel> 
          <DateLevelApp>2025-03-27</DateLevelApp> 
        </PriorAttain> 

 

Business Intelligence - 21st January at 14:30

ILR Compliance Reporting

We’re excited to launch an addition to our enterprise reporting suite, giving early insights into ILR Validation Errors and Warnings and key DfE Funding Rules Monitoring (FRM) reports. More details are in our helpdesk article.

ILR Validation Rules
This release includes the top ILR Validation Rules, with more to be added in future iterations. Use these reports to spot data issues early, resolve errors throughout the month, and minimise the month-end rush. Reports replicate DfE logic for guidance only—your DfE files remain the final source of truth.

FRM Reports
FRM reports highlight learners who could be flagged against DfE rules. These checks run against your tenancy’s ILR data only, so they may show a subset of issues compared with full DfE reports across all Training Providers. Use them to identify potential issues early, but remember your official DfE submissions remain authoritative.

 

Data Warehouse Fields

The following field has been added to the data warehouse as part of this release:

Table Name Column Name Description Data Type
User Is Turnitin administrator Is a Turnitin administrator int