Setting up a QMS for medical device development is not a single project decision. It is a sequence. ISO 13485:2016, FDA 21 CFR Part 820, and EU MDR Article 10 all expect the same baseline before product work begins: a defined scope, documented processes, controlled records, assigned responsibilities, and evidence that the system has been verified. Skipping or reordering these steps tends to surface during the first internal audit, when missing approvals or unclear role assignments force expensive rework.
A defensible initial-implementation sequence usually covers:
- Defining the QMS scope and organisational structure with named roles and decision rights
- Mapping the processes the QMS must control (design controls, document control, CAPA, supplier management, training)
- Establishing document controls with version history, approval workflows, and retention policies
- Configuring approval workflows that produce system-generated audit evidence
- Setting up a controlled project for the QMS rollout itself, with milestones and deliverables
- Restructuring existing SOPs, work instructions, and templates into the controlled environment
- Tailoring process workflows so the system mirrors the company’s actual procedures
- Building the Quality Manual as the top-level reference document
Done in this order, the QMS produces audit-ready evidence from day one rather than retroactive paperwork before each audit.
The whitepaper below covers how qmsWrapper handles all of the above for medical device teams.
