How do I get specific feedback on copy instead of vague comments?

The tool forces the specificity. When clients can click the exact sentence and leave a pinned note, they do — because it's easier than describing the location. Email and chat replies produce 'the opening feels off.' An inline comment produces 'this first sentence buries the benefit.' Ask two or three focused questions in your send message to guide the review rather than leaving it open-ended.

Can a client comment on a Google Doc without a Google account?

A client can view a Google Doc without an account, but leaving a comment requires signing in. If they're not logged in, they can suggest edits in Suggesting mode (if you've granted that permission) — but suggested edits and comments behave differently, which can create confusion. For clients without Google accounts, a review link on the rendered doc is easier: they open the URL and comment as a guest with no login.

What is the best format to share copy with a client for review?

Google Docs with Comment access is the most common and usually the right default — your client likely already uses it, comments are tied to specific text, and you can resolve each thread as you revise. For copy that lives on a live page (a landing page, a product description), a shared review link is better: the client reviews the copy in context, not stripped out into a plain document, which often surfaces feedback you wouldn't get on the raw text alone.

How many rounds of copy feedback is normal?

One to two rounds when the brief is solid. Three or more usually signals a misaligned brief, not a writing problem — the copy was answering a question the client wasn't asking. Front-loading one call to align on audience and goal before you write cuts the revision count more than any tool does. After the first draft, ask the client to read it once for overall impression before they comment line by line: first-pass global feedback and second-pass line edits are different tasks and are easier when separated.

How do I stop clients from rewriting the copy instead of giving feedback?

Ask for diagnosis, not a fix. In your send message, phrase the request as: 'Flag anything that doesn't feel right and tell me what's not landing — I'll handle the rewrite.' Clients rewrite because they're trying to help; if you give them a clear instruction that their job is to identify the problem, most will stick to it. When they do rewrite, ask 'what felt wrong about the original line?' before you use their draft — the answer often reveals a brief issue, not a copy issue.

How do I collect copy feedback from multiple stakeholders without losing track?

Send everyone the same link rather than separate files. Multiple people commenting on the same Google Doc — or the same review link — means all feedback is in one place, not scattered across four email replies with different priorities. Assigning comment resolution to yourself (not the stakeholders) keeps the doc clean: you resolve each thread once you've addressed it, and the comment history stays as a record.

drafty

How to get feedback on a copy from a client

Quick answer

To get feedback on copy, share it in a format where the client can comment on the exact line they mean — not a paragraph of impressions emailed back. Google Docs with commenting enabled is the standard method. A shared review link on a rendered doc works better when you need pinned, threaded notes without asking your client to log in to anything. Either way, ask about specific passages up front: vague prompts get vague feedback, and 'make it more punchy' pinned to the actual headline is far more useful than 'the tone feels a bit flat' in a reply email.

Step 1

Share a Google Doc with Comment access

Paste your copy into a Google Doc, click Share, set the permission to 'Anyone with the link can comment', and send the link. Your client opens it in a browser — no Google account required to view, though they need one to leave comments. Highlight the phrase, press Ctrl+Alt+M (or right-click → Comment), and type. The most common mistake here is sharing with 'Viewer' access by accident: the client can't leave a note, so they copy the text into a reply email and you get feedback disconnected from the specific line. Double-check the permission before you send. One gotcha that catches almost every freelance designer the first time: clients who don't use Google Docs regularly will rewrite the sentence directly in a comment — 'Here's how I'd say it: [entire paragraph]' — instead of saying what the underlying problem is. Ask them explicitly to mark what isn't working and why, not to redraft it. Their instinct is to solve it; your job is to understand the diagnosis.

Step 2

Record a walkthrough and send it with specific questions

Record a short Loom of yourself reading through the copy and narrating your thinking on each section: 'This headline is written for the engineering team — I'm not sure it lands for the VP audience you mentioned.' Send the Loom link with two or three concrete questions in the message body: 'Does this opening line make the value prop clear in one read?' and 'The bullet on line 14 — too technical for the buyer persona?' This is more work upfront but usually gets you more useful feedback than an open prompt. Clients who would otherwise reply 'I think it's fine, maybe tighten it up?' will watch a six-minute video and respond specifically to the moment you flagged. Loom's time-stamped comments let them react inline to the exact part.

