How to Track Addenda So Every Revision Gets Priced Before Bid Day

Key takeaways

• One master addenda log should control the bid.
• A revision is not closed until it is priced, clarified, or documented as no impact.
• Revised sheets should be reviewed by direct comparison, not by memory.
• Every addendum item should point to a specific estimate reference or proposal update.
• Bid-day addenda review should be a short audit, not a search through emails.

Track addenda in one master log that connects each revised sheet, specification change, bulletin, and bid-impacting RFI answer to a reviewer, an impact status, and a specific estimate line or proposal change. An addendum is not closed until it is priced, carried as a clarification, or documented as no impact.

Use one master addenda log for the bid

One control log should govern the bid. Personal notes, PDF markups, and inbox flags can help individual reviewers, but the team needs one place that shows what changed, who reviewed it, and what was updated in the estimate and proposal.

For a general contractor, that log usually sits above trade-level review. For a subcontractor or specialty contractor, it often becomes the working control sheet for the entire pursuit.

A practical addenda log should capture:

• addendum number and date
• document type, such as drawing revision, spec revision, bulletin, sketch, or RFI answer
• affected trade, discipline, or bid package
• sheet number, detail, schedule, keynote, or spec reference
• reviewer or owner
• impact status, such as pricing change, scope clarification, vendor quote update, or no impact
• estimate line, worksheet, or cost code reference
• proposal impact, such as inclusion change, qualification update, exclusion revision, alternate update, or no proposal change
• open follow-up items
• close date

If the team cannot see the status of a revision in one place, the item is still exposed.

Review revised sheets by change, not by memory

Compare old and new documents directly and work outward from each change until the scope effect is clear. Revision clouds help, but they are not enough by themselves.

A reliable review pass usually looks like this:

• confirm the current addendum index and revised document list
• open prior and current sheets side by side, or use a document compare workflow
• mark each visible change on the working set
• trace the change into related details, schedules, legends, notes, and specification sections
• note whether the revision affects quantity, material, labor, access, phasing, coordination, or vendor scope
• send unresolved conflicts into an RFI or clarification log before closing the entry

Review by scope impact, not by sheet count. If a door schedule changes, check frames, hardware, power, access control, wall conditions, and finishes. If site utility routing changes, check trenching, backfill, patch-back, restoration, and coordination. If a reflected ceiling plan changes, check framing, ceiling types, light fixtures, diffusers, sprinkler heads, soffits, and device relocations.

Tie each revision to a priced estimate line and a proposal note

Every revision should point to a priced line, an allowance, an alternate, or a documented no-impact decision. That is what turns document control into estimate QA/QC.

If an addendum changes acoustical ceiling types in selected rooms, the log should point to the ceiling quantity line, any related trim or accessory line, the affected vendor quote if one is involved, and the proposal note if the scope basis changed. If a hardware set adds electrified components, the entry should point to the doors and hardware line, the supplier quote version, and any coordination note that now affects the bid.

The format can vary. Some teams use cost codes. Others use worksheet names or estimate item IDs. The method matters less than consistency. Another reviewer should be able to open the log, find the reference, and confirm that the revision landed in the estimate.

A final check should confirm that:

• quantities changed where required
• pricing inputs or vendor quote carries were updated
• labor assumptions still fit the revised scope
• duplicate scope was removed where multiple trades were affected
• proposal language matches the final pricing basis

If a scope change has no estimate reference, it is still open.

Update scope sheets, quote tracking, and exclusions in the same pass

The estimate is not fully updated if the scope sheet and proposal still reflect the old set. Addenda control works only when drawing review, pricing, vendor follow-up, exclusions, qualifications, alternates, and proposal language move together.

That matters on both multi-trade bids and trade-specific bids. A finish schedule revision can affect flooring, wall base, transitions, adhesives, phasing, and moisture-related assumptions. A mechanical revision can affect equipment tags, controls responsibility, supports, startup requirements, and procurement timing. A sitework change can affect pipe material, utility depth, paving restoration, and testing scope.

When an addendum drops, update these items in the same pass:

• the internal scope sheet or bid summary
• vendor quote requests and quote version tracking
• inclusions, exclusions, and qualifications
• alternates and allowances
• proposal clarifications
• subcontractor or supplier scope comparison notes

If a revision touches a quoted product or lead-time-sensitive item, reconfirm the quote instead of assuming the earlier carry still applies.

Run a short bid-day addenda audit

The final addenda check should take minutes because the log has already done the work. Bid day is for verification, not for rebuilding revision history from email threads.

A practical final audit should confirm that:

• the latest addendum on the plan room or invite matches the team log
• all revised sheets and revised specification sections are in the final working set
• each addendum item is closed, carried as an open question, or signed off as no impact
• every pricing-impact item points to an estimate line, quote revision, allowance, or alternate
• every scope-impact item points to a scope sheet or proposal update
• the proposal acknowledges the correct addenda by number and date
• unresolved issues are carried clearly as clarifications or qualifications when needed

A second reviewer helps. The person who made the revisions is often too close to the estimate to spot what was missed.

Treat addenda tracking as estimate QA/QC

Addenda tracking is part of pricing control, not side administration. Gaps between revised documents, vendor pricing, estimate lines, and proposal language are where bid exposure usually starts.

Tribuild Consultancy is a multi-trade estimating, preconstruction, and project-administration company.

This workflow matters because addenda review connects directly to takeoffs, pricing, vendor follow-up, proposal preparation, change documentation, procurement planning, and downstream project administration.

If you want to review one estimating workflow for an upcoming bid, discuss the addenda-control handoff before bid day.

Sources

• https://tribuildconsultancy.com