How to Annotate a PDF for Client Review — Clean Proofing

You open the email. Attached: final_v9_FINAL_really.pdf. The client added ten red arrows in MS Paint and a single line: “make it pop.” That’s not feedback. It’s a starting pistol for more rounds.

Your job: turn chaos into direction. This guide shows how to annotate a PDF for client review so fixes are actionable, rounds are fewer, and approvals actually mean something.

Why sloppy PDF annotating costs you hours

A rough count: every ambiguous comment costs you 20–45 minutes. You parse it, make an educated change, send it back, wait 48 hours, then repeat. Two unclear rounds = 2–4 hours lost. Four unclear rounds adds up to a wasted day.

Bad annotations look like:

• scribbled arrows with no context
• “change this” with no location or spec
• comments spread across email threads and Slack

Good annotations are specific, tiny, and tied to the design element. They should answer: who, what, where, and why.

A PDF with ten 'fix this' arrows is a map to disaster. Replace it with ten clear pins and one approval note.

how to annotate a PDF for client review — step-by-step

1) Export a single-source PDF

Export a paginated PDF from your source file (Figma, InDesign, Illustrator). Name the file clearly: project-page-v3-2026-06-17.pdf. That date stamp saves guesses when clients say “you changed spacing.”

2) Set the ground rules before you share

Tell the client exactly how you want feedback: pin annotations to specify location, one comment per issue, and short video notes for interactions. You’ll sound like a pro and reduce vague asks.

3) Choose the right annotation method

Quick tool notes you’ll actually use:

• Adobe Acrobat: full feature set, but heavy and requires the client to know Acrobat.
• Mac Preview: fast for simple notes, but no versioned review flow.
• Figma: great when the file lives in Figma; not helpful if the client prefers PDFs.
• Email threads: terrible for locating comments.
• MS Paint markups: charming in spirit, disastrous in practice.
• ClientMarkup (/): lets clients open a share link with no account, pin/draw annotations, upload short screen recordings, and sign off with a typed signature—ideal if you want fewer cycles and an audit trail.

Pick the one your client can actually use. If the client can’t install software, use a web link.

4) Make each annotation functional

Every note should include:

• A precise pin (don’t say “header” — pin the exact pixels).
• A short summary: what to change and why. Example: “Increase H1 weight from 600 to 700 to improve scannability on mobile.”
• A priority label if it matters (must-fix, optional, editorial).

If the fix touches spacing, give a number: “Top padding +8px.” If it’s visual preference, show a quick 20–30s screen recording explaining the intent.

5) Group related changes and avoid nitpicking

If 12 text tweaks are all copy corrections, call them out in one “Copy edits” note and attach a short numbered list or replace the page with a revised PDF. Clients love to feel heard; they hate repetitive micro-comments.

6) Version everything and call the next step

After you make changes, upload a new PDF with a clear version label and respond to each pin with a resolution comment. Don’t leave comments unresolved. Add one “Ready for approval” pin when done and ask for a typed signature or an explicit “Approved” comment.

Real-world templates you can steal

• Quick UI tweak: Pin > “Reduce button radius from 8px to 6px for consistency with header.”
• Copy change: Pin to paragraph > “Replace sentence with: ‘Start your free trial today—no card required.’”
• Interaction note: Pin to CTA > attach 25s screen-record explaining tooltip timing and expected behavior.

Use short timestamps in recordings: “00:03 — hover state should delay 200ms.”

Handling clients who want to ‘draw it in’

If a client insists on freehand sketches, accept them, but follow up. Convert their sketch into a pinned action. Restate their intent in your own words and get confirmation. Example: “You sketched a dropdown here—do you want it to include these six options? If yes, I’ll add labels and send V4.”

Sign-off: make approval meaningful

A final approval should be a single explicit action. Ideally: a typed signature next to the final PDF and a timestamped confirmation. That prevents late-stage “oh, but change the footer” surprises.

If you want a lightweight option that handles pins, recordings, and a one-click approval without forcing clients to create accounts, try ClientMarkup. It’s what many freelancers use to collect client feedback and close the loop without hunting through email.

Rules I live by

• One issue per annotation. Keep the comment unit small.
• If it will take you less than five minutes, fix it and note the fix; if five minutes or more, ask for clarification first.
• Limit rounds: two rounds of annotated feedback, then a paid revision or an explicit approval.

Common mistakes and how to avoid them

• Mistake: uploading v12 without clearing resolved notes. Fix: maintain a review log with resolved/unresolved states.
• Mistake: letting clients annotate screenshots in Slack. Fix: migrate comments into a single PDF review session and summarize changes.
• Mistake: accepting vague language like "make it pop." Fix: ask what ‘pop’ means—contrast, scale, color saturation, or microcopy?

Final thought

You’ll never stop getting fuzzy, subjective feedback. Your job is to translate that fuzz into tasks. Pin precisely, write plainly, version obsessively, and make approval a real action. Do that, and you’ll spend less time arguing about spacing and more time designing the work that deserves to be shown.