Quality · eQMSCAPA Management

CAPA software that follows every action to verified closure.

Swat iQua Suite CAPA software gives you one corrective and preventive action register for the whole site. Deviations, OOS investigations, lab quality events, audits, stability failures and audit-trail reviews all raise their CAPAs into it — and every action is verified, closed and, where you choose, reviewed for effectiveness.

  • Raised from the source record — approved with it
  • Segregation of duties with no admin bypass
  • Hard overdue gate on final close
  • Optional effectiveness review

Real product footage

Watch a CAPA from source to approval.

CAPA lifecycle

From the event that raised it to a closed, effective CAPA.

A standalone CAPA goes Draft → In Review → In Approval → Open. A CAPA raised from a deviation, OOS or audit opens when its source record is approved. Both paths then run the same controlled close-out.

  1. OpenSource or standalone

    CAPA opened

    Approved through its own review chain, or in the same step as the deviation, OOS or audit that raised it.

    Open
  2. ActionsOwner ≠ verifier

    Actions verified

    Each action is verified by someone other than its owner. Extensions are requested and approved inside the window.

    Actions verified
  3. CloseOverdue gate

    In closure

    Final close is blocked while any action is overdue without an approved extension.

    In closure
  4. ReviewOptional

    Effectiveness review

    Confirm the fix worked before the CAPA is finally closed — or close directly where no review is needed.

    Closed

Extension Requested is a side-state at any point — every request, approval and rejection is in the audit trail.

Key capabilities

A CAPA management system built around controls, not reminders alone.

  • Two entry modes

    Raise a standalone CAPA, or let the source record raise it. A source-raised CAPA cannot be approved on its own — it is approved when the deviation, OOS, audit or event is approved.

  • Segregation of duties

    Preparer ≠ reviewer ≠ approver. An action’s verifier ≠ its owner. An extension’s approver ≠ its requester. Checked on the server, with no admin bypass.

  • Extensions and overdue gate

    Extension requests are allowed inside a 30-day window. Without an approved extension, an overdue action blocks final close.

  • Effectiveness review

    An optional effectiveness review step before final close, so you can show the root cause was really addressed.

  • Daily reminder digest

    A daily email digest lists overdue actions and extension requests waiting for approval.

  • Controlled print & API

    Controlled PDF print, watermarked preview and blank form. CAPA records are also available through the REST API.

How it works

One CAPA hub, worked from wherever the problem started.

In many plants CAPAs live in a spreadsheet that nobody fully trusts: actions are copied from investigation reports, due dates drift and the link back to the original deviation is a reference number typed by hand. Swat iQua Suite removes the copying. The CAPA is created from the source record itself, so the deviation, OOS, audit observation or lab event and its CAPA stay linked for good.

Source-driven approval

When a CAPA is raised from a source record, its approval moves with that record. Approving a deviation approves its CAPA in the same step; approving the final level of an OOS investigation approves the CAPA raised from it. The CAPA hub refuses to approve a source-raised CAPA by itself, so the investigation and the corrective action can never be approved by different chains.

Work the CAPA from inside the source record

The full CAPA work panel — verify actions, request extensions, close and record effectiveness — is also available inside each source record. A QA reviewer looking at a deviation can see and work its CAPA without leaving the page.

Where CAPAs come from

  • Deviation Management — a CAPA raised from the deviation and approved with it.
  • OOS & Lab Incident Investigation — one CAPA per OOS or lab quality event when CAPA is required.
  • Audit Management — internal, external and supplier audits, one CAPA per observation.
  • Stability Study Management — escalation for a failure or out-of-trend result.
  • Audit Trail Review — a finding from a periodic audit trail review raises a CAPA.

Change control is deliberately not a CAPA source: a change’s corrective mechanism is its own set of verified change actions. Open CAPAs also count at batch release — the release checklist cannot be attested while linked deviation, OOS or CAPA records still block it.

Keeping the register honest

Every change to a CAPA is written to the audit trail in the same transaction, with a mandatory reason. A read-only integrity check scans the register for rule violations, so QA can show an inspector that the controls hold across every record, not only the ones they open.

Regulations

Designed to support GMP CAPA expectations.

  • US FDA cGMP

    Investigations and their follow-up documented, reviewed and approved by the quality unit, with a complete record.

    FDA cGMP
  • 21 CFR Part 11

    Audit trail on every change, a reason for each change and electronic signatures where your site requires them.

    21 CFR Part 11
  • Revised Schedule M · WHO GMP

    Corrective and preventive actions tracked to closure as part of a documented pharmaceutical quality system.

    Revised Schedule M

FAQ

Frequently asked questions

Can’t find your answer? Talk to our team — we reply within one business day.

What is CAPA software?

CAPA software manages corrective and preventive actions in a controlled system instead of spreadsheets. In Swat iQua Suite, CAPAs are raised from the deviation, OOS, audit or other record that found the problem, then tracked through action verification, closure and an optional effectiveness review.

Can a CAPA be raised without a deviation?

Yes. A standalone CAPA (type “Other”) has its own review and approval chain: Draft, In Review, In Approval and Open. Source-raised CAPAs skip that chain because they are approved with their source record.

How are overdue CAPA actions handled?

Owners can request an extension inside a 30-day window, and the approver must be a different person. An overdue action without an approved extension blocks final close, and a daily email digest lists overdue items and pending extension approvals.

Does Swat iQua Suite check CAPA effectiveness?

Yes, as an optional step. After the actions are verified and the CAPA is in closure, you can record an effectiveness review before the CAPA is finally closed.

Does change control raise CAPAs?

No. Change control has its own change actions, verification and effectiveness review. CAPAs are raised from deviations, OOS investigations, lab quality events, audits, stability and audit trail reviews.

Ready to see Swat iQua Suite in action?

Book a free, personalised demo and see how Swat iQua Suite takes your plants, labs and quality teams from paper to inspection-ready.

Download the brochure →