How to Build a Tender Opportunity Tracking System

Most businesses that bid for tenders in Sri Lanka start informally: someone clips a newspaper notice, another person spots a notice on an entity website, and details live in email threads and memory. That works for one or two bids a month. Beyond that, opportunities slip through, deadlines are missed and nobody can say which tenders were won, lost or never pursued. A tender tracking system fixes this by turning scattered notices into a structured pipeline you can manage, measure and improve.

This guide explains how to build one — from the sources you monitor, to the data you record, to the reports that tell you where to focus. It does not require expensive software; a well-designed spreadsheet and some discipline go a long way.

Note: A tracking system organises information, but the official bidding documents always govern. Verify every requirement, date and submission method with the tender document and procuring entity.

What a Tender Tracking System Should Do

A good system answers five questions at any moment:

1.What's new? Which relevant tenders have been published recently? 2.What are we pursuing? Which ones have we decided to bid on, and who is responsible? 3.What's due? Which deadlines and milestones are approaching? 4.What happened? Which bids were submitted, won, lost or cancelled? 5.What have we learned? Where do we win, where do we lose, and why?

If your current method can't answer these quickly, it's time to build something better.

Step 1: Define Your Target Profile

Before tracking anything, define what's relevant so your system doesn't fill with noise.

• Categories: e.g. stationery, IT equipment, civil works, cleaning services, medical supplies
• Geography: provinces or districts where you can deliver
• Buyers: ministries, provincial councils, local authorities, state corporations, hospitals, universities, private companies
• Value range: contracts large enough to be worthwhile, small enough to be realistic
• Eligibility: e.g. CIDA grade for works, licences or authorisations you hold

Write this down. It becomes your filter for screening.

Step 2: Identify and Schedule Your Sources

Tender notices in Sri Lanka appear across several channels:

| Suggested check | |---|

| Source | What you find there | |---|---|

| frequency | |---| | Weekly | | Daily / as published | | Several times a week | | Weekly for key buyers | | Daily or via alerts |

An aggregator can reduce the manual effort considerably. TenderHub.lk, for instance, aggregates public and private tenders, lets you filter by category, province, keyword, value band and deadline window, includes a gazette tenders section, and offers email alerts. Your tracking system then focuses on the opportunities you select, not on finding them.

Assign each source to a named person and a schedule so monitoring doesn't depend on who happens to remember.

Step 3: Design Your Tracking Fields

Start with a spreadsheet (or a database or project tool if you prefer). Each row is one tender. Recommended columns:

Identification - Internal ID - Tender title - Reference number - Procuring entity - Category - Province / district - Source and date found - Link or location of documents Key dates - Document purchase/download deadline - Pre-bid meeting / site visit - Clarification deadline - Closing date and time - Bid validity end date

Requirements - Eligibility notes (grading, licences, experience, turnover) - Bid security required (yes/no), amount, validity - Submission method (paper/e-GP) and location

Management - Bid/no-bid decision and reason - Owner - Stage (see next step) - Estimated value (your estimate, if not published) - Our bid price (after submission)

Outcome - Result (won/lost/cancelled/no award) - Winning price, if published or disclosed - Lessons learned

Keep dropdown lists for fields like category, stage and result to keep data clean and easy to filter.

Step 4: Set Up Pipeline Stages

A pipeline shows where every opportunity stands. A simple set of stages:

1.Identified — found and recorded 2.Screening — checking fit and eligibility 3.Declined — not pursuing (record why) 4.Preparing — bid in progress 5.Review — final compliance and approval 6.Submitted — delivered or uploaded, with proof 7.Under evaluation — awaiting decision 8.Won / Lost / Cancelled — final outcome

You can view this as a filtered spreadsheet or as columns on a task board. Either way, everyone in the team should see the same picture.

Step 5: Assign Roles and Routines

Even a two-person team benefits from clear routines.

| Role | Responsibility | |---|---| | Monitor | Checks sources/alerts and records new tenders daily | | Screener / decision-maker | Makes bid/no-bid decisions within a set time | | Bid owner | Prepares the bid and updates its row | | Reviewer | Checks compliance before submission | | Finance contact | Handles bid securities and pricing approval |

Weekly routine example:

• Daily: record new tenders; update stages.
• Twice weekly: screening meeting (short) to decide on new entries.
• Weekly: review the upcoming deadline list for the next two weeks.
• Monthly: review outcomes and metrics.

Step 6: Add Alerts and Reminders

A tracking system should push important dates to people, not wait for them to look. Options include:

• Calendar entries for every closing date and milestone, with reminders
• Conditional formatting in the spreadsheet (e.g. highlight rows closing within 7 days)
• Email alerts from a tender information service for new notices in your categories

Step 7: Store Documents Consistently

