How to Get Client Feedback on a PDF (Without 40 Email Replies)

The fastest way to get client feedback on a PDF is to share it as a link the client can click on directly, so every comment lands pinned to the exact spot it refers to. No account, no download, no markup software. Emailing the PDF and asking for notes is what creates the 40-reply thread, because a flat file has nowhere to put a comment. Below is how to set that up in about five minutes, and what to do when the client insists on sending you a photo of a printed page anyway.

The real problem: a PDF has nowhere to hold a comment

You export styleguide-v2.pdf, 14 pages, and email it to the client on a Thursday. Monday morning you get this:

Hi! Looks great overall. The headline on page 4 is a bit big, and the blue feels off. Also my colleague had a few thoughts, she'll send separately.

So now you have three problems and none of them are design problems.

First, "page 4" is not a location. Page 4 has a headline, a subhead, two captions and a pull quote. You do not know which one is too big, or by how much, or whether "a bit" means two pixels or twenty.

Second, "the blue feels off" is the single most expensive sentence in freelance web design. There are four blues in that document. One of them came from the client's own brand guide. You are about to spend forty minutes finding out which blue they meant, and there is a real chance the answer is the one they gave you.

Third, the colleague is going to send her thoughts separately. Probably from her phone, probably as a photo of a printed page with a pen circle on it, probably with the page number cropped out of frame.

Then it compounds. You fix what you think they meant, export v3, and now the client's original feedback refers to page numbers that no longer exist because you removed a spread. Someone approves "the version you sent Tuesday". Nobody can say which file that was. Two weeks later, at invoice time, the client asks why the blue changed and you have no record showing that they asked for it.

None of that is the client being difficult. It is a file format problem. A PDF is a picture of a document. It has no idea where a comment belongs, so the comment has to travel separately, in prose, through whatever channel the client happens to have open. Prose is a terrible container for spatial information.

Five ways to collect PDF feedback, compared

Method  ·  Client needs an account  ·  Comment pinned to exact spot  ·  Survives a new version  ·  Works on a phone  ·  Work for you

Email replies  ·  No  ·  No  ·  No  ·  Yes  ·  High: you translate prose into locations

Printed, marked up, photographed  ·  No  ·  Sort of, if the photo is readable  ·  No  ·  Yes  ·  Very high: manual transcription

Acrobat comments in the file  ·  Acrobat or Reader  ·  Yes  ·  No: comments live in that one file  ·  Poorly  ·  Medium, plus you teach them the tool

Google Drive or Dropbox preview comments  ·  Usually yes  ·  Roughly, per page not per element  ·  No  ·  Yes  ·  Medium, plus account friction

Visual feedback link (dotts and similar)  ·  No  ·  Yes  ·  Yes, comments stay with the project  ·  Yes  ·  Low: read the list, work down it

The pattern is not subtle. Every method that keeps the comment attached to the thing being commented on either demands software from the client or locks the feedback inside a single file. The one exception is a shared link where the PDF is rendered in the browser and the client clicks where they mean.

That is the entire pitch. Everything else in this article is about using it well, because the tool is the easy half.

How to collect feedback on a PDF in six steps

1. Decide what you are actually asking for

Before you share anything, finish this sentence: "I need you to tell me whether ___." Not "let me know what you think". Whether the headline hierarchy reads correctly. Whether the product names are spelled right. Whether this can go to print.

An open invitation gets open feedback, which means you get opinions on things that are not up for discussion yet. If you are showing a layout, say the copy is placeholder. If you are showing near-final work, say so plainly, because the cost of a change is now much higher and the client deserves to know that before they start.

2. Upload the PDF once and share a link, not a file

Attachments create copies, and copies create version arguments. A link has one canonical state. When you update the document, the link still works and the feedback history stays intact.

In dotts this is: create a project, upload the PDF, copy the link. The client opens it in whatever browser they already have, on whatever device is nearest. There is no signup screen, which matters more than it sounds. Every account wall you put between a client and their feedback is a reason for them to close the tab and reply by email instead, and then you are back to page 4 and the blue.

3. Set the rules before they click

Send the link with three lines, not thirty:

