Addenda acknowledgment and impact drafting

The job

The estimator at a US general contractor doing about $5–10M a year — often the owner wearing an estimator hat, or one person who also takes off drawings, levels subs, writes proposals, and walks jobs. There is no bid coordinator and no document-control clerk. Mid-bid, Addendum 2 arrives as a 40-page PDF at 4 p.m. the day before bids are due. Someone has to open it, figure out which sheets and spec sections changed, decide what that does to the takeoff, the sub quotes, and the proposal package, and still put the right Addendum numbers on the bid form. If that pass is skipped, you submit a non-responsive package or a number that never saw the last sheet. If a fluent AI draft invents “Addendum 4 acknowledged” or “no cost impact,” you have worse than a missed addendum — you have a record that looks official and is wrong.

This job is use an agent, not build a model. The estimator already has a desk: the invitation / advertisement, the Instructions to Bidders (often AIA A701–2018), every Addendum PDF actually received (or a G804 / own register listing them), a takeoff summary, a leveled-quote sheet, scope-gap notes, a draft proposal or bid-form checklist, Word/Excel/PDF, and email. The agent sits in the extract-and-draft step only. It does not decide whether an Addendum applies. It does not revise a quantity. It does not revise a price. It does not claim “no cost impact” as fact. It does not check the acknowledgment box on the bid form. It does not submit.

Without an agent the work is still the same: open each Addendum, list what it says changed (drawing number, spec section, date, bid-date extension), walk those changes against the takeoff and the quotes and the proposal sections you already own, decide incorporate / question / live-with-it, fill the bid-form acknowledgment with only the Addenda you actually received, then submit under the Instructions.

What this job is, and what it is not. This page is the mid-bid addenda acknowledgment + impact log — which Addendum, what changed, which takeoff lines / quotes / proposal sections may need a human re-check. Sister estimator jobs produce numbers, holes, and the outbound package; they do not replace this seat when a new Addendum lands.

• The measure step is quantity takeoff — SF, LF, and EA from drawings. This page may flag takeoff rows that may need re-measure after an Addendum; it does not re-measure.
• The sister compare step is bid-leveling — lining up unlike sub quotes against each other. This page may flag trades whose quotes may need a re-ask after an Addendum; it does not re-level.
• The sister document walk is scope-gap review against specs — takeoff and quotes against specs and drawings, flag holes. This page tracks what the Addendum changed and which prior holes / decisions may need another look; it is not a full re-walk of the project manual.
• The sister outbound package is first-pass bid proposal drafting — cover letter, inclusions/exclusions, proposal narrative. This page feeds the addenda list and owned impact decisions into that package; it does not write the cover letter.
• A construction-phase RFI, ASI, or change order is a different seat after award. Bidding uses A701 clarification and addenda. Do not rewrite those pages.

What A701 actually says about Addenda. Official A701–2018 summary: used when competitive bids are solicited; Instructions to Bidders inform Bidders how to obtain documents; how to submit requests for clarification, interpretation, and substitutions; how addenda will be transmitted; and how to submit Bids. Coordinated with A201; information from G612–2017 Part B (Bidding Procedures) should be used to complete A701. Official change note for § 1.3: the definition of Addenda clarifies that these written or graphic instruments, which are part of the Proposed Contract Documents, are issued prior to the date for receipt of Bids — not prior to execution of the Contract. Official instructions: § 3.2.2 fill-in for the form of clarification/interpretation requests; § 3.4.1 fill-in for the form in which Addenda will be transmitted to Bidders; § 4.3.1 form in which a Bidder shall submit its Bid; Article 8 enumerates the Proposed Contract Documents. Practical point: the project’s Instructions / bid form tell you how to acknowledge Addenda. The agent may list Addenda present in the upload and draft an acknowledgment sentence that matches that list. It must not invent Addendum 4 because “projects usually have four.”

Addenda on the bid form are a human check, not a model memory. Missing an Addendum on the bid form is how you submit a non-responsive package or a number that never saw the last sheet. Official G804–2001 (forms overview): Register of Bid Documents — a log of documents issued to bidders during bidding; tracks documents issued, deposits received, and documents and deposits returned; useful as a single point of reference when parties call for information during bidding. Use G804 (or your own register) as the source of truth for what you received; do not let the model invent the register.

Bidding documents vs Contract Documents — why acknowledgment still matters. Official A201–2017 § 1.1.1: the Contract Documents include Addenda issued prior to execution of the Contract. Unless specifically enumerated in the Agreement, they do not include the advertisement or invitation to bid, Instructions to Bidders, sample forms, other information furnished by the Owner in anticipation of receiving bids or proposals, the Contractor’s bid or proposal, or portions of Addenda relating to bidding or proposal requirements. Practical point for this job: you still acknowledge every Addendum the Instructions require on the bid form, and you still decide what each Addendum does to your number — even when some Addendum portions are bidding-only instruments under § 1.1.1. After award, complementary documents under § 1.2.1 still bind. An agent-drafted “no impact” line does not become a Modification.

