Why procurement is worth paying attention to
Procurement is not the most interesting part of police technology, and it is routinely skipped over in coverage that prefers to argue about a system once it is already running. That sequencing is the problem. By the time a technology is visible enough to argue about, the contract has been signed, the system integrated, staff trained and a business case written that assumed it would be used. Reversing a decision at that point is expensive in a way that declining to make it never was.
Procurement records are also, quite often, the first public evidence that a force is using something at all. A force is under no general obligation to announce a new capability. It is under an obligation to publish contracts above a threshold value. That gap is why procurement filings are a standing source for this site's deployment tracker.
The routes in, and how visible each one is
Formal tender. Above statutory thresholds, a contract must be advertised and the award published. In the UK that means Contracts Finder and Find a Tender, both searchable by contracting authority, so by force. This is the most visible route and the one that produces usable records.
Framework agreements. A force buys through a pre-competed arrangement negotiated centrally. This is efficient and entirely legitimate, but it compresses the visible decision: the competitive stage happened once, centrally, possibly years earlier, and an individual force's call-off against it generates much less documentation than a standalone tender would.
Bundled features. The system arrives as part of software the force already licenses. This is how generative AI reached English policing at scale: Microsoft 365 Copilot became available through the Police Digital Service's national platform rather than through any force-level procurement decision about generative AI specifically. There is no tender to find, because from a procurement standpoint nothing was bought. That case is covered in full on the generative AI guide.
Free trials. A vendor provides the system at no cost. With no money changing hands there may be no procurement process, no contract, and no publication threshold engaged. Clearview AI's spread through Australian police agencies happened this way: agencies trialled it free of charge from late 2019, and the fact only became public when the company's customer list leaked. Australia's information commissioner subsequently characterised the federal police trial as unapproved, conducted without the privacy assessment that would normally have been required.
Commercial confidentiality and what it obscures
Vendor contracts commonly contain confidentiality provisions, and vendors routinely resist disclosure of technical detail on commercial sensitivity grounds. Some of that is reasonable: pricing structures and implementation specifics are genuinely commercially valuable.
The difficulty is that the same argument is often extended to information that goes to whether the system works. Accuracy testing, error rates by demographic group, the composition of training data, and the thresholds at which a system reports a match are all things a defendant might need in order to challenge evidence, and all things a vendor may prefer not to publish. Where a public body has adopted a system it cannot fully explain, because its supplier will not explain it, the accountability chain has a break in it that no amount of force-level policy can repair.
What has actually improved
Several mechanisms now generate a paper trail earlier than they used to.
In the US, Community Control Over Police Surveillance ordinances, adopted in a growing number of cities, require council approval and public disclosure before police may acquire surveillance technology. This moves the visible decision point to before acquisition rather than after deployment, which is the single most useful structural change in this area. Federal spending is separately published on USASpending.gov.
In the UK, the Algorithmic Transparency Recording Standard offers a route for public bodies to publish structured records of algorithmic tools in use. It is voluntary, and uptake among police forces has so far been limited, which is a material caveat, but it exists and it is checked as a source when this site's tracker is updated.
Reading procurement records usefully
A contract award tells you that money was spent and roughly on what. It does not tell you that a system is in operational use, how it is being used, or whether it survived a trial. Treating an award as proof of deployment overstates what the record supports, which is why entries on this site's tracker distinguish between operational, trial, paused, discontinued and proposed rather than collapsing them into a single "in use" category.
The reverse inference is weaker still. An absence of contracts does not indicate an absence of technology, given how much arrives bundled or free. Procurement records establish a floor on what a force has acquired, never a ceiling.
Follow the coverage
PoliceAI News tracks police technology procurement as it happens: contract awards, framework agreements, trial arrangements, vendor relationships and the disclosure disputes that follow them. The feed refreshes every 30 minutes.
View Procurement Stories