Tips & Tricks

Tracking Public Tenders: How to Build a System That Never Misses a Bid

A practical system for tracking public tenders — from monitoring to go/no-go decisions to deadline management. Concrete steps, no buzzwords.

TenderWolf Team
Lees ook in: Nederlands Français
Tracking public tenders — complete guide to systematic tender management
Tracking public tenders — complete guide to systematic tender management

Last month I spoke with the managing director of an engineering firm in Ghent. Twenty employees, three million in annual revenue, a third of it from public contracts. He told me they had missed two framework agreements the previous year — not because they couldn’t deliver, but because nobody on the team had seen them. One was discovered through a competitor’s LinkedIn post. The other surfaced during a debrief with a contracting authority: “Shame you didn’t bid, you would have had a good shot.”

Estimated missed revenue: somewhere between €400,000 and €600,000. Not because they lacked capability, but because they had no system for tracking public tenders.

This isn’t an unusual story. It’s the default. Most companies that bid on public contracts do it reactively: they check e-Procurement when they remember to, lean on their network, or wait for a colleague to forward an interesting publication. That works, until it doesn’t.

This article describes a working system for tracking public tenders — from finding relevant publications to managing deadlines and team decisions. Not exhaustive, but actionable. Each component is something you can implement this week.

1. Monitoring: stop searching, start getting found

The first step is obvious but rarely done well. Most companies that say they “monitor” tenders are actually searching for them — they log into e-Procurement, type a few keywords, and scroll through results. That’s searching, not monitoring.

The difference is fundamental. Searching is something you do when you have time. Monitoring runs whether you have time or not.

What effective monitoring requires

Multiple dimensions, not just keywords. A search term like “IT consultancy” misses “digital transformation”, “software development”, and “business analysis”. Effective monitoring combines keywords with CPV codes (the EU classification system for procurement), geographic scope (NUTS codes), and specific contracting authorities you want to follow.

Full-text search inside tender documents. The title of a tender often tells you nothing. “Framework agreement for services” could be anything. The real information is in the specifications. If your monitoring doesn’t search inside those documents, you’re fishing with a net full of holes.

Fuzzy matching. “Cleaning”, “sanitation”, “building maintenance” — a human understands these are related. Exact keyword matching doesn’t. Your monitoring system should be smarter than a search box.

Cross-platform coverage. Belgian tenders appear on e-Procurement. European tenders above threshold values appear on TED. Dutch tenders on TenderNed. French on BOAMP. If your market doesn’t stop at the border, your monitoring shouldn’t either.

The litmus test

Ask yourself: if a perfectly relevant tender was published on e-Procurement yesterday, would I know about it today?

If the answer is “depends on whether I checked,” you’re not monitoring — you’re hoping.

2. Triage: the daily fifteen minutes

Monitoring is only useful if someone actually looks at the results. This sounds trivial, but it’s precisely where most systems break down.

The pattern is predictable: you set up monitoring, it works, you get daily emails. In week one, you open every alert and review each tender carefully. By week three, the emails pile up. By week six, you’ve stopped opening them.

The fix is timeboxing

Block fifteen minutes per day — not more — to review new matches. This constraint forces two things:

Your monitoring must be precise enough that fifteen minutes is sufficient. If you’re drowning in irrelevant results, the problem isn’t time management — it’s your search profiles. Tighten your criteria until the daily batch is manageable: typically 5 to 15 new matches.

Your triage must be binary. For each tender: relevant or not relevant. No “maybe later” pile, no “I’ll look at this when I have time.” If it might be relevant, it’s relevant. Move it to the next step. If it’s clearly not, mark it and move on.

What this looks like in practice

Per tender:

  • Read the title and short description (10 seconds)
  • Check the contracting authority — is this someone you want to work with? (5 seconds)
  • Check the estimated value — is this in your range? (5 seconds)
  • Check the deadline — is there enough time? (5 seconds)
  • Decision: advance or dismiss (immediate)

That’s 25 seconds per tender. In fifteen minutes, you can triage 35+ tenders. More than enough for most companies.

3. Go/no-go: the decision that saves you money

Most companies skip this step entirely. They either bid on everything that looks vaguely interesting (expensive) or only bid on things they feel completely certain about (too conservative). Both approaches burn money — the first through wasted proposal effort, the second through missed opportunities.

A structured go/no-go decision doesn’t need to be a formal committee meeting. It’s a checklist. Takes 10 to 20 minutes per tender and saves you weeks of wasted bid preparation.

The five questions that matter

QuestionWeightRed flag
Do we meet all selection criteria?Must-haveAny “no” = stop
Can we deliver what the specs describe?Must-haveWishful thinking = stop
Do we have a realistic price for this?HighGuessing = risky
Is the deadline feasible given our current workload?HighRequires heroics = risky
Can we differentiate on the award criteria?Medium”We’ll figure it out” = risky

