ISO 13485 clause 4.1 requires manufacturers to do more than list their quality procedures. It requires identifying each process that affects product conformity, mapping the inputs and outputs of that process, defining the sequence and interaction between processes, assigning adequate resources, and establishing monitoring criteria. That structural requirement is what distinguishes the process approach from a document library. A quality manual that describes activities without tracing how those activities connect, consume resources, and produce verifiable outputs does not satisfy clause 4.1 in substance.
The distinction between a documented procedure and a controlled process is one of the most audited gaps in ISO 13485 implementations. A documented procedure captures what people are supposed to do. A controlled process has defined inputs, produces records that confirm the outputs were achieved, carries measurable performance criteria, and is reviewed when results fall outside acceptable limits. Under FDA QMSR (21 CFR Part 820, 2024 alignment) and EU MDR Annex IX, auditors look for evidence that processes are monitored, not just described.
Process flowcharts serve a dual purpose in a compliant QMS. At the design stage they are planning tools, forcing teams to identify decision points, responsible roles, and the records each step must generate. Once the process is live, those same flowcharts become objective evidence of how the system was intended to operate, which an auditor can compare against actual practice. When the flowchart and the records diverge, that divergence is a nonconformity.
Process metrics feed directly into management review under clause 5.6. Cycle time, nonconformance rate, escape rate, and on-time completion are common process-level indicators. The common failure mode is collecting metrics that are never acted on: numbers reported at management review with no trend analysis, no comparison to targets, and no corrective actions initiated. A second common failure is process isolation, where a process exists in the QMS but the records it is supposed to generate live in a separate system, making traceability between process execution and output difficult to demonstrate during an audit.
The whitepaper below details how qmsWrapper structures and connects controlled processes so that every step from input to record is traceable, measurable, and audit-ready.
