An engineering drawing checker — with the tuning controls engineering work actually needs
Engineering drawings get reviewed against revisions constantly: P&IDs against the latest process flow, fabrication drawings against approved-for-construction sets, instrumentation drawings against control philosophy updates. PDFverifier automates the visual review and gives you proper sensitivity controls.
The thing that separates an engineering drawing checker from a generic PDF comparison tool is calibration. Real engineering drawings come from many sources — laser-printed master copies, scanned archive prints, modern CAD exports at different DPIs, vendor drawings rendered at varying quality. A tool with a single fixed sensitivity will be useless on at least half of these. PDFverifier exposes sensitivity as a controllable parameter and explains what it does, so you can dial it in for your specific drawing pair.
Drawing types this is built for
P&ID and PFD
Process and instrumentation diagrams — pipe runs, valve tags, instrument loops, control elements.
Piping isometrics
Routing, fittings, line numbers, dimensions, weld points.
Mechanical drawings
Part geometry, dimensions, GD&T, surface finishes, hole patterns.
Electrical schematics
Wiring, components, single-line diagrams, control logic.
Structural details
Connection details, rebar layouts, framing plans, weld symbols.
Fabrication drawings
Shop drawings, member sizes, cut lists, BOM tables.
Understanding the sensitivity setting
Sensitivity controls how much pixel-level difference is required before PDFverifier registers a change. Think of it as a threshold below which differences are ignored.
| Setting | Best for | What you sacrifice |
|---|---|---|
| Low | Two scans of the same physical print. Old archive drawings. Source images with visible scan noise. | Small real changes (a single line move, a tag character change) may be ignored. Use only when you're confident no critical details are subtle. |
| Medium | One CAD export vs one scanned drawing. Drawings from different revision numbers with significant rendering differences. | Subtle text-character changes may be missed (e.g. tag P-101 → P-102 might or might not be flagged). |
| High | Two CAD exports with identical export settings. Standard production workflow. | Some rendering jitter from different export passes can appear as false positives. Easy to dismiss during review. |
| Extreme | QA checks where you must catch every pixel — final approval before issue, regulatory review, claims documentation. | You'll get a lot of micro-detections. Plan to spend time dismissing rendering noise. |
The right setting is per-drawing. PDFverifier lets you set sensitivity individually within a multi-drawing batch — so a P&ID pair from clean CAD output can run at High while a mechanical sketch revised over a scan can run at Low, all in the same session.
A practical calibration approach
If you're unsure where to start, this is the workflow that converges fastest:
- Run at Medium first. Look at the change list. Are real changes you know about being caught? Are there obvious false positives?
- If real changes are missed — increase to High. Re-run.
- If false positives dominate — decrease to Low. Re-run.
- For QA / final issue checks — always run at Extreme, even if it's tedious. The cost of a missed change at issue stage is much higher than the cost of dismissing extra noise.
- Document the setting you used — it's part of the review record.
What the engineering review workflow looks like
Most engineering offices use the tool in roughly this rhythm:
- On revision receipt — run the comparison immediately, generate the change list, log it in the project register
- During internal review — distribute the annotated PDF as the review starting point; reviewers add comments per detected change
- Before issue — final QA run at high sensitivity to confirm no unintended changes slipped in during the revision cycle
- Post-issue archive — annotated PDFs stored alongside the issue package as a contemporaneous change record
Multi-discipline coordination check
If you're doing coordination work (e.g. checking that piping revisions don't conflict with structural updates), the workflow is slightly different:
- Run the comparison for each discipline separately (piping rev A → rev B, structural rev A → rev B)
- Overlay the resulting change lists in your coordination tool of choice
- Where two disciplines both flag changes in the same area, that's where you focus the coordination check
PDFverifier itself doesn't do cross-discipline coordination — but it produces the change-list inputs that make manual coordination much faster.
Test the calibration on your own drawings
Free previews are enough to evaluate the sensitivity controls on a real drawing pair.
Open PDFverifier →