Skip to main content

How to Review Feedback on a Specification

How to find, respond to, and act on reviewer comments and suggested edits as the document owner.

This article covers working through feedback once reviewers have started submitting it. For tracking overall progress across stages and reviewers, see How to Manage an Active Approval Workflow. Once you've addressed everything, head to How to Publish a Specification.


Finding Reviewer Feedback

To see and respond to it, go to the Spec editor tab of a spec that's currently in the approval process — the same place reviewers do their reviewing.

On the right side of the editor, the Comments panel shows every comment and suggestion left so far, with a running count. Two filters help you narrow things down:

  • All reviewers — Filter to see feedback from a specific reviewer instead of everyone

  • All (status filter) — Filter by whether feedback is Open, Resolved, Accepted, or Rejected

Comments vs. Suggested Edits

Feedback shows up as one of two types, and each works a little differently.

Comments

A comment is general feedback that isn't tied to a specific text change, like "Looks good overall, just flagged a couple of questions." You can reply to start a conversation, or mark it resolved once you've addressed it.

Suggested Edits

A suggested edit proposes a specific change to the text, shown inline as a tracked change (additions in green, deletions struck through) and as its own entry in the Comments panel describing exactly what's being added or removed. Each entry gives you two options:

  • Accept — Applies the change to the specification

  • Reject — Discards the suggestion and keeps the original text

You can also Reply to a suggestion if you have a question about it before deciding.

Making Your Own Edits

You're not limited to accepting or rejecting what reviewers propose. Click into any section of the specification to edit it directly at any time during the review process. This is useful when a comment points to a real issue but you want to phrase the fix differently than what was suggested.

You don't have to wait for a stage to finish before responding. Many document owners prefer to address feedback in batches as it comes in rather than all at once at the end.

Next Steps

Once you've worked through feedback from every reviewer across every stage, you're ready to publish. See How to Publish a Specification for that final step.

Did this answer your question?