Home›Guides & Information›Child Maintenance Service›CMS Is Using Predictive Analytics to Score Paying Parents

CMS Is Using Predictive Analytics to Score Paying Parents

An official UK Government transparency record confirms that the Child Maintenance Service is using a machine-learning system to predict whether currently compliant paying parents may miss a future payment.

About this guide

An official UK Government transparency record confirms that the Child Maintenance Service is using a machine-learning system to predict whether currently compliant paying parents may miss a future payment.

CMS • DWP • Predictive Analytics

An official UK Government transparency record confirms that the Child Maintenance Service is using a machine-learning system to predict whether currently compliant paying parents may miss a future payment.

Right First Time UK information page • Updated 28 August 2026

This is confirmed by the Government itself

The Department for Work and Pensions has published an official Algorithmic Transparency Record titled:

“DWP: Child Maintenance Service (CMS) – Predictive Analytics Compliance”

It confirms that machine learning is being used to predict which compliant CMS cases may become financially non-compliant.

Read the Official Government Record
IMPORTANT: The Government record says the predictive system does not itself make the final decision about a CMS case. The prediction is shown to a human caseworker who is expected to review the case and decide what action, if any, should be taken.

However, the automated prediction can influence which cases are prioritised for attention, what risk information the caseworker sees and what potential actions are presented.
~100,000 cases processed by the model each month
~200,000 records used in the compliance model dataset
86% published May 2025 model accuracy
79% published May 2025 precision

What exactly is CMS doing?

CMS operates a predictive analytics system designed to identify paying parents who are currently considered compliant but who the model predicts could miss an upcoming payment.

According to DWP, the system analyses current and historic information held within its CMS2012 system.

1 CMS case data is collected
2 Data is processed by the model
3 A risk score is created
4 Case is classed High, Medium or Low risk
5 Prediction is shown to a CMS caseworker

DWP says the objective is to identify cases at risk of a payment breakdown early enough for caseworkers to intervene before payments stop.

Who is being assessed?

One of the most important points in the transparency record is that this is aimed at cases which are currently compliant.

In other words, the system is not simply identifying someone who has already failed to pay.

It is attempting to predict whether someone who is currently compliant may become non-compliant in the future.

This is predictive risk profiling.

Past and current case information is analysed to calculate the probability that a future payment may be missed.

What information can be used?

The Government transparency record identifies a wide range of CMS information feeding into the model.

Case information Information concerning the paying parent's case and connected CMS cases.
Employment status Employment information is among the case features identified in the Government record.
Liability amount Information about how much maintenance is due.
Payment history Previous payments, amounts due, amounts paid and balances.
Payment method Current and historic changes to the person's method of payment.
Changes of circumstances Service requests including reported changes can form part of the data.
Communications Information concerning inbound and outbound telephone calls and letters can be used.
Service requests The number and type of CMS service requests can be included.
Financial transactions Payments, refunds, liabilities and balances are included.
Previous compliance Paid-versus-due information over the previous rolling quarter is used.

Your communications with CMS can form part of the data

The transparency record specifically refers to information concerning communications exchanged between paying parents and CMS.

It also lists service requests such as changes of circumstances, employment changes and liability changes.

This creates an important transparency question:

Could the frequency or type of contact a person has with CMS affect how their case is scored?

The published record identifies communications as part of the dataset but does not provide the public with a complete list of every engineered model feature, its weighting or exactly how an individual communication affects a particular person's score.

What technology is being used?

Part Official information
Machine-learning model XGBoost classification model
Explanation system SHAP feature explanations
Cloud platform AWS SageMaker
Model training A new model is trained each month
Output Risk score plus High / Medium / Low risk category
Caseworker system Predictions are displayed through CMS2012
Status Live / Production

This system is live — not merely experimental

The Government record lists the system's phase as “Production”.

DWP says it was rolled out to a wider group of operational caseworkers in March 2025.

The model is run at the beginning of each month and around 100,000 cases are processed.

The resulting prediction is then available within the CMS2012 system used by caseworkers.

What does CMS receive about a parent?

The published record says each prediction can contain:

  • A risk score
  • A High, Medium or Low risk level
  • The date the prediction was created
  • An expiry date
  • Information supporting the prediction
  • Potential actions for the caseworker

These predictions are displayed to CMS caseworkers as part of the case-management process.

DWP itself identifies the risk of incorrect predictions

Officially identified risk: Accuracy

DWP acknowledges that there is a risk that the system could incorrectly identify a case as likely to default and assign the wrong risk score.

DWP recognises that this could mean caseworkers prioritise the wrong cases.

