Estimate Revision Numbering for Contractors

Example: A remodeler sends a kitchen estimate for $36,480. The customer asks for quartz countertops, then under-cabinet lighting. The remodeler sends two updated PDFs, both called “final.” The customer signs the revision with quartz but no lighting; the office thinks the lighting was accepted too.

Revision numbers help everyone identify the same proposal, but a number alone does not withdraw an offer or prove what the customer accepted. Keep the issued files, the changes between them, and the approval record together.

Give the estimate a stable ID

Give the estimate a stable ID and link it to the job ID. Add a revision to each distinct customer-facing version. For example, EST-1042-R00, EST-1042-R01, and EST-1042-R02 identify three versions of estimate 1042. Starting with R00 or R01 is a numbering convention; choose one format and use it consistently.

Put the ID, revision, and issue date on the quote or estimate. If there is no dedicated revision field, include the revision in the document number, for example EST-1042-R02, and check that it appears in the PDF. Use the same reference in the email and file name, such as EST-1042-R02_2026-10-30_issued.pdf. A construction estimate can use the same method when several trades contribute to the price.

Keep revision and status separate: R02 identifies the content, while “draft,” “issued for review,” and “accepted” describe different workflow states. State the packet's purpose when sending it and track its status in the register. Record the evidence behind an “accepted” status; sending a file is not proof of acceptance. Do not overwrite the issued PDF to add a later status.

FTC guidance for hiring contractors after a weather emergency recommends written estimates identifying the work, materials, completion date, price, and contractor contact information. Those details still need to be clear in each revision; a version number is not a substitute for the estimate itself.

Record what changed between issues

Now imagine the remodeler issued numbered versions for the same kitchen and kept this register alongside the complete PDFs:

The figures are illustrative, not pricing guidance. R02 includes the quartz change from R01 as well as the lighting. The register records the signature on R01 without assuming it settles the scope of the agreement. A summary helps the customer compare versions, but the full R02 packet must describe the complete offered scope and terms.

For each issue, record the reason, changed scope, amount or credit, revised total, schedule or payment effects, attachments, sender, recipients, and delivery date. A revision may change a completion window or product without changing the total. If a tax, allowance, expiration date, or assumption changes, say so instead of recording only “updated quote.”

Use the scope-attachment guide to describe the assumptions and exclusions behind the price. If the revised estimate relies on a scope attachment, name its own ID and revision. A changed drawing or specification should also be identified by sheet and revision; don't assume a reader has the same attachment just because the estimate number matches.

Issue the complete packet and keep its history

Use the same issue process each time:

1. Check that the scope, amounts, dates, and referenced attachments agree. Explain what changed, whether the packet is for review or acceptance, and whether it is intended to replace a prior proposal or present a separate alternative.
2. Save the issued PDF and its identified attachments as a separate, readable packet. Send the full packet, not just the changed price page.
3. Record whom the packet was sent to, when, and how; retain any delivery confirmation or response. Ask the customer to review the complete version and identify any questions or missing attachments.
4. In the office register, identify older copies as prior issues so staff do not mistake them for the latest proposal. If marking a copy, keep the original issued file intact and clearly distinguish any annotated office copy.

Whether an earlier offer was withdrawn or accepted depends on the communications and applicable law, not the label in a file. If there is uncertainty, resolve it before treating a later issue as the agreed work.

NIST's document-control procedure offers a useful analogy: its safety program identifies revisions, makes current versions available, and archives obsolete documents. It governs NIST's own program, not contractor estimates, and does not impose this article's numbering scheme on a private business.

Keep the correspondence and any approval evidence with the versions it concerns. The job-folder guide explains how to organize access, backups, and retention without placing every sensitive record in a shared crew folder.

Match acceptance to the actual version

Ask the authorized customer representative to identify the estimate ID, revision, date, and included attachments when accepting. Retain the complete accepted packet, the acceptance evidence, and a copy delivered to the customer. The written-quote guide explains why an approval needs to be connected to the scope, not just a price.

If the customer signs R01 after R02 was sent, do not assume either that R01 is void or that R02 was accepted. Hold the affected work and preserve the signed copy and communications. Ask whether the customer intended the $39,000 R01 scope without lighting or wants to discuss R02 at $39,650 with lighting; confirm which attachments belong with the decision. Obtain whatever documentation and approvals the actual transaction requires; get legal advice if the parties disagree about the existing agreement.

Where a separate contract agreement is required or used, identify the accepted estimate and attachments in that packet. Review applicable signature, notice, cancellation, and delivery requirements. A revision register or a customer's reply does not by itself satisfy every contract requirement.

For transactions in or affecting interstate or foreign commerce, ESIGN, 15 U.S.C. §7001, generally prevents denial of legal effect solely because a record or signature is electronic. It preserves other legal duties and sets conditions for providing required consumer disclosures electronically and for retaining required records. Keep the accepted packet accessible and reproducible; do not rely on a link whose contents can later be replaced.

Separate a revised proposal from a change to an agreement

Before an agreement is formed, a revised estimate can communicate a proposed scope and price. Once work is covered by an existing agreement, preserve the accepted version and follow that agreement's change process rather than silently replacing it with a new estimate.

For example, California Business and Professions Code §7159 generally requires changes to covered home-improvement contracts to be written and signed by the parties before the changed work begins. California's Contractors State License Board also describes this requirement. Additional requirements may apply, and other transactions and jurisdictions can have different rules.

Use a change order to record the proposed additions or credits, time and payment effects, and required approvals. The change-order guide covers the decision and approval record in more detail. A revised estimate can support the price discussion, but it is not automatically an approved change order.

After the necessary approvals and start-work conditions are met, update the work order to identify the accepted scope and applicable changes. Tell the crew which documents to use and what remains outside their authority. Keep the earlier issued documents and approval history accessible to the office rather than overwriting them.

Sources

The linked FTC, NIST, ESIGN, California statute, and CSLB sources were reviewed October 30, 2026. The NIST example describes agency practice; the California example is jurisdiction- and transaction-specific.