How to Compare Plan Revisions and Control Estimate Changes

To compare plan revisions, put the new sheet and the old sheet on the same screen or the same light table. Find every change, tie each change to a revision marker, and then price it. Do these four things in order: confirm which sheets were reissued, overlay or visually compare each one, log every difference with its sheet number and revision, and turn each cost-bearing difference into an estimate update or a change order. Skip one and the field builds from the wrong sheet, or you eat the cost of a change nobody wrote down.

This guide is for commercial subcontractors in the US. It covers the manual method, the digital method, and how to keep your estimate revision control tight. It also covers the limits of any comparison, because a clean overlay does not prove what is in the wall.

TL;DR

• Comparing drawings only finds the change. You still have to price it, notify the GC, and get it into the estimate or a change order.
• Revision control tracks formal, approved changes (Rev A, B, C). Version control tracks every working draft. Field crews should only ever build from the first.
• A revision cloud or delta is a hint, not a guarantee. Compare the full sheet, because not every change gets clouded.
• Keep one log: sheet number, old revision, new revision, what changed, who found it, and what it costs. That log is your evidence in a claim review.
• Drawings are diagrammatic. Field-verify hidden work and use RFI responses, not just overlays, for exact locations.

Table of Contents

• Why revision comparison costs subcontractors money
• Revision control vs. version control
• Compare plan revisions by hand: the reliable baseline
• Compare plan revisions digitally
• Estimate revision control: turning changes into numbers
• Why the audit trail matters in a dispute
• What a comparison cannot tell you
• Perspective: where we see revision control break
• A 30-minute routine for every new drawing issue
• Where Won2Build fits
• Common mistakes to avoid
• FAQ
• Sources

Why revision comparison costs subcontractors money

A revised set rarely arrives with a tidy list of what changed. It arrives as a new PDF, a bulletin, an addendum, or a handful of replacement sheets. The GC may cloud some changes and miss others. Meanwhile your estimator already priced the earlier set, your foreman already has a printed copy, and your crew is already laying out.

Three things go wrong:

1. Stale prints stay in the field. The old sheet is still in the trailer or on a phone, and someone builds from it.
2. Unpriced changes get absorbed. An extra run of conduit, a larger duct, or one more fixture type shows up in the revision. Nobody compares, so nobody bills.
3. The paper trail is thin. When the schedule or cost shifts, you cannot show which revision caused it, or when you first saw it.

The second one hurts most. We have written separately about how unbilled work builds up through scope creep, and plan revisions are one of the main ways it starts.

Revision control vs. version control

Subcontractors often use these terms as if they meant the same thing. They do not, and mixing them up is how crews end up building from a working copy.

• Revision control covers formal, approved changes to issued documents. These carry a letter or number in the revision block: Rev A, Rev B, Rev C, or a bulletin number.
• Version control covers every iteration, including drafts and markups that were never issued. These are often labeled V1, V2, V3.

The Revizto blog draws the same line. The practical rule for your office: anything that goes to the field must show a formal revision in the revision block. If a sheet has no revision block entry, or the entry does not match your log, stop and ask before anyone builds from it.

Compare plan revisions by hand: the reliable baseline

Even if you use software, know the manual method. It is what you fall back on when a GC sends a flattened scan or a photo of a markup.

Step 1: Build the sheet index first

Before you look at any line work, list every sheet in the new issue against every sheet in your current set. Note three things for each: sheet number, revision letter or date, and whether it is new, replaced, or deleted. Many missed changes are not line changes at all. They are a sheet that was added, or one that was dropped.

Step 2: Check the revision block and the cloud

Open the revision block on each reissued sheet. It should tell you the revision number or letter, the date, and a short description. Revision clouds and delta symbols mark where the designer says the change is. Per one drafting firm’s IFC guide, clouds, deltas, revision blocks or formal bulletins are all ways a job identifies what changed, so you may see any of them on one project.

Treat clouds as a starting point. Compare the whole sheet anyway. A designer who moves a wall three feet may cloud the wall and forget the dimension string, the door schedule, or a detail on the next sheet.

Step 3: Overlay or flip

If you can print both sheets, hold them over a light table or window with the title blocks aligned. If you work on screen, use a viewer that lets you toggle between two layers. Either way, check these areas on every reissued sheet:

• Dimensions and grid lines
• Schedules (doors, finishes, equipment, fixtures)
• Notes and general notes, which change quietly
• Legends and symbol definitions
• Section and detail references that now point to different sheets

