Run an RFP tracker your team decides with
An RFP tracker is the one list a bid team keeps of every RFP it is weighing, working on or has submitted. The bid manager sets its columns and stages, and the team reads it on a set day.
On this page
The buyer moved the clarification deadline forward, and the tracker still shows the old date because the amendment reached one writer's inbox. An RFP tracker is worth keeping when everyone fills a few columns the same way, a named person moves each bid's stage as it changes, and the team reads it on a set day. Without those three, it becomes a list the bid manager rekeys before each meeting, and nobody trusts it in between.
Where an RFP tracker breaks
Take an illustrative team of a bid manager and two writers, sharing a spreadsheet with one row for each RFP. Their tracker breaks wherever a bid passes from one person to another, because every handover relies on someone remembering to change a cell.
In APMP's Winning Business Ecosystem, planning a single bid sets milestones for writing, reviews and submission and defines who owns each. RFP tracking is keeping those owners and dates current across every bid at once. It runs across the wider RFP response work, and the gaps open at the handovers.
A writer uploads a response to the buyer's portal and moves straight on. The row still says "in progress", so the bid manager plans next week on finished work, and nobody watches for the buyer's clarification requests.
The buyer then issues an amendment that moves a deadline. It reaches the writer named as contact, while the other writer and the bid manager keep planning to the old date.
Two rows due in the same week name the same subject matter expert. Nobody reads them side by side, so the expert finds the clash when both drafts are due, and both answers get whatever time is left.
Then a bid closes and someone types "lost" in the outcome cell, with no reason. The next bid/no-bid call for that buyer starts from nothing.
Set the columns everyone fills the same way
An RFP tracker template is only as useful as the rule behind each column. Write one rule per column, and use a fixed list of choices wherever the answer is one of a few, because free text in a counted column can't be counted.
Columns for the decision
- Buyer: the name as it appears on the RFP, spelt the same way in every row.
- Reference: the buyer's own reference so that an amendment can be matched to its row.
- Where found: one choice from a fixed list, such as a portal, a direct invitation, a framework or a buyer's published pipeline.
- Submission deadline and clarification deadline: the date and time the buyer states.
- Estimated value: in the buyer's currency, with no conversion.
- Owner: one named person.
- Stage: one of the stages defined in the next section.
- Bid/no-bid decision and reason: the decision, its date and one reason from a short fixed list.
The "where found" column shows which sources produce bids worth pursuing, a question finding RFP opportunities takes further. Some buyers publish a pipeline of planned contracts before any tender exists. In the UK, central government buyers are told to update theirs at least every six months under the Sourcing Playbook, the government's guidance to its own buyers, so an entry there can be logged as an early signal.
Columns for the outcome
Three columns close each row. The outcome column takes one of won, lost, no award or withdrawn, and awarded value holds the contract value the buyer announced, in its currency. Reason given holds the buyer's stated reason, in its words, with a category beside it.
In APMP's close-out step, a bid that is not selected leads to a review of the feedback and the gaps it shows for future bids, which needs the buyer's reason on record.
Define each stage once, with who moves it
Give each stage an entry test and the one person who moves a bid into it. Without both, "in progress" means drafting to one writer and waiting for a result to another, and counting bids by stage stops meaning anything.
| Stage | A bid enters it when | Moved by |
|---|---|---|
| Found | it is logged with buyer, reference, where found and both deadlines | whoever finds it |
| Qualifying | an owner is named to assess it | bid manager |
| In progress | the bid decision is recorded with its reason and who approved it | bid manager |
| No bid | the no-bid decision is recorded with its reason | bid manager |
| Submitted | the response is uploaded and the buyer's receipt is saved | row owner |
| Under evaluation | the submission deadline has passed | row owner |
| Outcome | the buyer's decision arrives, or the team withdraws | row owner |
Two lines carry most of the weight. Nothing reaches "in progress" without a recorded decision. APMP places the bid/no-bid call in the pre-bid stage, under qualifying opportunities, judged on ROI, win probability and risk, with leadership buy-in before formal pursuit starts. Recording who approved it shows that buy-in, and the go/no-go decision covers the call itself.
Keep "submitted" apart from "under evaluation". In APMP's post-bid stage, the team monitors the evaluation and handles the buyer's clarification requests, which is live work with an owner. A bid left in "submitted" looks finished, so a request arriving then waits for someone to notice it. In the illustrative team, the writer who uploaded the response saves the receipt and moves the row to "submitted", and owns any clarification request that follows.
Update the tracker when a bid changes stage
The row's owner updates it on the day the bid changes stage, not at month-end.
Each row has one named owner, who keeps it current; the stage table says who moves a bid into each stage. The milestones inside a single bid live in that bid's own plan, built around its sign-offs as the tender timeline sets out. The row carries only the dates and stage the team reads across every bid.
A date the buyer moves needs its own rule, because an overwritten cell hides the change. Keep the original date, add the new one beside it, and record the amendment's reference and the day it arrived. When the illustrative team's amendment reaches the writer named as contact, that writer logs it on the row that day, and the whole team plans to the new date.
Read the tracker on a set day
Read the tracker on a fixed day, weekly or fortnightly as your volume needs, with the same short agenda each time. The bid manager runs it, and each row owner comes ready to answer for their rows.
- Which submission and clarification deadlines fall in the same week.
- Who owns, or is named on, more live bids than the team's set limit.
- Which rows are overdue to move stage, such as a submitted bid whose deadline has passed.
- What the RFP pipeline holds.
The RFP pipeline is every row at found or qualifying, read by its deadline, so the team sees what will need staffing before the bid/no-bid call.
Each question ends in an action. A clash is resolved by moving an internal date, bringing in another writer, or revisiting bid/no-bid on the weaker of the two bids. An overloaded owner hands a row on, and an overdue row is moved or explained before the read ends. The illustrative team's two rows naming the same subject matter expert surface under the first question, before either draft is due, while there is still time to move a date or bring in someone else.
Record outcomes you can learn from
Report win rate two ways, by number of bids and by value, and leave out no-bids, withdrawn bids, and those still pending. The two numbers answer different questions, and the exclusions keep the rate focused on results rather than bids the team never finished competing for.
By number, divide bids won by bids with a decided outcome. By value, divide the awarded value of bids won by the value of all decided bids, using awarded value where the buyer published it and estimated value otherwise (marked as such). Reading the RFP win rate goes further once these columns are filled.
Give the reason a category from a short list so that losses can be counted by reason, and add one yes/no column for whether price alone decided. In EU public procurement, the European Commission's Single Market Scoreboard tracks the share of procedures awarded solely because the offer was the cheapest. Where the illustrative team once typed only "lost", the row now holds the buyer's reason and its category, so the next bid/no-bid call for that buyer starts from it.
Know when the spreadsheet stops keeping up
An RFP tracking spreadsheet does the job for as long as the set-day read can be answered from it alone. When it can't, RFP tracking software is worth weighing, and the same test judges both.
Spreadsheet failures are documented. A 2026 analysis by Thorne and Collins of 121 publicly reported spreadsheet incidents from 1995 to 2026 found formula errors, data-entry slips and data-handling mistakes in 71 of them. These are reported failures, not a rate for ordinary spreadsheets. The paper also argues the risk covers visibility, disclosure, governance and trust, which is what a tracker carries once decisions rest on it.
Run the test on your current spreadsheet first, then on each option you weigh, with the same person and the same live bids. Answer each agenda question from the tracker alone, with no inbox or memory, and count an answer only if every row behind it matches the bid's documents.
The spreadsheet's result is the pass mark. An option passes if it answers more questions than the spreadsheet did. If nothing passes, keep the spreadsheet. Budget one set-day read per option for the bid manager and each row owner, and for every option beyond the spreadsheet, the set-up of columns and stages, security clearance and training for row owners.
How SEQUESTO runs RFP tracking
In SEQUESTO's agentic operating system (aOS), each bid is its own project, started from the team's set-up. The set-up carries the tracker's columns as the bid's fields and the team's own stages as its statuses, with no fixed review chain to fit. "Submitted" and "under evaluation" stay two statuses if the team defines them that way, and the team records the bid/no-bid decision on the bid itself.
Agent Force, the specialist agents, extracts every dated requirement from the tender documents into the bid's task list from day one. James, SEQUESTO's AI bid agent, adds the team's sign-off stages and review gates as milestones, each with time and a named reviewer.
Dashboards for pipeline, deadlines, workload and win rate, by number of deals and by contract value, are built on those bid fields, so nobody rekeys a copy before the set-day read. Every chart clicks through to the bids behind it. Each expert named on a bid also sees it on their own dashboard of everything assigned to them. The bid manager still takes each decision the read surfaces.
RFP tracker checklist
Run these against your current tracker before the next set-day read.
- Every column has one written rule for how it is filled, with fixed choices where the answer is one of a few.
- Every row holds buyer, reference, where found, both deadlines, estimated value and stage, and an owner from qualifying on.
- Each stage has a written entry test and one named person who moves bids into it.
- No row reaches "in progress" without a recorded decision, its reason and who approved it.
- Each row is updated by its owner on the day its bid changes stage.
- Every date the buyer moved keeps the original, the new date and the amendment reference.
- The set-day read is held on its day, with the same agenda.
- Every closed row holds the outcome, the awarded value, the buyer's reason and whether price alone decided.
- Win rate is reported by number and by value, without no-bids, withdrawn bids and pending bids.
Frequently Asked Questions
Sources
- Winning Business Ecosystem, APMP
- The Sourcing Playbook, Cabinet Office
- Single Market Scoreboard: public procurement, European Commission
- Anatomy of a Spreadsheet Failure, Analysing the EuSpRIG Horror Story Corpus, arXiv, Thorne and Collins (EuSpRIG horror story corpus)
