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.
| Comment ID | Document or drawing | Reviewer | Comment | Severity | Owner | Response | Due date | Status | Weight | |
|---|---|---|---|---|---|---|---|---|---|---|
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.
Related Tools
Engineering Change Board Meeting Minutes Template
Fill in a clean ECB or CCB meeting record with decisions per change, actions and sign-off, and export it to PDF or Word.
Engineering & PLMDrawing Release Package Transmittal Template
A transmittal sheet that lists every drawing, revision and file sent in a release package, with a receipt acknowledgement line.
Engineering & PLMEngineering Change Implementation Task Tracker Worksheet
Track ECO implementation tasks by owner and due date, with planned and actual hours and a late-task indicator.
Engineering & PLMNew Part Introduction Request Form Template
A request form that gives engineering and master data teams everything needed to create a new part in the ERP correctly the first time.
More Engineering & PLM tools
See all- SAP Super BOM Design Worksheet
- SAP Engineering Change Number Checklist
- SAP Document Info Record Template
- SAP Change Master and Revision Level Log
- SAP Engineering Change Request (ECR) Template
- SAP BOM Usage and Item Category Reference
- SAP Engineering Change Obsolescence Exposure Calculator
- SAP Engineering Change Affected Materials Impact Worksheet
- Cloud MRP BOM Data Cleanup Worksheet
Keep exploring
Free tools
- Engineering Design Review ChecklistA scored checklist for design reviews covering requirements, manufacturability, supply chain, test and release readiness.
- CAPA Action Tracker WorksheetTrack every open corrective and preventive action with owner, due date, days open and status, and see how many are overdue or ageing.
- Design History File Index TemplateAn editable index of the records that make up a medical device design history file, with status, owner and review date for each document.
ERP fixes and how-tos
- Sage X3 Error: Due Date Is Being Paid, and How to Clear ItSage X3 refuses a payment because the due date is already being paid. Find the open payment or proposal holding it, release it and retry safely.
- Resolving SyteLine multi-site replication conflict errorsSyteLine multi-site replication conflicts happen when the same record is changed at two sites before the sync runs. Here is how the conflict log works and how to clear a stuck replication queue.
- JD Edwards table conversion: how it works and how to run oneWhat a JD Edwards table conversion does to a JDE table's structure and data, when it runs in a package build, and how to run or design one manually.
Guides
- ERP Duplicate Data Identification and ResolutionIdentify and resolve duplicate records in your ERP with fuzzy matching, survivorship rules, and merge strategies. Reduce duplicates by 90% before migration.
- SyteLine Upgrade Error Resolution: Complete GuideResolve common SyteLine upgrade errors including schema migration failures, customization conflicts, and post-upgrade validation issues step by step.
- AS9100 Contract Review Checklist for Aerospace Machine ShopsAS9100D contract review checklist for build-to-print machine shops: what to verify on every PO and RFQ, who signs, and the records an auditor expects.
AI on your ERP
- AI for Infor LN in Aerospace and Defense ManufacturingAI grounded on Infor LN project, contract, and configuration management data for aerospace and defense manufacturers, with on-prem deployment for ITAR.
- On-Prem AI for ERP in Aerospace, Defense, and Electronics ManufacturingA hub guide to on-prem AI across SAP, Infor LN, Costpoint, IFS, and Oracle EBS for aerospace, defense, and electronics manufacturers under ITAR, CMMC, and AS9100.