Why an addendum needs its own register
Most estimating teams already keep a drawing log and a request for information log. An addendum register is different because it tracks the commercial effect of a formal issuance rather than the existence of a document. The same addendum can add a door, delete a roof section, extend a schedule, and restate a substitution rule.
If those effects share one check box, the estimate cannot show which priced line came from which instruction. The register also protects the team when the bid is challenged. A reviewer who was not in the preconstruction meeting should be able to open the register, find the addendum number and issue date, and follow a path to the affected takeoff lines.
Without that path, a change is either invisible or accepted on memory. Both outcomes create rework later.
Capture the identity and issue path first
Record the addendum number, the issue date, the issuing party, and the exact document set that it modifies. Note whether the addendum arrived through the owner, the architect, or a plan room, and whether the team received it before or after the last quantity refresh. The timing matters because it determines whether the change can be priced from a clean baseline or must be layered onto an already adjusted estimate.
Attach the received files rather than a link that may expire. Keep the base specification section and the revised section side by side, and mark the paragraphs that changed.
This step is administrative, but it is the difference between a defensible register and a list of remembered changes. The drawing revision review uses the same evidence habit for sheet-level changes.
Translate each change into affected quantities
For every addendum item, name the trade, the drawing or specification reference, and the takeoff line that must move. Write the quantity before and after the change, the unit of measure, and the arithmetic used to get from one to the other. If the change cannot be expressed as a quantity yet, create a placeholder line with the question that must be answered rather than forcing a number.
Some items change a condition rather than a count. A revised fire rating may add assembly thickness, a substituted product may change waste, and a new phasing note may add temporary protection.
Treat those as quantity drivers and record the affected assumption. The register should show the driver, not only the final dollar amount, so a reviewer can test the logic when a supplier or subcontractor challenges the result.
| Register field | What to record | Review question |
|---|---|---|
| Identity | Addendum number, issue date, issuing party | Is this the current issuance? |
| Document effect | Sheet or specification section changed | Can the change be located in the reissued set? |
| Quantity effect | Before and after quantity with unit | Does the arithmetic trace to the drawing? |
| Commercial effect | Direct cost, schedule, and risk separated | Which effect still needs an owner decision? |
| Decision | Included, excluded, allowance, or withdrawn | Does the bid packet state the same position? |
| Residual gap | Open question, owner, needed date | Who closes it before release? |
Separate price effect from schedule and risk
A single addendum can create three different exposures. The direct price effect is the cost of the added or deleted scope. The schedule effect is the labor duration, escalation, or general conditions consequence.
The risk effect is the uncertainty that remains because a detail is still unresolved. Mixing all three into one adjustment hides the part that needs a decision. Give each effect its own line and its own owner.
The estimator prices direct scope, the scheduler or project lead tests duration, and the commercial lead decides how much uncertainty to carry. The AACE recommended practices library is a useful reference for separating estimate basis from contingency and for documenting a change without inventing a precision the documents do not support.
Set the review sequence before pricing changes
Price only after the affected quantity and source are confirmed. A common failure is to price an addendum from an email summary, then discover that the formal drawing shows a different extent. The register should have a review state between received and priced.
During that state the estimator confirms the document set, checks for a superseding addendum, and verifies that the specification section was actually reissued. Use a short sequence that everyone can remember: received, mapped, priced, reviewed, and released. Each transition needs a name and a date.
If an item jumps from received to priced without a mapping note, the reviewer sends it back. This sounds rigid, but it prevents the quiet assumption that an addendum only affects the obvious trade.
Record the decision and the residual gap
When an item is priced, write the decision in plain language. State what was included, what was excluded, and which clarification will be submitted if the bid form allows one. If the team decides to carry an allowance instead of a firm number, record the allowance amount, its basis, and the condition that would trigger a change.
The bid submission readiness check should then confirm that the decision made it into the final packet. Residual gaps deserve their own column. A gap is not a failure if it is visible.
Mark the owner, the question, and the date by which an answer is needed. At bid close, the commercial lead reviews the gap list and decides whether to qualify, carry risk, or walk away. That decision is a business judgment, and the register exists to give the decision a factual base.
Keep the register alive through post-bid questions
The register should not close when the bid is submitted. Post-bid clarifications, negotiated scope, and award conditions often refer back to addendum items. If the register is archived with the estimate, the team can answer a question in minutes instead of rebuilding the change history.
Add a final column for the outcome: included in bid, excluded, allowance, or withdrawn. A simple test tells you whether the register works. Hand it to an estimator who did not work on the bid and ask them to explain one priced change without opening email.
If they can follow the item, the source, the quantity, and the approval, the register is doing its job. If they cannot, the missing field is the next improvement.
