Design Review Evidence for Medical Devices: Agenda, Minutes, Independence, and FDA/ISO Expectations

Why Design Review Evidence Is One of the Most Audited Elements in Medical Device Development

Design reviews are mandatory checkpoints in medical device development where cross-functional teams formally evaluate whether the design is progressing correctly. But conducting the review is only half the requirement — documenting it properly is what separates compliant companies from those receiving FDA Form 483 observations and warning letters.

The FDA has cited design review deficiencies in numerous warning letters. In one published case, a manufacturer "performed design review sporadically throughout the device design development, did not identify the stage being covered or what information was covered, and did not include an independent individual without direct responsibility for the stage being reviewed." This single observation encapsulates the three most common failures: irregular timing, incomplete documentation, and lack of independence.

Under FDA 21 CFR 820.30(e), ISO 13485:2016 Clause 7.3.5, and the QMSR effective February 2, 2026, manufacturers must plan, conduct, and document formal design reviews at appropriate stages. This guide explains exactly what constitutes adequate design review evidence, how to structure agendas and minutes, and how to satisfy independence requirements.

Regulatory Requirements for Design Reviews

FDA 21 CFR 820.30(e) — Design Review

The FDA regulation states:

Each manufacturer shall establish and maintain procedures to ensure that formal documented reviews of the design results are planned and conducted at appropriate stages of the device's design development. The procedures shall ensure that participants at each design review include representatives of all functions concerned with the design stage being reviewed and an individual(s) who does not have direct responsibility for the design stage being reviewed, as well as any specialists needed. The results of a design review, including identification of the design, the date, and the individual(s) performing the review, shall be documented in the design history file (the DHF).

This regulation establishes five concrete requirements:

1. Procedures must exist for planning and conducting design reviews
2. Timing must be at "appropriate stages" — not ad hoc or sporadic
3. Cross-functional participation from all functions concerned with the design stage
4. Independent reviewer(s) who do not have direct responsibility for the stage being reviewed
5. Documented results including design identification, date, and participant identification, filed in the DHF

ISO 13485:2016 Clause 7.3.5 — Design and Development Review

ISO 13485 states that systematic reviews shall be performed at suitable stages to:

• (a) Evaluate the ability of the results of design and development to meet requirements
• (b) Identify and propose necessary actions

Participants must include representatives of functions concerned with the design stage being reviewed and other specialist personnel. Records of results, actions, identification of the design, participants, and dates must be maintained.

Key Difference Between FDA and ISO 13485

The FDA explicitly requires an independent reviewer — someone who does not have direct responsibility for the design stage being reviewed. ISO 13485 does not contain this explicit requirement but instead requires "representatives of functions concerned" and "other specialist personnel."

Under the QMSR, the FDA incorporates ISO 13485 by reference but preserves the independence requirement through 21 CFR 820.10 supplemental provisions. In the FDA's CDRH Town Hall on QMSR design and development, the agency confirmed that "ISO 13485 provides adequate flexibility for organizations to balance personnel resources while ensuring effective independent review." The FDA expects manufacturers to include appropriate personnel who can provide meaningful oversight of the design process.

What the FDA Looks for During Inspections

Based on published FDA inspection data and the MDSAP Companion Audit guidance, inspectors specifically review:

• Whether design reviews were conducted at planned, documented stages
• Whether attendance records include an independent reviewer
• Whether minutes capture decisions, action items, and their closure
• Whether the review content matches the design stage being evaluated
• Whether action items from previous reviews were addressed before advancing to the next phase

Planning Design Reviews: When and How Many

Number and Timing of Reviews

There is no prescribed number of design reviews in the regulations. The requirement is "appropriate stages," which means the number and timing depend on device complexity and risk level.

For a typical Class II or Class III medical device, the following design review structure is common and well-accepted by regulators:

For simpler devices, some reviews may be combined (e.g., DR-4 and DR-5). For complex devices with software, additional reviews may be needed at software architecture and detailed design stages. The key is that the design plan documents when reviews will occur, and the actual reviews follow the plan.

Practical Timing and Duration

Design reviews should typically be limited to 60–90 minutes to maintain focus and engagement. Sharing all relevant documentation with attendees at least one week in advance allows participants to prepare questions and comments, which dramatically improves review quality. Keep the discussion strictly to the agenda — if unrelated topics arise, capture them as parking lot items and address them outside the review.

Equally important is creating a culture where honest critique is valued over rubber-stamping. The independent reviewer must feel genuinely free to challenge assumptions, question the design direction, and raise concerns without social or professional repercussions. Companies that build this culture of trust consistently produce safer, more effective devices.

