Quality checklist for comparing plan revisions
This checklist helps teams document results from visual PDF comparison in a reproducible, project-ready way.
Before the comparison
- Is it clear which version is reference (A) and which is new (B)?
- Are page size, order, and orientation comparable?
- Are filenames unambiguous (date, index, status)?
- Are there known export changes that may cause visual noise?
During the comparison
- Was standard mode used first and only adjusted when needed?
- Are markers reviewed technically, not only visually?
- Are critical pages prioritized (safety, cost, schedule)?
- Are text changes assessed separately from graphical changes?
After the comparison
- Are relevant findings documented with page references?
- Is it clear which differences are accepted and which require follow-up?
- Were exports and notes stored in the project filing system?
- Is the approval decision traceable for third parties?
Recommendation: Make this checklist a fixed step in your revision and approval process.
Short template for internal reporting
- Compared files: Reference A / New B
- Reviewed by: Name, date, project
- Checked pages: List or range
- Critical deviations: Yes/No + reference
- Approval recommendation: Release / Query / Correction required