The information that decides whether you win usually arrives after the Request for Proposal (RFP) is published — and almost nobody is watching for it.
Here is an RFP* open right now, with three weeks left on the clock.
The State of Washington is looking for technical support on federal hazard-mitigation benefit-cost analysis. Proposals are due October 2. If you found it the week it was published and decided to bid, you had a clear picture of the work.
Then the government entity changed it three times.
On August 26, it posted the pre-bid conference deck and set the window for written questions. On August 27, Amendment One replaced Attachment D — the pricing form — and instructed bidders not to price on the superseded version. On September 3, it published its final answers to the twenty-five questions bidders had submitted. One of them confirmed that prior experience with the Federal Emergency Management Agency (FEMA) Benefit-Cost Analysis Toolkit is a mandatory minimum qualification, not a preference. Businesses without it are not eligible.
The deadline never moved. If the only thing you were tracking was the due date, nothing happened — while two of those three changes could disqualify your bid on their own.
That gap, between when an opportunity is published and when it is actually understood, is what we spent the last month building for.
Left: one live RFP as it actually reaches you. Right: the same RFP on one page on RFPGo.ai kept current.
Government RFPs do not sit still
An RFP is not a document. It is a document plus everything the government entity issues afterward. Amendments move deadlines, revise scope, replace forms, and strike requirements. Written answers do something more consequential: they bind. An answer can narrow eligibility, lock in your pricing, or reveal the incumbent. It is not commentary on the RFP. It becomes part of it. And answers often land within days of the deadline, when you have the least time to react.
Every lead now carries a last-updated date: the most recent amendment or published answer, whichever came later. On cards, it sits under the title as an Updated badge; in list view, it becomes a Last Updated column. September 8. September 3. August 31. August 28. And a dash where nothing has moved yet. On a normal page of active leads, those dates are not the exception.
What we shipped
1. Changes since published
Every lead now carries its own changelog. Each entry shows the date, the amendment number, and what it touched — tagged as Due Date, Proposal Submission, Scope / Requirements, Documents, or Question and Answer (Q&A) / Clarification. When a deadline moves, the old date appears struck through beside the new one. Above the entries, a summary line counts the changes and flags any that moved a deadline.
The Washington RFP reads as three entries: the pricing-form replacement flagged as a submission change, the September answers as Q&A. Neither is a date change — neither would have surfaced if the deadline were all you watched.
2. A document set that shows its own history
Original documents are listed first. Anything issued after publication is grouped under "Added since publication," labeled with the date it appeared and where it came from — for instance, "From amendment · Aug 27."
That settles a question businesses usually cannot answer without re-downloading everything: is my copy still current? For the Washington RFP, anyone holding the original package is holding a superseded pricing form.
3. The questions other bidders asked, and what the agency answered
Every lead with a published Q&A now shows it in full, filterable by what each answer affects. Above roughly thirty questions, the list opens to the ones capable of changing a bid decision.
The Washington solicitation's twenty-five answers are a fair sample. Some are administrative — electronic signatures are acceptable, a single award is anticipated. Some quietly widen the field: a sole proprietor can win this, and there is no minimum staffing requirement. And one of them decides whether you are allowed to bid at all.
None of that is in the RFP. All of it is binding.
The most useful answers are sometimes not answers at all. Washington's Department of Labor and Industries has a separate solicitation out for physician consultation services, due October 16. Its first amendment struck a requirement: bidders no longer need to attach every provider's license and board certification to the proposal, but can supply them on request. Its second round of answers left a question about transferring claim files to a bidder's own environment explicitly unresolved — the department is still confirming options with its information technology division. If your approach depends on that, you now know to keep watching.
4. Saved RFPs tell you when answers land
Your bookmarks and lead cards flag when a government entity has answered something since you saved the opportunity — so the RFPs you have committed to come find you when the terms shift.
Also in this release
Every lead is now graded Strong, Good, or Partial against the tags, NAICS codes, and natural language tags saved during onboarding, and shows the overlap behind the grade. You can add a tag or code to your preferences without leaving the page. And lead cards now carry enough — deadline, entity, budget, amended status, match strength — to triage a page without opening anything.
Why this is a different product
Why this is a different product
Discovery is the first problem, and it is a real one. State and local procurement is scattered across hundreds of portals that all behave differently, post on their own schedules, and share nothing with each other. Small firms lose here constantly — the work was posted somewhere they do not check, or they found it with nine days left and no time to write. That is where we started, and it is still the larger part of what we do.
But finding the RFP only gets you to the starting line. The second problem begins the moment you commit: is this opportunity still what I thought it was when I decided to pursue it?
Small firms lose there too, and more expensively. You commit under one set of assumptions and learn too late that they moved — the pricing form changed, the qualification hardened, the scope narrowed to something you cannot staff. Large competitors absorb that with staff whose job is monitoring portals. A three-person firm has no such person, and the cost is not just a lost bid but a week of unpaid proposal work.
Answering that second question means tracking what the government entity issues after publication and telling you plainly what moved. Not a link to a portal. Not a notification that something, somewhere, was updated. The specific change, what it affects, and when it happened.
One honest caveat: change tracking is in Beta while we widen coverage. Treat the changelog as a prompt to read the source document, not a replacement for it — and tell us when we miss something.
Check it out
Every week, we turn hundreds of messy government procurement documents into clear, actionable professional services RFP leads — from cities, counties, state agencies, tribal governments, and special districts across California, Washington, Oregon, and Idaho. Now we track what happens to them after they publish. See what's live right now on RFPGo.ai.
*Only the due date for this RFP was adjusted for illustrative purposes.
