HO Asset Recovery IT (ARIT) Alpha reassessment report
HO's Asset Recovery IT (ARIT) Alpha reassessment report
Asset Recovery IT (ARIT) Alpha reassessment report
| Assessment date | 27/04/2026 |
| Assessment stage | Alpha |
| Assessment type | Reassessment |
| Service provider | Police Digital Service |
| Result | Amber |
Previous assessment reports
• Initial alpha assessment 27/11/2025
Service description
JARD is the central case management and data recording tool used to support asset recovery cases across England, Wales, and Northern Ireland. However, JARD is 20+ years old, has become outdated and presents significant limitations. The system cannot support integration with other law enforcement systems, relies on high levels of manual data entry, has poor user experience, experiences frequent outages, and no longer aligns with government cloud-first and digital strategy principles. As a result, JARD is now considered a barrier to progress, with serious implications for data quality, efficiency, and the overall success of asset recovery efforts. Missed opportunities for recovering criminal assets and ensuring justice are directly attributable to the system’s limitations.
The Asset Recovery IT (ARIT) service will serve as a centralised platform for recording, managing, and reporting asset recovery cases across UK policing, government and law enforcement agencies. It will be built to meet modern security, data, and interoperability standards. This new system will support the entire lifecycle of asset recovery under the Proceeds of Crime Act (POCA) 2002. The ARIT service will be designed to address the limitations of the outdated JARD system by providing a cloud-native, integrated case management solution.
Service users
ARIT users are from 183 organisations, split into the following areas:
• Financial investigators – such as police and HMRC
• Prosecution staff – such as the CPS
• Enforcement Authority staff – such as the courts services
• System administrators
Things the service team has done well:
● It was good to see how the team have joined up with communities in Government, andreally taken on board the feedback they got – we are sure this will help them deliver outcomes and reduce risk.
1. Understand users and their needs
The service was rated green for point 1 of the Standard.
2. Solve a whole problem for users
The service was rated green for point 2 of the Standard.
3. Provide a joined-up experience across all channels
The service was rated amber for point 3 of the Standard at the initial alpha assessment.
4. Make the service simple to use
The service was rated green for point 4 of the Standard at the initial alpha assessment.
5. Make sure everyone can use the service
The service was rated amber for point 5 of the Standard at the initial alpha assessment.
6. Have a multidisciplinary team
The service was rated amber for point 6 of the Standard at the initial alpha assessment.
7. Use agile ways of working
The service was rated amber for point 7 of the Standard at the initial alpha assessment.
8. Iterate and improve frequently
The service was rated amber for point 8 of the Standard at the initial alpha assessment.
9. Create a secure service which protects users’ privacy
The service was rated green for point 9 of the Standard at the initial alpha assessment.
10. Define what success looks like and publish performance data
The service was rated amber for point 10 of the Standard at the initial alpha assessment.
11. Choose the right tools and technology
The service was rated green for point 11 of the Standard at the initial alpha assessment.
12. Make new source code open
The service was rated amber for point 12 of the Standard at the initial alpha assessment.
13. Use and contribute to open standards, common components and patterns
The service was rated green for point 13 of the Standard at the initial alpha assessment.
14. Operate a reliable service
The service was rated amber for point 14 of the Standard at the initial alpha assessment.
Next Steps
This service can now move into a private beta phase, subject to addressing the amber points within three months’ time and GDS spend approval.
To get the service ready to launch on GOV.UK the team needs to:
● get a GOV.UK service domain name
● work with the GOV.UK content team on any changes required to GOV.UK content