Skip to content
Certifyi

Glossary

What is CAPA?

CAPA, short for corrective and preventive action, is the plan, owner and due date attached to an audit finding or incident, tracked until the fix is confirmed and the underlying cause addressed. It is how a management system shows that it learns from what went wrong.

Correction, corrective action and prevention

A correction fixes the immediate problem, such as removing an account a leaver still had. A corrective action removes the cause, such as fixing the offboarding step that missed it. A preventive action deals with a problem that has not happened yet, such as checking whether other systems have the same gap.

Current ISO management system standards handle prevention through risk planning in clause 6.1, so clause 10.2 is titled “nonconformity and corrective action”. The term CAPA is still widely used, especially by teams with a quality management or medical device background.

What ISO 27001 and ISO 42001 ask for

When a nonconformity occurs, clause 10.2 expects the following, plus changes to the management system where the cause calls for them.

At a certification audit, a minor nonconformity needs a corrective action plan the auditor accepts. A major nonconformity has to be resolved and verified before a certificate is issued.

  • React. Control and correct the problem, and deal with its consequences.
  • Find the cause. Review the nonconformity, work out why it happened, and check whether similar ones exist or could occur.
  • Act. Carry out the action needed to remove the cause.
  • Check effectiveness. Review whether the action worked.
  • Record. Keep documented information on what went wrong, what was done and the result.

What a good CAPA record looks like

Each record links to the finding or incident, describes the problem, states the root cause, and sets out the action, owner and due date. It then holds evidence that the action was done and, after a suitable interval, a check that the problem has not come back.

Auditors see the same weak patterns often: records closed on the correction alone, “retrain staff” given as the cause of everything, and no effectiveness check. SOC 2 has no CAPA clause, but auditors read management’s responses to exceptions, and the same exception appearing again in the next period is noticed.

Questions

CAPA, answered

Is a CAPA the same as a POA&M?

They do a similar job in different settings. A POA&M is the CMMC and NIST format for tracking unmet security requirements to closure, while CAPA is the broader management system term for acting on findings and their causes.

How long do we have to close a CAPA?

Your own procedure sets internal deadlines. For findings from a certification body, the auditor sets the timescale for the plan and its completion, and a major nonconformity has to be closed before a certificate is issued.

Does every finding need a root cause analysis?

ISO 27001 requires you to evaluate the need for action on the causes of every nonconformity. Scale the effort to the finding: a short note for a one-off slip, a proper analysis for anything that recurs or affects many systems.

Working through this for an audit?

Talk it through with someone who has run the audit before, or look up another term.

  • Each customer workspace has its own database
  • Every change written to a tamper-evident activity log
  • Auditors get scoped, read-only access
  • AI suggestions wait for a person to accept them
Scroll to Top