what_you_need
Prepare the inputs before opening the apps
- Clean review-ready PDF masters
- Approved proof wording such as DRAFT or CLIENT PROOF
- A client/project naming convention
- A dedicated proof-output folder
step_by_step
The working process
-
1
Freeze the review source
Identify the exact version being sent for review and keep it in the clean-master folder. Do not watermark the only copy or continue editing an ambiguously named source.
-
2
Choose unmistakable temporary wording
Use a short status such as CLIENT PROOF, DRAFT, or NOT FOR PRODUCTION. Include a project or date only when it will remain readable and useful.
-
3
Design for review readability
Use Batch Watermark PDF to set a visible but not obstructive opacity, diagonal rotation, and centre or tiled placement. Avoid covering text that the client must approve.
-
4
Preview difficult pages
Check dark artwork, blank pages, full-bleed pages, and pages with essential small text. Adjust colour, opacity, placement, or above/below layering as needed.
-
5
Create and name the proof set
Write outputs to a project-specific proof folder. Include `proof` or a review round in filenames so nobody mistakes them for clean or approved files.
-
6
Remove the mark only from approved delivery
After approval, return to the clean master and produce the final deliverable. Never try to remove a temporary mark from the proof as the final-production workflow.
human_checkpoint
Review before you call it finished
- Does every shared file clearly say it is a proof?
- Can the client still review all essential content?
- Are review round and filename unambiguous?
- Will the final file be regenerated from the clean master?
honest_boundaries
Limits and privacy
Practical limitation
A proof watermark reduces accidental confusion; it cannot stop a recipient from capturing or reconstructing visible content and should not be treated as access control.
Privacy boundary
Proof generation stays local. Sharing occurs only through the channel you choose after reviewing the watermarked copies.
faq
Questions worth answering
Should I watermark the master file?
No. Keep a clean master and create a separate proof derivative so final delivery remains reproducible.
Does a proof mark prevent unauthorized use?
No. It communicates status and discourages confusion, but it is not a technical access-control system.