Google Docs Collaboration: Suggestions, Comments and History
Practice3 minInnovialabs editorial team
In short
Edit other people's text in Suggesting mode, ask questions with assigned comments, save key milestones as named versions and lock the final version through an approval.
The short answer
Google Docs has everything a team needs to edit together without emailing files around:
- Suggesting mode: edits appear as proposals that the author accepts or rejects.
- Assigned comments: a question becomes a task for a specific person.
- Version history: see who changed what and restore any state.
- Smart chips: links to people, files, dates and meetings right in the text.
- Approvals: a formal sign-off on the final version.
Suggesting mode
The mode switcher is in the top right, next to the pencil icon: Editing, Suggesting, Viewing.
In Suggesting mode, deleted text is struck through, added text is colored, and a card with Accept and Reject buttons appears in the margin. The document owner sees exactly what changed and decides.
Use it when:
- you are editing text you did not write;
- the document is already agreed and every change must be visible;
- an outside participant is making edits.
If certain people should only suggest, give them the Commenter role: they can comment and suggest edits but cannot change the text directly.
Comments and assignments
Select a passage and press Ctrl+Alt+M (Cmd+Option+M on Mac). To turn a comment into a task:
- Type @ and a colleague's name.
- Tick Assign to.
- Post the comment.
The assignee gets an email, and the comment shows up in their assigned list. When the task is done, click Mark as resolved: the thread leaves the margin but stays in comment history.
Version history and named versions
Go to File, Version history, See version history (Ctrl+Alt+Shift+H). The panel lists versions with authors and timestamps, and each person's changes are highlighted in their own color. You can restore or copy any version.
There are many automatic versions, so name the important ones: File, Version history, Name current version. For example: "Sent to client", "After legal review", "Final". The history panel can show named versions only.
Smart chips
Type @ in the text to open the menu:
- people: a contact chip that shows the email and a quick message option on hover;
- files: a link to a doc, sheet or slide deck with a preview;
- dates: handy for deadlines and meeting minutes;
- Calendar events: quickly create meeting notes;
- dropdowns: for example a section status such as Draft, In review, Done.
Chips keep a document alive: links survive file renames and statuses are visible at a glance.
Approvals
On some Google Workspace editions, File, Approvals is available. You choose approvers, optionally set a due date, and each approver approves or rejects the document. When requesting approval you can lock the file so people approve exactly the version you sent.
Team editing etiquette
- Do not edit someone else's text directly. Use Suggesting.
- One comment, one point. That makes threads easier to resolve.
- Resolve and close discussions instead of leaving dozens of open threads.
- Do not delete other people's comments. Mark them resolved.
- Name versions before sending externally and before a major rewrite.
- Agree on a document owner who makes the final call on edits.