Construction drawing addenda and takeoff revision checklist
Use this checklist to log an issued change, preserve the takeoff baseline, review affected scope, update costs, and approve the revised estimate.
Log the issue before opening the revised set
Record the project, sender, received time, issue identifier, documents included, stated bid-date impact, and review owner. Save the transmittal or formal issue record with the project.
Confirm that the package is complete before measuring. Missing specifications, schedules, or referenced details can make a changed drawing appear simpler than it is.
- Issue identifier and date
- Sender and received time
- Affected documents
- Bid-date change
- Named review owner
Related: Manage takeoff revisions — Keep source, quantity, and estimate context together.
Preserve the existing takeoff
Create a dated backup or export and record the drawing issue used for the current quantities. Note assumptions, RFIs, quotes, allowances, and exclusions that may be affected.
Do this before replacing sheets or editing estimate lines. A preserved baseline is the comparison point for both technical and commercial review.
Related: Prevent outdated-plan estimates — Build the drawing-control routine around this checklist.
Review documents systematically
Read the narrative first, then the drawing index, changed sheets, specifications, schedules, and details. Inspect adjacent and referenced sheets, not only the areas with revision clouds.
For every change, state whether it affects scope, quantity, method, access, sequencing, temporary work, or an external quote.
- Narrative read
- Index checked
- Changed and referenced sheets reviewed
- Specifications and schedules checked
- Unclouded changes considered
Related: PDF takeoff software — Verify scale and measure the changed scope.
Map each change to estimate impact
Tie the issue to affected takeoff items and estimate lines. Record quantity variance, labour, material, equipment, subcontractor quote, waste, procurement, schedule, allowance, exclusion, and tax implications as applicable.
If scope is unclear, raise an RFI and record the temporary pricing treatment. Do not hide uncertainty inside a final total.
Review, approve, and release
Compare the revised estimate with the prior version. Investigate unusually large changes or unchanged totals, resolve each logged issue, and check that the proposal reflects the approved scope.
Share the approved revision with procurement and field staff, including its drawing issue and the person responsible.
- Cost changes reviewed
- Open RFIs visible
- Assumptions approved
- Proposal updated
- Recipients told which revision to use
Frequently asked questions
What should an addenda log contain?
Project, issue identifier, received date, affected documents, bid-date change, owner, review status, and estimate impact.
Should every changed sheet trigger a new takeoff?
Review every changed sheet and remeasure affected scope. The exact update depends on how the change intersects the existing quantities.
How should unclear addendum scope be handled?
Record an RFI and use an identified assumption or provisional allowance under the company's review process.