Where Division 00 parks Addenda (verified numbering language). CSI MasterFormat 2026 is the current North American numbering; Division 00 remains Procurement and Contracting Requirements. A published MasterFormat 2018 numbers listing (AGC Austin PDF) indexes 00 91 00 – Modifications to Bidding Documents, 00 91 13 – Addenda, and 00 91 16 – Bid Modifications / Bid Revisions. MasterFormat is numbering language, not an acknowledgment form. Your invitation, Instructions to Bidders, bid form, and Division 00 win. Kevin O’Beirne on CSI (Part 2, 2025): procurement-stage questions are usually email; if a response binds, it goes by Addendum; informal Q&A documents can undermine duly prepared Addenda. Do not invent a bidder-question clock or treat an email reply as an Addendum the model “found.”

Parallel-family citation only. ConsensusDocs 270 (private) and 271 (public) are parallel-family bidder instructions; the 270 public page notes that the form explains how clarifications or additional information will be issued. Citation only — your project’s Instructions win.

Why a $5–10M GC still does this. There is one estimator. Addenda stack late. The bid form still asks which Addenda you received. Without a first-pass impact log forced to cite the uploaded PDFs — drawing numbers, revision dates, spec sections as stated in the Addendum — the acknowledgment gets filled from memory and the takeoff never gets the last sheet. Expected shape of the gain: a complete acknowledgment checklist plus a structured “may need re-check” log that a human can walk before submit. There is no published, independent hours-saved or accuracy number for a $5–10M GC addenda-tracking agent that this page will invent. Time one of your bids (run the log with and without the agent) before you change anything you pay for.

Use

This is a use workflow. You do not train a model. You do not ask it to invent an Addendum number, invent “no cost impact,” revise a quantity, revise a price, or check the bid-form acknowledgment box. You give it the Addenda you actually have, the invitation / Instructions, and the summaries you already own; you get a draft acknowledgment checklist and impact log; you own every incorporate-or-not call and the submit.

1. Keep a register of what you actually received. Invitation / advertisement; Instructions to Bidders (A701 or the project’s form); the bid form the project named (especially the Addenda acknowledgment lines); every Addendum PDF you downloaded (or a G804 / your register listing them). Official A701: how addenda are transmitted (§ 3.4.1 fill-in), how clarifications work (§ 3.2.2), how to submit Bids (§ 4.3.1). If Addendum 3 is not in the folder, it is not in the draft.
2. Export the upstream summaries the impact log will point at. Takeoff summary, bid-leveling export, scope-gap decision log, and any draft bid proposal outline or bid-form checklist. Excel is fine. Do not ask the addenda agent to re-measure, re-level, re-walk the whole manual, or write the cover letter.
3. Feed the agent only those files. Prompt shape: draft (a) an acknowledgment checklist listing Addenda only from the upload / register, (b) an impact log with one row per stated change in each Addendum (Addendum number, stated drawing/spec/date/revision as printed in the PDF, short quote of the change language, linked takeoff row / quote trade / proposal section if present in the upload, flag may need human re-check — never “no cost impact” as fact), (c) a short “questions still open” list if the Addendum tells you to acknowledge receipt of something you do not have. Every factual claim cites the upload. If a required fact is not in the upload, say “not in the uploaded files.” Footer: do not submit — estimator owns which addenda apply, every incorporate-or-not call, every price/quantity revision, bid-form acknowledgment, and the submit.
4. Human walks the impact log against the documents — not against the model’s confidence. Open each flagged drawing and spec section. Decide incorporate / re-ask the sub / question by the Instructions’ clarification path / live with it. Revise quantities and prices yourself (or send the human-owned re-ask). Strike invented Addenda. Strike any row that says “no cost impact” unless you decided that after opening the sheet.
5. Fill the bid-form acknowledgment yourself. Copy only the Addendum numbers present in your register onto the form (or the project’s required checkbox / blank). Do not attach the raw AI transcript to the Owner.
6. Feed owned decisions downstream. Update the takeoff, the leveled sheet, the scope-gap log, and the proposal package with decisions you made. The agent drafts the log; it does not become the Bid.
7. Submit is human. Name, date, signature / electronic submit under the Instructions. The agent does not click send on the portal and does not drop the sealed envelope.
8. Log the way you already do. Keep the edited Excel/Word impact log with the bid file, plus the addenda register (G804 or your sheet). Do not stand up a new vendor for this job.

Expected shape of the gain: a first-pass acknowledgment + impact log that matches the uploaded Addenda, so late Addendum day is decide-and-revise rather than invent-from-memory. That is not “the model incorporated the Addendum.” There is no published, independent hours-saved or accuracy number for a $5–10M GC addenda-tracking agent. Time one of your bids before you change anything you pay for.