The mitigation recorded by DWP is that the human caseworker should be shown the score and the case file and determine whether the information is accurate.

Published performance

DWP published the following results based on data from May 2025:

  • Accuracy: 0.86 / 86%
  • Precision: 0.79 / 79%

DWP also says a newly trained model will not be accepted unless its precision is at least 0.62 / 62%.

What does precision mean?

Broadly, precision measures how often cases identified by the model as belonging to the positive target category actually belong to that category within the validation data. It should not simply be read as saying that “79% of everything the system does is correct”.

The important point is that DWP itself accepts that false-positive predictions are possible.

What about discrimination and bias?

DWP states that the model dataset does not contain sensitive attributes.

Its Equality Assessment says protected characteristics are not impacted and that the machine-learning system has been trained to reduce or eliminate bias.

However, the transparency record also says:

The model's published performance was not separately broken down by demographic or other characteristics.

This does not prove that discrimination is occurring. But it is a legitimate transparency issue when assessing how confidently differential effects can be ruled out.

Does the computer make the final CMS decision?

According to DWP: No.

DWP says the prediction provides background information to support the caseworker and that the caseworker remains responsible for reviewing the case and deciding what action should be taken.

That distinction matters.

The published information does not establish that CMS is allowing an algorithm to automatically impose enforcement action or automatically change somebody's maintenance liability.

However, the system can determine which cases are highlighted as being at greater risk and therefore which cases receive earlier attention from caseworkers.

Right First Time UK believes there should therefore be clear accountability showing that the required human review is meaningful and that staff are not simply relying upon the automated score.

Questions that now need answering

  • Are parents told when their case has been processed by this predictive system?
  • Are parents told whether they have been classed High, Medium or Low risk?
  • Can a parent see their actual risk score?
  • Can a parent see which factors contributed to that score?
  • Can a parent challenge inaccurate information before it affects how their case is handled?
  • Are caseworkers recording that they independently checked the prediction?
  • How often do caseworkers disagree with the algorithm?
  • How many parents identified as high risk actually remain fully compliant?
  • What specific interventions are triggered by a High-risk prediction?
  • Are parents contacted differently because of an algorithmic prediction?
  • Have any enforcement processes indirectly followed from a case first being prioritised through the predictive system?
  • How does DWP assess whether historic errors already held within CMS2012 could contaminate the prediction?

Bad data in = potentially bad prediction out

This is particularly important for CMS because the machine learning model depends upon information already held within the Child Maintenance system.

If underlying information about a case is wrong, disputed, incomplete or out of date, an obvious question is:

Could that incorrect information also influence the predictive risk score?

The Information Commissioner's Office says organisations must take reasonable steps to make sure personal data is not incorrect or misleading and must carefully consider challenges to its accuracy.

ICO Guidance – Accuracy of Personal Data

Can you ask DWP what information it holds about you?

You have a right to ask DWP for copies of personal information it holds about you through a Subject Access Request (SAR).

Where relevant, a person may wish to ask DWP whether information connected with the Predictive Analytics Compliance system forms part of their personal records.

Questions you may consider including in a SAR

  1. Has my CMS case been processed through the Predictive Analytics Compliance model?
  2. Please provide any risk score recorded in connection with my case.
  3. Please provide any High, Medium or Low risk classification associated with my case.
  4. Please provide the creation and expiry date of any prediction.
  5. Please provide the information or factors presented to caseworkers as contributing to the prediction.
  6. Please provide any potential actions generated or displayed alongside the prediction.
  7. Please provide caseworker notes showing how the prediction was reviewed or verified.
  8. Please provide records showing whether any action taken on my case was influenced by or connected with the predictive score.
  9. Please provide any audit trail identifying when predictive information concerning my case was accessed.

Whether every requested item must be disclosed will depend on data-protection law and any applicable exemptions, but asking specifically for the information can help establish what personal information DWP holds.

Make a DWP Subject Access Request

Data protection and profiling

The Information Commissioner's Office provides guidance covering automated decision-making and profiling.

Profiling broadly includes automated processing of personal information used to evaluate or predict aspects of a person's behaviour, reliability or economic situation.

Special protections apply to decisions that are made solely by automated means and have legal or similarly significant effects.

DWP's published position in relation to this CMS system is that the predictive score is not itself the decision and that a human caseworker makes the decision about how the case is managed.

That makes the quality and independence of the human review especially important.

ICO – Automated Decision-Making & Profiling

Impact assessments

The official transparency record identifies several assessments connected with the project.

