April 2026 release 1

Centralised management of signature requests for compliance documents

When an administrator uses the tenant settings to manage compliance document signature requests, they can now centrally enable and configure automated email notifications for outstanding signatures at the tenant level.

This change introduces a dedicated Email Notifications page within Branding & Customisation, allowing configuration by compliance document type, frequency, programme start date, and learner status. It streamlines setups for all customers, and ensures notifications are sent only to relevant managers based on selected frequency, date and programme statuses.

Users receive email when document is available for signature

When a learner, tutor, or employer needs to review documents in Aptem that require their signature, they now receive an automated email prompting them to sign.

This change introduces email notifications for any user who has not yet added their signature to a required document. It ensures users are informed without needing to log in to check for pending signatures, helping prevent delays in workflows and improving timely completion.

Please note, emails will be sent to users who are yet to sign the document upon the following events:

• When the document is generated (i.e. a review is finished, or a compliance document is created)
• When any other user signs the document

This follows the system notification behaviour. Note that the email settings need to be set to at least "Only essential emails" for the notifications to be received.

Employer signature invitation email

The format of the employer signature invitation email for compliance documents has been updated and the link in the email will take them to Console if they have access.

Additionally, employers who are invited to sign compliance documents will receive periodic reminders for any outstanding signatures if enabled at the tenant level. Note that the email settings need to be set to at least "Only essential emails" for the notifications to be received.

Users receive reminder where document remains unsigned

When a learner, tutor, or employer is required to sign a document in Aptem, they will now receive automated reminder emails prompting them to complete their signature where this is configured in console settings.

This change introduces a configurable reminder that sends follow-up emails to any user who has not yet signed a required document. Reminders are triggered as per the start date and frequency set at the tenant level, until the document is signed. Tutors and employers are directed to the signatures grid, while learners are taken to their documents folder.

Note that the email settings need to be set to at least "Only essential emails" for the notifications to be received.

Centralised management of signature requests for reviews

When a tenant administrator uses Branding & Customisation in Console to configure email notifications for reviews, they can now enable and manage automatic reminder emails for outstanding review signatures at tenant level.

This change centralises the configuration of review signature reminders, allowing customers to control reminder cadence, learner enrolment start date, and applicable programme statuses from a single location.

The update ensures reminders are sent to the employer defined as the learner’s manager, while respecting user email preferences and existing manual signature requests.

Auto actions

When a tutor uses the review summary to track actions, they can now generate actions directly from the summary with a single click of the Generate actions from summary button. The button will appear if the Meeting Summary section is enabled. The button is only available for tutors, and only tutors can edit/delete the actions generated from the summary.

This change enables automatic extraction and addition of actions to the actions section, displays a “Generated from summary” label for each, and provides user feedback during processing. Actions are saved automatically and linked to the summary for traceability. 

Notification of successful actions generation

When a tutor generates actions from the summary, they will be notified when the generation is complete and will see the actions on the screen straight away.

Prevention of concurrent requests

When a tutor uses the auto actions feature to create actions for a review, they can now rely on built-in safeguards that prevent duplicate actions from being generated. The button is automatically disabled after being clicked, and the backend now restricts concurrent requests to one per particular review.

This change addresses an issue where multiple clicks could trigger duplicate action generation, leading to redundant data. If a tutor refreshes the page mid-generation and clicks the button again, or if multiple tutors click the button at roughly the same time, a notification will inform them that actions are already in progress.
 

Warning message when re-generating actions 

This change introduces a confirmation dialog to prevent accidental duplication, clarifying that re-generating actions may result in duplicates requiring manual deletion.

It may impact review workflows, and users may need to review and delete any duplicate actions if they choose to proceed.

Tutors will be able to see the actions from the previous review by selecting the ‘Generated from previous review summary’ link, this will open up the previous review actions in a new tab. The review ID number will be seen at the end of the URL.

Funding Dashboard: Learner data fields restored

When an administrator uses the Funding Dashboard to review learner funding information, they can now see all expected fields in the Learner aims, status and funding data table on the Funding data page.

This change fixes an issue where several fields were missing from the table. The table has been restored to its previous structure, ensuring all learner, status, and funding fields are now displayed as expected.

It may impact how learner funding data is viewed and exported, and Admins may wish to revisit the table if previously missing fields affected analysis or reporting.

Funding Dashboard: Group filtering added across reports

When an administrator uses the Funding Dashboard to analyse and monitor data by organisational structure, they can now filter reports using Group selections across all applicable pages.

This change introduces consistent group filtering across the Funding Dashboard (excluding the Funding Data page), aligning it with other dashboards and enabling users to segment and view data by their selected groups. The implementation ensures accurate data is returned while maintaining overall dashboard performance.

It may impact how data is filtered and segmented across reports, and admins may wish to apply Group filters to tailor views and compare performance across different organisational structures.

Quality Dashboard: Ofsted inspection label correction

When an administrator uses the Quality Dashboard to review Ofsted inspection information, they can now see the Ofsted inspection page labelled correctly.

This change fixes a spelling error in the page title to ensure the terminology matches the official Ofsted naming and maintains consistency across the dashboard.

This update does not impact data, calculations, or reporting, and no action is required from admins.

Quality Dashboard: Break in Learning status display corrected

When an administrator uses the Quality Dashboard to monitor learners currently on a break in learning, they can now rely on the Learners on a Break page to display only learners who are actively on a break.

This change fixes an issue where learners who had returned from a break in learning were still appearing in the Learners on a Break view. The logic has been corrected so that learners who have resumed their programme are no longer included in this page.

It may impact how break in learning figures appear within the dashboard, and Admins may wish to refresh or review the page to confirm that only active breaks are now displayed.

