All insights
    PreconstructionOctober 19, 20268 min read

    How to Track Addenda During Bidding So Every Bid Prices the Same Documents

    Keep an addendum log, confirm acknowledgments, and catch proposals that price an outdated set before you level bids.

    Addenda are how the bid documents change while bidding is open. They revise drawings and specifications, answer bidder questions, adjust the bid form, and sometimes move the bid date. Each one is necessary. Together, they create a quiet risk: by bid day, different bidders may be pricing different versions of the same project.

    A low number that skipped the last addendum is not a low number. It is a different scope. Catching that before award depends on tracking addenda as carefully as the bids themselves.

    What an addendum can change

    An addendum can change almost anything the original documents established:

    - Revise, add, or delete drawing sheets - Change specification sections or add new ones - Answer bidder questions and clarify intent - Modify the bid form, alternates, allowances, or unit prices - Extend or confirm the bid date and time

    Some addenda are minor. Others change quantities, equipment, or sequencing enough to move price. The team needs to know which is which, and which bidders saw them.

    Keep an addendum log

    The addendum log is the single list of what changed and when. For each addendum, record:

    - Number and issue date - A short summary of what changed - Affected sheets, specification sections, and bid form items - The bidders and subcontractors it was distributed to, and how - Whether each recipient acknowledged it

    Keep the log next to the bid documents, not in someone's inbox. When the scope document is updated to reflect an addendum, note the addendum number beside the changed requirement so the history stays visible.

    Route questions into addenda

    During bidding, bidders ask questions. Answering them one at a time by phone or email feels efficient, but it gives one bidder information the others do not have. Collect questions, resolve them with the design team, and issue the answers to everyone, usually by addendum. Set a question cutoff far enough before bid day that the final answers can be issued and priced.

    Watch the late addenda

    The riskiest addendum is the one issued in the last few days before bids are due. Bidders may already have their sub-tier pricing, and a change at that point may not make it into every number. When a late addendum changes scope or quantities, consider whether the bid date needs to move, and say so in the addendum itself.

    Require acknowledgment, then check it

    Most bid forms ask bidders to acknowledge each addendum by number. That acknowledgment is only useful if someone checks it against the log. When proposals arrive, confirm for every bidder:

    1. Which addenda the proposal acknowledges or references. 2. Whether that list matches the full log. 3. Whether the proposal language reflects the changes, not just the numbers.

    A proposal that acknowledges Addenda 1 through 3 when Addendum 4 was issued needs a question before it is leveled: did the bidder price Addendum 4, and does the number change?

    Make addenda part of the scope you level against

    Treat "price all issued addenda" as a scope requirement like any other, with its source and the list of addenda it covers. Then every proposal is checked against it during leveling, instead of the check happening informally, if at all. When an addendum changes a specific scope item, update that requirement too, so the comparison reflects the current documents rather than the original ones.

    How Mobus helps catch an outdated set

    Mobus Bid Leveling reads each proposal separately against the same cited scope requirements, so an addenda requirement in the scope becomes a line every bidder is checked against. A proposal that cites Addenda 1 through 3 when the scope requires 1 through 4 surfaces as a finding, with the proposal quote and cited page beside the scope language that requires the full set.

    Mobus also drafts the follow-up, such as asking the bidder to confirm that pricing incorporates Addendum 4 and to identify any price change. The draft stays editable, and the estimator decides what is sent and how the finding is resolved.

    A bid-day addenda routine

    - Freeze the addendum log at the question cutoff and confirm distribution. - Add the full addenda list to the scope requirements. - Check every proposal's acknowledgment against the log. - Send clarification questions for any gap before leveling the numbers. - Record each answer with the bid, so the award record shows which documents every price was based on.

    Related guides