A design review checklist that is just a box-ticking exercise is worse than useless — it creates false confidence that a design has been validated when it has merely been processed. A checklist that actually works forces structured thinking on the design’s most likely failure modes before metal is cut.
Design reviews are formal gate events in a product development process where a design is evaluated against established criteria by a multidisciplinary team. Done well, they catch problems that individual designers miss because of familiarity bias, optimistic assumptions, or simple blind spots. Done poorly — with vague checklists, no pre-read, and attendees who have not reviewed the materials — they consume hours of engineering time and produce no actionable findings. This article covers the types of design reviews in mechanical product development, how to structure a checklist that generates genuine insight, how to run the meeting effectively, and how to track action items to closure.
Types of Design Reviews: PDR, CDR, and FDR
Product development programs typically include three formal design reviews at increasing levels of design maturity:
Preliminary Design Review (PDR): Conducted after the concept phase is complete and a preliminary design approach has been selected. At PDR, requirements allocation has been done, the major architecture is defined, and key trades (weight, cost, performance, risk) have been analyzed. The checklist focuses on: Are the requirements captured correctly? Is the design approach technically feasible? What are the highest technical risks and what is the mitigation plan? PDR gates the transition from concept to detailed design — a failed PDR (significant unresolved requirements gaps or high-risk architectural choices) should require further concept work before design begins.
Critical Design Review (CDR): Conducted when the detailed design is substantially complete — drawings are at or near release quality, analysis is done, and manufacturing and procurement plans are in place. CDR is the most rigorous review and the final opportunity to catch design deficiencies before production tooling and component procurement are committed. The checklist covers all technical disciplines in depth: structural margins, thermal management, manufacturing feasibility, assembly sequence, GD&T completeness, BOM accuracy, and safety analysis.
Final Design Review (FDR) / Production Readiness Review (PRR): Conducted after design iterations from CDR are incorporated and first articles (prototypes) have been tested. FDR verifies that all CDR action items are closed, prototype test results confirm analytical predictions, manufacturing processes are validated, and the design is ready for production release. The checklist is focused on verification closure and production readiness, not on fundamental design adequacy (that should have been confirmed at CDR).
Checklist Structure: Categories That Matter
A design review checklist should be organized by functional category, not by document type. Categories that consistently produce actionable findings:
1. Requirements Compliance
- Is every customer/system requirement allocated to a component or subsystem?
- Are derived requirements documented and traceable to parent requirements?
- Are there any requirements that have no analysis or test to verify them?
- Have any requirements been waived? Is the waiver documented and approved?
2. Structural and Mechanical Analysis
- Have all load cases been identified (static, dynamic, fatigue, impact, thermal)?
- Are all structural margins positive with the required safety factor (typically 1.25–2.0 depending on application and material uncertainty)?
- Has fatigue life been calculated for cyclic load cases?
- Are stress concentrations (notches, holes, sharp corners) identified and analyzed?
- Has buckling been checked for all slender/thin-walled features?
- Are bolted joint calculations complete (preload, torque, fatigue)?
3. Manufacturing and Producibility
- Has a manufacturing engineer reviewed all drawings for processability?
- Are tolerances achievable with the intended manufacturing process at reasonable cost?
- Are there features that require special tooling or processes not currently available?
- Are GD&T callouts complete, consistent, and measurable?
- Are surface finish requirements appropriate — neither too tight nor too loose for function?
- Are weld joints accessible for the specified welding process and inspection?
- Are thread callouts complete (tolerance class specified)?
4. Assembly and Disassembly
- Can every component be assembled in the correct sequence without interference?
- Is there adequate clearance for tools at all fastener locations?
- Are there blind fasteners that cannot be inspected after assembly?
- Can the product be disassembled for servicing without damaging non-replaced components?
- Are anti-rotation and anti-loosening features (locking fasteners, thread-locking adhesive) specified for all critical fasteners?
5. Safety and Regulatory
- Has a Failure Mode and Effects Analysis (FMEA) been completed?
- Are all failure modes with severity rating ≥ 7 mitigated to acceptable risk levels?
- Are all sharp edges accessible to users chamfered or radiused?
- Are guarding and warning requirements identified and incorporated?
- Are all required certifications (CE, UL, ATEX, etc.) identified? Is a certification plan in place?
6. Reliability and Life
- Has a design life target been set and is there analysis supporting it?
- Have wear items been identified with replacement intervals?
- Are wear surfaces protected (hardening, coating, material selection)?
- Are seals and gaskets appropriate for the operating environment (temperature, fluid compatibility)?
7. Cost and Schedule
- Has a design-to-cost estimate been completed?
- Are there cost reduction opportunities that do not compromise function?
- Are long-lead purchased items identified and procurement initiated?
- Is the BOM complete enough to support accurate costing?
Who Should Attend
A design review is only as good as the expertise in the room. Required attendees:
- Design engineer(s): Present and defend the design; answer technical questions
- Manufacturing engineer: Reviews producibility; flags process constraints
- Quality engineer: Reviews inspection plans, GD&T, and regulatory requirements
- Stress/structural analyst: Reviews analysis assumptions and margins
- Procurement/supply chain: Reviews BOM for sourcing risks and long-lead items
- Technical lead or chief engineer: Provides technical oversight and decision authority
For CDR and FDR, additional attendees may include: reliability engineer, safety engineer, test engineer, customer technical representative, and manufacturing plant manager. The review should be led by a facilitator who is not the design engineer — this prevents the designer from managing the discussion in a way that deflects scrutiny of weak areas.
Running the Review Effectively
- Pre-read package distribution: Send all review materials (drawings, analysis reports, BOM, checklist with self-assessment) at least one week before the review. Attendees who have not read the materials cannot contribute meaningfully.
- No surprises rule: The review meeting is for discussion and resolution of concerns identified during pre-read, not for first-time presentation of the design. Presenting new information at the meeting itself indicates inadequate preparation.
- Capture all findings: A dedicated scribe records every concern, question, and action item with the person responsible and a due date. Verbal-only findings that are not captured disappear.
- Distinguish findings from actions: A finding is an identified issue; an action is the specific activity needed to resolve it. Not all findings result in design changes — some result in analysis, testing, or documentation that confirms the design is adequate.
- Review exit criteria: Define explicitly what constitutes a successful review. “Zero open critical findings” and “all action items have owners and due dates” are typical criteria. Do not close the review without meeting the exit criteria.
Action Item Tracking to Closure
Action items from a design review are only valuable if they are actually closed. Best practices:
- Maintain a numbered action item log with: action description, responsible engineer, due date, current status (open/in-progress/closed), and closure evidence (what was done)
- Review open action items at weekly program team meetings — items without progress get escalated
- Require documented closure evidence (revised drawing, updated analysis, test report) — “discussed and resolved” is not a closure
- Critical actions (those affecting safety margins, regulatory compliance, or fundamental design choices) require review of the closure evidence by the technical lead before the action can be marked closed
Common Design Review Mistakes
- Reviewing too early: PDR conducted before the design is mature enough to evaluate — results in generic concerns rather than specific, actionable findings
- Reviewing too late: CDR conducted after production tooling is ordered — too costly to change fundamental design issues
- Social pressure against findings: Team culture where raising concerns is seen as “being difficult” — the most important function of a design review is being suppressed
- Checklist compliance without insight: Items checked “yes” without genuine evaluation — “we’ve always done it this way” substitutes for technical judgment
- No follow-through: Action items are recorded but never tracked; the review generates paperwork but no design improvement
Conclusion
A design review checklist that actually works is specific, multidisciplinary, tied to the design’s maturity level, and used by people who have genuinely studied the design beforehand. The categories — requirements, structural analysis, manufacturing, assembly, safety, reliability, and cost — should be calibrated to the product’s risk profile and refined after each program based on what kinds of findings were missed. The review itself is a team sport: the value comes from the diversity of expertise applying focused scrutiny to a common design package. Action items tracked to closure are the proof that the review produced value. Organizations that invest in rigorous design reviews consistently deliver better products with fewer late-stage surprises.
コメント