Select committee: Public Accounts Committee

Conclusion 11

54th Report - Afghanistan Response Route Published 14 Nov 2025 Addressed to HM Treasury
Conclusion (the committee's words)
We asked the Department to outline how the February 2022 data breach had occurred. The Department told us that the systems it used to manage case work for the ARAP scheme—a Sharepoint site and Excel spreadsheets—were not appropriate for handling many thousands of lines of personal data.22 The Department said that the context for this was that it built up the ARAP scheme at pace throughout 2021 as it became clear that the situation in Afghanistan was deteriorating rapidly.23 The Department also told us that the individual who sent the email which caused the data breach had asked for data on 150 individuals, but that the underlying data was hidden and that they emailed the data out, not knowing the underlying database was there.24 In correspondence received after our evidence session, the Department stated that the February 2022 incident was a result of a one-off action, rather than reflecting a wider culture of non-compliance, but that it was facilitated by the lack of appropriate systems to prevent or mitigate the error.25

From: Public Accounts Committee, 54th Report - Afghanistan Response Route (HC 1391), 14 November 2025

Government response

Latest Treasury Minutes progress report to the Committee of Public Accounts on the Fifty-fourth Report of Session 2024-26

The government responded to the whole report on 4 June 2026 (deadline 14 January 2026).

Read the government's response ↗ Report an error

Treasury minutes: Government response to the Committee of Public Accounts on the Fifty-fourth report from Session 2024-26

Published 19 January 2026.

Summary written by Accountability Index from the government's response. It is not the government's own words.

The government agrees with four of the Committee's recommendations, including six-monthly updates on ARR resettlement from March 2026, and disagrees with the recommendation on separately capturing ARR costs.

  • On updates, the government agrees to write to the Committee every six months from March 2026 until the ARR is complete, though it "may not always be possible to provide a precise breakdown by scheme".
  • On the case working system, it agrees, stating the recommendation is implemented and that DACS (introduced in May 2022) addressed "many of the vulnerabilities", with the department "equipped with the right tools to minimise the risk" of a recurrence.
  • On scrutiny, it agrees and gives a target date of Spring 2026. The Treasury will issue a Dear Accounting Officer letter on sharing information with the Comptroller and Auditor General in the event of a super-injunction.
  • It disagrees on separate ARR costing, saying this would be "disproportionately complex and resource intensive", and instead offers an indicative cost allocation at the end of each financial year, included with the six-monthly updates.

Read the government's response ↗ Report an error