The decision rule: if both must-haves are green and at least 2 of the remaining 3 questions are also green, it’s a go. Otherwise, it’s a documented no — with the reason recorded.

Why you must document the “no”

That documentation isn’t bureaucracy. After six months, you’ll have data on why you pass on tenders. And that data improves your monitoring: if you consistently pass because “wrong region,” tighten your NUTS code filter. If you pass because “deadline too short,” configure your monitoring to catch publications earlier.

The feedback loop between go/no-go decisions and monitoring criteria is what turns an ad-hoc process into a self-regulating system.

4. Deadline management: the silent killer

You’ve found a tender. You’ve decided to bid. Now you have three to six weeks to prepare your proposal. What could go wrong?

Everything, if you’re tracking deadlines in your head, on sticky notes, or in a shared spreadsheet that nobody checks proactively.

Critical dates per tender

  • Publication date — when the clock starts running
  • Questions deadline — your last chance to ask for clarification (often 10 days before submission)
  • Submission deadline — one minute late = disqualified
  • Expected award date — when to expect a result
  • Standstill period — window for legal challenges after award

The hidden deadline: asking questions

Most companies focus on the submission deadline and forget that the questions deadline is often more important. This is your only chance to surface ambiguities in the specifications, challenge potentially restrictive requirements, or obtain information that changes your approach. Once the questions deadline passes, you’re bidding blind on anything unclear.

What’s more: the answers to other bidders’ questions sometimes contain information that fundamentally changes your assessment of the tender. Anyone who doesn’t read those answers is missing a crucial piece of the puzzle.

What works

A shared calendar or task system where each active tender has its critical dates as calendar events. Not email reminders (they get lost), not mental notes (they fail), not a spreadsheet (nobody opens it proactively). A calendar event that appears in your daily schedule, unavoidably.

5. Team coordination: easiest to ignore, hardest to get right

In most companies, tender management is either one person’s side job or everyone’s shared responsibility — which means nobody’s actual responsibility.

Neither scales. Once you have 5 to 10 active tenders at different stages, you need clarity on three things:

  • Who is responsible for each tender? One name, not a team.
  • What is the current status? Triaged, go/no-go decided, in preparation, submitted, awaiting result.
  • What’s the next action and when? Not “work on proposal” but “finalize technical reference by Thursday 4pm because the submission deadline is Monday.”

A kanban board works for this

Four columns: New matches → Evaluating → Preparing bid → Submitted. Each card is a tender with an owner, a deadline, and a next action. Weekly standup of ten minutes to flag blockers and reassign where needed.

The tool doesn’t matter — it could be Trello, Notion, a whiteboard, or the built-in workflow of your tendering platform. What matters is that every active tender is visible and owned.

The sixth component: using data to get better

After six months of working systematically, you’ll have data. How many tenders you monitored, how many you pursued, how many you won. Most companies calculate a “hit rate” at this point and stop.

But the interesting data is in the patterns:

  • Which monitoring profiles generate the most won tenders? Double down on those.
  • Which contracting authorities do you win most often with? Prioritize those relationships.
  • At which estimated values do you have the best hit rate? Focus your efforts there.
  • How long is your average preparation time for a winning bid vs. a losing one? If losing bids take longer, you’re over-investing in weak opportunities.

This isn’t business intelligence for its own sake. It’s calibration. Your monitoring criteria, your go/no-go checklist, and your time allocation all improve when you feed data back into the system.

A concrete example: a construction company that, after a year of systematic tracking, discovered their win rate on municipal contracts under €500,000 was 35%, but on provincial contracts above one million it was just 8%. They narrowed their monitoring, sharpened their go/no-go criteria, and their overall win rate climbed from 18% to 27% — not by bidding more, but by bidding more selectively.

Start simple, build out

If you’re currently handling tenders ad hoc, don’t try to implement all five components at once. Start with monitoring — that’s the foundation. Everything else falls apart if you’re not systematically finding relevant tenders.

The sequence:

  1. Week 1: Set up monitoring with the right search dimensions. Invest half a day here. This is the most important half day of the entire process.
  2. Weeks 2–3: Install the daily triage routine. Fifteen minutes, every morning, no exceptions.
  3. Week 4: Introduce the go/no-go checklist. Print it out and pin it next to your screen if that helps.
  4. Month 2: Formalize deadline management — all critical dates in a shared calendar.
  5. Month 3: Start tracking results and feeding data back into your criteria.

After three months you’ll have a working system. After six months you’ll have data to optimize it. After a year you’ll wonder how you ever worked without it.

TenderWolf offers a free plan with unlimited search profiles and daily alerts for public tenders in one European country of your choice. No trial period, no credit card — you can start today and see for yourself whether systematic monitoring makes a difference.

Start free with TenderWolf


Further reading

Was this article helpful?

Track public tenders yourself?

TenderWolf helps you find, analyze, and win relevant public tenders. Start for free, no credit card required.

Start for free