Modular Learning

In this release, you can tailor a learner’s Learning Plan by adding whole modules of content rather than individual activities, then fine-tune each module to suit them.

For example, many providers add Functional Skills into Programme templates, then spend around 15 minutes exempting activities for learners who don’t need them. Combined with the aim management improvements in Release 7.4, you can now add a Functional Skills aim and its module content in two simple steps, only for the learners who need it.

If you’re interested in finding out more about our Modular Learning feature, please see this article.

Add a full module to a learner’s Learning Plan in one step

Published modules can now be imported into a learner’s Learning Plan, bringing all the module’s assigned content with them. During the import process, the user can set the due dates of all the content in one simple step, making the process of adding lots of content far more efficient.

For more information on importing Modules into Learning Plan, see this article.

Tailor a module to the learner once it’s in their plan

Trainers can now add extra content from the Library directly into a module within a learner’s Learning Plan, allowing your teams to tailor modules to specific learners’ needs.

View the Learning Plan by month or by module

With modules now in the Learning Plan, users have the choice to view content by month or grouped by module.

Modules in the Library can go through approval

Modules in the Library can now be sent for approval, where they can be accepted or rejected by the Programme Manager before use.

For more information on creating and publishing Modules, see this article. 

If you’re interested in finding out more about our Modular Learning feature, please see this article.

Generate a new Training Plan straight after recording a change 

You can now generate a new Training Plan without leaving the change workflow. When you submit an Edit aim or Add aim change, the Changes submitted screen offers a Generate training plan document option. 

Confirm, and Bud generates a refreshed Training Plan that includes your change and takes you straight to it. Until now, you had to leave the workflow and find the learner’s application to generate the plan from there.

Generating a new Training Plan clears any signatures already collected, so the plan will need to be signed again.

You don’t have to use the option. Your change is already saved, and returning Back to Manage changes takes you to the change history as before.

For step by step guidance, see Change Automation: Generate a Training Plan Document

Bug Fixes

In this release, we have resolved the following bugs:

• Employer contact resets when the Training Plan is re-signed: In some scenarios, re-signing a Training Plan caused the updated employer contact on the Learning Plan to revert to the original employer contact. This is now fixed.
• 400 error when creating an OST application via API without the trainer ID: The trainer ID is now optional, as it can be added in the platform later. This means you will no longer receive a 400 error when creating an OST application without the trainer ID.
• Funding adjustment for prior learning removed from a restarted maths or English aim on withdrawal or completion: When an apprentice returned from a break in learning, the restarted maths or English aim showed a Funding adjustment for prior learning on the ILR. If the learner was then withdrawn or completed, that value was removed. This is now fixed, and the value stays on the aim after withdrawal or completion. No action is needed. The ILR is corrected the next time it is generated. If you have already put the value back with an override, the override stays in place.
• Removing an older exemption through Edit aim did not put the aim back on the ILR: If an aim was made exempt before the 15 September 2026 update, removing the exemption through Edit aim did not add it back to the ILR. This is now fixed, and the aim returns to the ILR when its exemption is removed.
• Typo corrected in Gateway Review: A typo in the Gateway Review has been corrected.
• Files couldn’t be downloaded from the activity preview in Programmes: Files attached to activities from the library couldn’t be downloaded when previewing the activity within a Programme template. This is now fixed; files download as expected.
• Exempted activities with pending hours showed as ‘In Progress’ on the Hours Logged page: Exempted activities that had pending hours were showing a status of ‘In Progress’ on the Hours Logged page. This is now fixed; these activities now display the exempt status.
• Unset activities were removed from the Learning Plan when enrolment documents were signed after the start date: Where enrolment documents were signed after a learner’s start date, unset activities with a due date before the signature date were removed from their Learning Plan. This is now fixed and will not occur going forward. Learning Plans already affected are not restored automatically.
• Programme Assessment content updates weren’t following propagation rules: Changes to assessment content in a Programme were reaching all assigned learners, including those who shouldn’t have received the update under propagation rules. This is now fixed; content changes now follow propagation rules. Assessment scheduling was not affected.

Business Intelligence Release - 11th November 2026 (2:45pm)

Please note your reports may be blank for a brief time afterwards

Standard Reports - Wellbeing Concerns

As part of our continued work on inclusion and wellbeing, we’ve added a new report to the Standard Reports suite. It shows all concerns raised for learners in Bud’s wellbeing concern log, along with the actions managed within each concern, so you can follow a learner’s full wellbeing journey in one view.

To find it, go to Standard Reports > In-Flight Learners and Breaks > Learning Support, then select the Wellbeing Concerns link in the page header.

Bug Fixes

In this release, we have resolved the following bugs:

• MFA % Required displayed as a decimal in the admin report: The 'MFA % Required' value in the admin report was showing as a decimal. This is now fixed, and it displays as a percentage as expected.