Intelligence Reports · Guide

Tender alerts arrive too late

A tender alert tells you a document has been published. By then the requirement is written, the budget is set, and everyone bidding found out on the same morning you did. The alert is working perfectly. It is just reporting the end of a process you needed to know about at the start.

Written from running weekly opportunity monitoring for organizations from lean teams to a Fortune Global 500 enterprise. The worked examples are invented; the pattern is not.

What a tender alert actually does

A tender alert service watches procurement portals — national and regional government platforms, the big public-sector notice boards, sometimes private-sector procurement pages — and emails you when a new notice matches your keywords or classification codes. Most also cover prior information notices, contract awards and framework renewals.

That is a genuinely useful thing to have, and it is cheap. If you sell into public procurement and you are not watching the portals at all, start there before you read anything else on this site.

But it is worth being exact about what the service is: it is a publication monitor. It tells you when a document appeared. Everything below follows from that one fact.

Three things that already happened before the notice went up

A published tender is the visible end of a long private process. By the time it reaches a portal:

1 · The requirement is written

Somebody decided what good looks like — the standards, the volumes, the service levels, the integration the winner has to support. Those choices were made in conversations you were not in, often with help from whoever is already supplying them. A specification is never neutral; it is a description of somebody’s idea of the answer.

2 · The money was approved

A budget exists, which means a business case was argued and signed months earlier. The scale of the thing is fixed. If your best offer is a different scale — smaller and cheaper, or larger and staged — the document has already ruled it out.

3 · Everybody was told at once

Simultaneous publication is the point of a tender, and it is exactly what removes your advantage. A faster alert does not help: your competitors’ alerts fired in the same minute. The only lead you can have over a published tender is a lead you built before it was published.

What that costs, in ordinary numbers

Take an invented but unremarkable case. A components supplier gets an alert on a Tuesday: a regional transport operator is tendering for depot equipment, submissions close in five weeks.

The team does everything right. They read it that morning, qualify it by Thursday, and spend three weeks on a careful response. They lose. In the debrief they learn the operator ran a market consultation fourteen months earlier, spoke to four suppliers during it, and built the specification around what those conversations suggested was normal. Two of the four bid. One won.

Nothing went wrong in those five weeks. The work was lost in a meeting the previous year, and the alert could never have told them about it, because no document had been published.

The useful question after a loss like that is not “how do we bid better?” It is “what was visible fourteen months ago, and were we looking at it?”

What is visible earlier

A surprising amount, and almost all of it public. A capital commitment — a depot, a line, a plant — is announced, planned and financed long before anything is bought for it. A rule with a compliance date tells you exactly when a purchase becomes unavoidable. A new head of procurement or engineering reviews inherited suppliers in their first months. A merger creates two supplier lists that will be cut to one.

Each of those has a lead time measured in quarters rather than weeks, and each is reported somewhere — often in regional press, planning notices or a regulator’s own site, and often in a language nobody on the team reads.

We wrote those up separately, with the lead time each one buys: the signals that come before an RFP.

Keep the alerts

None of this is an argument for switching your alerts off. They cost little, they are the only complete record of what actually got published, and they catch the requirements nobody could have predicted — an emergency replacement, a framework you did not know you qualified for, an award notice that tells you who your real competition is and what they charged.

Treat them as the floor, not the strategy. A tender you find only through an alert is a tender you are bidding on somebody else’s terms. That is worth doing when the fit is genuinely good. It is not worth building a pipeline on.

The ratio worth watching is what share of your wins came from work you knew about before it was advertised. If that number is zero, the alerts are carrying the whole pipeline and every deal is a price fight.

Four tests before you spend three weeks on a response

When an alert lands, these tell you quickly whether you are early or late to it:

  • Was there a prior notice or a market consultation? Portals publish these, and almost nobody reads them. If one exists and you were not part of it, someone else was.
  • Does the specification name something only one supplier comfortably meets? A standard, a certification, an interface, an installed-base requirement. That clause did not write itself.
  • Who holds the current contract, and when was it awarded? Award notices are public. An incumbent finishing a good five-year run is a different proposition from one who has had a bad year.
  • Is the window shorter than the work? A three-week window on a complex requirement usually means the buyer already knows who can answer it in three weeks.

Failing one of these is not a reason to walk away. Failing three is a reason to put the effort into the next one instead, and to start watching the events that would have told you about this one a year ago.

Intelligence Reports
Automated, customizable industry intelligence reports for business.
Request a sample·Privacy·Terms·Part of The Intelligence Bulletin·
© 2026 LevTech Global. All rights reserved.