A brochure PDF goes out for approval, and a week later it comes back five times over: one copy with tracked changes, one with yellow sticky notes, two forwarded emails saying "see attached", and a phone screenshot with an arrow drawn on it. None of the copies agree, there is no master, and you lose an afternoon reconciling contradictions instead of making edits.
This guide is about reviewing PDFs with clients - brochures, print proofs, proposals, one-pagers - without that mess. We will look at the honest options for marking up a PDF, why the round so often goes sideways, and a repeatable workflow that keeps every comment in one place. It is tool-agnostic where it can be, and specific where being specific actually helps.
Why PDF review goes sideways
The PDF format is part of the problem. A PDF is a snapshot: it looks identical on every screen, which is exactly why we send it, but that also means the obvious way to comment on it is to draw on a copy. The moment two people each draw on their own copy, you have two masters and no way to merge them.
The usual failures are boring but expensive:
- Version drift. "brochure-final-v3-CLIENT-edits-2.pdf" is a genre, not a filename. Nobody is sure which file is current.
- Lost context. An email that says "the headline on page two is too long" is fine until there are two headlines on page two, or the layout shifts and there is no page two anymore.
- Silent tool gaps. You assume the client has Acrobat's commenting tools. They open the PDF in a browser preview that cannot annotate, so they reply in plain email instead.
- No single deadline. Feedback trickles in over ten days, and the last comment contradicts an edit you made on day two.
None of these are the client's fault. They are workflow gaps, and they are fixable without buying anything fancy - but you do have to pick a lane instead of letting everyone improvise.
Ways to mark up a PDF
There are four common approaches, and each one is genuinely right for some situation. The trick is matching the method to the job rather than defaulting to whatever is already open.
| Method | Best for | Downside |
|---|---|---|
| Desktop PDF editor / annotations | Solo detailed markup by someone who owns the software | Assumes everyone has the same editor; comments live in one person's copy |
| Emailed marked-up copies | A single, one-off review with one reviewer | Falls apart with two or more reviewers; no master, endless version drift |
| Shared PDF review tool | Client review where feedback must stay in one place | Another tool to learn; the good ones remove the friction, the clumsy ones add it |
| Print-proof workflow | Anything heading to a printer with bleed and trim | Slower and more exacting; overkill for a screen-only proposal |
The desktop editor and the emailed copy are the defaults most people reach for, and they are fine right up to the point where a second reviewer joins. That is the moment a shared tool earns its keep: one document, everyone's comments on it, and no reconciling copies afterward.
A repeatable PDF review workflow
Whatever tool you land on, the workflow matters more than the software. This is a sequence you can reuse on every proof, and it holds up whether the reviewer is one client or a committee of five.
- Keep one master. Upload the current export to a single shared location and delete or archive the older ones so nobody can comment on a stale file. One master is the whole game; everything else is downstream of it.
- Share a link, not an attachment. Send reviewers a link to that one document rather than mailing the PDF around. A link cannot be duplicated and re-marked the way an attachment can, so the comments have only one place to land.
- Comment in context. Ask reviewers to pin each note to the exact spot on the page it refers to, instead of writing "third block down". A comment attached to a location survives a layout change far better than one that describes a position in prose.
- Set one deadline. Give a single date for all feedback and hold to it. Staggered comments are how you end up editing the same paragraph three times. One deadline turns a trickle into a batch you can action in one pass.
- Resolve and export. Work through the pins, mark each one resolved as you go, and when the round is done export a clean summary of what changed. That summary becomes the paper trail for the next version and the sign-off.
If your work also spans live pages and static images, the same five steps carry over almost unchanged - the principles are the point, not the file type. We walk through the on-page version in the guide to annotating a live website for feedback, and the broader client-facing version in how to collect website feedback from clients.
Print proofs are different
Everything above applies to a screen PDF like a proposal or a one-pager. Print proofs add a layer, because the file is going to a press and mistakes cost real money to reprint. A few things change:
- Bleed and trim are in scope. Reviewers should be looking at whether images run properly to the edge and nothing important sits too close to the trim line. That is a comment category screen review never has.
- Colour notes need context. Colour on a backlit monitor is not colour on paper. Flag colour concerns, but treat the physical proof, not the screen, as the source of truth for the final call.
- Review the final proof, not an old export. The single most common print mistake is signing off on a PDF that is one version behind the file actually sent to the printer. Make sure everyone is commenting on the current proof.
The workflow does not change; the checklist does. Keep one master, share the link, pin comments to the spot, one deadline, resolve and export - just widen what reviewers are watching for.
Where Roundmark fits
To be straight with you: this is Roundmark's blog, so we have a horse in this race. Here is the honest version of where it helps. Roundmark renders your uploaded PDF page by page directly in the browser, so a client opens one link and clicks anywhere on a page to drop a numbered pin and comment - no install, no account, and no assumption that everyone owns the same desktop editor. Because everyone is commenting on the same rendered document, you get one master by default instead of a folder of near-duplicate files.
Feedback lands as threaded pins you can reply to and mark resolved, and the AI assistant on the Pro plan reads the whole thread and summarises it into a clear list of what to change, which is handy when a five-reviewer round leaves you with forty comments to untangle. Every plan includes unlimited reviewers, so a busy approval round never inflates the bill. If that sounds like the lane you want, the pricing page lays out the plans, and the free tier gives you three projects to test the flow with no card.
If instead you are a solo reviewer marking up one file for yourself, a desktop editor is genuinely simpler and you should just use it. The shared tool earns its place the moment a client is involved and the comments need to stay in one place.
FAQ
What is the best way to mark up a PDF for client review?
Share the PDF in a tool that lets the client comment directly on the page, pinning notes to the exact spot, rather than emailing a marked-up copy back and forth. Keep one master version so comments do not fragment across duplicate files, and set a single deadline.
Can clients comment on a PDF without special software?
Yes. Modern review tools open the PDF in the browser and let clients click and comment with no install and, in the better ones, no account. That is far more reliable than assuming everyone has the same desktop PDF editor.
How do I handle print proofs versus screen PDFs?
For print, keep an eye on bleed, trim and colour notes, and make sure reviewers comment on the final proof rather than an earlier export. For screen PDFs like proposals, focus on copy and layout. Either way, one shared master and a clear deadline keep the round tidy.