How to audit construction tender alerts and keep saved searches manageable

What the official services say they do

According to the GOV.UK guide for the central digital platform and the enhanced Find a Tender service, the platform publishes regulated public procurement notices and allows users to search notices free of charge. The same guide says there are search tools, filters and notifications, including saved searches that can email you when a notice meets your criteria.

That guidance gives a few concrete examples of live functions. It says users can filter by notice type, use a contract location filter to select one or more regions, and save a search with a chosen name and email frequency. It also gives examples of key notice types, including pipeline notices, tender notices and contract award notices.

Contracts Finder describes a different service. GOV.UK says it lets users search for information about contracts worth over £12,000 including VAT with the government and its agencies, look for opportunities in different sectors, see what is coming up and view previous tenders and contracts. It also says users can create an account to get email updates and save searches, although searching and applying can still be done without an account.

• Verified Find a Tender features in the supplied evidence: search, filters, notice type selection, contract location filtering, saved searches, email notifications.
• Verified Contracts Finder features in the supplied evidence: search, saved searches, email updates, sector searching, future opportunities, previous tenders and contracts.
• Do not assume both services have identical filters or identical notice categories just because both support alerts.

Why construction tender alerts become noisy

Most alert problems are not technical failures. They come from broad search design. A saved search may mix early market visibility with live bid opportunities, cover too many regions, or rely on terms that pull in unrelated maintenance, consultancy or supply contracts.

The Find a Tender guidance is useful here because it distinguishes notice types. A pipeline notice shows expected procurements, a tender notice signals an opportunity to tender for, and a contract award notice appears after tenders have been assessed and the authority intends to enter into a public contract. If your team wants live bid opportunities, receiving award notices in the same alert may create unnecessary volume.

Location is another common issue. GOV.UK says Find a Tender allows filtering by contract delivery region. If your saved search covers every region, the resulting alert volume may be too high for a local or regional contractor. Likewise, Contracts Finder may still be useful for some lower-value opportunities, but it should not be treated as the only source for high-value UK contracts, because GOV.UK says high-value contracts should usually be found through Find a Tender instead.

• Common causes of irrelevant alerts: too many regions, mixed notice stages, broad construction terms, no internal review rules.
• A noisy alert is not always a bad search term problem; it may be a scope problem.

A practical saved-search audit you can run monthly

The workflow below is a recommendation, not a platform feature. It works best as a small spreadsheet or shared review note. Audit each saved search separately so you can see whether one search should be refined or replaced rather than endlessly adjusted.

Start by pulling a sample of recent alert results for each saved search. You do not need a huge sample. The aim is to understand patterns in irrelevant notices, not to score the whole market. For each result, record only factual review notes such as notice title, portal, visible notice type, visible location and your reason for keeping or rejecting it.

Then classify irrelevant results. This helps you improve the search without guessing. A high number of wrong-location results suggests a geography problem. A high number of award notices in an opportunity alert suggests a notice-type problem. A high number of professional-services notices in a works-focused search suggests a term or scope problem.

• Suggested audit columns: saved-search name, portal, intended purpose, current terms, current locations, notice type included, sample size, relevant results, irrelevant results, main rejection reasons, decision, next review date.
• Suggested rejection reasons: wrong geography, wrong notice stage, wrong buyer type for your business, wrong works category, too large, too small, duplicate monitoring value, unclear relevance.
• Suggested review decisions: keep as is, tighten terms, remove a region, split by region, split by notice type, lower email frequency, retire search.

Separate evidence from your internal recommendations

It is worth being strict about what the portal definitely does and what your team is choosing to do. From the supplied GOV.UK evidence, you can safely rely on the existence of search, filters, saved searches and email notifications on the named services. You can also rely on the notice-stage descriptions given for pipeline, tender and contract award notices on Find a Tender.

By contrast, an audit score, a monthly review meeting, a rule such as 'retire any alert with less than 10 per cent useful results', or a naming convention such as 'FT-Works-East-TenderOnly' are internal management choices. They may be sensible, but they are not official platform functions. Keeping that distinction clear helps your team avoid designing a process around features the source material does not confirm.

• Evidence-backed portal fact: Find a Tender saved searches can send email notifications when notices meet chosen criteria.
• Recommendation: name saved searches consistently so anyone can tell the purpose from the title.
• Evidence-backed portal fact: Contracts Finder accounts can save searches and get email updates.
• Recommendation: review old searches after any service-area or capability change in your business.

Fictional worked example: cleaning up two overlapping alerts

Fictional example. A regional construction subcontractor has two alert searches. Search A covers all UK regions and all notice types with broad construction terms. Search B covers only one region but still includes previous contract information and notices that are no longer useful for live bidding.

After a four-week sample, the team finds most irrelevant items fall into three groups: award-stage notices, regions it does not serve and notices outside its works focus. The team keeps one search for tender-stage opportunities in its active regions and creates a second, lower-frequency monitoring search for pipeline notices only. It retires the overlapping broad search.

Nothing in this example guarantees more suitable opportunities. The value is operational: the inbox becomes easier to review, and the team can explain why each alert exists.

• Search purpose 1: live opportunities to assess for bidding.
• Search purpose 2: early pipeline visibility for capacity planning.
• Decision rule: if a search has no clear purpose, redesign or remove it.

Limitations and next checks

This guide is limited to the features and scope stated in the supplied GOV.UK evidence. It does not confirm every filter, workflow or account option on every UK procurement portal, and it does not cover commercial alert tools or devolved-nation portals beyond GOV.UK's statement that separate public sector procurement websites exist for Scotland, Wales and Northern Ireland.

It also does not tell you whether a notice is commercially suitable, whether your firm meets the requirements or whether a bid is worth pursuing. Those are business decisions that need review of the notice and tender documents.

Your next check should be to open each live saved search, compare its current settings with its actual purpose, and confirm whether the portal and jurisdiction are still the right fit. Then record a simple keep, change or retire decision for every alert.

• Check whether the search is on the right portal for the contract value and jurisdiction.
• Check whether notice type matches your purpose: pipeline monitoring, live tendering or post-award intelligence.
• Check whether regions still match your delivery area.
• Check whether the alert frequency is manageable for the person reviewing it.
• Check the original source pages for current service details before changing your internal process.