Map the source of truth for the addendum log

Why the addendum log needs its own control

A team working in construction estimating can complete a task and still leave the next person unable to verify it. The control for the addendum log exists to make the work reconstructable from a source, a decision, and a close. The cost is not only rework.

When the addendum log record is thin, managers spend time asking what changed, customers hear a different version, and the next reviewer has to rebuild the story from memory. Treat the "why the addendum log needs its own control" control as an evidence problem before treating it as a speed problem. The estimating support specialist can prepare an addendum log, but the chief estimator keeps the decision when the item involves bid deadline moves without a written notice.

Record bid deadlines missed by cause with its denominator and window, then use the weekly sample to check whether the same gap keeps returning. Keep the addendum log queue separate from the general inbox. A shared queue without a named owner hides the oldest item and makes the weekly report look cleaner than the work.

Start with the source record

Begin with the record that governs the addendum log. Record who created it, the version or date observed, the field it supports, and the person who can confirm it. Concrete example: a bid package references a drawing that was superseded.

The estimating support specialist opens a subcontractor quote comparison, records subcontractor scope and quote validity and project and bid package identifier, and asks one precise question instead of filling the blank from memory. The item leaves the bid package, takeoff, and subcontractor-quote queue only after the chief estimator accepts the next action and the evidence link is attached. For the "start with the source record" section, define the stopping condition before the estimating support specialist starts the task.

The addendum log should show addendum number and date, quantity and unit of measure, and the evidence that let the chief estimator accept the result. If the item involves quantity mismatch between takeoff and quote, document the reason and route the decision to the subcontractor coordinator; a reopened item needs a new dated action, not a copied closure note.

Separate preparation from approval

Name the owner before the VA prepares any action. The VA may collect, compare, label, calculate, and route; the chief estimator decides whether the evidence is enough. Before scaling the "separate preparation from approval" workflow, make a subcontractor quote comparison readable to someone outside the original team.

It should show the request, the source, drawing and specification version, the chief estimator, and the next date in one place. The chief estimator reviewing the bid package, takeoff, and subcontractor-quote queue should see exceptions, not a clean activity count that hides unresolved work. Treat the "separate preparation from approval" control as an evidence problem before treating it as a speed problem.

The estimating support specialist can prepare an addendum log, but the chief estimator keeps the decision when the item involves drawing version conflicts with the addendum. Record bids with all addenda acknowledged with its denominator and window, then use the weekly sample to check whether the same gap keeps returning.

Keep a short decision log for the addendum log queue. The log should show the question, the owner, the decision, the date, and what would reopen it.

Build the daily routine

Build a short daily routine for the addendum log: open the queue, check the source, record the exception, and leave a next action with a time. The bid package, takeoff, and subcontractor-quote queue in construction estimating and bid preparation usually fails at the handoff, not at the first task. For the "build the daily routine" section, the estimating support specialist should capture the source, the version, the accountable chief estimator, and the next review date in a subcontractor quote comparison.

If the item involves quantity mismatch between takeoff and quote, route it to the project manager and keep the exception reason attached so a later reviewer can see why the normal path did not apply. The addendum log is useful for the "build the daily routine" control only if another person can audit it. The estimating support specialist records quantity and unit of measure and project and bid package identifier, keeps the source attached, and marks a case involving bid deadline moves without a written notice with the owner who accepted it.

Review bids with all addenda acknowledged during the weekly check and test one recent correction against the original evidence. Before scaling the "build the daily routine" workflow, make a takeoff worksheet readable to someone outside the original team.

It should show the request, the source, project and bid package identifier, the chief estimator, and the next date in one place. The design lead reviewing the bid package, takeoff, and subcontractor-quote queue should see exceptions, not a clean activity count that hides unresolved work.

Handle exceptions before they age

Define reason codes for the addendum log: missing evidence, identity mismatch, conflicting record, stale version, unavailable owner, access failure, and scope change. Before scaling the "handle exceptions before they age" workflow, make a bid package register readable to someone outside the original team. It should show the request, the source, subcontractor scope and quote validity, the chief estimator, and the next date in one place.

The subcontractor coordinator reviewing the bid package, takeoff, and subcontractor-quote queue should see exceptions, not a clean activity count that hides unresolved work. The control that matters for the "handle exceptions before they age" section is a short, reviewable record, not a longer checklist. The estimating support specialist captures project and bid package identifier and quantity and unit of measure, labels a case involving quantity mismatch between takeoff and quote, and leaves the decision with the chief estimator.

