Glossary
CAPA stands for Corrective and Preventive Action. It is a systematic, documented process for investigating problems, finding their root causes, and implementing changes that prevent recurrence. CAPA is defined under ISO 9001:2015 (Clauses 10.2 corrective action and 10.3 continual improvement) and is core to quality management across regulated industries. This guide covers the standard CAPA workflow with an apparel-specific worked example.
CAPA (Corrective and Preventive Action) is a quality management discipline for responding to product, process, or system failures in a structured, documented way. The objective is not just to fix the problem in front of you; it is to find the root cause and prevent the problem from recurring across the operation.
ISO 9001:2015, the international standard for quality management systems, is the primary framework. Clause 10.2 (Nonconformity and corrective action) sets the requirement for organisations to react to nonconformities, evaluate the need for action, implement action, and review effectiveness.
Clause 10.3 (Continual improvement) extends this to ongoing improvement of the quality management system.
Industries with regulator-grade quality requirements (pharmaceutical, medical devices, aerospace, automotive) typically operate CAPA as a formal documented procedure with named roles, escalation paths, and review cycles. Apparel, footwear, and textiles operate CAPA more variably.
The ESPR's growing data and traceability requirements are pushing apparel toward more formalised CAPA, particularly for defects that produce destruction or rework volumes reportable under Article 24.
A complete CAPA cycle has six steps, each with its own documentation. The steps are sequential but the cycle iterates: a CAPA closed in step 6 may surface a new problem that initiates the next CAPA.
The problem is detected and described. Source can be internal (inspection, audit, returns analysis) or external (customer complaint, regulator finding, supplier notification). The identification record captures what was observed, when, where, by whom, and the immediate containment action if any.
The investigation that distinguishes symptoms from causes. Common methods include the 5 Whys, Ishikawa (fishbone) diagrams, Fault Tree Analysis, and Is/Is Not analysis. The output is a root cause statement: the specific underlying condition that, if changed, would have prevented the problem.
The proposed corrective action (fixing the cause of the existing problem) and preventive action (preventing similar problems elsewhere) are specified. Each action has an owner, a target date, and a verification method. Action plans are approved by a designated authority before implementation begins.
The actions are executed. Implementation evidence (records, photos, training certificates, updated procedures) is captured. Implementation may take days or months depending on the scope; long-running CAPAs maintain progress checkpoints.
After implementation, the organisation verifies that the action achieved its objective. This is the step most often skipped in immature CAPA processes. Verification methods include re-inspection, audit, statistical monitoring of the affected process, and customer feedback over a defined period.
Once verification confirms effectiveness, the CAPA is formally closed. The closure record includes the verification evidence, any lessons learned for the organisation's broader process, and references to related CAPAs. Closed CAPAs feed into the organisation's CAPA history for trend analysis.
The two halves of CAPA are easy to confuse. The distinction matters because they apply to different scenarios and produce different types of evidence.
Corrective action responds to a problem that has already occurred. It fixes the specific instance and changes the underlying condition so the same problem does not recur.
Example: a stitching defect found on 5 percent of a production batch triggers an investigation, the root cause is traced to an out-of-calibration sewing machine, the machine is recalibrated, and the operator training is updated. The action is reactive but systematic.
Preventive action addresses a potential problem that has not yet occurred. It changes a condition that creates risk before that risk becomes a defect.
Example: an analysis of warranty data shows that brands sourcing from a particular factory have a higher rate of seam failure 6 months post-purchase; the brand introduces a more rigorous incoming inspection protocol for that factory before defects appear in the current production batch. The action is proactive and statistical.
ISO 9001:2015 places more emphasis on corrective action than the earlier ISO 9001:2008 framework did. Preventive action in 2015 is largely subsumed into the risk-based thinking embedded throughout the standard rather than treated as a separate clause.
In practice, brands distinguish the two when scoping a CAPA: is the trigger an observed problem (corrective) or a forecast risk (preventive)?
Consider a sporting goods brand that begins receiving returns from retail for a particular t-shirt SKU, with the same defect across multiple units: a side seam failure under moderate stretch. The returns rate on this SKU has risen from 0.3 percent to 1.8 percent over six weeks.
Step 1, identification. The returns analytics team logs the pattern, captures the unit identifiers and the defect photos, and opens a CAPA in the quality system.
Step 2, root cause analysis. The quality team applies the 5 Whys. Why is the seam failing?
The thread tension is below the design specification. Why is the thread tension low?
The sewing machine for this SKU has been operating with a worn tension assembly. Why has the worn assembly not been replaced?
The maintenance schedule for the assembly was set at 18 months but the operational hours on this machine have been higher than assumed. Why was the higher operational hours not flagged?
The maintenance schedule is based on calendar time, not operational hours. The root cause is the maintenance scheduling methodology, not the worn part itself.
Step 3, action planning. The corrective action is to replace the tension assembly on the affected machine and inspect adjacent machines. The preventive action is to shift the maintenance schedule from calendar time to operational hours across all sewing machines, with the operational hours data captured automatically from the machine control system.
Step 4, implementation. The assembly is replaced within 48 hours. The operational-hours-based maintenance schedule is rolled out over the next 6 weeks, requiring data integration with the machine control system.
Step 5, verification. Returns rate on the affected SKU is monitored for 12 weeks post-implementation; it returns to 0.3 percent within the first 4 weeks and remains stable.
Step 6, closure. The CAPA is closed with the verification evidence. The lessons-learned record flags maintenance scheduling methodology as a candidate review topic across the wider operation.
CAPA software is a category of quality management tools that automate the CAPA workflow. The capabilities typically include a structured issue intake form, automated routing to the assigned investigator, root cause analysis templates (5 Whys, Ishikawa, fault tree), action planning with owners and dates, implementation tracking with evidence capture, verification scheduling, and closure with audit-grade documentation.
For apparel and textiles, the CAPA-software conversation often runs alongside the broader quality management system (QMS) selection. Brands typically choose one of three approaches: a general-purpose QMS with a CAPA module, a quality-specific platform with strong CAPA capability, or a specialist tool focused on a specific industry vertical.
The selection criteria that matter most for apparel: how the tool handles supplier-side CAPA (where the issue originates with a manufacturing partner rather than internal operations), how the tool captures photo evidence at the unit level, and how the tool integrates with the operational systems that produce the underlying data (PIM, ERP, rework coordination, returns analytics). A CAPA tool that requires separate data entry from these systems creates a parallel-data-entry burden that erodes the discipline of the CAPA process itself.
Flexireo is not a CAPA platform. The platform's purpose is the operational coordination of rework, refurbishment, and disposition decisions for apparel and footwear.
CAPA is the broader quality management discipline that may or may not be running in parallel.
What Flexireo contributes to the CAPA discipline is the operational evidence that feeds CAPA investigations: unit-level identifiers, time-stamped status changes, photo evidence at decision points, supplier-side workshop records, and chain-of-custody data for batches routed through rework. For a brand running CAPA on a separate quality system, the Flexireo record is the operational source of evidence that the CAPA process can reference and attach.
The brands we have worked with run CAPA in their existing QMS and use Flexireo as the operational layer for rework specifically. The two systems coexist; the data flow is one-directional from Flexireo (operational events) to the QMS (CAPA records).
Book a 30-minute demo and we will show you how the operational data layer for rework coordination produces CAPA-grade evidence as a byproduct: unit identifiers, time-stamped status changes, photo evidence at decision points. The data flows back into your quality management system without parallel data entry.