A review contains many comments and the delivery team needs to know which ones prevent acceptance.
The useful bits
- Reviewed version
- Existing acceptance criteria
- The response should give each important comment an actionable priority with a reason.
Before you write
Use this example when a review contains many comments and the delivery team needs to know which ones prevent acceptance. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Reviewed version
- Existing acceptance criteria
- Reviewer responsible for prioritization
An email you can adapt
The subject “Please mark blocking items in [review]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Please mark blocking items in [review] Hi [name], Thank you for reviewing [version]. To plan the next pass, could you mark which comments are required for acceptance and which are suggestions for later improvement? Where a comment blocks acceptance, please link it to [criterion] or explain the specific issue. We can then estimate the work and agree the next review date. We are not asking you to remove concerns, only to make their effect on readiness clear. Best, [sender]
Check the boundary
Do not label a safety, accuracy or contractual concern optional merely to preserve a planned date.
What a useful reply should settle
The response should give each important comment an actionable priority with a reason.
Confirm the prioritized change list before implementation and preserve the reviewer’s original meaning.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction