Bluebeam, Procore, AutoCAD, Autodesk Docs, Fieldwire, Bentley ProjectWise, and Adobe Acrobat each ship a compare or overlay feature that highlights what changed between two drawing issues. By each vendor's own description, none of them checks whether the changed geometry still agrees with a door schedule, a specification section, or another discipline's sheet — that comparison has to happen somewhere else.
What "compare" means in seven tools
The table below paraphrases what each vendor's own current help pages say their tool does, and where that page's own wording draws the line. Every source was opened directly and accessed 2026-09-14.
| Tool | What it compares | Stated limit |
|---|---|---|
| Bluebeam Revu | Two PDFs: cloud-marked differences (Compare Documents) or merged, color-coded content (Overlay Pages) | Compare Documents suits scans; Overlay Pages needs clean vector content — running the wrong one on the wrong file type "won’t produce the desired result," per Bluebeam’s own instructions |
| Adobe Acrobat | Two versions of one PDF: a differences report, with a text-only mode | General-purpose PDF diff; no mention of reading a schedule row, a tag, or a cross-sheet reference |
| AutoCAD | Two DWG files, or two revisions of one, in model space | DWG only; model space only; does not support OLE objects, images, coordination models, point clouds, or comparing a result against a third drawing |
| Procore | Two uploaded versions of the same drawing number, overlaid with removed content in red and added content in blue | Drawings of different sizes cannot be compared, by Procore’s own support page |
| Autodesk Docs (ACC) | Two versions of a PDF or DWG, or two different files, in overlay or side-by-side view | Shows what is new, modified, or removed on the sheet; no stated schedule or specification cross-check |
| Fieldwire | Two sheets — two versions of one plan, or two different plans for coordination | Paid Pro/Business/Business Plus feature; unchanged content shown greyscale, differences in red/blue |
| Bentley ProjectWise | Matched DGN or DWG model pairs (with Saved Views) or IPARM/IPS plot sets | Detects actual element edits only — explicitly not appearance changes from symbology, plot-time scripts, view attributes, or color tables |
Pick your tool below for the source links and the worked example of what its comparison would and would not have caught.
A clean overlay is not the same question as a coordinated set
An overlay or compare tool answers one question: what is geometrically different between file A and file B. That is a real and useful question, and every tool above answers it well within its stated scope. It is a different question from whether the drawing still agrees with the door schedule, the specification section, or the other discipline's sheet that depends on it.
In Groundbook's published hotel review, the door-rating finding is exactly this shape: the door symbol on the plan had not moved between issues, so a sheet-to-sheet overlay would show no difference at that location. The disagreement was between the schedule's rating and the surrounding separation requirement — two documents that were never the two files loaded into the compare tool.
Use each tool for the half of the job it was built for
Keep your team's existing compare or overlay tool for what it is good at: a fast, familiar, already-licensed way to see what moved on a sheet, cloud it, and route it for response. Do not ask it to answer a question it was not built to answer.
For the dependent documents an overlay does not read, use a review scoped to that relationship: cross-discipline coordination for what another discipline's sheet needs to agree with, and drawings vs. specifications for the written requirement behind the drawn one. Groundbook's own drawing version comparison workflow, available to beta users on request, is built to trace a changed requirement into the schedules and specifications that depend on it rather than stopping at the sheet.
Pick your tool
Each guide sources its facts from that vendor's current help pages, dated 2026-09-14, and shows one published finding an overlay of that shape would not have caught on its own.