Addenda acknowledgment log: know which bidder has which revision

Identify the exact issue before distribution

Record the project, bid package, approved addendum ID, issue date, source documents and the person authorizing distribution. A filename such as latest update is difficult to match to a later response. Preserve a stable reference that the estimator and bidder can use when discussing the same issue.

Confirm the package's actual document-control and bid instructions. An internal draft, clarification question and issued addendum can have different statuses. Do not distribute an unapproved change as though it were the current bid basis merely because it arrived in an inbox. Route uncertainty to the person who owns the package.

Keep the issue contents and any stated deadline or scope changes connected to the reference. A brief email summary can help explain the request, but it should not replace or broaden the controlled issue. The bidder needs access to the actual documents and a clear route for questions the summary does not answer.

Use a bidder roster with contact and scope context

Identify the invited company, relevant scope, responsible contact and approved channel. One company can have several contacts or price several scopes. Decide how the register counts a bidder and which contact can confirm the requested basis. Two email addresses should not automatically become two independent bids in a coverage summary.

Keep contact changes traceable. If a company asks that its estimator replace an earlier recipient, link the referral and confirm the new route. Do not assume the replacement received every earlier issue. The handover should identify the package and issues still needing access or acknowledgment.

Preserve declined or withdrawn intent with its source and the estimator's outreach decision. A bidder's decline is different from a failed email or unanswered call. Use the approved process to determine further contact rather than treating every unresolved document status as permission for another automated reminder.

Record what was sent and through which source

Capture the issue version, distribution time, recipients, channel and the actual message or transmittal reference. If a document link changes, retain which link the recipient received. A later successful link does not explain an earlier failed access request unless the two events are connected.

A sent message is a transport event. Delivery or open signals, where available, can help diagnose routing but do not establish that the bidder reviewed the issue. Keep those signals in their own fields instead of automatically marking acknowledged. The acknowledgment should have the response basis required by the actual process.

If the approved distribution list changes, identify the added recipients and relevant issues they need. Reconcile the roster against the issue rather than relying on an old email group. The estimator should be able to identify who has not yet received the current basis without assuming the original invite list stayed correct throughout the bid period.

Resolve access problems before chasing acknowledgment

When a bidder reports an inaccessible link, wrong permission or missing attachment, record that specific problem and route it to the document or bid-platform owner. Repeating please acknowledge does not solve a file the recipient cannot open. Keep access unresolved until the appropriate confirmation arrives.

Use the authorized sharing route and access rules. Do not bypass restrictions by forwarding sensitive project documents through an unapproved personal channel. If the bidder's normal contact changes, confirm the recipient and permissions through the process before treating a successful send as a complete handoff.

Preserve the access correction and the bidder's response separately. A platform owner can fix permissions while the bidder still needs to confirm receipt or review. Conversely, a bidder may acknowledge receiving a notice while explaining that the actual drawings remain inaccessible. The register should retain both facts.

Ask for an explicit, issue-specific response

A starting request is: For [project/package], please confirm receipt and access to addendum [ID/version] issued [date]. Identify any missing or inaccessible document. Please also tell us whether your proposal [reference, if known] addresses this issue or whether revised pricing or a clarification remains pending. Send questions through [approved route] by [actual checkpoint].

Keep receipt acknowledgment and pricing coverage as separate answers. A bidder can truthfully say it received addendum 3 while still reviewing the change's effect on its price. Do not convert that answer into a statement that the quote includes every revised requirement. The estimator needs the actual proposal basis or specific clarification source.

If the response simply says yes after several questions, clarify what it confirms. Preserve the original response and the follow-up. An explicit answer to addendum 2 should remain against that issue; it does not automatically acknowledge addendum 3 merely because both are discussed in the same thread.

Link the issue to the submitted proposal revision

Identify the current proposal reference, date and stated document basis. Ask the bidder about a mismatch or omission rather than rewriting its quote. A revised price may incorporate an addendum, retain earlier qualifications or introduce a new exclusion. Keep the actual source so the estimator can assess what changed.

Procore's official submitted-bid guidance notes that changed drawings, specifications or addenda can require a bid update. That is a product-specific context for connecting document issues to proposal revisions. This guide does not prescribe a platform deadline exception or decide whether a particular proposal satisfies a tender's requirements.

Record a proposal revision received separately from the estimator's review of its coverage. A new PDF arriving is progress, but it may still need clarification. The acknowledgment log can point to that question without pretending to perform the bid evaluation or infer a complete scope from the file's name.

Sources: Procore: Update a Submitted Bid

Worked example: four bidders, different next actions

