Introduction to Automated Processes (Trackers)

In this article:

  1. Overview
  2. Types of Trackers
  3. Why, who and what?
    1. Why automate processes?
    2. Who is involved?
    3. What are these automated processes?
  4. Example workflows
  5. Breaks in learning and returning to learning
    1. Extending a break in learning
    2. Making the Return to Learning tracker available
  6. What you might assume
  7. What you might query
    1. "Data isn't showing in the ILR as expected"
    2. "I've entered all the details into the tracker, but nothing has changed"
    3. "A tracker has been rejected. Can I change it and reassign it?"
    4. "Why isn't the Notes field filled in when we create a tracker through the REST API?"
    5. "Can we add extra steps to process automations to fit our workflows?"
    6. "We don't want to use some process automations," or "We don't have a process automation available"
  8. Related articles

Overview

This article introduces automated processes (Trackers) in Aptem. Trackers manage changes to learner records and provide a full audit trail of those changes. Because the automated processes are tested, they reduce manual errors and keep data consistent across Aptem.

For IT and Management Information System (MIS) teams, they save time, automate workflows for learner management tasks, and keep the full audit trails government funding schemes require.

Types of Trackers

Trackers let you document and manage internal cases for learners' Individualised Learner Records (ILRs), compliance and other parts of the learner journey. Tutors and admins can create and manage trackers in Aptem Classic or Aptem Console.

There are three types:

  • Basic tracker: shows information about learner activity when opened, for example a request to change an official name.
  • Automated tracker: sends internal messages to tutors, admins or assignees to show the request.
  • Process automated tracker: makes the changes needed in the ILR when learners request changes, such as a new name or address.

Why, who and what?

Why automate processes?

Process automation in Aptem:

  • provides a workflow for everyday learner management tasks
  • updates the relevant parts of the platform automatically
  • creates admin tasks so actions are completed
  • includes one-stage or two-stage approval
  • uses permissions so only responsible users can act
  • keeps a full audit trail of who did what and when.

In short, it saves time, reduces admin effort, lowers the risk of errors and keeps data consistent.

Who is involved?

Government funding for apprenticeships requires strict compliance with Department for Education (DfE) rules. The main roles in process automation are:

Compliance manager and/or head of MIS

Usually responsible overall for approving or rejecting process automation requests and committing the changes.

MIS officer and/or compliance administrator

Creates some process automation requests, and reviews and edits requests from tutors.

Regional manager and/or operations

May pre-authorise or reject initial requests, especially those from tutors.

Learners can also start some processes, such as registering a change of name or address.

What are these automated processes?

Aptem developed Trackers from its experience with a wide range of customers, to document and manage internal cases for learners' ILRs, compliance and journey. It can help to think of an automated process as an intelligent tracker.

Available automated processes

Automated process What it does
Change of name and change of address Captures the request and supporting evidence; updates the details across the system when approved
Break in learning Captures the details of the break; updates the system and ILR
Withdrawal from learning Captures the reasons and dates of withdrawal; updates the system and ILR
Recognition of Prior Learning and Calculator (RPL) Evidences adjustments to the training price; updates the price in the ILR
Change in working conditions Processes changes to working hours, working location or job title; updates the system and recalculates related figures
Return to learning Returns a learner to their training programme after a break
Change of (training) programme Moves a learner from one programme to another, after a requested change or an error
Additional Learning Support (ALS) Identifies ALS needs; applies ALS funding in the ILR; lets you start and stop funding claims for a learner
Successful completion of a (training) component aim Completes aims in the ILR when a set level or status is reached
Change of employer Captures the change and the new employer record; updates the ILR
Completion of a (training) programme Identifies successful completion of a programme; confirms all conditions for achievement or closure are met; updates the ILR and compliance documents

 

Example workflows

Learners usually move from active, to a break in learning, then either back to active or to withdrawn. A learner who withdraws can't return to active, but a learner on a break can.

Workflow diagram showing a learner moving between Active, Break in Learning and Withdrawn statuses

Some cases need several changes. For example, a learner returning from a break who has changed employer may also need to change training programme. Where several changes are needed, we recommend treating them as separate processes, in the order shown by the amber arrows.

Workflow diagram showing a learner returning from a break, then changing employer and programme, with amber arrows showing the order

Breaks in learning and returning to learning

Extending a break in learning

The return date on the Break in Learning tracker form is an estimate for monitoring. It doesn't need to be exact, and the planned return date isn't recorded in the ILR.

To extend a break, or if you don't know the exact return date yet:

  1. Update the tracker task with the correct details and reschedule the Return to Learning meeting.
  2. When the learner returns, raise a Return to Learning tracker and enter their return date in Date of return to learning. When the tracker is processed, the learner's aims show the correct return date. You don't need to update the ILR directly.

You can't change the return date on a tracker form once the tracker has been processed.

Making the Return to Learning tracker available

The Return to Learning tracker only shows for a learner if the ILR token is enabled on their programme, as well as the tracker being enabled in your tracker settings. If it doesn't show, enable the ILR token on the learner's programme. See Configure Process Automation settings for your tenant and A how-to guide for completing the ILR template.

What you might assume

People sometimes make wrong assumptions about automated processes:

  • "These process automations will correct errors for me." The platform relies on correctly entered data. It prevents obvious mistakes, such as wrong date formats, but can't stop incorrect data being entered.
  • "Using automated processes will mean that we lose control of our data." Processes are only carried out by users with the right roles. If you're concerned about control, use the pre-authorise role for initial oversight, with a second, senior user with the right permissions processing the change.

What you might query

"Data isn't showing in the ILR as expected"

Check:

  • the data entered in the tracker is correct
  • whether you or other users have changed ILR values manually since the tracker was processed, which can cause inconsistencies
  • the tracker has been set to Process. If it hasn't, no changes are saved.

"I've entered all the details into the tracker, but nothing has changed"

Check:

  • the tracker has been set to Process
  • the learner is in a suitable status for the process. For example, you can't put a withdrawn learner on a break
  • the learner has a valid ILR
  • the learner's ILR hasn't been excluded. If it has, the tracker doesn't update it.

"A tracker has been rejected. Can I change it and reassign it?"

No. Once a tracker is rejected it can't be reassigned or processed. Raise a new tracker instead. To remove a tracker raised by mistake, see Remove a tracker created in error.

"Why isn't the Notes field filled in when we create a tracker through the REST API?"

This is expected. The Notes field is only available once the tracker has been created, and doesn't keep what was entered. When you reopen the tracker, the field is empty, and previous notes are only in the tracker's audit history.

"Can we add extra steps to process automations to fit our workflows?"

No. The fields in each automated process are fixed and can't be changed. If you need to collect more information, use a custom review alongside the automated process.

"We don't want to use some process automations," or "We don't have a process automation available"

Process automations are optional and must be enabled for your tenant. See Configure Process Automation settings for your tenant.

Was this article helpful?
1 out of 1 found this helpful