How to Review Construction Tender Addenda

Quick answer

Review each tender addendum against a frozen baseline of the documents it changes. Record every addition, replacement, deletion, and clarification. Then trace each change into the estimate, programme, scope matrix, qualifications, and supplier enquiries.

An addendum is not closed because the team downloaded it. It is closed when every material change has an owner, an impact decision, and evidence that the bid was updated.

Table of contents

1. Start with a frozen baseline
2. Build a change map
3. Classify the type of change
4. Trace the commercial impact
5. Control revised drawings and schedules
6. Close the loop with suppliers
7. Where AI helps
8. Addendum review checklist
9. Frequently asked questions

The email subject says "deadline extension."

The attachment is 63 pages long.

Most of the team reads the new submission date on page one and moves on. Buried on page 47 is a revised testing frequency that changes laboratory cost, inspection planning, and programme float.

The deadline changed. So did the job.

Start with a frozen baseline

You cannot identify a change if nobody agrees what came before it.

At tender start, create a document register with the filename, title, revision, issue date, and source for every document. Include drawings, specifications, BOQs, schedules, forms, and clarifications. Preserve the original package as a read-only baseline.

When an addendum arrives, do not silently replace the old files in the working folder. Store the new issue beside the superseded version and mark the relationship clearly.

A useful naming rule is simple:

discipline_document_revision_date_status

The exact format matters less than consistency. The team should be able to tell which file is current without opening it.

Build a change map

The addendum cover letter rarely tells the full story. It may list revised files without explaining every consequence.

Create one row for each changed item:

Use the addendum as the entry point, but cite both the new and previous sources. A reviewer needs to understand what changed, not only where the new wording appears.

Classify the type of change

Four labels cover most addendum changes:

Added: A new requirement, drawing, form, or scope item appears.

Replaced: A revised document or clause supersedes an earlier version.

Deleted: A requirement or item is removed from the tender package.

Clarified: Existing intent is explained without an obvious change to the requirement.

Treat "clarified" carefully. Wording that looks explanatory can still change price or risk. If a clarification narrows an acceptable product range, assigns responsibility, or defines a date, it needs the same impact review as a formal replacement.

Trace the commercial impact

Every material change should be checked against five places:

1. Estimate: Quantities, rates, allowances, and indirect costs
2. Programme: Milestones, access, sequencing, procurement, and testing
3. Scope: Package ownership, interfaces, temporary works, and client-supplied items
4. Submission: Qualifications, exclusions, forms, bonds, and proposed alternatives
5. Supply chain: Supplier and subcontractor quotes based on earlier information

A revised drawing can affect all five. It may change a quantity, introduce a procurement lead time, move work between packages, invalidate an exclusion, and require suppliers to reprice.

Do not use "no cost impact" as a default. Make it a decision with an owner.

Control revised drawings and schedules

Revision clouds are helpful, but they are not a complete review method.

A cloud may show geometry that changed without showing the downstream effect on another discipline. A revised schedule may change a product or quantity without a visible mark on the plan. A drawing can also be reissued with a new revision even when the change is limited to notes.

For every revised drawing:

• Compare the full sheet, not only revision clouds.
• Check schedules, legends, and general notes.
• Identify details referenced from other drawings.
• Confirm that takeoff teams are using the current revision.
• Check whether the BOQ and specification were revised as well.
• Record which previous version is superseded.

The goal is to stop mixed-revision pricing, where one discipline works from the new plan and another still uses the old schedule.

Close the loop with suppliers

Supplier quotes often arrive before the final addendum.

When a change affects a quoted package, send a focused revision notice. Do not forward a large addendum and assume the supplier will find the relevant pages.

State:

• The addendum reference
• The exact revised documents
• The affected scope
• The required response date
• Whether a full reprice or confirmation of no impact is needed

Track replies in the change map. If a supplier cannot reprice before bid close, document the internal allowance and approval used in its place.

Run a final addenda reconciliation

Before bid approval, reconcile four lists:

• Every addendum issued by the client
• Every document in the current tender register
• Every open change-map item
• Every estimate, programme, or submission revision made in response

Then ask one uncomfortable question: Is any part of the bid still based on a superseded document?

A signed addendum acknowledgement confirms receipt. It does not prove that the bid incorporated the changes.

Where AI helps

Addendum review is a comparison problem spread across many document types.

Brickato's tender analysis platform can search specifications, tender instructions, BOQs, and addenda together, with page-level citations for each answer. That helps teams identify where a new issue changes or supersedes a requirement in the baseline package.

Useful questions include:

• Which requirements in Addendum 4 change the original technical specification?
• Which revised drawing notes have no matching BOQ update?
• Does this addendum change any submission form, bond, milestone, or testing requirement?
• Which clarification responses are superseded by the new issue?

AI can accelerate the comparison and surface evidence. The team still decides the cost, programme, contractual, and submission impact.

For the broader tender review workflow, see Construction Tender Document Analysis: Manual vs. AI.

Addendum review checklist

• Preserve the original tender baseline
• Register the addendum and every revised attachment
• Mark superseded files without deleting them
• Record added, replaced, deleted, and clarified requirements
• Compare full drawings, schedules, notes, and references
• Check the estimate, programme, scope, submission, and supply chain
• Issue focused revision notices to affected suppliers
• Assign an owner and action to every material change
• Link closed items to evidence in the working bid
• Reconcile all addenda before final approval
• Confirm no one is pricing from a superseded revision

Frequently asked questions

Who should control tender addenda?

One person should manage receipt, registration, and distribution, usually the bid coordinator or document controller. Discipline owners remain responsible for assessing and closing the impact on their work.

Should old document revisions be deleted?

No. Keep them in a controlled superseded area. They are needed to understand what changed and to explain decisions made before the new issue arrived.

Is an addendum acknowledgement enough?

No. It confirms receipt, not implementation. The team still needs evidence that material changes reached the estimate, programme, scope, qualifications, and supplier quotes.

What if an addendum arrives after supplier quotes are due?

Send the affected changes immediately and request either a revised quote or written confirmation of no impact. If that is not possible before bid close, use an approved internal allowance and document the assumption.

Can AI compare drawings?

Capabilities vary by platform and document type. Do not assume that every visual change has been captured automatically. Verify critical drawing, quantity, and design changes in the source documents.

Do not let the new deadline hide the new requirement

Addenda create pressure because they compress review time while changing the basis of the bid.

The answer is not faster reading. It is controlled comparison: freeze the baseline, map every change, assign the impact, and prove the bid moved with the documents.

Start a 30-day Premium trial and review tender revisions with sources attached to every finding.