The Improvement module is distinct from the Findings & PAC module. Findings tracks individual corrective action plans linked to specific non-conformities. The Improvement module manages broader improvement initiatives with formal root cause analysis and multi-stage lifecycle tracking.
Status pipeline
Every improvement action passes through six stages:| Stage | Description |
|---|---|
| Identificado | Action has been recorded but analysis has not started. |
| Análisis de Causa | Root cause analysis is underway. |
| Plan Definido | A corrective or improvement plan has been documented. |
| En Ejecución | The plan is being implemented. |
| Verificación | Implementation is being verified for effectiveness. |
| Cerrado | Action is complete and verified. |
Root cause analysis methods
When registering an action, select the root cause analysis methodology being applied:| Method | Description |
|---|---|
| 5 Porqués | Iterative questioning to trace a problem to its root cause |
| Ishikawa | Cause-and-effect (fishbone) diagram |
| Pareto | 80/20 analysis to identify the most significant causes |
| FMEA | Failure Mode and Effects Analysis |
| Otro | Any other methodology |
Registering a new improvement action
Click Nueva Acción
Click the Nueva Acción button in the page header to expand the registration form.
Fill in the action details
Complete the required fields:
| Field | Description |
|---|---|
| Título | Short, descriptive title for the improvement action |
| Método de Causa Raíz | Select the root cause analysis method to apply |
| Responsable | Person or team accountable for executing the plan |
| Fecha Límite | Target completion date |
| Hallazgo Vinculado | Optionally link to an existing finding from the PAC module |
| Causa Raíz Identificada | Documented root cause from the analysis |
| Plan de Acción | Step-by-step description of the corrective or improvement actions |
Tracking progress
Each action card in the list shows:- ID and title
- Current stage badge
- Responsible and due date
- Progress bar (0–100%)
- Vencido (overdue) alert if the due date has passed and the action is not closed
Linking to findings
When registering an action, you can link it to an existing finding from the Findings & PAC module. The Hallazgo Vinculado dropdown lists all registered findings by ID and description. This link provides traceability from the root cause analysis back to the originating audit finding.Default example actions
ISOwl ships with two pre-configured example actions to illustrate the workflow:| ID | Title | Method | Responsible | Status | Progress |
|---|---|---|---|---|---|
| MC-001 | Implementar capacitación en seguridad | 5 Porqués | CISO | En Ejecución | 45% |
| MC-002 | Actualización de política de contraseñas | Ishikawa | Director TI | Plan Definido | 20% |
Unlike other modules, improvement actions are stored in local React state and are not persisted to
localStorage via the Zustand store. Actions reset to defaults on page reload. For persistent corrective action tracking, use the Findings & PAC module.Related modules
Findings & Corrective Actions
Register and track PAC items derived from audit findings. Link findings to improvement actions for full traceability.
Internal Audit
Log audit findings that generate the non-conformities addressed by improvement actions.
Security Metrics
Monitor closure rates and overdue findings to identify where improvement actions are needed.
ISO 27001 Reference
Clause 10 — Mejora covers corrective actions, nonconformity management, and continual improvement requirements.