CAPA, correction and Action differences

Not every Action is CAPA

A correction, an Action and corrective and preventive action—often shortened to CAPA—can concern the same event, but they are not the same record. A correction removes the observed condition. An Action follows assigned work with an owner, due date and state. CAPA is a broader process defined by an organisation’s quality system and may bring root-cause review, scope, corrective or preventive decisions, and effectiveness evaluation together.

An Action in Teftiş Go does not automatically become a formal CAPA record. The product follows the owner, due date, resolution Evidence and Verification history connected to a Finding. It does not independently create an organisation’s formal CAPA method, interpret regulations or establish certification compliance.

This is more than a naming choice. Reporting every Finding as “CAPA opened” mixes simple field corrections with systemic concerns. Management can no longer distinguish what was removed immediately, what requires assigned work and what needs root-cause analysis.

Fix the meaning of a Finding first

A Finding is the recorded observation that does not meet the standard during an Audit. It retains the source Question, Answer, original Evidence, severity, Location and Audit context. A Finding is not the work to be done. It explains the condition that requires a decision.

Suppose boxes are found blocking an emergency exit in a store. The auditor connects a photograph to the Answer and records severity under the published Template rule. Moving the boxes, changing storage design and reviewing whether the condition returns are separate layers of the response.

If a team goes straight to a task list without preserving Finding context, the reason behind an Action becomes unclear. Reports should navigate from an Action back to the source Finding and Audit, not only from the Audit forward.

Correction removes the observed condition

A correction is the direct intervention that removes a detected nonconforming condition. It often happens during the Audit or immediately afterwards.

Moving boxes away from an emergency exit is a correction. Closing a cold-storage door, replacing a missing price label or repositioning a safety sign can serve the same purpose.

A correction has three important boundaries:

• It removes what was observed; it does not by itself explain why the condition can recur.
• Acting quickly does not require the original Finding to disappear from the record.
• A new image or note should not overwrite original Evidence; it should show the later state as separate resolution Evidence.

“Corrected in the field” can mean that the immediate condition is gone. It does not necessarily mean an authorized Role has accepted the outcome. Keep the Verification decision separate.

An Action follows owned and dated work

An Action records the work to be done, responsible User, due date and lifecycle. It can be generated from a Finding or created independently. Its value lies not only in its title, but in its retained accountability and decision history.

A dependable Action answers:

Question	Expected record
Why was it opened?	Source Finding or explicit reason
Who will do it?	Authorized responsible User
By when?	Due date in the Organisation time zone
What changed?	Resolution explanation
How was it shown?	New resolution Evidence
Who assessed it?	Verifying User, decision and reason

The Teftiş Go lifecycle distinguishes Open, In progress, Resolved, Verified and Closed states. Resolved represents the Action owner’s submission. Verified represents acceptance by an authorized Role. A rejection preserves history and returns the Action to an active state for more work.

The guide From a Finding to a verified Action explains that submission and rejection cycle in more detail.

CAPA is a broader management process

CAPA is a quality-management process whose exact design depends on the organisation. It is not a single product status. A formal CAPA record may address some or all of these questions:

• What is the event scope and its possible effect on similar processes or Locations?
• Was the immediate correction completed and supported with Evidence?
• How was root cause assessed?
• Which decisions are intended to prevent recurrence?
• When several Actions exist, who owns each one and when is it due?
• When and by what criterion will effectiveness be reviewed?
• Which Role can close the process and what record supports that decision?

One CAPA process can therefore relate to several Findings and Actions. Conversely, not every Action needs CAPA. The organisation should classify the event through risk, recurrence, breadth of impact and its own quality procedure.

Teftiş Go Action Management provides a traceable workspace for ownership, due dates, resolution Evidence and Verification. The product does not decide that a record satisfies formal CAPA requirements. Root-cause or effectiveness steps required by an organisation must remain explicit in its defined process.

Root cause is not the observation repeated

Statements such as “staff were careless” or “the procedure was not followed” often restate the observation in different words. Root-cause review asks which element of system design, capacity, training, equipment, communication or control allowed the condition to recur.

For boxes near an emergency exit, possible factors include inadequate storage capacity, temporary congestion during deliveries, invisible floor markings or a missing end-of-shift check. The record alone cannot establish which explanation is valid; the responsible team must investigate.

Making a root-cause field mandatory does not guarantee a useful analysis. The review owner, method, supporting records and approving Role should be clear. Selecting from a generic cause list before evidence is reviewed can create false certainty.

Effectiveness review is different from closure

Verification of an Action means that the submitted resolution was accepted. CAPA effectiveness asks whether the decision produced the intended result over time. These moments do not have to occur on the same day.

After a storage area is rearranged, a new photo can demonstrate completion of the Action. Evidence that the exit remained clear during the next four weeks or at a planned follow-up Audit can support a later effectiveness decision. The period and criterion depend on organisational risk; there is no universal number.

Instead of reducing effectiveness to an unsupported yes/no field, define the decision evidence: a Follow-up Result in the next Audit, recurring Finding rate, a relevant process indicator or qualified expert review.

Which record should you use?

Situation	Correction	Action	CAPA assessment
A single condition can be removed in the field	Usually	When a trace or follow-up is needed	Depends on risk and procedure
Work needs a due date or different owner	May address the initial condition	Yes	Based on recurrence and impact
The same Finding appears across Locations	Can happen locally	Can be local or central	Strong candidate
Root cause and system change are required	Handles the initial condition	Several may be needed	Usually opened under the organisation’s process
Effectiveness will be measured later	Not sufficient	Carries implementation work	Carries the evaluation framework

This table does not establish compliance. Final classification belongs to the organisation’s procedure, risk owner and qualified specialists where needed.

Illustrative example: recurring cold-area records

The following flow is not a customer case study or compliance claim. It is an illustrative example of the concept boundaries.

A regional manager at a restaurant chain sees that a cold-area log does not meet the internal standard during a before-service Audit. The missing entry becomes a Finding. The branch manager completes that day’s record, which is a correction. Two Actions are also assigned: reposition the log board and update the shift handover step.

If a similar Finding appears again at three branches, central quality may open a broader CAPA assessment. The team can investigate whether the Template is unclear, training is insufficient or shift ownership is ambiguous. Decisions become separate Actions. Effectiveness can then be evaluated during the next programme period by reviewing recurrence and on-time record completion.

The product’s role is to connect the records and retain the decision trail. The need for CAPA and its effectiveness criterion remain management decisions made by the organisation.

A short implementation decision list

1. Limit the Finding statement to the observed condition.
2. Record immediate correction and new Evidence separately.
3. Create owned and dated Actions for lasting work.
4. Define a verifying Role in advance when the Action owner cannot verify their own submission.
5. When recurrence, broad impact or a system cause exists, begin CAPA assessment under the organisation’s procedure.
6. Keep the relationship between root cause and selected Actions visible.
7. Define the effectiveness criterion and review date before closure.

Use the Field Audit Management Guide for the end-to-end model, industry scenarios for operating contexts and the product decision page for product boundaries.