Documenting the Review Plan

The design and development plan (required by ISO 13485 Clause 7.3.2) should specify:

• Planned review stages and their timing relative to design milestones
• Required participants for each stage
• Expected deliverables (inputs, outputs, risk assessments) for each review
• How reviews will be documented and filed

Design Review Agenda: Structure and Content

Every design review should have a prepared, documented agenda distributed to participants in advance. The agenda serves as both a planning tool and evidence that the review was structured, not informal.

Recommended Agenda Structure

1. Administrative Information (5 minutes)

• Design project name and identification
• Design review number (e.g., DR-3)
• Date, time, and location (or virtual meeting link)
• Attendance — all participants sign in, including name, role, and signature

2. Review Objectives (5 minutes)

• Statement of the design stage under review
• Summary of what is expected to be evaluated at this stage
• Reference to the design plan section governing this review

3. Design Status Update (15–30 minutes)

• Summary of design progress since the last review
• Key deliverables produced (inputs, outputs, risk assessments, test results)
• Status of action items from previous reviews

4. Technical Review (30–60 minutes, varies by stage)

• Detailed evaluation of the design artifacts specific to this stage
• For DR-2: Review of each design input for completeness, verifiability, and traceability
• For DR-3: Review of design outputs against inputs, acceptance criteria, and risk controls
• For DR-4/DR-5: Review of verification/validation protocols, results, and deviations
• For DR-6: Review of DMR completeness, process validation status, supplier readiness

5. Risk Management Review (10–20 minutes)

• Status of risk management activities per ISO 14971
• New risks identified, risk control measures implemented
• Residual risk acceptability assessment
• Integration of post-market surveillance data if available

6. Open Issues and Action Items (10–15 minutes)

• Identification of problems, concerns, or gaps
• Assignment of action items with owners and due dates
• Closure status of previously assigned action items

7. Independent Reviewer Comments (5–10 minutes)

• Formal input from the independent reviewer
• Documented observations, concerns, or recommendations

8. Decision and Conclusion (5 minutes)

• Go/no-go/rework decision for the design stage
• Conditions for advancement to the next stage
• Signatures of reviewers

Design Review Minutes: What Must Be Documented

Design review minutes are the primary evidence artifact. If the minutes are inadequate, the review effectively did not happen from a regulatory perspective.

Required Elements in Design Review Minutes

Both FDA and ISO 13485 require specific content in review records:

Minutes Template

DESIGN REVIEW RECORD
═══════════════════════════════════════════════════════════
Project: [Device Name]                Review #: DR-[#]
Stage: [Design Input / Output / Verification / etc.]
Date: [YYYY-MM-DD]                    Time: [HH:MM] – [HH:MM]
Location: [Room / Virtual]

ATTENDANCE
═══════════════════════════════════════════════════════════
Name              | Role                  | Independent? | Signature
------------------|-----------------------|--------------|----------
[Name]            | Design Lead           | No           | ________
[Name]            | Quality Engineer      | Yes          | ________
[Name]            | Regulatory Affairs    | No           | ________
[Name]            | Manufacturing Eng.    | No           | ________
[Name]            | Risk Management       | Yes          | ________

AGENDA ITEMS
═══════════════════════════════════════════════════════════
1. [Agenda item 1]
2. [Agenda item 2]
3. [...]

DISCUSSION SUMMARY
═══════════════════════════════════════════════════════════
[Item 1]: [Summary of discussion, key findings]
[Item 2]: [Summary of discussion, key findings]

ACTION ITEMS
═══════════════════════════════════════════════════════════
ID     | Description                  | Owner     | Due Date  | Status
--------|------------------------------|-----------|-----------|--------
AI-001  | [Action item description]    | [Name]    | [Date]    | Open
AI-002  | [Action item description]    | [Name]    | [Date]    | Open

PREVIOUS ACTION ITEMS REVIEW
═══════════════════════════════════════════════════════════
ID     | Description                  | Status    | Closure Evidence
--------|------------------------------|-----------|-------------------
AI-XXX  | [Previous action item]       | Closed    | [Reference to evidence]

INDEPENDENT REVIEWER STATEMENT
═══════════════════════════════════════════════════════════
[Independent reviewer's formal observations, concerns, or
recommendations. This section must be present and substantive.]

DECISION
═══════════════════════════════════════════════════════════
[  ] APPROVED — Proceed to next design stage
[  ] APPROVED WITH CONDITIONS — [List conditions]
[  ] REWORK — [List required changes before proceeding]

