A practical change-control method for tracking RFP addenda, updating affected response work, completing acknowledgments, and establishing a new baseline.
Track an RFP addendum as a controlled change to the solicitation, not as another file in a folder. Capture it from the official source, record its number and date, compare the changed language with the prior version, and classify every impact: deadline, scope, evaluation, pricing, form, contract term, or submission instruction. Then update the affected compliance rows and response files, assign owners, complete any acknowledgment the buyer requires, and establish a new document-set baseline. Unchanged solicitation terms still matter, so the work is not complete when the addendum has been read. It is complete when every affected response decision and artifact has been reconciled.
An addendum or amendment is the buyer's formal method for changing or clarifying a solicitation. Terminology varies by jurisdiction and procurement method, but the operational rule is consistent: use the official issued document and follow its instructions.
For federal negotiated acquisitions, FAR 15.206 says the contracting officer amends the solicitation when the government changes its requirements or terms and conditions. It also identifies information an amendment should contain, including its number, a description of the change, and a revised closing date when applicable. (Acquisition.gov — FAR 15.206)
FAR 52.215-1 adds an important point for offerors: terms not amended remain unchanged, and receipt of amendments must be acknowledged by the date and time specified. (Acquisition.gov — FAR 52.215-1) State and local rules can differ, so apply the language in the solicitation and governing portal rather than importing the federal process.
A reliable tracker records both the change and its downstream effect. A filename such as Addendum_3.pdf does not show whether pricing, a form, and the deadline all changed.
| Field | What to record | Why it matters |
|---|---|---|
| Addendum identity | Number, issue date, official URL, downloaded filename | Establishes provenance and sequence |
| Changed citation | Document, page, section, or attachment | Lets reviewers verify the change |
| Before and after | Concise old and new requirement | Prevents vague interpretations |
| Impact type | Date, scope, evaluation, price, form, term, or submission | Routes the change to the right workstream |
| Affected artifacts | Matrix rows, narrative sections, forms, estimate, package files | Shows what may now be stale |
| Owner and due date | Named person and internal completion date | Turns analysis into action |
| Acknowledgment | Required method, signer, status, evidence | Prevents acknowledgment from becoming an afterthought |
| Verification | Reviewer, date, and new baseline version | Closes the change-control loop |
Download the addendum from the agency portal or official posting. Record the source URL and download time. Do not treat a forwarded copy as authoritative until it matches the official document.
Washington explains that solicitation changes are posted in WEBS. Vendors who download the original solicitation receive amendment notices, but bidders are also told to check WEBS frequently. (Washington Department of Enterprise Services) Build a monitoring routine instead of relying on one inbox.
Check the addendum number, page count, referenced solicitation, attachments, and any replacement files. Determine whether you have all preceding addenda. A later addendum may refer to an earlier change without restating it.
Add the new document to the state and local RFP response checklist, but preserve prior versions. A controlled history is more useful than overwriting the original file.
Read the addendum itself before using an automated comparison. Record what it adds, deletes, replaces, or clarifies. Pay special attention to:
Official questions and answers may also be delivered through an addendum. Oregon states that oral comments during a pre-proposal conference are not binding unless confirmed in a written addendum posted through OregonBuys. (Oregon Procurement Manual)
Do not stop at "reviewed." For each change, decide which response objects are affected. A revised scope paragraph may change the technical approach, staffing, schedule, subcontractor plan, and price. A new form may change both the package manifest and signature plan.
Use three simple states:
Revise the compliance matrix with the new source citation and version. Reopen affected assignments, update the response outline, and replace buyer-issued templates rather than copying values into an old version. If the addendum changes evaluation criteria or response organization, revisit the guidance in following the buyer's response format.
Keep a brief decision note when a team concludes that a change has no response impact. That record is more useful than an unchecked box if the issue returns during final review.
Follow the addendum's exact acknowledgment method. It may call for a signed page, a portal action, a form entry, or another method. Washington says that when required, bidders must sign and return each amendment before the bid due date. That wording is deliberately conditional: not every addendum in every jurisdiction requires the same action. (Washington Department of Enterprise Services)
A historical GAO decision involving a material federal amendment found rejection proper when the bidder's acknowledgment was not received. It illustrates the potential consequence, but it is not a rule that every missing acknowledgment in every procurement is automatically fatal. (GAO B-212039)
Give the updated document set a new version. Confirm that each affected artifact is revised, re-approved, or explicitly queued for review. Then run the final package review against the new baseline—not against the original solicitation.
The baseline record should show:
Someone circulates the addendum, but no requirement, estimate, or response file changes status. Replace "FYI" distribution with named impact ownership.
The matrix changes, but the narrative, pricing workbook, or form remains old. The tracker must point to the affected artifacts and confirm their current versions.
Email filtering, incorrect portal profiles, or missed commodity codes can interrupt notices. Use the monitoring process recommended by the relevant portal.
A signed addendum does not prove the response incorporates the change. Acknowledgment and implementation are separate controls.
GreenLight tracks document-set versions and can surface response artifacts that need review after the solicitation set changes. Its package inventory can also include detected addendum-acknowledgment items, supporting a later submission-ready check.
GreenLight does not decide whether a particular amendment legally requires a signature or acknowledgment. Automated comparisons also do not replace review of the official addendum. Users remain responsible for confirming the impact, current files, and buyer-specific instructions. Book a 15-minute call to discuss a more controlled bid-readiness workflow.
No. The acknowledgment method depends on the solicitation, addendum, portal, and applicable procurement rules. Follow the exact issued instructions and record evidence of the required action.
Usually, no. Preserve the original and every addendum as a controlled document set unless the buyer explicitly issues a complete replacement. Unchanged original terms may remain in effect.
Update the authoritative calendar, internal milestones, acknowledgment due date, portal plan, and every document that states the old date. Still review the rest of the addendum; a deadline change may not be its only change.
See how GreenLight helps your team qualify the opportunity, organize the buyer's requirements, and check the package before you submit it.