Here is the deck: [link]. Click anywhere on the page to leave a comment right where you mean it. You do not need an account. Please put everything in there rather than in email, so nothing gets lost. Deadline: Thursday 5pm.

That is the whole onboarding. Clients understand clicking on a thing to comment on the thing, because that is how every tool they use socially works. What confuses them is being asked to describe a location in words.

4. Give a deadline and one channel

A feedback request with no deadline is a feedback request that arrives in eleven days, in four pieces, from three people. Name a date. Name the channel. Then hold it: if a comment shows up in email anyway, reply once with "could you drop that in the link so it stays with the file?" and paste the link again. You will need to do this roughly twice per client, then it sticks.

5. Work the comments as a list, and resolve as you go

Do not read all the comments and then start working. Open the list, pick the first one, fix it, mark it resolved. The client sees the status change, which does two useful things: it tells them you are working without you having to send a progress email, and it makes the remaining pile visibly shrink.

If a comment is not actionable, reply to it rather than guessing. "Which of these two blues do you mean?" attached to the actual element takes the client four seconds to answer. The same question in email takes a paragraph of setup.

6. Get the sign-off in the same place

When the list is empty, ask for approval in the same thread: "All 23 comments are resolved. Can you confirm this is approved for build?" Now the approval, the comments and the document are in one artifact with timestamps. That is what you point at three weeks later when someone asks why the blue changed.

Why "reply with your notes" produces bad feedback

Clients are not bad at giving feedback. They are bad at giving feedback in a format that strips out the information they are actually holding.

When a client looks at page 4 and feels that something is wrong, what they have is a spatial, visual reaction: this thing, here, next to that thing, feels heavy. To send that by email they have to translate it into language, which means naming the element (they do not know your naming), locating it (page numbers, "the top bit", "under the photo"), and diagnosing the problem (they are not designers, so "too big" often means "too dark", "too close to the edge", or "I do not like the font").

Three lossy conversions, and you receive the output. Then you reverse-engineer it. That reverse engineering is the actual work in a bad feedback loop, and it is invisible on your invoice.

Clicking removes two of the three conversions. The client points, and the only thing they still have to put into words is the feeling, which is the part they are actually qualified to describe. You get "this feels heavy" attached to a specific headline, which is a briefing. Not a puzzle.

There is a second effect worth knowing about. When feedback is pinned, clients leave more of it, and it gets smaller and more specific. A client writing an email will bundle nine thoughts into one paragraph and drop the three they think are too minor to mention. A client clicking will leave twelve separate comments, including the three minor ones, which are frequently the ones that would have come back as a complaint after launch.

Versioning: the part that quietly costs the most

Ask any freelancer where PDF review actually goes wrong and they will not say "the comments were unclear". They will say the client approved the wrong version.

It happens like this. You send v2. Client sends notes. You fix them and send v3. The client's boss, who was on the original email, opens v2 because it is higher up in their inbox, and approves it. Nobody notices for a week. You have now built against a document that was superseded, and the conversation about whose mistake that was is one you cannot win.

A link fixes this structurally rather than through discipline. There is one address. Whoever opens it sees current state. When you replace the file, the old one stops being reachable, so there is no stale copy sitting in anyone's downloads folder waiting to be approved by accident.

Keep two habits alongside it. First, never let a filename carry meaning that the link does not: if someone has to know that "final-v4-REV2" is newer than "final-FINAL", the system has already failed. Second, when you do make a significant change, say what changed in a comment on the document itself rather than in a separate email. Then the change log lives next to the thing that changed.

When the client will not stop sending marked-up printouts

Some clients are going to print it. Usually the most senior person, usually the one whose opinion decides the project. This is not a habit you are going to break with a link and a friendly note, and it is not worth spending relationship capital trying.

Handle it by absorbing the cost once and then redirecting. Take their photo, transcribe each mark into a pinned comment on the document yourself, and reply: "I have added your notes to the review link so they are all in one place, have a look and let me know if I have missed anything." Two things happen. Their feedback is now in the system without them having to change, and they get a first look at the interface with their own content already in it, which is far more persuasive than an invitation to learn a tool.

About half the time they start using the link directly on the next round. The other half you keep transcribing, which takes ten minutes and is still cheaper than running two parallel feedback systems for six weeks.