Approved by:
Design Lead: _______________ Date: ________
Quality:     _______________ Date: ________
Independent: _______________ Date: ________

The Independent Reviewer Requirement

Who Qualifies as an Independent Reviewer?

The FDA requires "an individual(s) who does not have direct responsibility for the design stage being reviewed." This means:

• The person must not be the designer, engineer, or project lead for the specific design stage under review
• The person must be qualified to evaluate the design content — they need relevant technical competence, not just any warm body from another department
• The person should be free from bias — they should not have their performance evaluation or compensation directly tied to the success of the specific design stage

Common independent reviewer choices:

Common Independence Mistakes

Mistake 1: Rotating independence within the same team Having the software lead serve as independent reviewer for the mechanical stage, and the mechanical lead serve as independent reviewer for the software stage, can satisfy the letter of the regulation but may not satisfy the spirit — especially if both individuals report to the same project manager and share project success metrics.

Mistake 2: Independent reviewer in name only An individual listed as the independent reviewer who did not actually attend the meeting, did not review the materials beforehand, or signed the minutes without providing any documented input. FDA inspectors have flagged this pattern in warning letters.

Mistake 3: No documented evidence of independence If the minutes do not clearly identify which participant(s) served as the independent reviewer and what their contribution was, the independence requirement is not met from a documentation standpoint.

Best Practice: Independent Reviewer Statement

Include a dedicated section in the minutes where the independent reviewer provides a brief written statement. This does not need to be lengthy — even a paragraph confirming they reviewed the materials, agree with the findings, and have no unresolved concerns (or documenting specific concerns) is sufficient. The key is that the statement exists, is substantive, and is signed.

Action Item Management

Design reviews almost always generate action items. How these are managed is itself a regulatory concern.

Action Item Lifecycle

1. Identification: Action items are raised during the review and captured in the minutes
2. Assignment: Each item has a named owner and a due date
3. Tracking: Open items are tracked in a log or database
4. Resolution: The owner completes the action and documents the evidence
5. Closure: The completed action item and its evidence are reviewed at the next design review
6. Filing: Closure evidence is filed in the DHF/DDF

Critical Rule

All action items from a design review must be closed before or at the next design review. Carrying open items across multiple reviews without documented progress is a red flag for auditors. If an item cannot be closed by the next review, the reason for the delay and the plan for closure must be documented.

Design Reviews in the Context of QMSR

Under the QMSR, effective February 2, 2026, design reviews fall under ISO 13485 Clause 7.3.5 as incorporated by reference. Key implications:

• Terminology: The Design History File (DHF) concept maps to the ISO "Design and Development File" (DDF). The FDA has stated it does not expect retroactive terminology changes, but new files should use consistent terminology
• Risk integration: ISO 13485 and QMSR expect risk management (per ISO 14971) to be integrated into design reviews, not treated as a separate activity. Each design review should include a risk management status update
• Design and development file: ISO 13485 Clause 7.3.10 requires a design and development file for each device type or family. Design review records are core contents of this file
• Continued updates: The FDA confirmed in its CDRH Town Hall that the design and development file must be continually updated for the life of the device — changes made post-market must be reflected through change control records that reference back to the original design reviews

Checklist: Design Review Evidence Readiness

Before each design review, verify:

• Design review procedures are established and current
• The design plan identifies this review stage and its timing
• An agenda is prepared and distributed in advance
• All required functions are represented (design, quality, regulatory, manufacturing)
• At least one independent reviewer is identified and confirmed to attend
• Materials for review are available to participants before the meeting
• Attendance sheet is ready for signatures
• Previous action items are updated with closure evidence

After each design review, verify:

• Minutes capture all required elements (design ID, date, participants, discussion, actions, decision)
• Independent reviewer participation is documented with a substantive statement
• All action items have owners and due dates
• A go/no-go/rework decision is recorded with rationale
• Minutes are signed by the required approvers
• Minutes and supporting materials are filed in the DHF/DDF
• Action items from previous reviews are closed or have documented justification for delay

Key Takeaways

Design review evidence is one of the most scrutinized elements in medical device quality system audits. The regulations — whether FDA 21 CFR 820.30(e), ISO 13485 Clause 7.3.5, or the QMSR — all require the same core elements: planned reviews at appropriate stages, cross-functional participation including independent reviewers, and thorough documentation of decisions and actions. The documented minutes must tell a complete story — who was there, what was reviewed, what was decided, and what actions were assigned. When this evidence chain is complete, design reviews become one of the strongest demonstrations of a compliant, well-controlled development process.