Workflow Template
Supplier Corrective Action Request Workflow
Enables a quality team to raise a Supplier Corrective Action Request, capture the nonconformance and containment requested, obtain the supplier's root cause and CAPA response with due dates, review and record a decision to accept or reject the response, verify effectiveness of accepted actions, and notify the requester and supplier when the SCAR is closed.
Quality teams lose track of supplier corrective actions when they're managed over email and spreadsheets. This workflow lets a quality team raise a SCAR, capture the nonconformance and containment needed, request and review the supplier's root cause and CAPA response, decide to accept or reject it, verify effectiveness, and notify everyone when it's closed. The quality manager or quality engineer runs it from raise to close.
Business Outcomes
- Helps cut the time it takes to get a compliant CAPA response from suppliers
- Reduces lost or forgotten SCARs by keeping every request in one tracked record
- Supports faster review decisions with structured accept/reject logic
- Improves visibility into which SCARs are stuck awaiting supplier action
- Makes it easier to demonstrate effectiveness verification during audits
Workflow Steps
Steps
- 1Create SCAR Recordcreate record
Registers the corrective action request submitted by the quality team.
- 2Set Status: Openupdate record
Marks the SCAR as opened.
- 3Notify Supplier of SCARsend email
Informs the supplier that a corrective action has been raised and containment is requested.
- 4Set Status: Awaiting Supplier Responseupdate record
Marks the SCAR as awaiting the supplier's root cause and CAPA response.
- 5Request Supplier Root Cause & CAPArequest external input
Sends the supplier a form to submit root cause, corrective action, preventive action and due dates.
- 6Persist Supplier CAPA Responseupdate record
Saves the supplier's root cause and CAPA response to the record for review.
- 7Quality Review of CAPA Responserequest approval
Quality team reviews the supplier's root cause and CAPA response and decides to accept or reject it.
- 8Route on Quality Review Decision
Routes based on whether the quality team accepted or rejected the supplier's CAPA response.
approval_status: "approved"→Persist Review Decision: Acceptapproval_status: "rejected"→Record Review Comments for SupplierDefault→End - 9Record Review Comments for Suppliercreate task
Quality reviewer records the comments explaining why a stronger response is required.
- 10Persist Review Decision: Rejectupdate record
Records the rejected review decision and reviewer comments on the record.
- 11Notify Supplier: Stronger Response Requiredsend email
Informs the supplier the CAPA response was rejected and a stronger response is required.
- 12Set Status: Returned to Supplierupdate record
Marks the SCAR as returned to the supplier for a stronger response.
- 13Restart CAPA Request Cyclerestart from step
Closes this iteration and restarts from the supplier CAPA request step so the supplier can resubmit.
- 14Persist Review Decision: Acceptupdate record
Records the accepted review decision on the record.
- 15Set Status: Verifying Effectivenessupdate record
Marks the CAPA response as accepted and moves the SCAR into effectiveness verification.
- 16Verify Effectiveness of Corrective Actioncreate task
Quality team verifies, after implementation, whether the corrective and preventive actions were effective.
- 17Persist Effectiveness Resultupdate record
Saves the effectiveness verification result to the record.
- 18Route on Effectiveness Result
Routes based on whether the corrective action was verified effective.
effectiveness_result: "Effective"→Set Status: Closedeffectiveness_result: "Not Effective"→Record Review Comments for SupplierDefault→End - 19Set Status: Closedupdate record
Marks the SCAR as closed following successful effectiveness verification.
- 20Notify Requester: SCAR Closedsend email
Notifies the requester that the corrective action request has been closed.
- 21Notify Supplier: SCAR Closedsend email
Notifies the supplier that the corrective action request has been closed.
Fields
- Requester Name*
- Requester Email*
- Supplier Name*
- Supplier Contact Email*
- Nonconformance Description*
- Affected Items / Part Numbers / Lot Numbers*
- +12 more fields
Forms
Supplier Corrective Action Request
8 fields
Data Views
Supplier Corrective Action Requests
supplier_name, scar_status, corrective_action_due_date, preventive_action_due_date +2 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Categories
FAQs
How do I set up this SCAR workflow for my quality team?
Publish the template in assess.one and it's live in seconds. There's no implementation project to wait on. Your team can start raising SCARs against suppliers right after you publish it.
What do I need before I can start using this workflow?
You just need your supplier contact details and a clear description of the nonconformance you're raising. Everything else, statuses, notifications, review steps, runs inside assess.one once you publish the template.
How long does implementation take?
Publishing takes minutes. Once it's live, your quality team can raise a SCAR and the supplier response cycle starts immediately, there's no separate rollout phase.
Can I customise the steps, like the review decision logic or notification content?
Yes. You can edit steps, roles, notifications, and approval logic directly in assess.one to match your quality process. This includes changing who reviews CAPA responses or how the reject-and-restart cycle behaves.
Who needs access to this workflow?
Typically the quality manager or engineer who raises and reviews SCARs, and the requester who gets notified on closure. Supplier contacts receive notifications but don't need platform access, communication happens through the configured email or Slack integration.
What happens if I reject the supplier's CAPA response?
The workflow records your review comments, notifies the supplier that a stronger response is required, and sets the status to Returned to Supplier. It then restarts the CAPA request cycle automatically so the supplier resubmits root cause and corrective actions.
How does effectiveness verification work?
Once you accept a CAPA response, the status moves to Verifying Effectiveness. Your team runs the verification step, records the result, and the workflow routes the SCAR to Closed or back for further action based on that outcome.
Are notifications to suppliers and requesters automatic?
Yes. The workflow triggers notifications at key points, when the SCAR is raised, when a stronger response is needed, and when the SCAR closes. These run through the email or Slack integration you configure inside assess.one.
Does this workflow support audit and compliance needs?
It's designed to keep a full record of the nonconformance, containment, supplier response, review decision, and effectiveness verification in one place. This makes it easier to pull evidence together when an auditor asks for supplier corrective action history.
Ready to use this workflow?
Create a free account and customise this workflow for your business.