Skip to main content

A DfE Service Manual and its content is intended for internal use by the DfE service community.

DfE Continuing Professional Development (CPD)

This site documents the technical standards and guidance that we expect teams working within the Department for Education to follow when building the CPD digital service.

It complements the DfE Technical Guidance, the GOV UK Service Manual and its Technology section, which covers service design more broadly.

It is inspired by the GDS Way and the Ministry of Justice Technical Guidance.

Overview

Continuing Professional Development (CPD) is owned and operated by the Developing Teachers and Leaders Division (DTLD) a part of the Teacher Workforce Directorate (TWD) within DfE.

CPD encompasses two teacher initiatives namely, Early Career Framework (ECF) and National Professional Qualifications (NPQ) and - as agreed with Mark Wood of the DfE Data Protection Assurance Team - is a national rollout (NRO) aimed at supporting teachers, schools, DfE and providers through the teacher training lifecycle.

The objective of the CPD reforms is to raise teacher quality by strengthening support for teachers in the early part and future progression of their careers. In turn, it is expected that this will improve teacher retention.

The flagship reform is a wider overhaul of teacher CPD. From the new ITT Core Content Framework to the suite of Specialist and Leadership NPQs, DfE is revolutionising teacher training and development by defining training content in detailed frameworks and designing delivery models to maximise fidelity to the underlying frameworks.

As with the suite of CPD reforms, it is important that the benefits are felt nationwide, with a universal national offer targeted disproportionately towards schools serving disadvantaged communities.

The CPD digital service

The digtial service enables users to validate their details against the Teacher Regulation Agency records, choose their provision/qualification, report partnerships between providers and schools and enable participants to be set up on the frameworks.

It is designed to support all future initiatives but initially will only support:

  • Early Career Framework (ECF) Induction programmes (Core Induction Program - CIP and Full Induction Program - FIP)
  • National Professional Qualifications (NPQ)

How the CPD digtial service will enable the policy

The digital service is a reporting platform designed to collect initial contact data ( name, email address, school ) for School Induction Coordinators and participants ( Trainees, Early Career Teachers and Mentors ) from schools to pass on to Lead Providers who will use their network of Delivery Partners to deliver the induction or training courses chosen.

The participants will then be engaged via email using the contact data and asked to enter their TRN. Additional information (Date of Birth, National Insurance Number) needs to be collected temporarily in order to validate the TRN against the DQT records held by the TRA so that the participants achievements and awards can be logged against the correct records.

The participants QTS status will be analysed from the DQT along with the pupil premium and sparsity status of their school to determine whether funding can be claimed by the Lead Providers from DfE for each participant. Lead Providers will declare when each participant reaches a milestone in their training or induction which will be validated against the participant records held to determine if the declaration is able to release funding to the Lead Provider.

External users of the service

There are four primary user groups that require access to the platform in order to perform tasks which contribute to the delivery of the public task.

Type Location Description
School Induction Tutors (SIT) in school Responsible for reporting on the school induction programme and any participants in training or induction activities
Lead Providers (LP) external Responsible for delivering training and induction programmes and reporting details on participants progress within those programmes
Participants in school and external Recipients of training and induction programmes

There are expected to be approximately 28k SITs, ~90k participants per year and 10 LPs. SITs and LP numbers will probably not grow much over time but the number of participants will grow by ~90k per year.

If you wish to know more please read a more detailed description of the service users

Contacts

Name Role
Kate Thompson / Stacy Singleton Deputy Service Owner
TBA Lead Delivery Manager
Fred Constable Senior User Researcher
Gemma Say Service Designer
James Rose Technical Lead
Matt Smith Technical Architect

Service Access

Sandbox

Technical Architecture

The CPD service comprises a centrally managed reporting platform for all of the interested parties, interactions and use cases supporting the public task.

The platform is developed in Ruby On Rails and is being deployed to GOV UK PaaS as a single network of containerised applications supported by Managed PostgreSQL and Redis DBs. Only UIs and APIs will be internet facing and all data access will be through those interfaces.

If you wish to know more please read a more detailed description of the technical architecture

Data

The processing of data for both ECF and NPQ is considered to have the lawful basis that they are both Public tasks (Article 6 (1)(e)) so that the processing is necessary for the organisation to perform the task in the public interest or for the organisation’s official functions and the task or function has a clear basis in law as shown by the following;

The CPD service is primarily a reporting and funding platform. The service is an authorative datasource on the progress of participants through their training and induction programmes and the outcomes of those programmes. The highlevel entities that this service tracks are:

  • Participants (ECTs, mentors and NPQ trainees) contact details
  • School induction coordinator contact details
  • Lead provider organisation information including contact data
  • Delivery Partner organisation information including contact data
  • The associations between schools, participants, Lead Providers and Delivery Partners
  • Participant progress through the course materials and training or induction programmes
  • Participant training status (active, withdrawn, deferred etc)
  • Participant outcomes for training or induction programmes
  • Data and metrics required for the justification of contracted payments

If you wish to know more please read a more detailed description of the domain data

Authorisation

Schools users are asked to confirm control of the associated email account to add participants and update their contact details.

Lead Providers have their own Learner Management Systems which integrate directly with the reporting APIs to report data for payment calculations and MI, this uses Bearer Authentication tokens managed by the service teams as they are contract managed. It is also possible for Lead Providers to submit report data via a management interface and they are asked to confirm control of the associated email account.

Participants contact details are passed to the Lead Providers as soon as they are gathered to faciliate onboarding, they are then are invited to fill in additional details about themselves to faciliate joining with the Teacher Regulation Agency Records inorder to verify their qualified teaching status, alerts and previous training history.

If you wish to know more please read a more detailed description of the lead provider quthentication process

Hosting

Hosting is with GOV UK PaaS.

If you wish to know more please read a more detailed description of the deployment architecture

Testing Strategy

Each component is tested at various stages to verify that and change to the system does not break its support of the required user journeys and does not introduce anything that might go against WCAG 2.1 AA standards.

If you wish to know more please read a more detailed description of the end-to-end testing strategy

Security Assurance

Manual and automated processes are used to ensure that the deployed components are free from as many residual security risks as possible.

If you wish to know more please read a more detailed description of our security assurance processes

Performance Testing

Automated performance tests are run to simulate the most intensive user journeys on components.

If you wish to know more please read a more detailed description of our performance test strategy