Example scenario
Post-Audit Actions — From Finding to Closure
An example workflow showing how to move from an audit finding to an assigned action, evidence of completion, verification and closure. The status of the whole process stays visible in one place.
This material shows one example of how actions after an audit or inspection can be organised. It does not present a client implementation or a full CAPA system.
Problem
Post-audit findings can easily get lost between reports, email and manual follow-up
This scenario starts with one audit finding and shows how to turn it into an assigned action, evidence of completion, verification and closure.
2026-07-14
- Company
- Northline Retail Services
- Location
- Poznań North Branch
- Business type
- Service and retail location network
- Auditor
- Anna Maj, Internal Auditor
Checklist item
CHK-4.2
| Requirement | Every customer complaint must include complete evidence of the actions performed and the verifier's signature. |
|---|---|
| Answer | No |
| Auditor comment | Two out of five cases did not include evidence of completion and formal verification. |
How the process works
From finding to assigned action
The finding is described, linked to an action and assigned to a specific person with a due date.
PA-2026-017
- Category
- Complaint handling and action oversight
- Finding description
- The complaint action closure process does not provide complete evidence of execution and formal verification.
- Initial cause
- There is no single place for tracking responsibility, deadlines and evidence.
Action
- Action
- Complete the missing evidence for open cases and introduce one standard for recording evidence of completion.
- Action owner
- Marta Zielińska, Location Manager
- Due date
- 2026-07-21
What the workflow covers
What the workflow covers
The workflow covers the finding, action, status, evidence, verification and case-level control in one place.
Finding
The source of the case, the finding description and the audit context.
Action
The action description, owner and due date linked to the finding.
Status
Registration, assignment, verification, correction and closure.
Evidence
A file, description and comment documenting execution.
Verification
Approval or send-back before formal closure.
Control
A view of cases, deadlines, statuses and recurring signals.
potwierdzenie-reklamacja-PA-2026-017-v1.pdf
Summary of closed cases signed by the shift manager
- Attachment
- potwierdzenie-reklamacja-PA-2026-017-v1.pdf
- Date added
- 2026-07-20
- Owner comment
- I am attaching a completion summary and the list of cases included in the correction.
- Verifier comment
- The document does not show which cases were checked after completion. Formal verification evidence is missing.
potwierdzenie-reklamacja-PA-2026-017-v2.pdf
Updated evidence with case numbers, dates and the verifier's signature
- Attachment
- potwierdzenie-reklamacja-PA-2026-017-v2.pdf
- Date added
- 2026-07-22
- Owner comment
- I added case numbers, completion dates and the verifier's signature.
- Verifier comment
- The evidence is complete. The scope of the action and formal verification are both visible.
Execution and closure control
Verification does not end when the action is marked as done
The verifier checks the evidence and either confirms closure or sends the action back for completion.
Below you can see the same case after the first rejection, the corrected evidence and the final approval.
First evidence
I am attaching a completion summary and the list of cases included in the correction.
Sent back for correction
The document does not show which cases were checked after completion. Formal verification evidence is missing.
Updated evidence
I added case numbers, completion dates and the verifier's signature.
Verification and closure
The evidence is complete. The scope of the action and formal verification are both visible.
Case history
- Closure date
- 2026-07-23
- Verified by
- Piotr Kaczmarek, Quality Coordinator
- Case history
- Finding registered → action assigned → evidence added → needs correction → updated evidence → verified → closed
Capabilities involved
Capabilities involved
The scope covers workflow design, responsibility, statuses, evidence handling, verification and management visibility.
One view of actions, deadlines and closure
One view of actions, deadlines and closure
The manager can see what is open, overdue, waiting for verification or already closed.
| Location | Case | Status | Due date |
|---|---|---|---|
| Poznań North Branch | PA-2026-017 | Closed | 2026-07-21 |
| Gdańsk West Branch | PA-2026-011 | Overdue | 2026-07-16 |
| Wrocław South Branch | PA-2026-013 | Waiting for verification | 2026-07-22 |
| Łódź Central Branch | PA-2026-019 | Action assigned | 2026-07-25 |
Similar findings also appeared here
- Gdańsk West Branch
- Wrocław South Branch
The management view shows recurrence but does not automatically assign a systemic cause.
Material type
Example scenario — post-audit actions
This material shows an example of how post-audit or post-inspection actions can be organised. The exact scope of an implementation depends on the process, roles and operating rules used in the organisation.
One case was closed in a controlled way: from the audit finding, through the assigned action and evidence of completion, to formal verification and closure. The manager can also see that a similar issue appeared in other locations.