Quality Teams in Medical-device Development

The quality team’s role

Quality teams design and maintain the organisational system through which regulated work is planned, performed, reviewed, recorded and improved. They advise on requirements, facilitate consistent processes and provide independent assurance. They do not “make the product compliant” after engineering has finished; quality is created through the decisions and evidence of every function.

Build a right-sized quality-management system

The QMS should describe how the organisation actually controls its products, responsibilities, records, suppliers and lifecycle decisions. Start with applicable regulatory and standard requirements, then define the smallest coherent process set that provides control. Procedures should identify responsibilities, required inputs, decisions, outputs and records; excessive detail that is routinely bypassed creates risk rather than assurance.

Use MTL-310 — ISO 13485 and Design Controls and MTL-302 — US FDA Medical-device Regulations — 21 CFR Overview to understand the external framework.

Put quality planning inside the development plan

• Identify applicable lifecycle processes, deliverables and approval authorities.
• Define competence, training and independence needs.
• Plan design reviews, audits, supplier controls and transfer readiness.
• Agree document, record, configuration and change-control arrangements.
• Identify metrics that reveal process health and product risk.
• Escalate unresolved quality or compliance risks through defined governance.

Quality planning should be visible in project decisions and resourcing, not held in a separate quality timetable.

Enable design controls without owning the design

Quality professionals help the team define approved inputs and outputs, conduct effective reviews, preserve traceability, control changes and assemble the design-and-development file. Engineering owns technical adequacy; authorised functions own their decisions; quality provides the process, coaching and assurance that the evidence chain is intact.

Connect this work to MTL-113 — Design Controls and Technical Documentation and MTL-129 — Configuration and Change Management.

Control suppliers according to product risk

Define selection, qualification, agreements, incoming controls, monitoring, change notification and re-evaluation according to the effect of the supplied product or service. Quality should ensure accountability is clear across purchasing, engineering and supplier management, while technical experts define what must be controlled.

Use MTL-123 — Supplier and Outsourced-process Control for the complete control model.

Make reviews and gates evidence-based

A quality signature should mean more than presence at a meeting. Confirm that required inputs exist, reviewers are competent and sufficiently independent, decisions and actions are recorded, unresolved issues have owners and due dates, and the approved conclusion matches the evidence. A gate may allow conditional progression, but the conditions and risk must be explicit.

Separate correction, investigation and corrective action

Do not force every defect into CAPA. Use risk, recurrence, systemic nature and regulatory impact to select the appropriate process and escalation.

Protect the trustworthiness of records

Records should be attributable, legible, contemporaneous, original or a controlled copy, accurate, complete and retrievable. Define ownership, approval, retention, access, correction and archival. Electronic systems require proportionate controls for identity, permissions, audit trails, backup, change and continued readability.

Quality must distinguish documentation that directs work from records that demonstrate what happened. Retrospective reconstruction weakens the evidence even when the underlying work was sound.

Use audits to test effectiveness—not formatting

Audit whether processes achieve their intended result, connect across functions and produce credible records. Sample real product journeys, changes, supplier decisions, deviations and complaints. Findings should describe evidence, requirement and impact clearly enough for the organisation to act. Prepare for external audits by making the system healthy, not by staging a temporary performance.

For the multi-regulator audit context, see MTL-316 — Medical Device Single Audit Program (MDSAP).

Create a quality culture that supports escalation

People must be able to raise bad news without being treated as the problem. Quality leaders should reward early disclosure, evidence-based challenge and learning; distinguish healthy control from bureaucracy; and make accountabilities visible. Metrics should expose delay, recurrence and risk rather than encourage closure at any cost.

Common misconceptions