The skill and its purpose
A proof version is more precise than a filename. The same name can be reused for changed bytes, while different filenames can contain identical data. A recorded content fingerprint helps distinguish those situations. Comments and decisions should remain tied to the version the reviewer actually saw. File identity does not establish print readiness or the reviewer’s authority.
Work through the decision
Record the artwork reference, version label, fingerprint, page or variant, review scope and creation date. Add comments against the exact reference. When a revised file arrives, create a new version rather than overwriting the old review. Compare the changes and reopen the affected decisions. A technical change and a wording change may involve different reviewers, but neither should inherit approval silently.
Practical exercise — fictional
A fictional agency sends poster-v3.pdf, then sends different bytes under the same filename. Use the file fingerprint tool or proof studio to distinguish them. Add one comment to the first version and identify the review state of the replacement. Export a record that preserves the earlier comment without describing the new bytes as approved.
Take it to the next job
- Record exact file identity as well as filename.
- Scope comments to page and version.
- Preserve earlier decisions when replacing bytes.
- Reopen only with attributable review authority.
Try the decision
The exercise stays in this session unless you choose to save it.
