How to annotate PDFs for client review (without the email chaos)

PDF review has a particular flavor of chaos that designers know intimately. The client downloads the PDF. They open Preview or Acrobat. They add sticky notes in Comic Sans. They email it back. The next version comes in as a new PDF with a different name. By revision 3, there are three PDFs in the thread and nobody is sure which one reflects the current state.

The problem isn't the PDF format. PDFs are excellent deliverables. The problem is the review mechanism: emailing files back and forth with annotations baked into the document is a workflow designed in 1995 that has not been updated.

What a good PDF review workflow looks like.

The deliverable is a PDF. The review happens on a shared canvas. The client opens a link, sees the PDF rendered page-by-page, and clicks any element to drop a comment pin. The comment is tied to a specific page, a specific position, and a specific version of the document. Nobody is emailing annotated files.

The distinction matters: the PDF is the deliverable, not the communication channel. When feedback lives in the PDF, the feedback is entangled with the document. When feedback lives on a canvas, the feedback is separate, addressable, and trackable.

Page-by-page review.

Long PDFs — brand guidelines, annual reports, proposal decks — need page-level feedback, not document-level. A comment like "see page 14" is unusable in an email thread where nobody is looking at the same version. A comment pinned to position (342, 188) on page 14 of version 3 is unambiguous.

Managing multiple reviewers.

Brand guidelines often go to multiple stakeholders: marketing, legal, the brand team, a senior exec. Each of them reviewing a separate PDF and emailing separate annotations is a reconciliation problem that takes an afternoon.

On a shared canvas, every reviewer's comments appear in the same space, organized by page. You see where they agree (two pins on the same element), where they contradict each other (two opposing comments on the same copy line), and where one reviewer flagged something the others missed.

Versioning PDFs correctly.

Every PDF revision should be uploaded as a new version — not a replacement. When a client can compare Version 1 to Version 2 side-by-side, they can confirm that their notes were addressed without having to remember what the previous version looked like. Version comparison is the fastest way to close a round.

Getting to sign-off on a PDF.

A PDF deliverable — a brand guide, a proposal, a legal contract for design work — often requires formal sign-off. The approval mechanism should be as formal as the document: named approver, version recorded, timestamp logged.

"LGTM" in a Slack message is not a PDF approval. A signed approval record with the document version and the approver's name is.