Amendments are the real RFP
Why the third amendment usually contains the evaluation criterion that decides the bid, and what it means for how teams structure intake.
The original RFP is the document that gets the kickoff meeting. The third amendment is the document that decides the bid.
This is a pattern that shows up across federal, state, and large-enterprise procurements often enough that we treat it as a default rather than a special case. The original RFP is broad: scope, requirements, instructions, evaluation criteria. By the second amendment, the buyer has answered Q&A submissions from bidders and clarified the parts that were ambiguous. By the third — and sometimes the fourth — amendment, the buyer has revised the evaluation criteria to reflect what they’ve learned from talking to bidders.
That revision is where the bid is decided. The original eval criterion might say “technical approach: 30 points.” The third amendment might say “technical approach: 30 points, with at least 15 of those points reserved for proposed migration plan.” That weighting is the criterion the proposal team should be building toward, and most teams never re-read amendment three closely enough to catch it.
Why this happens
Buyers run RFPs to surface information they didn’t have when they wrote the document. Q&A surfaces vendor questions that reveal where the requirements were under-specified. Amendments incorporate the answers. By the third amendment, the buyer’s procurement team has a sharper view of what they actually want than they had when the procurement opened — and the amendment text reflects it.
The bidders who win disproportionately are the ones who treat amendment three as a re-read of the whole RFP, not as an addendum. The bidders who lose disproportionately are the ones who got their team writing on the first version and never restructured the response when the criteria moved.
What this means for intake
Three implications for how a proposal team should structure intake — and the eight-stage pipeline post covers the full intake discipline.
Treat amendments as first-class artifacts, not edits. Each amendment gets a document record, a date, a diff against the prior version, and a notification to the response team. A subsequent amendment that changes the evaluation criteria triggers a mandatory re-read with the capture lead before the next color-team review.
Run a diff on the criteria explicitly. Most amendment artifacts are PDFs that don’t visually flag changes. The VisibleThread analysis of government RFPs makes the point sharply: “rushing into writing without fully understanding the requirements” is the leading cause of failure, and amendments are where that understanding is most often invalidated. An automated diff that surfaces every changed sentence in the criteria section saves the team from missing the change.
Re-validate the compliance matrix on every amendment. Three of every four matrices we have audited at customer onboarding had at least one row that referenced a requirement the buyer had revised in a subsequent amendment. The matrix lagged the source. This is the highest-leverage check on intake hygiene.
The takeaway
Amendments aren’t supplements. They are revisions to the contract you are bidding under. The team that re-reads them is the team that wins the procurement that hinged on the change.