Assign the next action
Record the owner, due date, immediate measure and cause context with the finding.
Corrective action workflow
CURRENTMove inspection findings from open to verified
Fenwix connects an inspection finding to the action needed, the responsible person, a target date and completion evidence. Evidence submission does not close the issue by itself: a separate verification step supports a clearer corrective-action trail from field observation to accepted result.
Separate proof from approval
Mark evidence as submitted before a reviewer verifies closure.
Keep the inspection link
The finding and its follow-up remain tied to the original checklist item and report.
Corrective action in five states
- Finding opened
- Action assigned
- Evidence submitted
- Result verified
- Closed or reopened
Create an actionable finding
A useful finding explains the observed condition and what must change. Fenwix keeps the description, priority context, immediate action, likely cause, owner and target date in the same workflow.
- Link the finding to its inspection item
- Attach field evidence
- Record responsible person and due date
- Keep critical and overdue context visible
Why evidence should not close the finding automatically
A photo or note shows that someone submitted something; it does not establish that the action is adequate. Fenwix separates evidence submission from verification so acceptance remains an explicit decision.
- Submission remains visible as an intermediate state
- Verification can identify who accepted the result when that information is provided
- A closed condition can be reopened
- The app does not make an automatic effectiveness claim
CAPA scope in the current product
Fenwix provides a practical corrective-action loop for inspection findings. It is not presented as a full enterprise quality-management suite with team roles, approval matrices, automated escalation and cross-system workflows.
- Current: finding, action context, owner, due date, evidence, verification
- Current: report visibility and local history
- Not current: shared team workspace and enterprise RBAC
- Not current: automatic email escalation or external QMS integration
Use the term CAPA precisely
- Fenwix supports corrective and follow-up records; it does not certify a regulated CAPA system
- Root-cause quality depends on the user and process
- Effectiveness review must reflect real verification, not a default status change
Corrective action questions
Can I assign a finding to a responsible person?
Yes. A finding can carry responsible-person and due-date information in the current local workflow.
Does adding a photo close the action?
No. Evidence submission and verification are intentionally separate.
Can a closed finding be reopened?
Yes. Reopening supports conditions that recur or were not effectively resolved.
Is this a cloud team CAPA system?
No. The current product is a local-first Solo workflow; shared enterprise coordination is roadmap scope.
Connect corrective action to its evidence
Follow one finding all the way through
Create a finding during an inspection, assign its next action, attach completion evidence and verify the result in Fenwix.
Try Fenwix on Google PlayContent status: CURRENT · Last reviewed: 2026-08-16
Claim basis: Fenwix current application flow · Fenwix product decision record · Fenwix.app aligned master brief