Step 3

Walk through it live on a screen share

A 20-minute call where you read the copy aloud and stop at each section beats five email rounds for copy that needs real buy-in. Share your screen on Zoom or Google Meet, pull up the doc, and read each section — don't explain what you were trying to achieve. Let the client form their first impression before you frame it. Ask 'does the first sentence answer why this matters to the reader?' before anything else. Take notes in a second doc during the call or let Zoom transcribe it, then share a bulleted action list after. The main failure mode for live copy reviews is letting the client co-write in real time on the call — you lose an hour to a sentence and leave with no clear sense of the bigger picture. Keep the call diagnostic; do the revisions after.

Step 4

Share an annotation link they open in any browser

For clients who won't log in to Google, paste your copy doc (a web page, a Notion export, an HTML file) into a shared review link. They open it in any browser, click the exact paragraph or sentence they mean, and leave a pinned note. No account, no app to install. You see every comment anchored to the specific line, reply in a thread, and mark it resolved. This is especially useful when the copy is embedded in a designed page — a landing page headline, a product description in context — rather than a standalone document. A client who tells you 'the bit near the top' via email can point at the exact sentence with a single click on a review link.

The faster way

If your client keeps giving copy feedback like 'it feels a bit flat' without pointing at anything specific, drop the doc URL or the page URL into Drafty and send the link. They click the exact line they mean and leave a note pinned right there — no account required. Every note is threaded, anchored to the passage, and stays live on the same link through every revision round. No re-sending files, no reconciling three annotated PDFs with version numbers in the filename.

Open a live demo

Questions

How do I get specific feedback on copy instead of vague comments?: The tool forces the specificity. When clients can click the exact sentence and leave a pinned note, they do — because it's easier than describing the location. Email and chat replies produce 'the opening feels off.' An inline comment produces 'this first sentence buries the benefit.' Ask two or three focused questions in your send message to guide the review rather than leaving it open-ended.
Can a client comment on a Google Doc without a Google account?: A client can view a Google Doc without an account, but leaving a comment requires signing in. If they're not logged in, they can suggest edits in Suggesting mode (if you've granted that permission) — but suggested edits and comments behave differently, which can create confusion. For clients without Google accounts, a review link on the rendered doc is easier: they open the URL and comment as a guest with no login.
What is the best format to share copy with a client for review?: Google Docs with Comment access is the most common and usually the right default — your client likely already uses it, comments are tied to specific text, and you can resolve each thread as you revise. For copy that lives on a live page (a landing page, a product description), a shared review link is better: the client reviews the copy in context, not stripped out into a plain document, which often surfaces feedback you wouldn't get on the raw text alone.
How many rounds of copy feedback is normal?: One to two rounds when the brief is solid. Three or more usually signals a misaligned brief, not a writing problem — the copy was answering a question the client wasn't asking. Front-loading one call to align on audience and goal before you write cuts the revision count more than any tool does. After the first draft, ask the client to read it once for overall impression before they comment line by line: first-pass global feedback and second-pass line edits are different tasks and are easier when separated.
How do I stop clients from rewriting the copy instead of giving feedback?: Ask for diagnosis, not a fix. In your send message, phrase the request as: 'Flag anything that doesn't feel right and tell me what's not landing — I'll handle the rewrite.' Clients rewrite because they're trying to help; if you give them a clear instruction that their job is to identify the problem, most will stick to it. When they do rewrite, ask 'what felt wrong about the original line?' before you use their draft — the answer often reveals a brief issue, not a copy issue.
How do I collect copy feedback from multiple stakeholders without losing track?: Send everyone the same link rather than separate files. Multiple people commenting on the same Google Doc — or the same review link — means all feedback is in one place, not scattered across four email replies with different priorities. Assigning comment resolution to yourself (not the stakeholders) keeps the doc clean: you resolve each thread once you've addressed it, and the comment history stays as a record.

Keep exploring

Get feedback on a web design Annotate a PDF Design feedback tool Client feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo