The current Contracts Finder threshold is £12,000 including VAT for central government and £30,000 including VAT for sub-central authorities, NHS Trusts, and NHS Foundation Trusts. If your monitoring only covers the obvious high-value portals, you're almost certainly missing work that sits in the gap these thresholds create.
That's the part many teams get wrong. They treat procurement portals as a list of websites to check, when the main issue is routing logic. Different contract values, buyer types, and publication rules send opportunities down different paths. If you don't map those paths properly, good tenders pass by unnoticed.
A lot of bid teams only realise this after the fact. They spot an award notice for something they could have delivered, then ask why nobody saw it live. The answer usually isn't poor bid writing. It's poor monitoring design.
Why You Might Be Missing Winnable Tenders
The usual pattern looks like this. A team keeps a close eye on Find a Tender because that feels like the serious market. Big contracts. Big buyers. Clear process.
Then a useful lower-value contract appears elsewhere, gets awarded quickly, and never makes it into the team's pipeline.
That's not bad luck. It's a blind spot.
The problem isn't effort
Most bid managers already work hard enough. They've got alerts, spreadsheets, bookmarked portals, and a daily check routine. What's missing is a way to sort opportunities by how the buyer is required to publish them.
That matters because lower-value public contracts are often the ones SMEs can win fastest. They can be easier entry points into an authority, easier to deliver, and easier to turn into repeat work. If you're only watching the channels used for larger procurements, you miss the contracts that build your account base.
A lot of “we didn't see it” problems are really “we watched the wrong route” problems.
I've seen teams put all their energy into high-profile frameworks while ignoring smaller published opportunities that would have been a cleaner fit. The contract value was manageable. The buyer was local. The incumbent wasn't unbeatable. But the opportunity never reached the right person internally because nobody had built a monitoring setup for that part of the market.
What this means in practice
You need to think less about portals as destinations and more about them as filters imposed by procurement rules.
That changes how you organise the team's search process:
- Buyer-first thinking: Know whether the target buyer is central government, local authority, or NHS.
- Value-first triage: Estimate where likely contracts sit by value band before you decide where to watch.
- Speed-first handling: Smaller contracts can move quickly, so delayed review kills otherwise good opportunities.
If your team wants a better starting point for that operating model, Bidwell has a useful page for bid managers handling busy public sector pipelines.
The important point is simple. Missing tenders rarely comes from not caring. It comes from monitoring the market as if all notices flow through one main channel. They don't.
The Official Contracts Finder Threshold Explained
Contracts Finder is a UK government portal used to publish public sector opportunities and award information. For bid teams, it matters because it catches work that may never appear in the higher-value notice routes you watch elsewhere.
The current rules are clear, but the practical effect is often missed.
The numbers that actually matter
Central government authorities publish at £12,000 including VAT.
Sub-central contracting authorities, NHS Trusts, and NHS Foundation Trusts publish at £30,000 including VAT.
These thresholds took effect on 21 December 2022 under the Contracts Finder transparency guidance in PPN 01/23.
In practical terms, central government means departments and bodies at the core of national government. Sub-central usually means bodies such as local authorities and other public authorities outside that central tier. NHS Trusts and NHS Foundation Trusts sit in the higher Contracts Finder publication band rather than the lower one.
The same guidance also requires award notices to include the winning contractor's full name, the award date, the contract value in pounds sterling, and whether the supplier is an SME or VCSE. That makes the threshold more than a technical line. It determines when useful market intelligence starts to appear.
Why bid managers should care
A threshold isn't just a compliance rule for buyers. It tells you where visibility begins.
If a buyer is operating above that line, you've got a much better chance of seeing the opportunity or the resulting award information in a structured way. If the buyer is below it, visibility gets patchy. Some authorities still publish voluntarily, but you can't build a reliable search process on voluntary behaviour alone.
That's why I tell new team members to stop treating Contracts Finder as an optional extra. It's one part of a routing map:
| Buyer type | Publication trigger |
|---|---|
| Central government | £12,000 including VAT |
| Sub-central authorities and NHS bodies | £30,000 including VAT |
The threshold tells you when a contract becomes visible enough to monitor consistently.
That visibility matters for all three parts of a modern bid workflow. Tender monitoring catches the live notice. The knowledge base stores what that buyer buys, who wins, and at what level. AI response generation then has a better starting point when a similar opportunity lands.
Contracts Finder vs Find a Tender FTS
Teams often talk about Contracts Finder and Find a Tender as if one should replace the other. That's the wrong comparison. They do different jobs.
Find a Tender handles the larger, above-threshold side of the market. Contracts Finder picks up the lower-value side and related transparency activity. If you only monitor one, you don't get incomplete data. You get a distorted view of where your realistic opportunities sit.
Think of them as two different news desks
Find a Tender is like the national bulletin. Big, formal, high-value notices. Contracts Finder is closer to the regional desk. Smaller public opportunities, plus award visibility that can be very useful when you're tracking buyer behaviour.
That doesn't make Contracts Finder less important. For many SMEs, it's the place where more winnable work shows up.
A simple way to think about it:
- Use Find a Tender when you're targeting major competitions, large frameworks, or bigger public contracts.
- Use Contracts Finder when you want visibility into lower-value opportunities and award patterns among central government, councils, and NHS bodies.
- Use both if you don't want your pipeline skewed towards only one type of work.
The routing logic most teams miss
The mistake is assuming “public sector tender search” is one job. It isn't. It's several jobs stitched together.
One search process is aimed at major strategic bids. Another is aimed at smaller entry-point contracts. Another is aimed at gathering award intelligence so your knowledge base gets sharper over time. Those are related, but they are not identical.
That becomes especially awkward with NHS buyers. Most bodies have a shorter award publication window, but NHS Foundation Trusts have 90 days. That creates a real lag in visibility and leaves suppliers waiting much longer to see confirmed award information. For a bid team, that delay slows post-bid learning and makes the knowledge base less current for NHS work.
If you're waiting for published award data before updating your NHS account view, you're often working behind the market.
So what works? Don't wait passively. During that gap, track buyer activity through meeting papers, procurement plans, local announcements, supplier engagement signals, and related service changes. None of that replaces a formal notice, but it helps your team build a more usable picture while official publication catches up.
What this means for your systems
Portal fragmentation hurts manual teams most. You have to monitor different channels for different reasons:
- Live opportunity capture for current bids
- Award analysis for competitor and buyer learning
- Account pattern spotting for future planning
If your tender monitoring only chases live notices, your knowledge base stays shallow. If your knowledge base is shallow, AI response generation has less context to work with. The tools only work well when the monitoring logic behind them is organised properly.
A Practical Monitoring Strategy for Bid Managers
Organisations don't need more alerts. They need a better triage model.
Start by building your monitoring around the way contracts are likely to be routed, not around whichever portals you happen to remember checking in the morning. That means splitting searches by buyer type, likely contract value, and strategic purpose.
Build three monitoring lanes
I usually recommend treating tender search as three separate lanes.
Entry-point opportunities
These are the smaller contracts that can get you in front of a buyer fast. They matter because they often lead to repeat work, a stronger account relationship, and better evidence for future bids.Strategic growth bids
These are the larger, more resource-heavy competitions. You won't pursue as many of them, so the filters should be tighter and the qualification standard higher.Award intelligence Many teams are weak in this area. They monitor live tenders but don't systematically harvest award notices and buyer patterns into a searchable internal record.
What to set up each day
A practical routine looks like this:
- Morning scan: Review new notices by buyer segment, not one mixed inbox.
- Fast qualification: Reject weak-fit notices quickly so the team keeps time for serious opportunities.
- Knowledge capture: Record buyer names, service categories, incumbents, contract values when published, and any recurring language.
- Response preparation: Feed recurring buyer requirements into your content library so future drafting starts from evidence, not memory.
Practical rule: If a notice is relevant enough to read, it's relevant enough to tag properly for future use.
That's where connected tooling matters. A proper system for tender monitoring across UK procurement portals should do more than send alerts. It should help the team decide what to act on now, what to store, and what to ignore.
Use routing assumptions, not guesswork
You won't always know a contract's exact value before publication. That's fine. You can still work from sensible assumptions.
If a service is likely to be a modest first-step engagement with a department, you should expect it to show up differently from a major long-term outsourced service. If you're targeting councils or NHS bodies, build separate searches rather than one broad “public sector” feed. The quality of your monitoring depends on how well your search structure mirrors buyer behaviour.
A good setup connects all three Bidwell-style pillars, even if you're using your own process. Tender monitoring catches the opportunity. The knowledge base turns repeated buyer activity into memory. AI response generation becomes far more useful because it can draft from organised, relevant material rather than generic boilerplate.
Common Threshold Mistakes and How to Avoid Them
The mistake I see most often is simple. People remember the threshold number, but not the calculation rule.
The Contracts Finder threshold is VAT-inclusive, not a pre-tax figure. That catches teams out because early internal estimates and supplier pricing discussions are often done ex VAT. Then someone assumes the contract sits below the line when it doesn't.
The VAT trap
Analysis has shown that 15-20% of SME bids face issues due to this VAT misalignment. That's a big operational problem, not a legal footnote.
A common scenario looks like this:
- The team estimates low: They talk about a contract as if the threshold test is based on the ex VAT number.
- The search logic goes wrong: They expect the opportunity to sit in one monitoring lane when the buyer treats it differently.
- The internal decision follows bad data: Time gets wasted chasing assumptions instead of checking the actual threshold position first.
You don't need a complicated procurement lecture to fix this. You need a habit.
What works and what doesn't
What works:
- Check VAT status early: Do it before you decide where an opportunity should have appeared.
- Train new team members on buyer type and threshold together: The number means nothing on its own.
- Record threshold assumptions in your CRM or bid tracker: That stops the same confusion repeating later.
What doesn't work:
- Relying on memory: People remember “£12k” or “£30k” and forget the VAT point.
- Assuming a buyer has published wrongly: Sometimes the issue is your calculation, not theirs.
- Using one generic search bucket for all lower-value work: That hides the very exceptions you need to spot.
When a notice appears in an unexpected place, check the VAT treatment before you question the portal.
This is also why a knowledge base matters. When your team records how buyers package and publish contracts, you stop treating every new notice as a fresh puzzle. Over time, the odd cases stop looking odd.
Automate Your Tender Search with Bidwell
Manual monitoring can work. It just doesn't scale well once you're tracking multiple portals, multiple buyer types, and multiple value bands at the same time.
That's the point where teams start missing things for boring reasons. An alert comes in too broad. A portal gets checked late. An award notice isn't captured. A useful pattern never makes it into the content library, so the next response starts from scratch again.
Bidwell fits this problem because it connects the three jobs typically kept separate. It handles tender monitoring across the key UK portals, helps build a usable knowledge base from opportunities and prior material, and supports AI response generation when it's time to write.
That combination matters more than any single feature. Monitoring on its own just creates more reading. AI drafting on its own can only work with whatever context you feed it. A knowledge base on its own goes stale if nobody updates it. When the three are connected, your process gets tighter and the handover between search, qualification, and drafting gets much cleaner.
If you're already thinking about how teams can boost efficiency with AI automation, that broader workflow question applies directly to bid operations too. The same principle holds. Good automation doesn't replace judgement. It removes repetitive checking and gives the team more time for the decisions that affect win rate.
For teams that want to see how that looks in practice, you can book a Bidwell demo.
If your team is tired of chasing portals, rebuilding the same answers, and missing contracts that should have been in the pipeline, Bidwell is worth a look. It gives you daily tender monitoring, a searchable knowledge base, and AI response generation in one place so you can spend less time hunting and more time bidding well.
