Don't accidentally build the old blueprint

Drawings get re-issued constantly during construction. IFC. Rev 1. Addendum A. RFI 47 response. Each new package can contain changes that affect scope, cost or program — and a missed change usually ends in a rework or a claim. PDFverifier compares any two blueprint packages and lists every change.

This is the kind of tool that pays for itself the first time it catches a wall that moved 150 mm between IFC and Rev 1. The construction industry runs on the assumption that everyone's working off the latest revision — but the latest revision is usually a 70-page PDF that's only marginally different from the previous one, and "marginally different" is exactly the failure mode that produces a 200,000 SEK rework bill.

Who this is for — site engineers, BIM coordinators, project managers, foremen, MEP coordinators, structural engineers reviewing architectural changes for impact, and anyone whose job involves looking at one revision and producing instructions based on it.

Three real scenarios where this matters

Scenario A — The moved column

Architect issues Rev 1 of the GA. A column on grid C-4 moved 200 mm to align with a revised facade module. The structural drawings, also at Rev 1, were updated to match. The MEP drawings still show the column in the original position because the consultant was working in parallel and didn't pick up the change. A ductwork run is then designed through where the column actually is.

What PDFverifier would have caught: the column move on the architectural Rev 0 → Rev 1 comparison, in 30 seconds. The MEP team could have flagged the conflict before issuing.

Scenario B — The silent dimension change

A drainage detail shows a 150 mm fall over a 6 m run. After review, the engineer realises that fall needs to be 100 mm to clear a new beam. The dimension is updated. The drawing is reissued. The contractor's foreman scrolls through the new revision, sees the same detail they already worked from, and doesn't notice the number changed. Slab is poured to the wrong fall.

What PDFverifier would have caught: the dimension change highlighted in green on the new revision. Even a 30-second review of the change list would have surfaced it.

Scenario C — The addendum hidden in a 200-sheet reissue

The architect issues a full updated set for tender stage. There are 12 actual changes scattered across 200 sheets. Most contractors don't have the time to read all 200 sheets a second time — they spot-check based on the revision cloud markings. But two of the 12 changes have no revision cloud (the architect forgot to add one). Those changes are invisible to spot-check review and don't appear in any bid.

What PDFverifier would have caught: every single one of the 12, regardless of whether a revision cloud was added or not.

How the workflow fits into construction projects

Most useful checkpoints in a typical project:

When a new revision package arrives. Run the comparison immediately, before anyone starts working off the new set. The change list goes into your daily report or transmittal log.
Before issuing site instructions. Confirm the change you're about to instruct on is actually in the latest revision. Saves a lot of "we already changed that" conversations.
During tender review. Run the IFA-vs-IFC comparison to scope what tenderers need to price the addenda. Attach the change list to your tender bulletin.
As-built reconciliation. Compare the final issued set against earlier revisions to produce a clean change log for the project record.
Claims and disputes. When a contractor claims they built to an earlier revision, the diff between revisions is your contemporaneous evidence of what changed and when.

Working with full drawing packages

Blueprints rarely arrive as a single PDF. They're usually a folder or ZIP of dozens of sheets. PDFverifier handles this directly:

Upload the old set as one ZIP and the new set as another
The tool matches sheets between revisions by filename (e.g. A-101_RevA.pdf matches to A-101_RevB.pdf)
Each matched pair gets its own comparison page in the result viewer
Unmatched sheets (added or removed between revisions) are flagged explicitly
You can export the combined result as one annotated PDF for the whole package

Practical limit: about 100 sheets per package on a single comparison. Above that, split into logical groupings (architectural, structural, MEP) and run separately.

Run a blueprint revision check

Free preview — upload an actual revision pair from your current project and see what's been changing.

Open PDFverifier →