Link each tracker row to a folder with a consistent naming convention, for example 2026- 045_EntityName_TenderRef. Inside, keep subfolders for the bidding document and addenda, working drafts, the final submitted bid, and correspondence. This makes it easy to find past bids when preparing similar ones.

Step 8: Measure and Improve

Once you have a few months of data, your tracking system becomes a source of insight.

Useful metrics:

• Opportunities identified per month, by category and source
• Bid rate — share of identified tenders you bid on
• Win rate — share of submitted bids won (by count and value)
• Loss reasons — price, technical non-compliance, documentation, late submission
• Average price gap to the winning bid, where known
• Source effectiveness — which sources produce the tenders you actually win

Illustrative example (hypothetical numbers): Over six months, a firm identifies 120 relevant tenders, bids on 30 and wins 6 — a 20% win rate. Its tracker shows that most wins came from local authorities in two provinces, while bids to large ministries were often lost on experience criteria. The firm decides to focus on local authority work and pursue subcontracting to build experience for larger tenders.

Keeping Data Quality High

A tracker is only as useful as the information in it. A few habits keep it reliable:

• Record from the official notice. Copy reference numbers, dates and times directly from the gazette, newspaper notice, entity website or bidding document rather than from memory or a colleague's message.
• Note the source of every date. If a date changes through an addendum, record the addendum number and update the row immediately.
• Avoid duplicates. The same tender may appear in several newspapers and on an aggregator. Search the tracker by reference number before adding a new row.
• Use consistent names. Decide how you will write each procuring entity's name and stick to it, so filtering and reports work.
• Close every row. Every tender should eventually reach a final stage — declined, won, lost or cancelled. Open rows that never close make your metrics misleading.
• Protect the file. Keep backups, limit who can delete rows, and if you use a shared online spreadsheet, review access when staff change.

A short monthly "clean-up" session, where one person checks for missing fields and stale rows, keeps the system trustworthy as volume grows.

Spreadsheet vs. Dedicated Tools

| Option | Strengths | Limitations | |---|---|---| | Spreadsheet (shared) | Free or low cost, flexible, familiar | Manual updates; needs discipline | | Task board / project tool | Visual pipeline, task assignment | Less suited to detailed data analysis | | CRM or bid management software | Automation, reporting, integrations | Cost and setup time | | Tender alert service + spreadsheet | Fast discovery plus your own pipeline | Two tools to maintain |

Start simple. Move to more sophisticated tools only when your volume justifies it.

Common Pitfalls

• Recording tenders but never updating stages
• Not recording declined tenders and reasons (you lose learning)
• No single owner per tender
• Ignoring addenda after the row is created
• Tracking only closing dates and missing clarification or site visit dates
• Not recording outcomes, so you can't measure win rate

Setup Checklist

• Target profile defined (categories, regions, buyers, value range)
• Sources listed with an owner and check schedule
• Tracker created with standard fields and dropdowns
• Pipeline stages defined and used consistently
• Roles and weekly routine agreed
• Calendar reminders and highlighting rules set
• Document folder naming convention in place
• Monthly review of metrics scheduled

Frequently Asked Questions

Do I need special software to track tenders?

No. Many small businesses run an effective system on a shared spreadsheet and calendar. Dedicated tools help when volume grows or several team members are involved.

How do I avoid missing new tenders?

Combine scheduled checks of key sources with alerts from a tender information service, and make one person responsible for recording new notices every day.

Should I record tenders I decide not to bid on?

Yes. Recording declined tenders and the reasons helps you spot patterns — for example, repeatedly lacking a certain licence or experience — that you can address to win more later.

How can I find out who won a tender I lost?

Award information may be published or available on request, depending on the procurement method and the entity's practice. Ask the procuring entity politely and record whatever you learn.

How long should I keep tracking records?

Keep them for several years. Historical data helps with pricing, shows seasonal patterns in procurement and provides evidence of experience for future bids.

Can a tracking system help with annual supplier registrations?

Yes. Add registration notices as rows with their own deadlines, so you don't miss annual registration windows with key entities.

Key Takeaways

• A tender tracking system turns scattered notices into a manageable pipeline.
• Define your target profile first to avoid noise.
• Monitor sources on a schedule, using alerts to save time.
• Record consistent fields, especially all deadline types.
• Assign owners and routines.
• Measure outcomes to focus on where you win.

Conclusion

A tender tracking system doesn't need to be complicated to be powerful. With a clear target profile, reliable sources, consistent fields and simple routines, you'll miss fewer opportunities, meet more deadlines and learn steadily where your business competes best. Feed your pipeline every day by following the daily tender notices on TenderHub.lk and setting alerts for your chosen categories.

Related guides

• How to Manage Multiple Tender Deadlines
• How to Prepare a Company Profile for Tender Applications
• Common Tender Documentation Mistakes
• How SMEs Can Become Government Suppliers

Browse live tenders in Sri Lanka, see what is closing this week and get daily tender alerts on TenderHub.lk.