A change, not a new job
An addendum that reached the folder but not the person doing pricing is a silent scope change. The original set was already read. Quantities may already exist. Vendor RFQs may already be out. Then a new PDF arrives that moves the close, revises a schedule, or adds a mandatory meeting, and the only system that knows is the file’s modified date.
ArosBid keeps an inbound log on the pursuit. Each addendum is read against what was already cited and already priced. A late package is a change to this job. It is not a second project you start from a blank page if you have time.
This is not a second essay about eligibility
The field note The line that disqualifies the bid is about a class of sentence that lives in the front end: mandatory attendance, prequalification, bonding thresholds. Those clauses can arrive in the original set or by addendum. The essay explains why they hide. This page does not retell that essay.
This page is the log. Addendum 1 received and read. Addendum 2 received and read. Addendum 3 sitting on the tray with a warning because the HVAC specification changed and the estimate did not. The supporting essay is linked because estimators search both problems. They are not the same page.
Dates move. Scope moves. The bid form asks.
A close date that moved by a week can save you or sink you, depending on whether you noticed. A new pre-bid can disqualify you the same way the original invitation never mentioned. A revised equipment schedule can make every vendor quote you already collected apply to the wrong machine. None of that is subtle. It is just easy to miss when the addendum lands in the same pile as twenty-eight other files.
Acknowledging addenda is usually a condition of a responsive bid. Readiness in ArosBid treats the list as a gate: bonding, addenda, alternates, recorded approvals. You still fill in the bid form. The product’s job is to make “we received Addenda 1 through 3” a statement you can defend, not a guess.
The same workspace as the rest of the bid
Document review cites the original set, front end included. That is AI tender review. Bid/no-bid can refuse to spend more hours if the log is incomplete. Vendor RFQs should not go out on a superseded package. Leveling should not compare quotes written against two different addenda as if they were the same job. Takeoff and estimate are in the product and replace Trimble AutoBid. The addenda log is why those quantities stay attached to the set that is actually current.
Isolated instance. Microsoft Entra ID. During training, nothing leaves without a recorded human approval, including a calendar invite drafted because an addendum moved a meeting. Named pursuits on this site, including Riverside Office Tower in the walkthrough, are fictional and labeled as such.
