TenderTech Market Benchmark 2026: 52 Vendors, 81 Features, One Clear Leader Read more

Track

Every bid on one board,and what is due.

Track shows each pursuit from active to won. Flow, the Tendersight agent, reads the tender files and reports what each bid still needs.

The Tendersight bid pipeline with pursuits in Active, Bid submitted and Won

Pipeline value per stage

Deadlines copied from the notice

Weekly summaries from Flow

The board shows where each bid stands. Flow tells you what it still needs.

Ask about any pursuit in plain words. Flow reads its requirements, documents and dates, and answers with what is missing and where it found it.

What a bid pipeline has to show.

A team with several live tenders needs the same picture every morning: what is due, who owns it and what is still missing.

  • Bids at different stages

    Some are in preparation, some are submitted and waiting, some are decided.

  • Dates that change

    Corrigenda and clarification answers can move a date after the work has started.

  • One owner per bid

    Each pursuit needs a person accountable for getting it submitted on time.

  • Documents still missing

    Guarantees, certificates and declarations that nobody has uploaded yet.

  • Value at stake

    Management asks what is in play, what was sent and what was won.

  • Late changes

    When a price or a document changes near the deadline, the team needs to see who changed it.

How the pipeline stays current.

Track holds the board. Flow does the reading: it finds tenders, pulls dates from documents and reports what each bid still needs.

  1. Pursuits sit in Active, Bid submitted, Won and Lost, each column with its count and pipeline value. Filter by deadline, value, owner or source.

    One board for every pursuit
  2. Ask Flow for tenders in plain words. It searches the notices, and the pursuits you create carry the deadline and value from the notice.

  3. Beyond the submission deadline, Flow finds clarification cut-offs, site visits and guarantee periods, quotes each one with its page and checks them against your documents.

  4. Flow opens the pursuit, checks its requirements and required documents, and tells you what is missing before the deadline.

  5. A scheduled task summarises the pursuits due soon, grouped by owner. Each run opens its own thread for the team.

Pipeline questions you can ask Flow.

Examples from bid managers who run several tenders at the same time.

  • Search

    Find engineering services tenders in the Netherlands and Belgium closing after 1 November, with an estimated value above €500,000.

  • Status

    Which active pursuits close in the next 14 days, and how complete is each one?

  • Documents

    Compare the required documents in the tender file with the pursuit library and list the gaps.

  • Dates

    Read the school renovation tender and list every date: clarifications, site visit, submission and guarantee validity.

  • Schedule

    Every Friday at 15:00, list the pursuits we submitted this week with their estimated value.

  • Research

    Show the contracting authority statistics for the regional water authority before we add this tender to the pipeline.

The detail behind each card.

Alerts that feed the board, tasks from the tender file and a record of progress on every pursuit.

Alert rules set up in a conversation

Describe the tenders you want in the pipeline. Flow drafts the alert rule and creates it once you approve.

Suggested tasks from the tender file

In-depth analysis lists the tasks a tender implies. Your team imports the useful ones and gives each an owner and a due date.

A timeline of who did what

Each pursuit keeps a recent activity feed of member actions, such as uploads and completed analyses, next to a contribution graph.

Completion and grade on every pursuit

The pursuit overview shows how complete the bid is across its modules, graded from F to A+ and synced with the final checkup.

Completion and grade on every pursuit

Every date, with its source.

The submission deadline travels with the pursuit. The other dates sit in the tender documents, and Flow reads them out.

Submission deadline

Where it comes from
Copied from the notice when the pursuit is created
Where your team sees it
Pursuit card, overview countdown and the Home start screen

Clarification cut-off

Where it comes from
Read by Flow from the tender documents, with the page
Where your team sees it
Flow's answer, with the quote

Site visits and other milestones

Where it comes from
Listed by Flow across all documents, each with its quote
Where your team sees it
The thread, with document and page

Guarantee validity

Where it comes from
Extracted by Flow with the amount and the source document
Where your team sees it
The thread, with document and page

Task due dates

Where it comes from
Set by task owners in task management, for works and services
Where your team sees it
Deadline widgets on Home

Pursuits due soon

Where it comes from
A scheduled task that Flow runs
Where your team sees it
A new thread on every run

See your own tenders on the board.

In a demo we set up pursuits from tenders you are following and ask Flow what each one still needs.

Track feeds Insights

Won and lost pursuits and their estimated values feed the win rate and pipeline reports in Insights.

See Insights

Questions about pipeline tracking

How does the bid pipeline work?

Every pursuit sits on a kanban board in Active, Bid submitted, Won or Lost. Your team moves cards as bids progress, and each column shows its count and total estimated value. You can filter by deadline, value, owner and source.

Where do the deadlines come from?

The submission deadline and estimated value are copied from the notice when a pursuit is created, or entered by hand for standalone pursuits. Other dates, such as clarification cut-offs and guarantee validity, Flow reads from the tender documents and quotes with the page.

Does Flow move pursuits between stages?

No. Your team changes the status of each pursuit. Flow finds tenders, creates pursuits, reports what each one still needs and can run a scheduled summary of the pursuits that are due.

Can we see who changed what on a pursuit?

Yes. The pursuit overview has a contribution graph and a recent activity timeline of actions taken by members, such as uploads and completed analyses. Changes that Flow proposes are approved in the thread, where each decision is recorded.

Can Flow send us deadline reminders?

Flow does not send emails. You can schedule it to summarise the pursuits due in the coming days, and each run opens a thread your team can read. Pursuits with approaching deadlines also appear on the Home start screen.

Know what is due before it is urgent.

Start free, create your first pursuits and ask Flow what each one still needs.