Updated October 23, 2026. The September example has closed, so this version follows one that is still active, and adds what we've shipped since.
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 that is active right now.
The Oregon Employment Department (OED) wants a cloud-based Enterprise Service Management system to replace an IT ticketing platform that runs as two unsupported instances it can no longer patch. The RFP was published August 26 with proposals due October 15. If you found it that week and decided to bid, you had a clear picture of the work.
Then OED issued seven addenda.
On September 24, Addendum 1 replaced the vendor evaluation workbook and told proposers to submit only the revised one. On October 2, OED published its answers to bidders' questions alongside Addendum 2, which revised the cost proposal form and took data migration out of the one-time costs. On October 8, Addendum 3 moved the deadline to November 6 and closed a door: only the software maker itself could implement the system. A systems integrator that wasn't the maker was ineligible, as prime or as subcontractor.
Two weeks later, Addendum 5 reopened it. Integrators, authorized partners and other qualified third parties can implement after all. A day later, Addendum 6 rewrote the scoring: implementation went from 50 points to 150, each of the six core criteria dropped from 150 to 125, and a new organizational change management criterion appeared at 50. Addendum 7 moved the deadline again, to November 16.
If you were an integrator who read Addendum 3 and walked away, you spent two weeks out of a contest you're now allowed to enter, and the part of the proposal you'd write has tripled in weight. If the only thing you were tracking was the due date, you saw it move twice and missed both changes that decided whether you could bid and how you'd be scored.
That gap, between when an opportunity is published and when it is actually understood, is what these features are built for.
Before: one live RFP as it actually reaches you. After: the same RFP on one RFPGo.ai page, 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.
Oregon is not an outlier. More than one in five government RFPs we followed changed their terms before the deadline, and the first change typically landed well into the bidding window, when many businesses are already writing.
Every lead 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. Oregon's reads October 23. A dash means nothing has moved yet. On a normal active leads page, a date isn't the exception.
What's on every lead
1. Changes since published
Every lead carries its own changelog. Each entry shows the date, the addendum, and what it touched, labeled Deadline, Eligibility, Scope/requirements, Documents, Q&A and so on, with a summary of what changed, not only that something did. When a deadline moves, the lead says so up top: Oregon's reads "Deadline moved 2× · latest was Nov 6 → now Nov 16."
Oregon's changelog has nine entries. Two are deadline moves. The two that matter most, Addendum 3 and Addendum 5, are labeled Eligibility, which is how you find the one that let you back in.
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 · Oct 22."
That settles a question businesses usually cannot answer without re-downloading everything: is my copy still current? For the Oregon RFP, anyone holding the original package is holding a superseded evaluation workbook and a superseded cost form.
3. What others asked
Every lead with published answers shows them in full, sorted by what each answer affects. Above roughly thirty questions, the list opens to the ones capable of changing a bid decision.
Oregon has answered 256. Some are administrative. Some settle the scope: post-go-live support, user counts, whether OED runs the ITIL framework today. And some get corrected. One of OED's answers on offshore support read, in full, "See Question #" with no number. Addendum 4 fixed it: staff in the United States must perform all support, and OED is not entertaining exceptions.
None of that is in the RFP. All of it is binding.
4. Saved RFPs show what landed since you saved them
Your bookmarks and lead cards mark when a government entity has answered something since you saved the opportunity, so the RFPs you've committed to show what's new the next time you open them.
5. Who can bid, before you read the whole thing
Minimum qualifications, insurance limits and preference programs usually sit deep in the solicitation. Every lead now shows them near the top: Who can bid (the requirements you must be able to show, insurance included), Where you'd have an edge (the preference programs the RFP names, if any, and whether they're scored), Who to ask, and the pre-bid conference and the deadline for questions.
Also on every lead
Every lead in Matched to you is graded Strong, Good, or Partial against the NAICS codes and natural language tags saved during onboarding, and shows the overlap behind the grade. You can filter to one grade at a time, each with a count, so you can start a short week with the Strong matches. You can add a tag or code to your preferences without leaving the page. And lead cards carry enough — deadline, entity, budget, amended status, match strength — to triage a page without opening anything.
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 scoring shifted toward work you didn't plan to emphasize. Or, as in Oregon, you rule yourself out and never learn the door reopened. Large competitors absorb that with staff whose job is monitoring portals. A three-person firm has no such person, and the cost isn't just a lost bid; it's a week of unpaid proposal work, or a contract you never knew you could pursue.
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 vague "this RFP was updated." The specific change, what it affects, and when it happened.
One honest caveat: treat the changelog as a prompt on how to review the source document with context.
Check it out
Every week, we turn hundreds of messy government procurement documents into clear, actionable professional-service RFP leads — from cities, counties, state agencies, tribal governments, and special districts across California, Washington, Oregon, and Idaho. Then we keep tracking what happens to them after they publish. See what's live right now on RFPGo.ai.
