Haluatko tehdä tarjouksia julkisista hankinnoista? Tutustu TaaS-tarjousvalmistelupalveluumme
Kilpailutusanalytiikka

AI for Public Procurement: What It Can and Can't Do

AI is genuinely good at four things in public procurement: ranking large volumes of tender notices against a supplier profile, summarising long tender documents, extracting requirements into checklists, and drafting first versions of response documents. It is not good at deciding whether to bid, guaranteeing compliance, pricing work, or producing evidence you do not have. The useful mental model is that AI compresses reading and drafting time; it does not replace judgement or accountability.

That distinction matters commercially. Procurement is a domain where a confident wrong answer has a cost — a missed mandatory requirement disqualifies a bid outright, regardless of how good the rest of it was. So it is worth being precise about which tasks are safe to delegate.

What AI does well

Reading at volume

The core problem in tender discovery is that there is far more published than any team can read. The Tendly data snapshot counts more than 50,000 active tenders open across 23 countries at any one time. Sorting that into "relevant to this company" and "not" is a text classification problem, and it is one that language models handle well — they cope with synonyms, with the same requirement described five different ways, and with notices published in languages your team does not read. This is the basis of AI tender matching.

Summarising and extracting

A tender pack can run to hundreds of pages across a dozen files: instructions to tenderers, specifications, draft contract, pricing schedule, and forms. Pulling out the deadline, the mandatory qualification criteria, the award criteria and their weightings, the required certifications, and the submission format is mechanical work that AI does quickly and consistently. The output is a checklist a human then verifies — which is much faster than building the checklist from scratch.

Drafting first versions

Most tender responses reuse the same underlying material: methodology, quality management, staffing, references. AI is effective at assembling a first draft that is structured against the buyer's questions and their weightings, so your specialists spend their time on the parts only they can write instead of reformatting last year's answer. That is what document generation is for.

Checking before you submit

A second read against the requirement list catches the failures that lose bids on technicalities: a missing signature block, an unanswered sub-question, a word count overrun, a form left in the wrong format. Automated document review is essentially a tireless proofreader with the specification open next to it.

Where AI falls short

It cannot make the bid/no-bid call

Whether to bid depends on facts a model does not have: your current capacity, the margin you need, whether the client relationship is worth a loss-leader, whether your best delivery lead is available in March. AI can score fit and surface risk. The decision stays with you — the bid/no-bid helper is a structured way to make it, not an automated verdict.

It cannot certify compliance

An AI check reduces the chance of a mistake; it does not transfer responsibility. Mandatory requirements are pass/fail and the consequences of getting one wrong fall on the supplier who signed the submission. Treat AI compliance output as a first pass that a named person then signs off.

It cannot invent evidence

The strongest parts of any tender response are specific: this project, that client, these measured outcomes. A model asked to write about experience you have not described will produce plausible generalities, and evaluators recognise generalities instantly. Worse, a fabricated reference or overstated capability is a misrepresentation with real legal consequences. Everything factual in a bid must come from you and be verifiable.

It is weak on price

Pricing is strategy, not text generation. It depends on your cost base, your competitors' likely behaviour, and how the buyer's scoring model converts price into points. Historical award data can inform it — company insights shows what buyers have paid and who has been winning — but the number is a commercial decision.

How to judge an AI procurement claim

Vendors describe very different capabilities with identical language. Four questions cut through it:

  • Does it explain itself? A relevance score with no reasoning cannot be checked, and an unverifiable output is not usable in a regulated process.
  • What is it reading? Matching on notice titles alone is shallow. Matching that reads the actual tender documents is a different product.
  • Where does the human sit? Any credible workflow has an explicit approval step before submission. Be sceptical of anything that markets full automation of a bid.
  • What happens when it is wrong? Ask how errors surface and who carries the consequence.

The confidentiality question

One practical constraint gets overlooked until it becomes a problem: what you are allowed to put into a model. Tender documents are usually public once you have registered for them, so summarising a specification is rarely sensitive. Your own material is different. Draft pricing, cost breakdowns, named CVs, client references under NDA, and anything covered by a confidentiality clause in the tender itself all deserve a deliberate decision rather than a copy-paste.

Before you adopt any AI tool into a bid workflow, establish three things: whether your inputs are used to train the provider's models, where the data is processed and stored, and who inside your organisation is allowed to upload what. Buyers increasingly ask about AI use in the bid itself, and a clear internal policy is a much better answer than an improvised one.

A realistic workflow

In practice the division of labour that works looks like this. AI narrows tens of thousands of tenders to a shortlist and explains why. A human spends ten minutes per shortlisted tender deciding whether to pursue it. AI summarises the pack for the ones that survive and builds the compliance checklist. A human validates the checklist and owns the qualification decision. AI drafts the standard sections; specialists write the technical and commercial ones. AI runs a final compliance review; a named person signs off and submits.

That workflow removes most of the reading and most of the formatting, which is where the hours actually go — without moving accountability anywhere it does not belong. If you want to see the discovery half of it working, browse live tenders by country and category, or read what tender intelligence software does for the layer underneath.