Machine Learning for Public Sector Suppliers

Two different questions

Businesses that sell to councils, NHS bodies, universities and government departments ask about machine learning in two ways. The first is internal: can it help us find and win more of the right contracts? The second is about delivery: a buyer wants a predictive component in a service, so what does it take to build one that survives public scrutiny?

Both are worth answering, and the second has become more pressing as public bodies publish more about the algorithms they use. We cover each in turn.

Using machine learning to decide which tenders to bid for

A 70-person facilities or IT services supplier might see hundreds of relevant notices a year and bid for dozens. Every bid takes days of work, and a poor win rate is usually a qualification problem rather than a writing problem. Bidding for contracts you were never going to win costs more than the bid team's time; it takes them away from the contracts you could win.

• Tender matching. Classifying published notices against your capabilities and past wins, so the bid team sees the relevant ones first rather than keyword matches.
• Bid or no-bid scoring. Estimating win likelihood from contract value, buyer, lot structure, incumbent, your history with that buyer and how closely the specification fits past successes.
• Pipeline forecasting. Predicting when contracts will be re-tendered from award dates and contract lengths in published data.
• Competitor analysis. Learning from award notices which competitors win which kinds of work and at what scale.
• Feedback mining. Classifying evaluation feedback across past bids to see where marks are consistently lost.

Win probability needs your own history

Published contract data is useful but thin on why suppliers win. The most predictive information is in your own records: every bid decision, the score you received, the feedback, the price position and whether you had met the buyer beforehand. Most suppliers hold this across spreadsheets and email folders, if at all.

1. Record every opportunity considered, including ones you chose not to bid
2. Capture outcome, score, rank and feedback for every submitted bid
3. Note relationship factors, such as prior contracts or pre-market engagement
4. After fifty or so bids, test whether a simple model predicts outcomes better than the bid manager
5. Use the score to challenge bid decisions, not to make them automatically

Be honest about volume. A supplier making twenty bids a year will not have enough outcomes for a reliable model for several years. A structured qualification checklist, reviewed against outcomes, gets most of the benefit sooner.

The cheapest bid is the one you decide not to write. A good qualification score earns its keep by saying no.

Public procurement rules and published data

In England, Wales and Northern Ireland the Procurement Act 2023 came into force in February 2025, bringing more published notices across the procurement lifecycle, including pipeline and contract performance information. That gives suppliers more structured data to work with than before, although quality varies between buyers and older records are patchier.

Collecting and analysing published notices is generally straightforward, but check the terms of each source and avoid anything that would breach them. Our post on the legal and practical limits of web scraping covers where the lines usually sit.

Delivering machine learning to public bodies

When a public body buys a service with a predictive element, such as prioritising inspections, forecasting demand for services or triaging casework, the bar is higher than in the private sector. Decisions may affect citizens' access to services, they can be challenged, and public bodies have duties around equality and transparency.

The UK's Algorithmic Transparency Recording Standard sets out how public sector organisations describe the algorithmic tools they use, and it is now required for central government departments. Suppliers who can supply that information readily make the buyer's job easier, which matters at evaluation.

When a rule beats a model in public services

Public buyers sometimes ask for machine learning where a transparent rule would serve citizens better. If the criteria for prioritising a case can be written down and agreed in policy, a rule is easier to explain, challenge and audit. A model makes sense when the pattern is genuinely too complex for rules and the outputs support rather than replace a caseworker.

Saying so in a bid can feel risky. In our experience, evaluators respond well to a supplier who explains why a simpler approach is safer. Our comparison of machine learning and rules engines sets out that trade-off in more detail.

How we work with public sector suppliers

At SpiderHunts we help in both directions. For bid teams, that usually means building a clean opportunity and outcome record, a tender matching tool and, once there is enough history, a qualification score. For delivery, we act as the technical partner behind a supplier's bid, building the model with documentation, explainability and equality testing that a public buyer will ask for.

Either way the work draws on our machine learning service and our experience of building systems that have to be explained to someone other than the people who built them.

Frequently asked questions