Comments, Suggestions, and the Review Workflow

Review, not chat

Feedback that lives in a chat thread or an email gets lost. StretchDocs keeps review attached to the document through two tools: comments (discussion anchored to specific text) and suggestions (proposed changes the author accepts or rejects). Together with status, they form a repeatable review workflow.

Comments

A comment is a note anchored to a piece of text. Each comment records the anchor text it refers to, the body of the note, and the author. Comments have a lifecycle so nothing falls through the cracks.

Leave a comment

1. Open the document (typically in Review status).
2. Select the text you want to discuss.
3. Click Comment, write your note, and post it. The selected text is saved as the comment's anchor so everyone knows exactly what it refers to.

Resolve a comment

1. Open the review panel and read the open comments.
2. Once addressed, set the comment's status to Resolved (or Accepted/Rejected where you're recording a decision).
3. Resolved comments drop out of the active list but remain on the record.

Comment statuses are open, resolved, accepted, and rejected.

Suggestions (tracked changes)

A suggestion proposes an actual edit without changing the document until the author agrees. Each suggestion captures the original text, the suggested text, the anchor it applies to, a type (for example, a replacement), and the author.

Propose a suggestion

1. Select the text you want to change.
2. Click Suggest, then type the replacement.
3. Post it. The suggestion is recorded with both the original and your proposed text so the author can compare them.

Accept or reject a suggestion

1. As the author or an approver, open the review panel.
2. Review each suggestion side by side (original vs. suggested).
3. Accept to take the change or Reject to decline it.

Suggestion statuses mirror comments: open, accepted, rejected, resolved.

The review panel

StretchDocs gathers a document's comments, suggestions, and snapshots into one review view. That gives an author a single place to work through every open comment, every proposed suggestion, and the restore points captured along the way — a complete picture of the review.

A recommended workflow

1. Author drafts the document (Draft).
2. Author sets status to Review and notifies reviewers.
3. Reviewers leave comments for discussion and suggestions for concrete edits.
4. Author works through the review panel: resolving comments and accepting/rejecting suggestions.
5. Author captures a snapshot of the approved state, then sets status to Published.

A realistic example

Priya submits a pricing policy for review. Her manager comments on the discount section ("anchor: up to 30% — should this be 25%?") and adds a suggestion replacing net-60 with net-30. Priya reads the comment, agrees, and updates the number; she accepts the net-30 suggestion with one click. She marks the comment Resolved, snapshots the approved version as Pricing Policy — approved, and publishes. Every decision is on the record.

Tips

• Use comments for questions and discussion; use suggestions for exact wording changes.
• Anchor feedback to the specific text — vague comments create rework.
• Resolve comments as you address them so the open list always reflects outstanding work.
• Snapshot the approved version before publishing so you can always return to exactly what was signed off.

FAQ

Can a reviewer edit the document directly instead of suggesting? Anyone with Docs access can edit, but suggestions are safer during review because they preserve the author's control and leave an audit trail.

Do resolved comments disappear? They leave the active list but remain part of the document's review record.

What's the difference between resolving and accepting a comment? Resolving means "handled"; accepting/rejecting records an explicit decision. Use whichever matches how your team tracks outcomes.