AI Software for Construction Drawings: Catch Changes Between Revisions

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Software for Construction Drawings: Catch Changes Between Revisions.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Software for Construction Drawings: Catch Changes Between Revisions.

Yes, for what is drawn. Overlay and compare tools, some now labelled AI, line up two revisions of a sheet and colour what was added or removed, and the better ones score each sheet by how much changed. They show differences, not importance, so a person still reads each flagged sheet and writes the change list.

They flag noise too, such as a changed title-block date or an estimator's old markup, and they miss anything that never reaches the PDF: specification updates, addenda, and the knock-on effect of one trade's change on another's. Most of the value is in the routine around the tool: what you feed it, which baseline you compare against and who signs the list.

Follow me on Instagram@sagnikteaches

Four kinds of comparison, and what each one actually does

The word AI on a comparison page can cover very different machinery. This is what I could confirm from vendor pages in November 2026, with prices in USD.

Connect on LinkedInSagnik Bhattacharya
KindWhat it doesWhat it needsWhere it misleads
Overlay (Bluebeam Revu's Overlay Pages)Stacks two PDFs in different colours: the first revision red, the second green, shared lines near blackCore plan or above ($330 a user a year); works best on vector PDFs; Page Align, Auto Align to find alignment points automatically, or Manual Align on three anchor pointsA misaligned page shows everything as changed
Compare documents (Revu's Compare Documents, Acrobat Pro's Compare files)Marks differences: Revu with markups on each difference, Acrobat with a summary report and a mode for scanned documents and drawings that compares pixelsRevu says it suits scanned images better than overlay does; Acrobat has a text-only optionScan quality and reflowed text create noise
AI-scored set comparison (Bluebeam Smart Overlay)Matches sheets across two versions of a set by title block, shows red and green differences and gives each sheet and discipline a percentage scoreMax plan ($590 a user a year, an introductory price); PDFs only; labelled preview; files go to Bluebeam's cloudScale or alignment differences show as changes; matching fails if sheet numbers differ; the download is a rasterised PDF
Chat assistant (ChatGPT, Claude, Gemini)Compares text you paste, such as drawing index entries and revision notesAn ordinary plan; the data terms matterDense linework and tags are easy to misread, and it may guess

Smart Overlay and its sibling Smart Review sit under Revu's Batch menu and open their results in Bluebeam on the web. Smart Review checks one set for things like missing sheets and mismatched tags, which is a completeness check rather than a revision comparison. If your drawings already live in a project platform, look in its sheet viewer for a compare or overlay view before paying for a separate tool. The details are on Bluebeam's own Smart Overlay help page.

Subscribe on YouTube@sagnikteaches

Prepare both revisions so the tool gets a fair comparison

Most bad comparisons are bad inputs. Bluebeam's own preparation guide for Smart Overlay is a good checklist for any tool, and it explains why so many first attempts light up red and green from corner to corner.

  • Vector PDFs where you can get them. Bluebeam's overlay help says Overlay works well on vector PDFs and points scanned drawings to Compare Documents instead, and its Smart Review page warns that low-quality scans hide issues and raise false alerts. Ask for PDFs exported from the source files, not printed and re-scanned.
  • Same page size and scale in both revisions. Bluebeam states that differences in scale or alignment will appear as changes, and its Smart Overlay help page offers no alignment option of the kind Overlay Pages has.
  • Unique, consistent sheet numbers. Smart Overlay matches sheets between versions by reading title blocks, so numbers must match across versions and the block must not be covered by a markup.
  • Flatten or remove markups on the old revision. Anything you drew on Rev B will show up as a change.
  • Keep within the limits. Bluebeam's page gives under 1.75 GB in total and 2,000 pages per version for Smart Overlay; split bigger sets into batches.
  • Name files so you can find them again, such as A-201_RevB_2026-09-14.pdf, and keep the originals untouched beside the comparison output.
The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

A comparison routine in eight steps

  1. Name the baseline. It is the last revision you priced or built from, which is not always the previous issue (more on that below).
  2. Collect the new issue with its transmittal. The architect's list of changed sheets and any revision notes are your cross-check.
  3. Prepare both sets as above: same format and scale, markups removed, file names clear.
  4. Run the comparison on the whole set, in batch where the tool allows, not only on the sheets the list says changed. The sheets nobody mentioned are where surprises sit.
  5. Sort the results. Read the sheets with the most differences first, but also open every sheet the transmittal names, even if the tool shows nothing on it. A disagreement between tool and list is the thing to chase.
  6. Read each flagged sheet at full size and tag every difference as a design change, noise or unclear. For design changes, write what, where (grid reference or room name) and what it affects.
  7. Reconcile with the transmittal. Changes that are not on the list get a written query. Changes on the list that the tool missed get a second look, because a text-only edit can be tiny.
  8. Issue the change list, then reprice or rebuild what it touches, and archive both PDFs, the comparison output and the list together.

Steps 5 to 7 are where the time goes, and no tool takes that time away. What the tool changes is where you look first, and how few sheets you read blind.

Rev B to Rev C on a 42-sheet fit-out: what the overlay flagged

A four-person general contractor priced a small commercial fit-out from Rev B of a 42-sheet set. Rev C arrives with a transmittal that names 7 changed sheets: A-102, A-201, A-301, A-502, M-201, P-201 and E-201. The contractor runs an overlay on all 42 sheet pairs. Everything below is illustrative.

What the overlay showedSheetsWhat the person found
No visible difference24Nothing to read
Differences that are real design changes9All 7 named sheets, plus A-401 and E-301, which the transmittal did not name
Title block only4Issue date and revision letter updated; no drawn change
Whole sheet lit up after re-export2Page margin shifted slightly; re-exported and compared again, no real change
Contractor's own markups3Estimator's Rev B notes left on the old set; removed and re-run
Total flagged18

Eighteen flagged sheets sound like a lot, but only nine needed reading for content, and the rest took a minute each to dismiss. The two sheets nobody had mentioned are the point of the exercise. On A-401, a ceiling height note changed from 9 ft 0 in to 9 ft 6 in. It is one line of small text with a tiny red and green smudge around it, easy to flip past in a manual compare. With 640 ft of partition running to ceiling, six inches is 320 sq ft on each face, or 640 sq ft over two faces, which at an illustrative $3.50 a sq ft installed is $2,240 that the Rev B price did not contain.

The time sum is plainer. A manual flip-through at about 4 minutes per sheet pair is 168 minutes for 42 sheets. The overlay run takes about 10 minutes to set up and run, reading the 9 sheets with real changes at 6 minutes each is 54 more, and dismissing the other 9 at a minute each is 9, so 73 minutes in all. The change list takes about 40 minutes either way. That saves roughly 95 minutes per revision, about $71 at $45 an hour, and the real gain is that sheets such as A-401 get seen at all. On a job with six revisions the saving is modest in cash and large in reliability.

Reading the output without being fooled by it

In the example on Bluebeam's overlay help page, the first revision is converted to red and the second to green, and where the same line exists in both they stack into a dark, nearly black line. Red therefore means present only in the old revision, so removed, and green means present only in the new one, so added. Smart Overlay uses the same red and green for version one and version two. A moved item shows as both: a red door at the old position and a green door at the new one. Pairs like that are one change, not two.

  • A thin halo around every line is misalignment, not change. If a whole sheet shows it, re-export or realign before you read anything.
  • A percentage score is a reading order, not an importance rating. Smart Overlay scores each sheet and discipline, and lower percentages mean more differences. A sheet at 99% can hold the one changed note that matters, like A-401 above.
  • Text changes look like specks. Zoom in on every coloured mark near a note, tag or schedule cell. A second pass with a text-only compare (Acrobat's Compare files has one) is a cheap way to catch edits to words.
  • Sheets that exist in only one revision need their own look. A new, deleted or renumbered sheet has nothing to be compared with, so find out how your tool reports it (some list it separately, some leave it out) and read it yourself.

What the tool cannot see

  • Specification and addendum changes. They are not on the drawing, and they move prices just as much. Read them separately every time.
  • Knock-on effects on other trades. A wall moved on an architectural sheet changes a duct route and a conduit run. Smart Overlay matches each sheet with its own earlier version by title block and sheet number, so E1.01 is compared with the old E1.01, never with M1.01, and an architectural change never shows on the mechanical sheets it affects. Someone has to walk the architectural changes across the other disciplines.
  • Meaning without linework. A note that changes from by others to by contractor is a few characters of text and a speck of colour, with a large price attached.
  • Changes that never print. The PDF holds what was plotted. Hidden layers, switched-off items and anything that exists only in the model never appear.
  • Intent and impact. The tool cannot tell whether a change was meant, whether it was agreed, or what it costs. An unclouded change might be a deliberate redesign or an accident, and only the designer can say.
  • Renumbered or split sheets. If numbers do not match across revisions, the title-block matching fails, and you are back to comparing by hand.

The change list, filled in

The comparison is only useful once it ends in a list that estimators, project managers and subcontractors can act on. These rows continue the fit-out example, with one subcontractor in each corner: a furniture maker for the reception counter, plus mechanical, plumbing and electrical subs.

SheetWhereChange, Rev B to Rev CAffectsAction
A-102Grid C-D/3Partition moved 2 ft east; store room smallerDrywall, ceiling grid, door positionReprice; confirm door D5 location
A-301Reception counterDepth increased from 24 in to 30 inJoinery subcontractor, flooring cutAsk the furniture maker to requote
A-401Ceiling noteHeight raised from 9 ft 0 in to 9 ft 6 in; not cloudedPartitions, ductworkQuery architect; about $2,240 at risk
M-201Grid B/4Duct drop moved to clear the new partitionMechanical subNotify mechanical sub
P-201Room 104Sink moved 3 ft; waste run lengthenedPlumbing subNotify plumbing sub; recount affected run
E-301Panel schedule, row 14Circuit rating changed; not cloudedElectrical subQuery architect

For an unclouded change, the query can be short and neutral:

Sheet A-401, ceiling height note: Rev B shows 9 ft 0 in and Rev C shows 9 ft 6 in. The change is not clouded and is not listed on the Rev C transmittal. Please confirm it is intended and whether it applies to the whole floor.

The query states what the drawings show and asks. It does not accuse anyone of an omission, and it leaves a dated record that the question was raised before pricing. Once a change is confirmed, pricing it is a separate job; turning site messages and changes into change orders covers the paperwork, and the affected quantities need retaking, which the plumbing takeoff checks show how to test.

Using a chat assistant on the paperwork, not the drawings

A chat assistant earns its place on the text around the drawings: the drawing index, the transmittal and the revision descriptions. Paste those in as text and ask it to compare. Do not ask it to find changes on a plan, and tell it not to guess.

Below are the drawing index entries for Rev B and Rev C of a set, copied as text. Compare them.
List: sheets added, sheets removed, sheets whose number or title changed, and sheets whose revision description changed.
Do not guess what changed on a drawing. If a revision description is vague, put the sheet under "needs checking" and quote the description.

REV B INDEX
A-201 Floor plan level 1 | Rev B | Issued for tender
A-301 Reception elevations | Rev B | Issued for tender
A-401 Reflected ceiling plan | Rev B | Issued for tender
A-502 Door schedule | Rev B | Issued for tender

REV C INDEX
A-201 Floor plan level 1 | Rev C | Partition revised, see cloud
A-301 Reception elevations | Rev C | Counter depth revised
A-401 Reflected ceiling plan | Rev B | Issued for tender
A-502 Door schedule | Rev C | Updated per RFI 14
A-503 Door hardware schedule | Rev C | New sheet

An illustrative reply: added, A-503; removed, none; number or title changed, none; revision description changed, A-201, A-301 and A-502. Needs checking: A-502, because "Updated per RFI 14" does not say what changed, and A-201, because "see cloud" refers to a cloud on the drawing that is not in the text. A-401 is unchanged on the index.

What you would fix: without the no-guessing line, a typical reply adds something like "A-502: door schedule updated with new hardware types", which is invented. The line forbidding guesses, and the "needs checking" bucket, are there to stop that. Then look at the last line. The index says A-401 is still Rev B, yet the overlay showed a changed ceiling note on A-401. A sheet whose content moved without its revision letter moving is the kind of silent change that matters, and neither tool alone would have raised it. The assistant compared words, the overlay compared drawings, and the gap between them is the finding. Try any assistant on two sheets where you already know every change before you trust it with more, and check what its plan does with uploaded files first. The drawing issue register and transmittal log from the architect's side shows why the index is worth keeping tidy.

Compare against the last revision you priced

The classic failure is a baseline slip. The contractor above priced Rev B. Rev C arrived, was compared as shown, and the three biggest changes were queried but not formally repriced while the architect replied. Two weeks later Rev D arrived. The estimator compared D against C, the previous issue, and found three further changes, which went into a revised price. The Rev C changes never did: roughly $2,240 for the ceiling height, $1,150 for the moved partition and $900 for the deeper counter, $4,290 in all, invisible in a C-to-D comparison because they were in both.

The rule is to compare the newest issue directly with the baseline you priced, here B to D, and then step through the intermediate revisions to see why things moved. The two views answer different questions. The direct one tells you what to price. The stepwise one explains it, and it can show reversals: if the door on A-102 changed from D3 to D5 in Rev C and back to D3 in Rev D, the direct comparison shows nothing, and you would have wasted time pricing the change. Label each saved comparison with the pair it covers, such as B-to-D, so nobody mistakes it for the last step.

Cost, data handling and sign-off

On cost, Bluebeam's pricing page lists overlay and compare from the Core plan at $330 a user a year, and lists Revu as a Windows desktop application with web and mobile access on every plan, so check that fits your team's computers. Its AI transparency page says Auto Align, which finds alignment points between two PDFs, runs on Core and above, with all processing on your machine. Smart Overlay is on the Max plan at $590 a user a year, shown as an introductory price, and is in preview. That page says Smart Overlay uploads PDFs to Bluebeam's servers to generate results, names the region where it processes them, and lets an administrator switch the feature off. Bluebeam's Max page answers its own question on how it uses AI and data by pointing to that AI transparency page, which, when I read it, did not say whether customer drawings train models, so read it and the terms of use against your contract, and ask in writing if you need a direct statement. Max also offers a connection from Revu to an AI assistant. Bluebeam's page says that, with your permission, it shares prompts, PDF text, markup data and file metadata with the assistant, so the assistant's own data terms then apply.

Drawings often arrive under confidentiality terms, so settle what may be uploaded to any cloud tool, a chat assistant included, before you start. Smart Overlay's downloaded comparison is a rasterised PDF, so keep the original vector PDFs next to it.

For sign-off, name one person who owns each change list, normally the estimator or project manager who priced the job, and have them date it and record the revision pair it covers. The tool narrows where they look; the signature says they looked. The same discipline applies on the architect's side, and sheet checks and schedules with AI sets out what a designer can check before issue. Once the list is agreed, reviewing the plans for scope gaps is a sensible second pass on the sheets that changed.

Drawing revision comparison: common questions

Can ChatGPT or Claude compare two drawing PDFs reliably?

Not reliably. Chat assistants can compare text you paste in, such as drawing index entries and revision notes, but dense linework and small tags are easy for them to misread. Test any assistant on two sheets where you already know every change before trusting it with a set, and never let it guess what a vague revision note means.

How do I stop the tool flagging everything as changed?

Align first. If a re-exported sheet shifted or changed scale, every line shows as different. Use the tool's alignment option where it has one, export both revisions from the same source at the same scale, keep sheet numbers consistent, and flatten markups before comparing. If a sheet still lights up end to end, re-export it instead of reading it.

Which revision should I compare against?

The last one you priced or built from, not just the previous issue. Compare that baseline directly with the newest revision, then step through the intermediate ones to see why things moved. A change made in one revision and reversed in the next shows up in the stepwise view but disappears in the direct one.

Do I need the top Bluebeam plan for revision comparison?

Not for a basic overlay. Bluebeam's pricing page lists overlay and compare from its Core plan, while Smart Overlay, which scores sheets by discipline, sits on the Max plan and is labelled preview. Check what your current plan and any project platform you already use include before buying something new.

Further reads

Sources: Bluebeam pricing, Smart Overlay, Overlay Pages and AI transparency pages, and Adobe Acrobat compare help, all read in November 2026.

Want revision checks built into your bid routine?

On a 1:1 call we'll look at how drawing revisions reach you now, set up a compare-and-sign-off routine your estimators can run, and decide where AI helps and where a person must read.

Book a 1:1 call with me