Step 4: Mark the superseded set

Stamp the old sheet as superseded right away, or move the file to a dedicated Superseded folder. A quality control procedure published by a UK town council recommends exactly this, along with naming electronic files by drawing reference and revision only, for example A-101-RevB. It is a UK document, but the habit works on any US job. Keep the old sheets. You need them to prove what changed.

Step 5: Write the change log

For each difference, record a single line. Use this format:

The example is illustrative, not drawn from a real project. The point is that every row names a sheet, a revision, a quantity, and an action.

Compare plan revisions digitally

Digital comparison speeds up Step 3. Tools that offer sheet comparison typically work in one of two ways. One is a stacked overlay with adjustable opacity. The other is a difference view that colors what was removed and what was added. Fieldwire’s help center describes this kind of side-by-side or stacked comparison, and notes that it can be used on two versions of the same plan or on two different plans. Whatever tool you choose, ask these questions before you rely on it:

• Does it align sheets automatically? If scales or sheet sizes differ between issues, a bad alignment shows false changes everywhere.
• Does it work on scanned or flattened PDFs? Many GC issues are not clean vector files.
• Can the whole crew see the result? A comparison on one estimator’s laptop does not protect the field.
• Does it connect to your pricing? Finding a change in one app and retyping it into another is where errors enter.

That last point is where most subcontractors lose time. You find the change, then rebuild the quantity in a spreadsheet, then email the PM, then someone remembers to open a change order a week later.

Estimate revision control: turning changes into numbers

Comparing sheets answers “what moved.” Estimate revision control answers “what does it cost, and what did we price before.” The two need to stay linked.

Keep every estimate as a numbered revision

Do not overwrite the original bid. Save it as the baseline, then create Estimate Rev 1, Rev 2 and so on, each tied to the drawing revision that triggered it. Your estimate revision log should mirror your drawing log. When someone asks why the number moved, you point to the sheet, the revision, and the quantity delta.

Re-measure only what changed, but prove it

On a revised sheet, re-measure the affected areas rather than the whole set, and keep the old and new quantities side by side. That is the evidence behind a claim. Our walkthrough on a PDF takeoff workflow for tracking revisions lays out five steps for doing this without losing the original count.

Decide: absorb, revise the bid, or change order

Not every change deserves the same response. Use this rule of thumb:

Check your own subcontract for notice deadlines before you rely on a rule of thumb. Notice windows differ by contract, and missing one can cost you the claim. If you are unsure how a clause applies to a specific revision, ask a construction attorney licensed in your state.

We cover the timing side in same-hour notices for change orders and the paperwork side in a same-day change order documentation checklist.

Why the audit trail matters in a dispute

A claim review does not ask who was right in general. It asks who knew what, and when. Practitioners emphasize recording who made each revision, what changed, and when, because that record is what lets you show why cost or schedule shifted. Revizto’s guidance on drawing management makes that point about revision control.

For a sub, the audit trail has four parts:

1. The date you received each revision, and from whom
2. The comparison showing what changed
3. The estimate or change order that priced it
4. The notice you sent and the response you received

If any part lives only in someone’s inbox, assume you will not find it when you need it.

What a comparison cannot tell you

A perfect overlay still compares two drawings, not two buildings. The AIA-MBA Joint Committee notes that most construction drawings are diagrammatic, and it recommends using the term “Record Drawings” instead of “as built.” In plain terms: the sheet shows design intent, not exact installed locations.

Three practical consequences for your crew:

• Do not imply your drawings show exact field conditions. Your shop drawings and markups carry the same limitation.
• Field-verify hidden work. For piping, conduit, and anything going behind a wall or above a ceiling, confirm locations in the field and document them.
• Use RFI answers and field sketches as the controlling record where precise location matters, not a generic overlay.

Contract language reinforces the duty to compare. The AIA A201-2017 general conditions require the Contractor, before starting each portion of the Work, to study and compare the various Contract Documents relating to that portion. Subcontract agreements commonly flow that duty down, so read yours. A missed conflict between two sheets can become your cost if you did not raise it.

Government work follows its own process. If you work on federal jobs, the Construction Contract Modification Process for equitable adjustments under FAR 36.211(b)(1) starts with a problem discovered in the field and an investigation, which is the same discipline your revision log supports.

Perspective: where we see revision control break

We build Won2Build for commercial subcontractors, so we look at this problem from the sub’s side of the table. Here is how we see it.

