Concern 848 · Working draft · editorial review in progress
AI in public procurement
Weak public procurement can lock government agencies into AI systems they cannot adequately test, inspect, maintain or leave.
Understanding the concern
Buying AI is more than purchasing a demonstration that looks impressive. A contract needs to address the public task, data handling, evidence of performance and responsibilities when the system changes or fails. Without these details, an agency may discover too late that it cannot obtain logs, correct an error or move to another supplier.
UK procurement guidance encourages buyers to examine these questions across the system's life. Think of buying a bus without checking maintenance, spare parts or who is responsible for defects. Public agencies need enough expertise to challenge vendor claims and ensure that the agreement protects the people who will rely on the service.
An example
A council buys an AI tool but later learns that the contract gives it no practical way to inspect why important decisions went wrong.
Illustrative unless identified as a documented case.
Words in plain English
- AI
- Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.
Evidence and its limits
The guidance supports responsible purchasing. It does not prescribe one universal contract or show that a particular supplier has failed its duties.
UK Government · Procurement guidance
Guidelines for AI procurement ↗ (opens in a new tab)Evaluating need, suppliers, data, risk and lifecycle responsibilities. Contract terms must match the actual purchase.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
A question to discuss
What rights and evidence must the buyer secure before signing, including a workable plan to stop or switch providers?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Accountability
Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.
Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.
Ask together: Who will answer for the outcome and help put things right?
Prudence
Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.
Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.
Ask together: What is a careful next step, and when should we stop or change course?
Unity
Unity means working toward shared purposes while making room for real differences. It does not require everyone to have the same experience, beliefs, or opinion.
Look for a goal people can share, then explore disagreements about how to reach it. Make sure quieter or less powerful voices can influence the result.
Ask together: What purpose can we share while respecting our differences?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.