PSNI fleet software costs £192,000 a year: the contract and the questions still unanswered
A significant cost hidden in ordinary fleet administration
The Police Service of Northern Ireland has disclosed that it spends £192,000 a year on dedicated fleet-management software used in an organisation operating approximately 2,700 vehicles. The figures come from freedom-of-information response FOI/16999, released on 16 April 2026. The response identifies a fixed-term, subscription-based agreement ending on 31 December 2026. It does not identify the supplier or the software product.
The public-interest issue is not that the sum is automatically excessive. Fleet software can help coordinate maintenance, scheduling, compliance and deployment across an unusually complex police operation. The more revealing question is what measures the authority uses to judge value for money when its contract is approaching its stated expiry date.
An annual figure alone is not the same as the total contract value. The disclosure did not establish when the present contract began, how many modules are licensed, whether the £192,000 includes migration or development work, or which operational benefits can be quantified. Without those details it would be irresponsible to label the expenditure wasteful.
What the FOI establishes — and what it does not
The response says that dedicated fleet-management software is in use, rather than functionality bundled with a vehicle-leasing service. It places the annual spend at £192,000, describes the licence as subscription-based and the agreement as fixed-term. PSNI said its earliest reference to the provider was in 2012, but explicitly indicated that this was well after it had begun using the product. That is not evidence of a contract continuously running unchanged since 2012.
A simple division of £192,000 by 2,700 produces approximately £71 per vehicle per year. This is a scale illustration, not a price charged for each car: a fleet-management contract may cover users, servers, integrations and other services rather than individual vehicles. Nor does an approximate fleet figure permit a precise vehicle-level cost comparison with other police forces.
The FOI gives the contract end date as 31 December 2026. As of the publication of this investigation, that future date is a prompt for scrutiny, not confirmation that a new agreement has been awarded or that existing software will be replaced. A contract can be extended, renewed or superseded, depending on procurement arrangements and legal obligations.
Why the supplier name is withheld
PSNI declined to identify both the provider and application, citing sections 31 and 38 of the Freedom of Information Act 2000. In its response it argued that publishing product details might help people identify vulnerabilities in systems supporting policing and could create safety risks. The authority also acknowledged the argument for transparency because public money is involved.
These are legal exemptions with tests attached, not a general rule that police technology suppliers may never be named. The Information Commissioner’s Office explains that section 31 concerns prejudice to law-enforcement functions and is subject to a public-interest test. The outcome of this particular FOI is PSNI’s disclosed decision; PureCar has not independently established whether the exemption would withstand an appeal.
Withholding a supplier name is also separate from withholding spend. It remains possible to evaluate a contract through redacted procurement information, decision records, public notices, performance indicators and audit findings without revealing operationally sensitive technical detail.
What taxpayers should expect from a contract review
A credible review would ask whether the software reduces periods when vehicles are unavailable, improves servicing and safety compliance, and gives managers reliable information about the condition and location of the fleet. It should distinguish those outcomes from simply recording that the organisation possesses a digital system.
Procurement accountability should also cover whether requirements have changed since the original system was chosen, whether market testing was carried out, what costs would arise from switching suppliers and whether any proposed extension has a documented business case. None of those specific answers appears in FOI/16999; they are reporting questions that need fresh evidence.
PSNI’s own 2026 accountability material describes fleet resilience, replacement programmes and modernising systems as management priorities. That wider context matters: police vehicles range from routine transport to specialist capability, and a software decision can affect far more than annual licence cost.
The next documents that could resolve the questions
The most useful follow-up request would seek the contract award date, procurement route, original and revised values, spending by financial year, non-sensitive contract performance measures and whether a renewal or extension decision has been made. Documents could be supplied with technical specifications and security-sensitive operational details removed where justified.
Until such material is disclosed, the verified finding remains narrow but important: a large public fleet uses a £192,000-a-year subscription whose current disclosed contract ends at the close of 2026, while supplier identity remains withheld. That is a legitimate subject for scrutiny without alleging wrongdoing or pretending that the full cost of ownership is already known.
Sources and methodology
This report examines the published PSNI freedom-of-information response and the additional official material linked below. Figures are attributed to their original reporting periods; no new response, interview or primary-data exercise is claimed. Conclusions described as questions or possible implications are analysis, not established findings.
- https://www.psni.police.uk/foi-disclosure-log/fleet-management-software
- https://www.psni.police.uk/sites/default/files/2026-02/Chief%20Constable%27s%20Accountability%20Report%20to%20the%20Northern%20Ireland%20Policing%20Board%2005%20February%202026.pdf
- https://ico.org.uk/for-organisations/foi/freedom-of-information-and-environmental-information-regulations/section-31-law-enforcement/
- https://ico.org.uk/for-organisations/foi/freedom-of-information-and-environmental-information-regulations/section-31-law-enforcement/how-should-we-apply-the-prejudice-test/
- https://www.legislation.gov.uk/ukpga/2000/36/contents