The comparison is rarely where the money leaks. Most estimators can find a moved wall. The leak is the handoff: the change is found on Tuesday, the quantity sits in a spreadsheet, the field hears about it by phone, and the change order is written two weeks later, if at all. Every gap between those steps is a place where margin disappears.

That is why our suite is built around one login. Takeoff handles digital plan quantification. Bid Track handles bid management and estimating. CO Hub handles change orders and T&M tickets. Time Budge handles labor tracking. A quantity measured in one place should not have to be retyped in the next, and the field and office should see the same data. We designed it around what a working subcontractor actually has to do between the plan revision and the invoice.

Our advice is simple. Pick one revision log and make everyone use it. Treat every reissued set as a pricing event, not just a document-control event. And keep your proof close to the work, because the sub who can show the sheet, the date, and the quantity usually gets paid.

— Jen Reese

A 30-minute routine for every new drawing issue

Use this when a revised set lands. It works with paper, PDFs, or software.

1. Minutes 0 to 5: Log receipt. Record date, sender, and what the transmittal says is included.
2. Minutes 5 to 10: Build the sheet index. Mark each sheet new, replaced, deleted, or unchanged.
3. Minutes 10 to 20: Compare each replaced sheet against the old one. Do not trust clouds alone.
4. Minutes 20 to 25: Write change log entries and flag the ones with cost or schedule effect.
5. Minutes 25 to 30: Pull the superseded sheets out of circulation and send the current set to foremen with the log.

Pricing happens after that, but you now have a defensible list. For a larger job, give one person ownership of the log. Shared ownership usually means nobody owns it.

Where Won2Build fits

If your revision process runs on spreadsheets and email, the weak point is usually the handoff between takeoff, estimate, and change order. Takeoff lets you measure digital plans, and it is listed at $0 per month on our pricing page. CO Hub, which manages change orders and T&M tickets, is $59 per month per company. Bid Track, for bid management and estimating, is $199 per month per company, and Time Budge, for labor tracking, is also $199 per month per company. Active field workers are billed at $2 per month each where a module counts them. You can subscribe to individual apps or to the whole Won2Build Hub under a single sign-on. If you are moving off spreadsheets, our pilot plan for replacing construction spreadsheets shows how to start with one project.

Common mistakes to avoid

• Trusting the cloud. Compare the full sheet.
• Comparing only plans. Specifications, addenda and schedules change too.
• Overwriting the baseline. Keep the original bid and every revision.
• Letting old prints live. Remove superseded sheets from the field the same day.
• Waiting to notify. Late notice is a common reason valid change orders go unpaid. Our guide to 48-hour change order management shows a tighter cadence, and the backlog article shows what slow handling costs.
• Skipping the field conversation. If the field cannot reach the office quickly, problems surface late. See our 30/60/90 plan for field-to-office communication.

FAQ

What is the fastest way to compare two versions of a plan sheet?

Overlay them, either on a light table or in a viewer that stacks or color-codes differences. Then check the revision block and any clouds to confirm what the designer says changed. Still scan the rest of the sheet, since not every change is marked.

What is the difference between a revision and a version?

A revision is a formal, approved change to an issued document, usually marked Rev A, B, C. A version is any working iteration, including drafts that were never issued. Crews should build only from formally issued revisions.

How do I keep estimate revisions organized?

Save the original bid as a baseline and create a numbered estimate revision for each drawing revision that changes scope. Record the sheet, the old and new quantities, and the cost effect. That gives you a clear answer when someone asks why the number moved.

Does a plan comparison prove what was built?

No. Most construction drawings are diagrammatic, so an overlay shows design changes, not installed conditions. For hidden work, rely on field verification, RFI responses, and documented field sketches, and talk to your attorney if a dispute turns on location.

Sources

• Drawings and Specifications, AIA-MBA Joint Committee
• IFC Drawing Guide: Issued for Construction for Projects
• Drawing management: How to organize, version, and distribute 2D sheets, Revizto
• Quality Procedure: Control of Contract Construction Drawings
• How to Compare Plans, Fieldwire Knowledge Base
• AIA Document A201-2017, SCOSE Version
• Construction Contract Modification Process, FAR 36.211(b)(1)

Recommended

• Construction Estimate Accuracy: AACE Ranges, QRA, and EVM Checks
• Construction Estimating Best Practices 2026: Field Guide
• Stop Unbilled Work: 5 Step Scope Creep Control for Subcontractors
• The Change Order Approval Process, Step by Step