The same approach works for the client who sends voice notes, the one who gives feedback verbally on calls, and the one who writes on WhatsApp at 11pm. You are not trying to change how they think. You are making sure that wherever the thought starts, it ends up attached to the document.

Real-world example: Marta, brand and web freelancer in Porto

Marta does brand systems plus a website build, which means every project has a stack of PDFs: moodboards, logo presentations, type specimens, a 30-page guidelines document, then the site itself.

Before: each PDF went out as an email attachment to a marketing manager who forwarded it to two colleagues and a founder. Feedback came back over four to nine days across email, WhatsApp and one recurring call. Her guidelines documents averaged six versions. On one project the founder approved a logo lockup from a PDF that was three versions old, and Marta discovered it after the signage quote came back.

She stopped attaching files. Now every deliverable goes up as a link, PDFs and website both, in the same tool, with the same instruction line. Clients click, comment, and she works down the list resolving as she goes.

After, measured across her next eight projects: revision rounds on PDF deliverables dropped from an average of 4.1 to 2.4, because the first round now contains specific comments instead of "the blue feels off". Time from sending a deliverable to having complete feedback dropped from about a week to two days, mostly because the deadline sits next to the link instead of in an email. And she has had zero wrong-version approvals, because there is no longer a wrong version to open.

The thing she mentions first, though, is not any of those numbers. It is that she stopped dreading the Monday inbox.

Bottom line

If a client is reviewing a PDF, the only thing that reliably fixes the feedback is putting the comment in the same place as the thing being commented on. Share a link instead of a file, tell the client to click where they mean, give them a deadline and one channel, and resolve comments as you go so the status is always visible. Everything else, the version confusion, the vague notes, the forwarded photos, is downstream of that one decision.

FAQ

What is the best way to get client feedback on a PDF?

Share the PDF as a link in a visual feedback tool where the client can click anywhere on the page and leave a pinned comment. This keeps every note attached to the exact element it refers to, works without the client installing anything or creating an account, and keeps all feedback in one place instead of spread across email and chat.

Can clients comment on a PDF without an account?

Yes. In dotts the client opens your link and comments straight away, with no signup and no login. This matters because every account wall between a client and their feedback is a reason for them to close the tab and reply by email instead, which puts you back to unclear prose feedback.

Is Adobe Acrobat good enough for client feedback on a PDF?

Acrobat's comment tools are genuinely good, but they assume both sides have Acrobat and know how to use it. Most clients do not, and the comments live inside that one file, so as soon as you export a new version the feedback history is orphaned. It works well for internal review between two people who both use it daily, and poorly for client review.

How do I stop clients from approving an old version of a PDF?

Stop sending files. A link has one canonical state, so whoever opens it sees the current document and there is no stale copy sitting in an inbox waiting to be approved by accident. If you must send files, never let the filename carry the version logic, because "final-FINAL" versus "final-v4" is a coin flip for the person opening it.

What do I do when a client sends me a photo of a printed page?

Transcribe their marks into pinned comments on the review link yourself, then reply telling them you have added their notes so everything is in one place and asking them to check you have not missed anything. You absorb the cost once, their feedback enters the system, and they see the tool with their own content already in it, which is far more convincing than being asked to learn something new.

How many revision rounds should a PDF deliverable take?

Two is realistic for most work: one substantive round and one confirmation pass. If you are consistently running four or more, the problem is usually not the design but the feedback format, because vague feedback guarantees a round spent guessing. Pinned comments plus a clear question ("does the hierarchy read correctly?") is what collapses those rounds.

Can I collect feedback on PDFs and websites in the same tool?

Yes, and you should. dotts handles websites, PDFs and images (JPG, PNG, SVG, HEIC) in the same project, so a brand PDF and the site it informs live in one place with one feedback history. Running separate tools for separate file types recreates the fragmentation you were trying to fix.

Does this work for multi-page PDFs?

Yes. Pinned comments carry both the page and the position within it, so a 30-page guidelines document produces a readable list of comments rather than an email that says "pages 4, 11 and somewhere near the end".

Stop translating prose into page numbers. [Try dotts free →](https://dotts.se)