Catch every change between drawing sets
Direct answer. Helonic compares two issues of a construction PDF drawing set and lists what changed, sheet by sheet, including changes nobody clouded. Each finding names the sheet, the location, and the change. Added, removed, and renumbered sheets are listed separately, and the drawings can be checked against the specs and schedules in the same pass.
Helonic is an AI construction drawing analysis platform for preconstruction teams using Helonic for revision comparison.
Compare drawing revisions to identify what changed between versions. Helonic catches the unclouded modifications that humans miss and gives you the scope of every revision before the next coordination meeting.
Why does revision tracking matter?
Unclouded changes between revisions reach the field as the wrong wall, note, or opening because the team thought nothing moved on that sheet.
| Figure | What it measures |
|---|---|
| 65% | Changes that go unclouded between revisions (PlanGrid) |
| $50K+ | Average cost of missed changes, per miss |
| 15-20 | Average revisions before construction (AGC) |
| 25% | RFIs from tracking failures (FMI) |
How does Helonic go from two versions to a change report?
Drop in the old and new sets and Helonic diffs them sheet by sheet, including changes the designer never clouded.
- Upload both versions. Upload your previous drawing set and the new revision. Helonic matches sheets automatically by number and title.
- AI comparison. Our AI compares each sheet pair, identifying visual and textual differences across every element.
- Change classification. Changes are sorted by type, dimensional, material, layout, notes, and administrative.
- Difference report. Get a sheet-by-sheet breakdown of what changed, including the unclouded modifications that humans miss.
What types of revision changes does Helonic detect?
Helonic detects both clouded revisions and silent edits to geometry, notes, dimensions, and schedules.
Clouded Changes
- Revision clouds and deltas
- Updated revision blocks
- New or modified details
- Changed dimensions within clouds
Unclouded Changes
- Modified dimensions without clouds
- Changed notes or keynotes
- Moved or deleted elements
- Material or finish changes
Layout Changes
- Wall relocations
- Door or window moves
- Equipment repositioning
- Room configuration changes
Administrative Changes
- New sheets added
- Sheets removed or superseded
- Title block updates
- Sheet renumbering
Where do teams use revision comparison?
Teams use it at each CD milestone, after addenda, and before issuing for construction so the field is not building from an assumed delta.
- Bid to Award Comparison. Compare the bid set against the contract set to identify scope changes before signing.
- Milestone Reviews. Track changes between 50%, 90%, and IFC sets to understand design evolution.
- ASI / Bulletin Review. See exactly what an ASI changes without manually flipping between versions.
- Subcontractor Updates. Show subs exactly what changed in the latest revision that affects their scope.
What is the unclouded change problem?
Design teams are supposed to cloud all changes between revisions. In reality, changes slip through unclouded. A dimension changes, a note gets modified, a door swings the other way, and there is no cloud to flag it.
This is dangerous. Contractors price based on one set, then build from another. If they miss an unclouded change, it becomes a field problem, a claim, or at minimum, a heated conversation about who should have caught it.
Helonic catches what humans miss. Our AI compares every element on every sheet, identifying changes whether they are clouded or not. You know exactly what changed between versions.
How is Helonic different from a Bluebeam overlay or visual diff?
Bluebeam's overlay and compare tools show where two sheets differ visually, and Helonic tells you what the difference is. Bluebeam Revu can layer two pages in different colors or cloud the areas that changed, and it is the right tool for markup.
| PDF overlay | Visual compare (auto-cloud) | Helonic | |
|---|---|---|---|
| What you get | Two sheets layered in two colors | Clouds around areas whose pixels differ | A written list of changes and conflicts, each tied to a sheet and location |
| Sheet matching | You pick the sheet pair and align it | You pick the sheet pair and align it | Sheets matched by number, title, and content, even when the order changed |
| Says what changed | No. You read the colors | No. You read inside each cloud | Yes. A dimension, note, tag, or element, described in words |
| Noise from title blocks and reflow | High when text shifts or the sheet is re-plotted | High when text shifts or the sheet is re-plotted | Lower, because it compares content rather than pixels |
| Checks drawings against specs and schedules | No | No | Yes |
| Who reads the result | The person who ran the overlay | The person who ran the compare | Anyone on the team, or straight into Procore or Autodesk as RFIs |
Many teams keep Bluebeam for markup and use Helonic to find what needs marking up. The full breakdown is in Helonic vs Bluebeam. For the manual method with light tables, overlays, and clouds, see how to compare drawing revisions.
Can you compare drawings against specs and schedules?
Yes, and an overlay cannot help here, because the two documents do not look alike. A spec section and a floor plan share no pixels, so the comparison has to read both.
- A door hardware set, fire rating, or finish on the drawings that the spec section describes differently.
- Door, window, and finish tags on plan with no matching schedule row, or schedule rows that never appear on plan.
- Equipment in the mechanical or electrical schedules that does not match what is drawn.
These checks are covered in specification analysis and schedule verification.
What does Helonic not compare?
Helonic compares 2D PDF drawing sets, specs, and submittals, not BIM models or CAD files. To diff two Revit models or two DWG files, use the authoring tool's own compare.
It also does not redraw sheets, calculate quantities from the changes, or decide which version is right. It tells you what changed and where the documents disagree, and your team makes the call. For a full review of a single set, see AI construction document review.
Frequently Asked Questions
How does Helonic compare two drawing revisions?
Can Helonic find drawing changes that were not clouded?
What kinds of changes does a revision comparison report show?
Does revision comparison catch sheets that were added, removed, or renumbered?
When should a GC run a drawing revision comparison?
How is Helonic different from Bluebeam's overlay and compare features?
Can Helonic compare drawings against the specifications?
Does Helonic compare CAD files or BIM models?
Milind Sagaram
Co-founder & CEO, HelonicMilind is the co-founder and CEO of Helonic, where he leads product and go-to-market for AI-powered construction drawing analysis. He works closely with general contractors, project managers, estimators, and owners to understand how drawing quality drives project outcomes - and where AI can reduce RFIs, change orders, and rework. Milind has interviewed hundreds of construction professionals across project delivery roles, from preconstruction estimators at ENR top-400 contractors to facilities directors at institutional owners, and uses those conversations to shape both product direction and the way Helonic talks about the work.
- Construction project delivery and preconstruction
- RFI and change order economics
- Owner and GC workflows for drawing QA/QC
- Estimating risk and bid-stage scope assessment
How this page was researched: Unclouded-change figures from PlanGrid, revision counts before construction from the AGC, and the share of RFIs traced to revision tracking failures from FMI. Change detection is built around the standard convention of marking revisions with clouds, deltas, and revision blocks, and around the changes that are issued without them.
Last reviewed by Milind Sagaram · October 2026