Design review no longer needs an outside reviewer

What 7.3.4 still asks for

Clause 7.3.4 requires systematic reviews of design and development to be performed at suitable stages, in accordance with the planned arrangements a design and development plan sets out under Clause 7.3.2. Each review has to evaluate the ability of the design and development results to meet requirements, and identify any problems and propose necessary actions. Participants have to include representatives of functions concerned with the design and development stage being reviewed, along with any specialist personnel the review needs. Records of the results and of any necessary actions have to be maintained, including the identification of the design under review, the participants involved, and the date. None of that changed when the clause moved from a voluntary standard cited by reference into FDA's own regulation.

The sentence that didn't cross over

What changed is a sentence the old Quality System Regulation carried and ISO 13485:2016 never did. 21 CFR 820.30(e) required participants in a design review to include representatives of every function concerned with the stage being reviewed, and, separately, an individual who does not have direct responsibility for that design stage — an outsider, staffed in by rule rather than by whoever happened to think of it. Clause 7.3.4 has no equivalent line. It asks for representatives of the functions concerned and specialist personnel “as required,” and stops there. FDA's own preamble to the QMSR final rule says as much directly: the agency agrees the final regulation differs from the prior QS regulation and does not carry forward the explicit requirement that each design review include an individual with no direct responsibility for the stage under review. A design review procedure written to satisfy 7.3.4's actual text, and nothing more, can staff every review entirely from the people who did the work, and still clear the clause.

A dropped sentence is not a dropped expectation

FDA's own comment response frames this as the regulation's text changing, not the agency's view of what makes a review worth trusting. The reason 820.30(e) wrote the outsider requirement into a rule in the first place hasn't gone anywhere: a person who spent the last three months solving a design problem is a poor judge of whether that solution still has a flaw, in a way no amount of diligence fully corrects for. An auditor reading a design file for evidence that a review was a real check, not a formality, still has reason to ask who was in the room and whether anyone there could have said no without contradicting their own prior sign-off. A design change record already has to function as something “closer to a second design review than a signature line” under Clause 7.3.9 — the same standard for what counts as a real review, not a staffing rule, is exactly what a team now has to hold itself to on the clause that dropped its explicit version of it.

What the record has to carry instead of a rule

With participant selection no longer constrained by regulatory text, the burden shifts entirely onto what the record can show after the fact. Clause 7.3.4's own record requirements — identification of the design reviewed, the participants involved, the date — are what a later audit has to work from, and a record that names only titles rather than actual reporting lines can't answer the question an auditor is really asking: did anyone in that room have standing to push back. That's the same distinction Clause 4.2.5's records are built to carry generally — dated, specific evidence that something happened, not a form that only proves a meeting was scheduled.

Where this meets the rest of the file

Design review sits between two clauses this blog has already covered: it comes after design inputs are fixed and before verification and validation test the output against them — the stage meant to catch a wrong turn while it's still a design decision, not a failed test result. Its place in the file hasn't moved even though one line describing who has to sit in it did, the same kind of renumbering this blog has already traced across QMSR's other design-control clauses. A design review procedure that still names an independent participant as a requirement, not just a habit, is previewed in the launch catalog. If your program draws this line differently, the shelf takes that correction directly.