Assessment Date / information published
Digital Enterprise Security Risk Assessment Completed December 2023
Data Protection Impact Assessment – Part 2 Completed 13 December 2023
Equality Assessment Completed 30 April 2024
Equality Assessment update 20 February 2025
Further Equality Assessment update 11 November 2025

The transparency record provides DWP's summary of these assessments. Anyone investigating the system may also wish to ask whether the complete assessments can be published or disclosed.

An external technology supplier was involved

The official record identifies:

Tata Consultancy Services Limited (TCS)

DWP says TCS provided technical expertise supporting the design, build and assurance of the tool and supports the live training and inference pipelines.

DWP states that the supplier does not have direct access to personal customer data in the live environment.

However, DWP says information such as logs or screenshots may be supplied to the contractor where needed to resolve incidents or problems.

Where is the model data stored?

According to the transparency record:

  • The system uses AWS infrastructure.
  • Data is stored in AWS S3.
  • DWP says the stored data is encrypted.
  • DWP Digital Children data engineers have access to the dataset.
  • The stated retention period for the training dataset is one year.
  • Caseworkers do not receive the raw model dataset.
  • Caseworkers instead see the predictions presented in CMS2012.

If the underlying CMS information is wrong

A predictive system cannot correct a person's case simply by analysing it.

If you believe CMS holds incorrect information about matters such as:

  • your income;
  • payments;
  • arrears;
  • employment;
  • liability;
  • changes of circumstances;
  • payment method;
  • communications; or
  • other factual case information,

raise the underlying error directly with CMS and keep copies of the evidence showing why you believe the information is wrong.

Remember: challenging the accuracy of personal data is not necessarily the same procedure as challenging a formal child-maintenance decision.

If you disagree with an actual CMS decision

If CMS has made a formal decision concerning your maintenance calculation which you believe is wrong, the normal challenge procedure may involve asking for a Mandatory Reconsideration.

GOV.UK says this can be requested where, for example, you think an error has been made, important evidence has been missed or you disagree with the reasons for the decision.

There are time limits, so always check your decision letter and the current official guidance.

Mandatory Reconsideration Guidance CMS Complaints & Appeals

What Right First Time UK believes should now be published

Genuine algorithmic transparency should allow the public to understand not simply that a system exists, but how it affects real people.

We believe further information should be published including:

  • The number of cases rated High, Medium and Low risk each month.
  • The percentage of High-risk cases which actually subsequently miss a payment.
  • The number of false-positive predictions.
  • The exact interventions carried out for each risk category.
  • How often caseworkers disagree with the prediction.
  • Whether a risk prediction has ever contributed to moving a case towards enforcement.
  • A complete list of the features used by the model.
  • The importance or weighting of those features.
  • How disputed CMS data is treated by the algorithm.
  • How corrected information is fed back into future predictions.
  • Whether parents are routinely informed that their information has been used to create a predictive risk score.
  • The complete Data Protection Impact Assessment, subject to any genuinely necessary redactions.
  • The complete Equality Assessment and subsequent reviews.
  • Independent testing of the system's accuracy and possible differential impacts.

Why this matters

Technology can potentially help public bodies identify problems earlier and provide a better service.

But when predictive technology is used by a public authority with significant powers over people's finances, transparency, accuracy and meaningful human oversight are essential.

A parent who has paid correctly should not be treated as though they have done something wrong simply because a computer predicts that they might not pay in the future.

Likewise, caseworkers need reliable information rather than automated assumptions based upon inaccurate or disputed historical data.

Predictive analytics should assist accurate decision-making — not amplify existing errors.

Official sources and further reading

GOV.UK – DWP Child Maintenance Service Predictive Analytics Compliance GOV.UK – Algorithmic Transparency Records GOV.UK – Algorithmic Transparency Recording Standard Guidance GOV.UK – Request Your Personal Information From DWP ICO – Automated Decision-Making and Profiling ICO – Accuracy Principle GOV.UK – CMS Complaints and Appeals GOV.UK – Mandatory Reconsideration

Right First Time UK – CMS Information Hub

We are continuing to investigate the use of technology, data, decision-making systems and administrative processes within the Child Maintenance Service.

If you have experienced incorrect CMS data, unexplained decisions, repeated calculation errors or believe automated systems may have affected the way your case was handled, keep your records and evidence.

Visit the CMS Information Hub
Important: This page provides public-interest information and commentary based primarily on the UK Government's published Algorithmic Transparency Record. It does not claim that CMS automatically makes maintenance or enforcement decisions using artificial intelligence. DWP states that human caseworkers review the information and remain responsible for deciding how a case is progressed.

This page is not legal advice. Always check the latest official guidance and obtain independent professional advice where appropriate.