Field Action and Recall Support Plan Template for Suppliers
When a customer opens a field action or recall that involves your part, speed and clarity of the first 48 hours matter. This template gives a supplier a structured plan covering the issue, the suspect population, containment and communications.
Fill in
Field Action and Recall Support Plan Template
Field Action Support Plan
Supplier: Acme Precision Components Customer: OEM Plant A, Supplier Quality Customer reference: FA-2026-114 Part: BRK-4410-R Response lead: R. Chen, Quality Manager Date: 2026-10-20
Reported issue
Weld porosity on mounting flange identified in vehicle crash test at the customer, possible reduced joint strength.
Suspect population
Lots produced on welding cell B between 2026-03-02 and 2026-06-18, serial range B0412000 to B0447250.
Traceability source: Lot and serial records in the ERP, welder parameter log, wire heat numbers
Containment and sort
100 percent visual and dye penetrant sort of stock at supplier, in transit and at customer, using certified sort personnel.
Action matrix
| Action | Owner | Due | Status |
|---|---|---|---|
| Lock suspect lots in ERP inventory | Materials | Day 0 | |
| Confirm boundary with process records | Quality | Day 1 | |
| Sort stock at supplier and in transit | Quality | Day 2 | |
| Support sort at customer and dealers | Customer service | As agreed | |
| Root cause and corrective action (8D) | R. Chen, Quality Manager | Per customer | |
| Update PFMEA and control plan | Engineering | After root cause |
Communications
All contact with OEM Plant A, Supplier Quality goes through R. Chen, Quality Manager. Statements to third parties or regulators are made only by the customer unless otherwise agreed in writing.
Approvals
A starting template, not legal advice. Safety recalls involve regulatory duties that belong to the vehicle manufacturer, and contracts allocate cost and liability. Involve your legal and insurance advisers and follow the customer's instructions and your quality agreement.
Lot and serial genealogy query for your ERP
An optional review of building a fast traceability report from your ERP lot and serial data.
Optional. The tool and every export work without this. No spam.
How to use the template
Complete the fields as soon as the customer notification arrives and refine them as facts emerge. The first draft will have uncertainty in the suspect population boundary, and that is expected. State the boundary you can defend from records, and widen it if the root cause evidence demands. Export to PDF to share with the customer and attach your 8D report when it is ready.
Defining the suspect population
The boundary is drawn from traceability: date, shift, line, lot, serial range, raw material heat or lot, tool and process settings. A narrow boundary needs strong records. If records are weak, the boundary has to be wider, which is the main cost of poor traceability.
- Start from the first and last known good lots
- Include material, tooling and process changes in the window
- Lock all suspect stock in the ERP immediately
- Cover stock at supplier, in transit, at the customer and at dealers
Containment, root cause and prevention
Containment protects the customer now, root cause explains how the escape happened and corrective action stops recurrence. Document the sort method and personnel certification, and record counts found. After root cause, update the PFMEA and control plan so that detection and prevention controls reflect what you learned, then verify with data.
Common mistakes
Suppliers sometimes defend the boundary before checking records, or report results without the sort method. Others forget stock in transit or at a sub-supplier. A third mistake is mixing commercial discussion with the technical response. Keep the factual response separate and let contract and insurance teams handle cost allocation.
Frequently Asked Questions
Who decides whether a field action is a recall?
The vehicle manufacturer normally makes that decision and handles the regulatory reporting. As a supplier you support with data, traceability, containment and root cause as the customer and your contract require.
How fast should the first response be?
Customers usually expect an immediate acknowledgment and a containment plan within one or two working days. Check your quality agreement for specific timing.
What records matter most for the boundary?
Lot and serial records, process parameter logs, material lot or heat numbers, tool and machine identification, inspection results and shipping records. Good genealogy from raw material to shipped part shrinks the population.
Does this template give legal advice?
No. It is a generic planning document. Liability, cost recovery and regulatory duties depend on your contracts and jurisdiction, so involve legal and insurance advisers.
Fast traceability is where an ERP earns its keep. Netray can help build read-only lot and serial genealogy queries for your ERP so a boundary can be proposed within hours.
Related Tools
Safe Launch Plan Template
Document the added controls, staffing and exit criteria for the first weeks of production on a new automotive program.
Quality & InspectionSpecial Status Notification Response Template
A written response to a customer special status such as controlled shipping or new business hold, with cause, actions and exit criteria.
Supply Chain & InventoryPremium Freight Incident Log Worksheet
Log every air, expedited truck or hot-shot shipment with its root cause and who pays, then see total premium freight spend and the average cost per event.
Maintenance & ReliabilityCustomer-Owned Tooling PM Log Worksheet
Log shots or hits against the preventive maintenance interval for each mold, die or fixture and see how much of the interval is used.
More Quality & Inspection tools
See all- PPAP Submission Level Requirements Reference
- PPAP Part Submission Warrant Template
- APQP Timing Plan Worksheet
- IATF 16949 Internal Audit Checklist
- Run at Rate Calculator
- PPAP Dimensional Results Worksheet
- Customer Specific Requirements Matrix Worksheet
- APQP Phase Gate Checklist
- PFMEA Worksheet with RPN for PPAP
Keep exploring
Free tools
- Containment Action Plan TemplateA fill-in containment plan that lists every suspect location, the sort or inspection action, the owner and the criteria for releasing stock.
- Product Recall and Field Safety Notice TemplateA fill-in recall notice that covers the product, hazard, affected lots, what the customer should do and how to reach you.
- Medical Device Recall Cost EstimatorEstimates the cost of a field action from units affected, retrieval and replacement costs, notifications and fixed overhead.
ERP fixes and how-tos
- How to Link a CAPA to ERP Lots and Serial Numbers for Containment and EffectivenessUse ERP lot and serial genealogy to scope containment for a CAPA, record affected jobs and shipments, and verify effectiveness with real data instead of opinion.
- Date Code and Lot Traceability in Cetec ERPHow to keep date code and lot traceability in Cetec ERP for electronics: capture at receiving, preserve through builds, and answer a recall trace quickly.
- How to Set Up Business Events and Actions in IFSConfigure IFS Business Events and Actions step by step: define triggers on an entity, enable the event, and bind an email, workflow, or webhook action.
Guides
- Infor M3 Lot Traceability and Recall Management ConfigurationConfigure Infor M3 lot traceability with forward and backward tracking, recall management, lot status workflows, and serialization for regulated industries.
- Lot Traceability for Medical Turned ComponentsLot traceability for medical turned components: heat numbers, ISO 13485 records, device history, recall readiness and how Swiss shops tie bar lots to shipments.
- How to Build Custom Actions in SyteLineGuide to building custom actions in Infor SyteLine, including toolbar button actions, context menu actions, and multi-record operations using the Action Designer and IDO methods.
AI on your ERP
- AI for JD Edwards Food and Beverage: Faster Traceability, Shelf Life, and Recall DrillsAI for JD Edwards food and beverage plants: lot traceability, shelf life, allergen control, recall drills and trade-promotion demand, private and read-only.
- AI for Food Manufacturing ERP: FSMA Traceability and Recall ReadinessAI on the ERP of a food manufacturer: FSMA 204 trace-back, lot and allergen checks, supplier verification and recall drills. Private, read-only deployment.
Software
- Oracle Field ServiceOracle Field Service schedules, routes and equips mobile workers within Oracle cloud applications. Modules, integrations, AI uses and alternatives.
- Dynamics 365 Field ServiceDynamics 365 Field Service handles work orders, resource scheduling and mobile technicians on Microsoft Dataverse. Modules, integrations and alternatives.