Quality Dashboard: Removal of legacy pages

Following the introduction of the Delivery Summaries page, we will soon be removing the following legacy pages:

• Delivery Table
• Delivery Table (Ethnicity)
• Delivery by Qualification

What this means: The Delivery Summaries page provides a full replacement for these pages, including:

• All existing data, plus additional insights
• Dynamic grouping by Qualification (default), Age range, Disability, Ethnicity and Gender
• Multi-level grouping and configurable grouping order
• Learner information included across all views

Action required: If you currently use these pages, please begin using the Delivery Summaries page ahead of the removal to ensure a smooth transition.

• When an administrator uses the learner profile in classic or console to manage apprenticeship programmes, they can now view and assign a numeric “Standard Version” field within the programme details. This change enables accurate identification and tracking of the standard version a learner is aligned to, supporting correct integration with epaPRO and reducing issues at gateway or certification.

  It may impact data workflows for apprenticeship programme management, and users may need to ensure the correct version is selected and maintained, especially when learners change programmes or standards.

epaPRO (Proficient) integration

(epaPRO is now called Proficient) 

When an administrator uses the Aptem epaPRO integration to manage learners’ end‑point assessments, they can now include and view the learner’s standard version as part of the integration.
 

This change:

• Adds an optional “Standard version” field to the epaPRO mapping.
• Ensures the same LARS code + version cannot be mapped more than once, preventing duplicate mappings.
• Uses the mapped version during manual epaPRO registration and during automatic enrolment after 42 days from the learner’s start date.
   

Impact on data / workflows

• Admins can rely on accurate standard version data flowing from Aptem into epaPRO.
• Duplicate or conflicting LARS+version mappings are prevented, reducing data quality issues.
• Admins will still be required to set up specialisms where this required for a standard.

Actions for users

• Review and, where needed, configure the optional standard version field in your epaPRO mapping.
• Check existing mappings to ensure each LARS code + version combination is unique.
• Confirm that relevant delivery programmes have the correct version value set so it is surfaced in the learner’s End‑Point Assessment screen.

• When an administrator uses the OData reporting feeds for learning plan evidence to review and report on recorded learning hours, they can now see the Hours Type (e.g. OTJT vs English & Maths) for each relevant evidence record. 
  This change adds a new Hours Type field to the following OData feeds and expansions, ensuring the correct data is returned and aligned with our OData dictionary standards:
  • LearningPlanEvidences (excluding ‘Activity Log’ hours)
  • LearningPlanEvidenceWithActivityData (including ‘Activity Log’ hours)
  • Expanded UserEvidences_Evidence (excluding ‘Activity Log’ hours)
  • Expanded UserEvidencesWithActivityData_Evidences (including ‘Activity Log’ hours)
     
• When a tutor or administrator uses OData or User Generic Reports to analyse user data, they can now view and report on the standard version field from the user's profile. This change adds the standard version field to the users table in OData and to User Generic Reports, enabling more detailed reporting and data segmentation.
  It may impact reporting workflows, and users may need to update their report templates to include or utilize the new version field.

• SCORM content display: When an administrator uses SCORM digital components in a learning plan, SCORM assets now display without unintended borders. This change updates our HTML/XSS protection configuration to correctly whitelist valid iframe attributes used by SCORM content. This may impact how SCORM content is rendered in learner views. Users should review existing SCORM-based components to confirm content displays as expected and report any remaining visual issues.

• Keyboard accessibility in Reviews (Console): When a Console user selects Actions within Reviews using the keyboard, checkboxes can now be toggled using both the Enter and Space keys. This improves accessibility and consistency. Previously, checkboxes could only be selected using the Space key, which did not align with expected keyboard interaction standards.

• Activity review counter updates: When an administrator reviews, accepts, rejects, or deletes a learner’s activity in the learner grid, the “activities to review” counter now updates immediately. This ensures the counter reflects the current review status in real time, improving visibility for tutors and admins. Users may need to monitor or refresh the grid to confirm status updates after each action.

• Organisation profile data visibility: When an administrator views an organisation record, all associated Employer Logins, Employer Users, Referrer Logins, and Referrer Users are now displayed on the Organisation profile page.

• Checkpoint: When a tutor or administrator uses the checkpoint question generator to create questions for apprenticeship standards, they can now generate questions only for leaf criteria (criteria with no children). This change ensures that questions are not created for intermediate criteria, improving the accuracy and relevance of generated questions.

We are enhancing how marking aid exercises are managed to provide a more streamlined, scalable experience and greater administrative control.

Centralised management of programme-level exercises

Management of marking aid exercises at programme level will move from Programme Builder to the Marking Aid Management area. This will include:

• Linking and unlinking exercises to Learning Plan components
• Creating and linking new exercises
• Creating new versions of exercises
• Optionally applying a new version of an exercise to enrolled learners

Admins who currently perform these tasks in Programme Builder will continue to have access in the new location, provided they also have the Manage marking aid exercises role. To support a smooth transition, these tasks will remain available in Programme Builder for two months following the release. After this period, they will be fully managed within Marking Aid management.

New role for learning plan-level permissions

A new dedicated role will be introduced to manage marking aid exercises at Learning Plan level, including linking, unlinking and version control.

Previously, these permissions were included within Advanced Delivery Management roles. Based on customer feedback, this update provides greater control and reduces the risk of unintended changes. Users who need to perform these tasks will require the new role to be assigned.

Enhanced learner data

Additional learner data will be available within the marking aid exercise details screen to support improved reporting and oversight.

Power BI reports will be refreshed at tenant level whenever a user selects Refresh. This ensures that all administrators are viewing the same, up-to-date dataset, removing inconsistencies caused by individual report refreshes and eliminating data mismatches across users.