Leadership and governance criteria are graded by Ofsted at whole-provider level, and the questions behind it are practical ones: do leaders know what is happening across delivery, do they act on it, and can a governor see enough to hold them to account.

Aptem is built so that the answers come out of the system rather than out of a reporting exercise. This article looks at the features that give leaders and boards that real-time oversight, and at what each feature changes in practice.

Caseload dashboard: highlighting pressure points

The caseload dashboard shows case owner caseloads, learner activity levels, programme progress and overdue or at-risk learner indicators across the provider. It is embedded in the platform as a Power BI dashboard, so no specialist software or licence is needed to read it.

What it changes is the conversation about workload. Distribution problems are usually invisible until someone is struggling: a tutor carrying more complex learners than their headcount suggests, or a team whose verification is quietly falling behind. Seeing caseload and activity side by side turns that into a resourcing decision a leadership team can take deliberately, rather than a problem that surfaces through absence or turnover.

Compliance dashboard: knowing where you stand before anyone asks

The compliance dashboard covers ILR status, funding status, learner compliance indicators and document signing status across the commitment statement, apprenticeship agreement and training plan. It also includes an Ofsted Inspection page presenting published inspection outcomes and ratings, drawn from external DfE and Ofsted data.

Compliance exposure is rarely one large failure. It is a handful of unsigned agreements, a few learners whose ILR data is incomplete, and no single place that shows all of it at once. A dashboard that reports the position continuously means leaders are managing a known number rather than discovering one, and the difference between those two positions is usually the difference between a correction and a clawback.

Funding dashboard: the financial picture next to the delivery priorities

The funding dashboard reports funding models, aims, planned against actual values, and Functional Skills funding data. It is built for monitoring the funding position and preparing ILR submissions.

Because it draws on the same records as delivery, financial and educational decisions stop being made from different versions of the truth. A leader looking at a cohort’s progress and a leader looking at its funding position are looking at the same learners, which makes questions about viability, growth and where to invest answerable in one conversation.

Quality dashboard: achievement in context

The quality dashboard calculates qualification achievement rates, retention and pass rates, and accountability framework measures including withdrawals, breaks in learning, learners past their planned end date and EPA registration. Results break down by gender, age, ethnicity and disability, and connect to published DfE and Ofsted data for comparison.

Those breakdowns are what make it a governance tool rather than a performance report. A headline achievement rate can look healthy while a particular group of learners does considerably worse, and that gap only becomes a board matter once it is a figure on a page. Seeing internal performance against published external data also gives a governor the context to judge whether a number is good, which is difficult to do from an internal report alone.

Programme Builder: one delivery model, applied consistently

Programme Builder is the central configuration tool for every programme. Onboarding steps, the learning plan, reviews, Trackers, compliance documents, placements and programme duration are all configured there, per programme, and programmes can be cloned.

This is where leadership intent becomes delivery practice. When a leadership team decides that every learner will have a review at a given interval, or that a particular document must be signed before delivery starts, Programme Builder is where that becomes structural rather than aspirational. It also means variation between teams is a choice someone made in configuration, which can be found and discussed, rather than a drift in process that nobody can account for.

Group structures: the right view for the right leader

Group structures segment the caseload, from a single flat group through to hierarchical structures for complex organisational models and employer-specific segmentation. Dashboards and reports can then be viewed through those structures.

Governance breaks down when everyone sees either everything or only their own area of responsibility. A curriculum lead needs their department, a regional manager needs their region, and a board needs the whole. Matching the data view to the accountability makes each of those people answerable for something they can easily monitor.

Trackers: decisions with an audit trail

Trackers document actions, queries and changes against a learner’s ILR, compliance or programme journey, and maintain an audit trail of every change. Process Automation Trackers go further and execute the change in the system, covering Break in Learning, Return to Learning, withdrawal, completion, change of employer, change of working conditions and changes to a learner’s name or address.

The governance value is that the reasoning survives. A Break in Learning recorded through a Tracker carries who initiated it, when, and why, and updates the ILR dates at the same time. Six months later, when someone asks why a cohort’s planned end dates moved, the answer is in the record rather than in somebody’s recollection. Providers can also build custom Trackers for workflows specific to their organisation.

Generic reports and OData: getting data out on your terms

The user generic report is the primary operational report for learner data, with a column picker covering personal information, ILR fields, programme status, learning plan progress, review completion, compliance document status and more, filterable by group, programme and status and exportable. Organisation and job generic reports do the same at employer and job level. OData endpoints provide read-only access that can be queried for feeding data into a provider’s own business intelligence tools, and a REST API supports integration with CRM, student record and HR systems.

This matters because no platform can anticipate every board requirement at any given time. Being able to build the report the governance cycle asks for or push the data into the tool the finance team already uses, is what stops reporting becoming a monthly manual assembly task.

Signatures: knowing every agreement is in place

Signatures underpin compliance documents and reviews. Every user creates a signature sample on registration, signatures are validated against Aptem account credentials, and they are recognised by the DfE and most funding bodies. A central grid shows signature status across all learners, separating compliance documents from reviews, and supports signing on behalf of employers, where permitted, as well as mass-signing.

For anyone accountable for funding, this converts a chase into a clear view. Rather than asking teams which agreements are outstanding and waiting for an answer that is already out of date, leaders can see the position and target the gap.

Access control and authentication

Governance covers the system itself, not only what it reports. Aptem supports role-based access control, Markers applied to user accounts, multi-factor authentication and verification, and enterprise single sign-on through a provider’s own identity provider. Accounts can be created, edited and archived centrally.

Being able to state precisely who can see and change what, and to enforce it through your existing identity provider, is a straightforward answer to a question that comes up in every due diligence conversation and most audits.

Frequently asked questions

Which Aptem features support leadership and governance?

Four embedded Power BI dashboards covering caseload, compliance, funding and quality; generic reports and OData for reporting on a provider’s own terms; Programme Builder for consistent delivery models; group structures for role-appropriate visibility; Trackers for auditable decisions; signatures for agreement status; and role-based access control with multi-factor authentication and single sign-on.

Do leaders need Power BI licences to use the dashboards?

No. The dashboards are fully embedded in the platform and are role-permissioned, so no specialist software is required. Data refreshes up to once per hour.

Can governors see data for just their part of the organisation?

Yes. Group structures segment the caseload into flat or hierarchical groupings, including employer-specific groups, and dashboards and reports can be viewed through those structures, so each leader sees the part of the provision they are accountable for.

How does Aptem evidence that a decision was taken and why?

Trackers record actions, queries and changes against a learner with a full audit trail, and Process Automation Trackers execute the resulting change in the ILR and programme status at the same time. The record shows who initiated a change, when, and the reason given.

Can Aptem data feed our existing reporting tools?

Yes. OData endpoints give read-only access for business intelligence tools, and the REST API supports create, read, update and delete operations for integration with CRM, student record and HR systems using scoped API tokens.

How does Aptem help leaders monitor performance between groups of learners?

The quality dashboard breaks achievement, retention and pass rates down by gender, age, ethnicity and disability, and sets them alongside published DfE and Ofsted data, so differences between groups appear as figures that can be tracked over time.

See how Aptem gives leaders and governors oversight across your provision, book a demo today.