Engineering & PLMFree worksheetPDF, Excel, Word exportAerospace and Defense

Design Review Comment Resolution Log Worksheet

A design review produces dozens of comments, and untracked comments return as defects. This log records each comment, who owns it, how it was answered and whether it is closed, so the gate decision rests on evidence.

Download:
Comment IDDocument or drawingReviewerCommentSeverityOwnerResponseDue dateStatusWeight
Total comment weight
8
Comments logged
5
Average weight per comment
1.6

Enter the weight by severity so the totals show how heavy the review was. Do not close a review gate while Critical or Major comments are Open. Keep rejected comments with a reason, since reviewers will ask why.

Connect review findings to change requests

Optional: see how review comments could become tracked changes in your PLM or ERP workflow.

Optional. The tool and every export work without this. No spam.

How to use the log

Number the comments as they are raised in the review. Capture the document, the reviewer, the comment itself and its severity. After the meeting, the owner chooses a response and a due date. Export to Excel and circulate it to reviewers so they can confirm closure. Close the review only when all critical and major comments are closed.

  • Write comments as specific, actionable statements.
  • Always record a reason when a comment is rejected.
  • Use consistent severity definitions across reviews.
  • Ask the reviewer, not the owner, to confirm closure of critical items.

Severity guidance

Critical means safety, regulatory or contractual non-compliance, or a failure of a key requirement. Major means a significant risk to function, cost or schedule. Minor is a clear defect without major consequence. Suggestion is an optional improvement. Agree these definitions before the review so debate does not eat the meeting.

Where it fits in the process

Use the log at preliminary and critical design reviews, manufacturability reviews and drawing checks. The design review outputs feed engineering change requests when a released design must be altered. Standards such as AS9100 expect design reviews to be recorded and their actions followed up, and a log like this serves as that record.

Common mistakes

Vague comments such as 'check this', no owner, and closing items without reviewer agreement are the main weaknesses. Another is mixing action items from the meeting with comments on documents; keep one log per review and separate lists for general actions.

Frequently Asked Questions

What is a comment resolution matrix?

It is a table listing every review comment with the response and result. It shows that each comment was considered, answered and either implemented or rejected with a reason.

Who closes a review comment?

The reviewer who raised it should agree that the response is acceptable, especially for critical and major items. The owner proposes closure, the reviewer confirms.

How many comments is normal?

It varies by project size and maturity. A very low number can mean a shallow review, while a very high number may indicate immature design. Track trends across reviews instead of judging one count.

Can I reuse the log for supplier design reviews?

Yes. Add the supplier name to the document column or add a column for the company, then share the Excel export with the supplier.

If review findings and change requests live in different places, we can help connect them to your PLM and ERP data.