London's Metropolitan Police will keep using a Palantir-built AI system to flag potential officer misconduct for another twelve months, even though Mayor Sadiq Khan personally killed the long-term contract that would have made it permanent. The episode is being read in some quarters as a mayoral climb-down. The more telling story is procurement governance: killing a sole-source award does not, on its own, displace the vendor already inside the system. It just changes the rules of the competition the vendor is now sitting in.
The extension was approved by the Mayor's Office for Policing and Crime, Mopac, weeks after Khan's office ruled that the original procurement amounted to a 'clear and serious breach' of the rules because the force had 'seriously considered only one supplier' on a path toward a roughly £50m long-term deal (the Guardian, 24 June 2026). Palantir is a US data-mining and intelligence-software company best known for work in military and intelligence contexts; here it has been operating inside the UK's largest police force on a system the Met publicly calls the 'Customer Service Engine.'
That public name obscures what the tool actually does. The Customer Service Engine pulls together officer data the force says it already lawfully holds and surfaces patterns the Met claims could indicate 'potential standards, welfare or cultural concerns' (Metropolitan Police news release on the CSE extension). Assistant Commissioner Rachel Williams, defending the pilot on the record, framed it as misconduct and welfare work and a tool for restoring public confidence in a force under a multi-year 'New Met for London' improvement plan. Civil-liberties writers argue the same system is a Palantir foothold that survives the procurement rebuke by other means (The Nerve on the CSE extension).
The mayor's intervention was real, and unusually pointed. City Hall found not just a flawed process but a process that had drifted toward one supplier on what would have been a multi-year award near £50m, and the BBC reported the block as a discrete decision by the mayor before the extension was granted (BBC News on the blocked Met Police contract). After the block, the Met posted a roughly £300m technology shopping list, with the deputymayor instructing that any new procurement be 'open to a wide range of potential suppliers' (The Register on the Met's £300m tech shopping list).
Palantir did not accept the block quietly. The company's lawyers wrote to Mopac signalling an intent to challenge the mayor's decision in court, as reported by the Times and carried in the Guardian's coverage. That legal posture, sitting alongside a renewed tender the company is now bidding into as the incumbent operator, is what makes the next twelve months structurally different from the past year.
The competitive question is straightforward. The mayor's intervention removed the sole-source path. It did not remove the operator. During a competitive procurement, the vendor already running the system benefits from accumulated data integrations, internal training, and the cost asymmetry of replacing a live platform mid-pilot. None of that is illegal, and the Met has every right to extend a working tool while it lawfully re-runs the competition. But it does mean the rebid is not symmetric, and the most consequential decision about Palantir's long-term role inside the Met may be made before the new tender is even published.
The unresolved public-interest question is oversight during the extension itself. Mopac has approved continued use of an AI tool to triage officer data, but neither Mopac nor the Met has, on this record, set out a published audit regime for that use over the next twelve months. The force is being asked to police itself, with vendor-supplied software, while a procurement the mayor's office found to be in breach is re-run. That is the part of the story worth watching: not whether Palantir wins the new competition, but what independent scrutiny applies to its tool while the competition is live.