Build

A general-purpose model that can read PDFs and spreadsheets can draft an acknowledgment checklist and a structured impact log from uploaded Addendum PDFs plus estimator-owned summaries. Whether an Addendum was received, whether a drawing change hits your takeoff, whether a quote needs a re-ask, whether “no cost impact” is true, and whether the bid-form acknowledgment is complete, need a person. Do not treat the draft as the Bid, and do not let it invent commercial conclusions.

A workable v1: a prompt template that returns three artifacts — (1) acknowledgment checklist (Addendum number, date as printed, transmission note if stated, “present in upload” / “not in the uploaded files”), (2) impact log table (Addendum #, stated change citation, drawing/spec/date as printed, linked takeoff/quote/proposal pointer or “no matching row in upload,” flag may need human re-check, human decision blank: incorporate / re-ask / question / live-with / N/A), (3) open-items list (missing sheets the Addendum references, clarification deadlines stated in the Instructions, bid-date changes as printed) — plus a footer on every artifact: do not submit; estimator owns which addenda apply, every incorporate-or-not call, every price/quantity revision, bid-form acknowledgment, and the submit. Forbid the phrases “no cost impact,” “no schedule impact,” and “fully incorporated” unless the human typed them into an owned note. Require “not in the uploaded files” instead of guessing. Keep the transcript with the bid file.

Do not build a custom classifier this quarter. Do not fine-tune. Do not build a “bid board.” This Addenda stack and these owned summaries are the only corpus that matters.

Deploy

1. Pick a recently submitted bid you still stand behind — one where an Addendum landed late, plus one where an acknowledgment line was almost missed.
2. Run the agent on the same invitation + Instructions + bid form + Addenda PDFs + takeoff summary + leveled export + scope-gap / proposal notes (no later award emails in the upload). Time upload, draft, and your edit.
3. Diff the draft against what you actually acknowledged and revised. Record invented Addenda, invented “no impact” claims, drawing/spec citations that are not in the PDF, missed revision dates that are in the PDF, and any row that quietly revised a quantity or price.
4. Decide using a rule set in advance: no package leaves the laptop with an unedited impact log; every Addendum listed must exist in the upload or register; every “may need re-check” flag gets a human decision before submit; if the model invents an Addendum, invents “no cost impact,” or fills a revised dollar amount you did not give it, it is not ready.

Use your project’s bid form and real Addendum PDFs, not a vendor demo set. Keep the workflow only if the acknowledgment you would still sign is still something you would put your name on.

Manage

What “good” looks like

• A named human owns which addenda apply, every incorporate-or-not call, every price/quantity revision, the bid-form acknowledgment, and the submit. Raw model text is never the Bid and never the portal upload.
• The upload includes the invitation, Instructions, bid form, and Addenda actually received (or a G804 / register). Memory of “the last job’s addenda” is not a search.
• Takeoff, bid-leveling, scope-gap, and bid-proposal remain sister seats. This job drafts the mid-bid acknowledgment + impact log. All five can be true on the same bid day.
• Impact rows flag may need re-check. They do not assert “no cost impact” as fact. Revised dollars and quantities are human-owned.
• Acknowledgment on the bid form matches the register. A701 § 3.4.1 transmission method and the project’s form of Bid (§ 4.3.1) win.
• If you already have a takeoff, leveling, or document app, the agent reads an export. This page does not sell a new one.

Who owns the seat

The estimator / owner-estimator owns the Addenda acknowledgment and every incorporate-or-not call. On a $5–10M GC that is one person and the laptop they already use. The architect / owner owns the bidding procedures (G612 Part B → A701) and issues the Addenda. An agent does not become the Bidder’s representation that it examined the Bidding Documents, and it does not become the submit.

When to skip the agent (what not to automate)

• You have not downloaded the Addendum or opened the Instructions. Search first. The model cannot acknowledge a PDF you never received.
• You expected the model to decide “no cost impact,” revise the takeoff, re-price a trade, or check the bid-form box. Wrong job.
• You expected it to re-do takeoff, re-level quotes, walk the whole spec for holes, or write the cover letter. Those are quantity takeoff, bid-leveling, scope-gap, and bid-proposal.
• A negotiated package where Part B / A701 was never the path (G612 instructions: if Contractors are selected by negotiation, Part B need not be completed). Different path; do not force an A701-shaped acknowledgment onto a negotiation.
• Life-safety, structural, or code changes in an Addendum you have not opened yourself. Flag; do not let the model close them as “no impact.”
• The Addenda stack is already one short sheet and acknowledgment is not the bottleneck. Leave it.

How to stand it up this quarter

Use the model you already have access to. Drop in last bid’s invitation, Instructions, bid form, Addenda PDFs, takeoff summary, leveled export, and proposal notes. Edit the impact log. Click every Addendum citation. Own every incorporate-or-not call. Fill the acknowledgment yourself. Submit only the human-edited package. Repeat on a live bid. Keep the workflow only if the signed Bid is still something you would put your name on. Do not buy a bid-board, document-AI, or takeoff product to complete this job.

Citations

Tools are citations, not new brand pages. Do not invent vendor homepages. This page does not create a Procore, Autodesk, BuildingConnected, Bid Board, STACK, or other bidding-vendor listing.

• AIA A701–2018 — official Instructions to Bidders. How to obtain documents; clarification, interpretation, and substitutions; how addenda are transmitted; how to submit Bids. § 1.3 Addenda issued prior to receipt of Bids. Instructions: § 3.2.2 / § 3.4.1 / § 4.3.1 fill-ins; Article 8 enumeration. FAQs: public or private; electronic and paper. Catalog: A701.
• AIA A201–2017 — keystone general conditions. Official preview: § 1.1.1 Contract Documents include Addenda issued prior to execution; bidding documents / bid or proposal and bidding-related addenda portions often out unless enumerated; § 1.2.1 complementary documents.
• AIA G612–2017 / instructions — Owner’s Instructions; Part B Bidding Procedures completes A701.
• AIA G804–2001 — Register of Bid Documents during bidding; deposits and returns.
• CSI Part 2 (O’Beirne) — pre-bid answers by Addendum; caution on informal Q&A. MasterFormat 2026 — Division 00; your project manual wins. Published MasterFormat 2018 PDF index: 00 91 00 Modifications to Bidding Documents; 00 91 13 Addenda; 00 91 16 Bid Modifications / Bid Revisions (numbering language only).
• ConsensusDocs 270 / 271 — parallel-family bidder instructions; citation only.
• Excel, Word, PDF, email — register, impact log, acknowledgment draft, submit path the Instructions named. Sister jobs: quantity takeoff, bid-leveling, scope-gap, bid-proposal.

Watch-outs

• Invented Addenda acknowledgments and invented “no impact.” Models write fluent “we acknowledge Addenda 1–4” and “no cost impact — fully incorporated” lines that are not in the upload. Same failure mode as legal citation hallucination: Dahl, Magesh, Suzgun & Ho, Large Legal Fictions, 16 J. Legal Analysis 64 (2024) (arXiv:2401.01301, doi:10.1093/jla/laae003) — public LLMs, asked verifiable questions about federal cases, hallucinated often and often could not tell. Those percentages are legal-case questions, not addenda-tracking accuracy; do not import them as a construction performance rate. Do import the habit: every Addendum number, every “no impact” claim, and every drawing/spec citation in the draft is unverified until you open the register and the PDF. Blank / “may need re-check” is honest; a confident fake acknowledgment is not.
• Model-revised prices and quantities. The agent does not own the Base Bid, Alternates, takeoff revisions, or sub re-asks. Flag may need re-check only. A fluent revised dollar or quantity without a human decision is a defect.
• Sister jobs confused with this one. Takeoff measures. Leveling compares quotes. Scope-gap walks the documents for holes. Bid-proposal assembles the outbound package. This page drafts the acknowledgment + impact log when Addenda arrive. Do not ask one prompt to do all five.
• Email reply treated as an Addendum. CSI (O’Beirne Part 2): binding procurement answers go by Addendum. Do not let the model promote a clarification email into an acknowledgment line.
• G716 / G701 on bid day. Construction RFI and executed change order are after award. Bidding uses A701 clarification and addenda. Do not cite G716 as the reason you skipped an Addendum.
• Unsigned AI as the acknowledgment. Fluent, late, and wrong is worse than a short human checklist. The estimator fills the bid-form acknowledgment and submits. The agent does not.
• Do not replace the estimator. The agent drafts from the upload. The estimator still owns every incorporate-or-not call and the submit.

Verdict

Yes — a $5–10M US GC should run this job this quarter if they already keep Addendum PDFs (or a register), takeoff / leveling / scope-gap / proposal notes as files (or exports), the bottleneck is turning late Addenda into an acknowledgment checklist and a structured “what may need re-check” log before the bid clock, and a person will still own which addenda apply, every incorporate-or-not call, every price/quantity revision, the bid-form acknowledgment, and the submit. Use an agent to draft the acknowledgment + impact log from uploaded Addenda and prior notes; the estimator owns the commercial calls and the submit. Skip this quarter if you expected the model to invent acknowledgments, assert “no cost impact,” revise the takeoff, re-price a trade, or click submit; if you thought this was takeoff, bid-leveling, scope-gap, or bid-proposal; or if you were about to buy a bid-board / document product you do not already have. Do not publish this page as a vendor listing.