The following package, bidders and dates are fictional. Cedar package BP-6 has an approved addendum 3 and a stated bid checkpoint of November 20, 2026, at 3:00 p.m. local time. Four invited companies appear in the review roster. The exercise counts companies, not individual email recipients.

Bidder A confirms access to addendum 3 and supplies proposal revision 2 with the stated issue basis. Bidder B confirms receipt but says pricing is still being reviewed. Bidder C reports an inaccessible document link and has not confirmed the issue. Bidder D declines to bid; the estimator records the outreach disposition under the package process.

At this checkpoint, two of the four companies have explicit issue-receipt acknowledgments, while only A has supplied the stated revised-pricing source. That is not a finding that A is qualified, responsive or awardable. The immediate actions differ: review A's proposal, follow B's pricing checkpoint, fix C's access and follow the recorded disposition for D.

Reopen the affected response when another issue arrives

When addendum 4 is approved, create its own issue-to-bidder records. Preserve addendum 3's acknowledgments and proposal references as history. A's earlier response may be useful context, but it does not establish that A received or priced the new issue. Keep the new request and response identifiable.

Ask the estimator which recipients and scopes are affected under the approved process. A change may concern one package or several. Do not silently narrow distribution based on a coordinator's interpretation of a technical revision, and do not tell unaffected bidders they must change a price without the authorized direction.

If a bidder says the new issue has no price effect, retain that statement and the proposal reference it applies to. The estimator still needs to review the actual basis. No price change is different from no response, just as an acknowledgment is different from an accepted commercial amendment.

Keep deadline and clarification decisions with the estimator

An issue arriving near the bid checkpoint can create questions about pricing time, access or the required submission basis. Record the question and route it promptly to the package owner. A coordinator should not invent an extension, declare a late response acceptable or promise that an unanswered issue will be waived.

Where the authorized process changes a deadline or instruction, preserve the decision source and distribute the approved update to the intended recipients. Track acknowledgment of that change as its own relevant information. Do not change the date in a spreadsheet and assume every bidder has seen the replacement instruction.

Keep clarification questions connected to the package's approved answer route. An estimator may need to issue a common clarification rather than provide private, inconsistent scope guidance. The log should show which question remains open and who owns the next decision without substituting an administrative status for a procurement ruling.

Summarize the evidence rather than one green percentage

A useful summary separates invited companies, issue acknowledgment, access problems, proposal revisions received and unresolved pricing questions. State the checkpoint and denominator. In the fictional roster, two acknowledgments out of four invited companies is 50%, but that figure does not describe bid coverage, reviewed scope completeness or award readiness.

If the team also reports active bidders after D's decline, define that denominator separately. Do not silently change from four invited to three active companies and compare the resulting percentage as though the population were unchanged. Keep the roster disposition source so another reviewer can reconstruct the summary.

Show the next actions beside the counts. One access problem may need the platform owner, while a pricing question needs the bidder and estimator. A single missing acknowledgment status can hide those different causes. The objective is a clear action list grounded in evidence, not a dashboard that makes all unresolved cases look alike.

Use the issue-to-bidder register

The free blank CSV includes project, package and revision, approved issue ID, source and distribution authority, bidder company, scope, current contact, distribution reference, transport state, access question, explicit acknowledgment source, proposal revision and issue basis, pricing state, estimator review, next owner and checkpoint. Use one row per issue and bidder relationship.

Populate BP-6 and check that B's receipt acknowledgment does not become confirmed pricing coverage. Fix C's fictional link and record a separate response. Add a second contact for A without counting another company. Then issue addendum 4 and preserve the earlier states while the new responses remain open.

Pilot one package with the estimator and bid coordinator. Ask them to identify who needs documents, who needs a pricing follow-up and which questions require a common answer. Clarify those distinctions before sending a larger automated sequence or presenting a summary to the bid-review team.

Track approved addenda follow-up with Buildalytic

Buildalytic's subcontractor-bid-follow-up page describes sending approved addenda, confirming document receipt, logging intent and routing unresolved questions to the estimator. Bring a redacted BP-6-style roster to a demo. Ask how each issue and bidder response stays connected to the current package basis.

Confirm the approved outreach wording, channels, contact windows and stop rules for the deployment. Keep pricing interpretation, deadline decisions, bid evaluation and award with the estimating and commercial team. Do not assume a receipt-confirmation workflow independently verifies every proposal's compliance or guarantees complete bid coverage.

Use the example to inspect a received-but-unpriced issue, an access failure and a declined bidder as different paths. A useful walkthrough shows the next owner when a response remains unresolved. The fictional roster does not claim actual acknowledgments, a bid-coverage improvement or a customer award result.

Sources: Buildalytic subcontractor bid solicitation and follow-up