Guide

Why spreadsheet estimates break when addenda arrive (and how to stop it)

The estimate was fine on Monday. Addendum 2 arrived on Wednesday, the bid is due Friday, and now nobody is sure the number reflects the current set. Why that happens, and a working method to keep every addendum under control.

Guide · Updated November 9, 2026 · About 9 minutes

Addenda are not unusual. On most commercial bids you will see at least one, often three or four, and the last one tends to arrive a day or two before the due date. Each changes the documents your price is built on. A good estimate absorbs them calmly. A fragile one quietly falls apart.

Spreadsheets are not bad at math. They are bad at change. Here is where the trouble comes from, and what a shop can do about it, with or without new software.

Five reasons spreadsheets break on addenda

1. The change is in the documents, the price is in the cells

An addendum says "Sheet S-201 revised: Stair 2 adds an intermediate landing." The spreadsheet does not know what Sheet S-201 is. Someone has to translate the document change into the rows it affects: the stair's stringers, the landing plate, the shop hours, the finish, maybe the erection time. The translation is manual, and it depends on the estimator remembering every place that stair touches.

2. Edits happen in place

The natural thing to do in a spreadsheet is to change the numbers where they are. The moment you do, the pre-addendum number is gone. If the GC later asks "what did Addendum 2 add?", the honest answer is "let me reconstruct that", and reconstructing under pressure is how mistakes are made.

3. Copies multiply

The cautious alternative is to save a copy before each addendum. Now there are four files: "Bid", "Bid ADD1", "Bid ADD2 final" and "Bid ADD2 final REV". Someone fixes an error in one copy and not the others. On bid day, two people are working in two different files.

4. Summaries drift from details

Most bid workbooks have detail tabs and a summary tab. An addendum adds a scope; the estimator adds a tab or a block of rows; the summary formula does not include it. The total looks plausible. Nothing turns red.

5. The proposal is retyped

Even when the price is right, the proposal is often a separate document. The addendum list, the scope descriptions and the exclusions are updated by hand, so the proposal can say "Addenda 1 through 2" while the number includes Addendum 3, or the other way round.

A method that holds up

The fix is less about tools than about discipline. These habits work in any system, spreadsheet included.

Price from the current set, always

The current set is the original documents with every addendum applied. Before an estimator prices anything, they should know which addenda are out and have the current version of every sheet and spec section they are using. A surprising number of wrong bids are priced correctly from the wrong drawing.

Freeze the number before each addendum

Before you touch the estimate for an addendum, freeze the current version and give it a name: REV00 for the base, REV01 for Addendum 1, and so on. Never edit a frozen version. All changes go into the new one. This one habit answers "what did the addendum add?" for the rest of the job.

Read the whole addendum before pricing any of it

Addenda often contain changes that interact: a revised detail on one page and a spec change on another, or an answer to a bidder's question that changes your scope more than the drawings do. Read it start to finish, mark every item that touches your trade, then price.

Map each change to the scopes it touches

Write down, for every addendum item that affects you, which scopes it changes. If your estimate is organized by scope (one scope per stair, per rail run, per elevation, per system), this is quick. If it is organized as one big sheet, this is where you find out.

Compare before and after

Once the addendum is priced, compare the new version with the frozen one: total, cost categories and each scope. Every difference should be explained by an addendum item. A difference you cannot explain is an error, found before the GC finds it.

Raise questions early

Addenda often create conflicts: a drawing that now disagrees with the spec, or a detail that no longer fits a dimension elsewhere. Write those down as RFI questions while you are reading, not on bid day. If the answer will not come in time, state your assumption on the proposal.

Update the proposal from the estimate

The list of addenda acknowledged, the scope descriptions, qualifications and exclusions should all come from the version you are submitting. If they are typed separately, check them against the estimate line by line before sending.

The addendum log

A simple log turns the method into a habit. One row per addendum item that affects your trade:

ExampleAn addendum log
AddendumItemScopes affectedRevisionStatus
ADD 1S-201: Stair 2 adds intermediate landingStair 2REV01Priced
ADD 1Spec 05 52 13: guardrail finish to galvanizedExterior guardrailREV01Priced
ADD 2A-501: lobby feature rail added as Alternate 1New scope, Alt 1REV02Priced
ADD 2Spec and S-201 disagree on landing elevationStair 2REV02RFI sent; assumption on proposal

An example only. Sheet and section numbers are for illustration.

The log does three jobs. It makes sure nothing in the addendum is skipped. It tells the reviewer exactly what changed and why. And when the job is awarded, it is the record that turns a scope question into a clean change order instead of an argument.

What changes with an estimating system

Everything above works in a spreadsheet if the team is disciplined. The problem is that discipline is hardest exactly when addenda arrive: late, under pressure, with three bids due the same week. A system that makes the method the default removes most of the risk.

In ScopeDive, for example:

  • Revisions are built in. You revise the whole bid and the old one is kept. REV00, the base, is locked. See revisions.
  • Comparison is a screen. Compare any two revisions by totals, cost buckets and scopes, with the change and the percentage change. Affected items are highlighted in every scope.
  • The estimate is organized by scope, so mapping an addendum item to the scopes it touches is natural.
  • Addenda are tracked against the bid in the Bid Inbox.
  • The proposal is built from the estimate, so it always matches the revision you submit.
  • ScopeDive AI can help with the reading. It reads the bid documents and the current set with addenda, drafts scopes with the source words quoted, flags document conflicts and drafts RFI questions. Its drafts land in an AI draft revision, and the estimator accepts, edits or rejects each line. It never prices. See ScopeDive AI.
ScopeDive revision comparison: project totals for two revisions side by side, including base bid, final bid, direct cost, every cost bucket and alternates, with the change and percentage change
Comparing two revisions in ScopeDive: totals and cost buckets side by side, with the change and the percentage change.

The short version: freeze before you change, price from the current set, compare before and after, and never retype the proposal. Do those four things, in whatever tool you use, and addenda stop being the week's biggest risk.

For a fair comparison of spreadsheets and an estimating system, see ScopeDive vs Excel for estimating.

See it on your work

Price your next bid in ScopeDive.

Book a 20-minute tour and bring a bid you recently priced. We will show you how your library, your rates and your cost structure would look in ScopeDive.