Let reviewers suggest changes in Google Docs without rewriting your draft

For a review in which you retain the final decision, share the Google Doc with the reviewer as a Commenter. Keep Owner or Editor access for whoever will approve the wording. The workflow below uses Google Docs in a desktop browser, with sharing examples centered on My Drive.

A reviewer does not need Editor access to rewrite a sentence as a proposal

Google’s current access guide says Commenters can comment and suggest changes, while Editors can change content and accept or reject suggestions. Viewer access is for reading; it does not allow comments or suggestions.

Consider an event announcement drafted by one person and proofread by a contractor. The contractor can be a Commenter. A colleague responsible for approving the schedule could be an Editor, but that colleague would also be able to accept suggestions. Giving several people Editor access does not reserve approval exclusively for the author.

Suggesting mode lets an editor propose changes voluntarily. It does not downgrade their role. Choosing it on your own screen before sending a link is therefore not a substitute for choosing the reviewer’s sharing permission.

A real Web Applications question illustrates a different requirement: opening a document in Suggesting while still letting collaborators switch to direct editing. That is a useful distinction when planning a review. A coauthor who must sometimes make immediate changes needs different access from a proofreader whose changes should await a decision.

Invite the account that will actually do the review

Open Share, enter the reviewer’s email address, choose Commenter, and send the invitation. For someone already listed as an Editor, change the role beside their name and save. For a review limited to named people, Restricted general access makes the intended audience easier to manage. These controls are described in Google’s sharing guide.

If the reviewer reaches a request-access screen, compare the invited address with the account they are using. A work-address invitation does not establish permission for their personal account. Work or school policies can also restrict external sharing.

The reviewer can select text and use Suggest edits in the margin, or select Suggesting from the mode menu. As illustrated in Google’s collaboration guide, insertions appear in another color and proposed deletions are crossed out. A suggestion can also carry a comment explaining the proposed change.

For a hypothetical announcement, suppose the draft says, “Registration closes on Friday.” A reviewer who knows the confirmed deadline can suggest replacing Friday with Monday. The author can inspect the replacement in context. If the reviewer does not know the deadline, a comment asking for confirmation is more useful than proposing an unverified day.

A short review request can make that distinction explicit: “Please suggest wording changes directly in the document. Leave a comment wherever a date still needs confirmation. I will apply the final changes.” This gives the reviewer permission to propose actual text without implying that they should decide unresolved facts.

Try one small suggestion before a long review if either person is unfamiliar with the workflow. Use a harmless example, have the author locate it, and agree who will process the remaining suggestions. The purpose is to establish a working handoff, not to create an extra approval round for every typo.

A file-level change may leave inherited Editor access intact

Google’s sharing documentation says a file cannot give someone less access than its parent folder. If the reviewer is an Editor on the team folder, changing an individual invitation on a document inside it is not enough to make that person a Commenter. General access also needs to match the intended restriction.

Suppose the reviewer must keep updating the team schedule but should only propose changes to an announcement. Leave the schedule in the shared team folder and place the announcement in a separately managed folder, or use a limited-access folder. You can then share the announcement with Commenter access while the schedule remains available for direct editing.

In Drive on the web, Google’s limited-access procedure starts with the folder’s Share settings. Enable Limit access, return to the sharing dialog, and manage the people allowed in. In My Drive, owners and editors allowed to change permissions can manage this; shared-drive Managers control the setting in shared drives. The setting is applied manually to folders, so a single document needs a dedicated folder.

Check allowed people, groups, and General access together. Google notes that membership in an allowed group or general access can still provide access even when a person appears under Access removed.

For example, a reviewer might receive Editor access through a “Content team” group. Changing only their individual entry would not address that route. Decide whether the group should participate in this review or whether the document belongs in a separately managed location. That decision avoids interrupting unrelated team work.

Afterward, ask the reviewer to reopen the document with the invited account and make a small suggestion. The author should see the proposed text awaiting a decision, and the reviewer should be unable to edit the body directly. If direct editing still works, revisit that account’s individual role, group membership and General access in the sharing settings.

Closing a comment does not insert its proposed wording

Resolving a comment closes a discussion. Accepting a suggestion changes the text. A comment can be reopened from the comments panel if the discussion needs to continue.

In the announcement example, resolving an ordinary comment saying “Change Friday to Monday” does not replace the weekday. An editor still needs to change the sentence. If Monday is already an inline suggestion, the approver can accept that suggestion instead. Read the resulting sentence after processing it.

For a longer review, open Tools → Review suggested edits and preview the text with the proposed changes included. After reading it, accept or reject the suggestions individually, or use Accept all if every change is settled. Closing a preview leaves the suggestions pending. Google’s review instructions describe the preview and acceptance controls.

A batch containing both punctuation fixes and an unconfirmed deadline should not be treated as one decision. Approve the settled wording and leave the uncertain date for its responsible person. A reviewer’s explanation may contain the condition that determines whether the proposal is ready.

If a Commenter cannot apply a suggestion, that does not mean the proofreading arrangement is broken. They have finished their part by proposing it. Add Editor access only when that person should also decide the document’s accepted wording.

Use version history for wording changed without a suggestion

When someone edited the text directly, there may be no pending suggestion to reject. Version history provides earlier versions, but browsing them requires edit permission.

Open Last edit at the top right and select an earlier version. Its More menu offers Make a copy. This lets an editor compare an older document with the current one before choosing what to recover. Restoring an entire earlier version is a separate action.

Suppose yesterday’s introduction was better, but today’s venue instructions must remain. Copy the earlier version, locate the introduction, and restore only that wording in the current draft. Restoring yesterday’s whole document would not match the request to preserve today’s additions. If the whole editing session was mistaken, inspect the relevant earlier state before choosing Restore this version.

Named versions can identify useful milestones such as “Sent for proofreading” and “Schedule confirmed.” They help locate a comparison point; they do not prevent future direct edits. If the reviewer should no longer be editing directly, fix the sharing arrangement as well as the sentence.

Hand over a document with an explicit review status

Before ending the review, make the outstanding wording decisions and read the actual text. In the announcement example, the deadline could appear in the opening paragraph and again beside the registration instructions. Accepting one suggestion does not establish that every occurrence now says the same thing.

Change a reviewer to Viewer if they only need to read the completed document, or remove access if their involvement has ended. Account for folder and group access rather than assuming a direct invitation is the only route.

Google’s suggestion guide also states that suggestions become tracked changes when converting to Microsoft Office formats. If you are sending a Word file for further review, explain which decisions remain open. If the recipient needs settled wording, finish those decisions first and read the exported file.

A useful handoff message is specific: “Monday is confirmed, and the accepted wording is ready to publish,” or “The deadline remains a proposal; please confirm it with the event team.” Those messages assign different next steps. Merely adding “final” to the filename does not communicate which one applies.