April 2025 release 1

Trainee tutors can now assess evidence.

When a trainee tutor is using Marking Aid and they want to assess learners' evidence, they can complete this task. The existing flow for trainee tutors now being respected for components utilising Marking Aid.

Learners will see tutor feedback only after trainee tutor’s feedback is accepted by an experienced tutor.

View/Edit Marking Aid exercises when the learning plan component template has been deleted.

When a learner or tutor accesses a Marking Aid assignment, they can now view and submit exercises even if the learning plan component has been deleted in the Programme Builder. This ensures that learners and tutors retain access to completed work and feedback. Existing workflows and status updates remain unchanged.

When a tutor is using the prior learning section in a review, this section will now be populated in the review PDF. Previously, the prior learning table was not exported to the review PDF.

Learners or employers who have access to view the review will see this section in the review PDF. The entire content of the table will be exported to the PDF including the cost section.

When the section is not populated in the review, an empty table will be exported and a description will read “No prior learning recorded”.

When a tutor who only has access to Console wants to review learner Reviews from previous programmes, they can now do so by going to the learner → documents → review documents. The UI for review documents from the current programme remains the same and displays signature data within the grid. Previous programmes will be shown in a collapsed section and once expanded, historic reviews will be listed, with the option to expand the individual review and download the specific PDF.

The compliance document version control functionality streamlines the management of compliance templates, saving significant administrative effort and improving reporting accuracy.

With version control, administrators can now update compliance templates directly within a programme without requiring learners to re-sign updated documents unnecessarily. This eliminates redundancy, reduces administrative overhead, and ensures that compliance document updates align seamlessly with programme needs.

For more information, see: Compliance Documents Template Version Control.

Improved OData Access Control.

Our OData API now aligns data access with your existing group permissions as part of our ongoing enhancements. Your API token will reflect your group hierarchy, ensuring that data access aligns to assigned groups. To avoid unnecessary access issues, please ensure that your admin accounts have the necessary group permissions to maintain access. This update is part of our continued work to ensure more granular control over your data, aligning to defined groups. These changes will impact our Power BI reports as they use the same OData Tables.

For more information, see: OData Feed Access - Generating Tokens and Group Limitations.

Responses for 'Individual Support Needs/Requirements' review section now available via OData.

As an administrator, when I am using the Review Responses OData feed to report on Review Responses, I can now report on newly added responses to the Individual Support Needs/Requirements section. The data will be accessed via the Review Responses OData table, and will be available immediately upon release for customers who already have the Review Responses feed enabled within their tenant. Please note the responses will be available for reviews started after the release date. A migration of historic responses will be available in a future release.

• As an MIS Manager I want the dashboard to correctly exclude specific types of withdrawals from QAR calculations according to ESFA rules so that the data aligns with compliance rules and accurately reflects performance measures. Learner aims that have transferred to a new provider or to a new aim at their current provider (within 120 days) are excluded from the QAR data.

• As an MIS Manager I want the dashboard to correctly identify when a learner aim has been forced into a particular year using the Force Include in Batch option so that reporting reflects accurately the hybrid years and complies with funding rules.

• As an MIS Manager I want the dashboard to accurately identify learner aims that are overdue from a planned break so that I can ensure timely interventions and maintain compliance with ESFA regulations. Learners are now flagged as overdue if they have failed to return before the end of the following academic year or have returned after that date.
  For example, a learner that went on a break on 8th October 2021 would need to return to learning on or before 31st July 2023 otherwise they will be flagged as overdue.

• As an MIS Manager, I want the dashboard to calculate the number of days in the minimum learning period according to ESFA rules so that the data remains accurate and compliant with funding regulations. The query has been updated to include both start date and planned/actual end dates in the number of days between the two dates, as per ESFA rules.

When a tutor is using the PLR section in a review, this section will now be populated in the review PDF. Previously, the table with PLR records and level that were chosen were not exported to the review PDF. Users who have access to view the review will see this section in the review PDF.

When exporting from Console, the entire content of the table will be exported to the PDF excluding the Certificate/Evidence section. The highest qualifications exported to the ILR will be included in the PDF. The calculated levels of attainment will not be exported to the PDF. When the section is not populated in the review, an empty table will be exported and a description will read “No PLR records available”.

When exporting from Classic, the entire content of the table will be exported to the PDF excluding the Certificate/Evidence section. In Classic, the user is not able to select the highest qualifications exported to the ILR as this part of the PLR is not visible in Classic. The PDF will therefore export this section with the default values of "None". The calculated levels of attainment will not be exported to the PDF. When the section is not populated in the review, an empty table will be exported and a description will read “No PLR records available”.

Note: To get the most up-to-date functionality, customers should use Console for Reviews.

• Admins with access to the ILR can now enter payment (PMR) records with up to 2 decimal places. When the ILR is exported these will be rounded to the nearest whole amount as per the ILR guidance. To avoid a breaking change to OData, these values will round to the nearest whole number. We aim to make this change in a future update.
• The “Meeting Notes and Transcripts” review section is now named “Meeting Details”. This change makes it clear that this section is used to display summaries as well as transcripts for those customers who choose to use Review Summarisation in the future.
  

• We have fixed an issue where an admin importing a .csv with learners without email addresses would not see an error. Now in this case an error message will be displayed on the import popup, preventing users from uploading.
• We have fixed an issue with heading level on the Caseload Dashboard. Prior to the fix there was no h1 present, we have now added a h1 and appropriate other heading levels. Users tabbing through using a screen reader will now move logically through the headings without the appearance that they have missed heading levels.
• We have fixed a defect whereby the Sign All button was unavailable for Employers in Console with the Compliance Mass Processing role. Now, when an employer user has the "Compliance Mass Processing" role, they will be able to "Sign All" documents from the Signatures grid.
  

We are working towards our next iteration of the Aptem Enhance Marking Aid and Feedback Assistant features. We will be gathering feedback from our early adopter customers to work towards an iteration that will extend existing functionality allowing us to wider the use of the feature for beta trial customers.

Within the Caseload dashboard, we are adding the ability to drill down on metrics - this functionality is already available for the Data Checks tab, and we are expanding this across the other applicable tabs.

We plan to change the periodic triggers in Checkpoint to be relative to the learner's start date, instead of the start date configured in Checkpoint settings. This will align with the way relative dates work in the Learning Plan and improve the user experience for learners, so that Checkpoints are staggered appropriately across their programme. This will allow customers who operate on a roll-on, roll-off basis to make use of the Checkpoint functionality.

We are developing a feature that will summarise key discussion points and themes from a Review, removing the distraction of notetaking and resulting in more meaningful conversations for all parties.