During the weekly review, compare quote coverage by trade with the unresolved items and note which fix changed the result. When the addendum log source is maintained by another team, name the contact and the expected response time. Escalation without a contact becomes a repeated chase.

Verify, close, and review

Close the addendum log only when the destination record shows the approved change. A sent message or a closed ticket is not proof that the schedule, ledger, access, or assignment changed. The subcontractor quote comparison is useful for the "verify, close, and review" control only if another person can audit it.

The estimating support specialist records addendum number and date and quantity and unit of measure, keeps the source attached, and marks a case involving drawing version conflicts with the addendum with the owner who accepted it. Review bids with all addenda acknowledged during the weekly check and test one recent correction against the original evidence. Ask what would let a new reviewer continue the "verify, close, and review" work without a conversation.

The answer is usually a takeoff worksheet with the source, version, owner, and next action. If the item involves bid deadline moves without a written notice, the estimating support specialist pauses the item, records the gap, and routes one question to the design lead; do not close the item just to keep the queue moving. Before scaling the "verify, close, and review" workflow, make a takeoff worksheet readable to someone outside the original team.

It should show the request, the source, quantity and unit of measure, the chief estimator, and the next date in one place. The subcontractor coordinator reviewing the bid package, takeoff, and subcontractor-quote queue should see exceptions, not a clean activity count that hides unresolved work.

What the VA may prepare and what the chief estimator decides

For construction estimating teams, the useful split is preparation versus authority. The VA can assemble the addendum log packet, check the fields, and write a precise question; the chief estimator owns the decision that changes money, policy, access, or a customer promise. For the "what the VA may prepare and what the chief estimator decides" section, define the stopping condition before the estimating support specialist starts the task.

The addendum log should show project and bid package identifier, subcontractor scope and quote validity, and the evidence that let the chief estimator accept the result. If the item involves bid deadline moves without a written notice, document the reason and route the decision to the project manager; a reopened item needs a new dated action, not a copied closure note. In practice, the estimating support specialist handles the "what the VA may prepare and what the chief estimator decides" work by preparing a bid package register and naming the decision boundary.

Include the source and retrieval date, addendum number and date, and the next action owner. When the item involves drawing version conflicts with the addendum, the item goes to the project manager with the evidence already checked; the bid package, takeoff, and subcontractor-quote queue should show the hold, not hide it.

Make the addendum log handoff visible in the record. A chat message can start the handoff, but the source, the open question, and the next owner belong with the case.

A weekly evidence review for the addendum log

Set one recurring point each week to review the addendum log queue: the oldest items, the blocked items, and one item that was corrected. Keep the meeting short and decision-focused. For the "a weekly evidence review for the addendum log" section, define the stopping condition before the estimating support specialist starts the task.

The addendum log should show addendum number and date, project and bid package identifier, and the evidence that let the chief estimator accept the result. If the item involves subcontractor quote excludes a required scope, document the reason and route the decision to the design lead; a reopened item needs a new dated action, not a copied closure note. The bid package, takeoff, and subcontractor-quote queue in construction estimating and bid preparation usually fails at the handoff, not at the first task.

For the "a weekly evidence review for the addendum log" section, the estimating support specialist should capture the source, the version, the accountable chief estimator, and the next review date in an addendum log. If the item involves bid deadline moves without a written notice, route it to the chief estimator and keep the exception reason attached so a later reviewer can see why the normal path did not apply.

Record the exact source for the addendum log and the time it was observed. A later reviewer should be able to tell whether the value was current when the first action was taken, even if the record has changed since.

What to fix first

Fix the source before you fix the report. If the addendum log record cannot show the version, the owner, and the close condition, a new dashboard will only make the gap easier to see. In practice, the estimating support specialist handles the "what to fix first" work by preparing a bid package register and naming the decision boundary.

Include the source and retrieval date, addendum number and date, and the next action owner. When the item involves drawing version conflicts with the addendum, the item goes to the project manager with the evidence already checked; the bid package, takeoff, and subcontractor-quote queue should show the hold, not hide it. The control that matters for the "what to fix first" section is a short, reviewable record, not a longer checklist.

The estimating support specialist captures subcontractor scope and quote validity and project and bid package identifier, labels a case involving quantity mismatch between takeoff and quote, and leaves the decision with the chief estimator. During the weekly review, compare quote coverage by trade with the unresolved items and note which fix changed the result. Write the next action as a sentence with an owner and a time.

A vague request to review the addendum log exception is not a next action; a named person, a specific check, and a deadline is. Review the estimating support lane and contact the team before changing the record. Public guidance is available in AACE recommended practices.

Frequently Asked Questions