How to Handle Bid-Day Addenda Without Re-Counting

When a late addendum lands, don't re-count the job. Find what actually changed on the revised drawings, adjust only those drops, and re-total. The goal is to reconcile deltas, not to start over.

That distinction is everything on bid day. An addendum dropped two hours before the deadline can add a wing, move an IDF, or swap device locations on three sheets. If your only response is to re-count from scratch, you either blow the deadline or rush and make errors. Neither is a good way to win work at a price you can build.

Why late addenda wreck manual takeoffs

A spreadsheet-and-highlighter takeoff has no memory of *why* a number is what it is. The count is a total, disconnected from the drawing it came from. So when Addendum 3 changes a few rooms, you can't see the change at the line-item level, only the bottom line you have to defend.

That leads to predictable bid-day failures:

Full re-counts under time pressure. Re-highlighting whole sheets to catch a handful of moved drops wastes the time you don't have.
Double-counting. You count the added rooms but forget to remove the deleted ones, or you count a revised sheet on top of the original.
Stale totals. The estimate reflects the original set, and nobody's sure which version the number is tied to.
Untraceable numbers. When the PM asks "where did 142 drops come from?" two days later, you can't reconstruct it.

Reconcile the deltas, don't re-count

Treat an addendum as a diff against what you already counted. The work is to identify the changes and apply only those.

Read the addendum narrative first. It usually lists affected sheets and a summary of changes. That tells you where to look before you open a single drawing.
Compare revised sheets to the originals. Find adds, deletes, and moves. Clouded revisions and revision triangles point you straight to them.
Adjust only the affected drops. Add the new ones, remove the deleted ones, relocate the moved ones. Leave the untouched 90% of the job alone.
Re-total and re-check pathway impacts. A new wing may add J-hook runs (supports typically every 4-5 ft, max 5 ft, sag under ~12 in) or push a run length. The 90 m permanent-link limit still applies on the changed drops.

You're auditing a small set of changes against a known baseline, not rebuilding the baseline.

Keep the count tied to the drawing

The reason deltas are fast is that each counted item stays linked to its spot on the sheet. When a count lives on the drawing, a changed drawing tells you exactly which counts to revisit. When it lives only in a spreadsheet cell, you've lost the thread the moment the drawing changes.

Keeping counts tied to the drawing also protects accuracy on the parts that *didn't* change. You're not re-touching them, so you can't accidentally fat-finger a number that was already right.

Version discipline that survives bid day

Addenda come in numbered for a reason. Your takeoff should mirror that.

Name the version. Tie every total to a drawing set and addendum number: "Base + Add 1-3."
Work from the latest issued sheets only. Swap in revised sheets and archive the superseded ones so you never count an old version by mistake.
Log what changed. A one-line note per addendum ("Add 3: +8 drops Level 2 east, -2 in conf room") makes the final number defensible.
Re-confirm assumptions. Apply your usual rules of thumb to the new scope too: waste factor ~10-15%, service loops and slack at both ends, and rough labor around 11 hours per 1,000 ft when you sanity-check the delta.

A short note: cabling standards numbers here are general design guidance, not a substitute for the published standards or a licensed RCDD/PE review.

The bid-day payoff

When your count is tied to the drawing and your versions are clean, a late addendum becomes a 10-minute task instead of a fire drill. You move the changed drops, re-total, and submit with a number you can defend line by line, the next morning and three weeks later when the PM has questions.

In Cable Takeoff, your counts live on the drawing, so when an addendum hits you just move the changed drops and the totals update in seconds, with each version stored encrypted to your account. That's one less reason to dread the hour before a bid is due.