Share a document for comments, without direct edits

Choose the kind of feedback you need

Ask for a specific task: check whether instructions are clear, identify missing information or propose wording changes. A reviewer who knows the purpose can leave more useful feedback than someone sent an unexplained document link.

Distinguish a comment from a suggested edit. A comment discusses a question or passage. A suggestion proposes a change for someone to accept or reject. Direct editing changes the working document under the service’s saving rules. Not every editor or file format supports all three.

Google Docs’ suggestion guide explains that suggestions do not replace the original text until accepted. It also says a commenter or editor can make suggestions in that product. That is an example to verify, not a feature to assume in every document app.

Check existing access and copied information

Review the people, groups and folders that already have permission. A file in an editable shared folder can have a broader audience or higher access than the invitation you are creating. Use a deliberately limited review location if your service supports it and the owner permits it.

Google’s sharing restriction guide describes controls for changing or limiting access. Its limits matter: preventing a supported download or copy action cannot stop every way someone could retain or share the contents.

Keep confidential notes and unrelated personal information out of the review file. Check existing comments too. A passage removed from the visible draft may still appear in a discussion or earlier version, depending on the service. Do not treat a comment permission as a document-cleaning tool.

Our file-sharing guide covers the broader access journey. This guide focuses on getting feedback without granting unnecessary direct editing.

Give reviewers a manageable request

Send the exact link with a short explanation of what is ready for review. Say which sections need attention, when feedback is useful and who will make the final changes. Avoid asking someone to review a moving draft without telling them it is still changing.

Keep comments close to the relevant passage where the editor supports that. One question per comment is easier to answer than a large list of unrelated points. A suggestion should explain the reason when the change is more than a small correction.

If you use AI to improve a message before sending it, our email editing guide helps keep the request clear and in your own voice. Do not paste confidential review material into a tool you are not authorised to use.

A fictional review of a club handout

Imagine a fictional community club prepares a one-page welcome handout. The organiser wants two volunteers to check whether a newcomer can follow it, while keeping the working text under one person’s control.

The organiser creates a clean review copy, grants the supported comment role to the two intended addresses and asks them to flag unclear steps. One volunteer proposes a simpler sentence through the product’s suggestion feature. The organiser accepts it only after checking the meaning.

The result is a review process, not a guarantee provided by the word “commenter”. The organiser still checks the effective permissions, the file type and whether the volunteers are signed into the invited identities.