NHTSA manufacturer safety recall reporting and execution
NHTSA vehicle recalls: defect decision, Part 573 filing, owner notice and remedy execution
A practical operating playbook for vehicle, tire, child restraint and replacement-equipment manufacturers. It follows the work from the first credible safety signal through the recall decision, the Part 573 report, owner and dealer notices, remedy operations and completion reporting.
National Highway Traffic Safety Administration (NHTSA), Office of Defects Investigation
Timing
Submit the initial Part 573 report no more than 5 working days after the manufacturer determines a defect is safety-related or a noncompliance exists. The initial filing must include the minimum required information; provide remaining information within 5 working days after it is confirmed, and amend specified information within 5 working days after learning it has changed. Mail owner notices no later than 60 days from the Part 573 filing. Give NHTSA the proposed owner notice and its reimbursement attachments at least 5 Federal Government business days before mailing. For an immediate and substantial threat, notify dealers and distributors within 3 business days after transmitting the Part 573 report electronically, or within 5 business days when transmission is by other means. Most campaigns also require recurring status reporting: current § 573.7 specifies six consecutive quarters beginning with the campaign quarter or until corrective action is completed for all affected items, whichever occurs first. NHTSA’s 2025 portal guide also exposes quarterly and annual completion-report workflows; reconcile each campaign’s portal alerts and current instructions before closeout.
Reviewed
Inside this guide
6 steps · 6 templates
Who it applies to
Use this guide when a manufacturer determines that a motor vehicle or item of original or replacement equipment has a safety-related defect or does not meet a Federal Motor Vehicle Safety Standard. It is written for manufacturers and their U.S. entities, including the people in engineering, field quality, legal, regulatory, manufacturing, service, communications, parts, dealer operations, data, customer care and finance who must deliver one coordinated campaign. Separate Early Warning Reporting, foreign recall reporting, state laws, consumer-protection duties and litigation holds may apply in parallel.
What you’ll produce
A fact-supported determination chronology; a correctly scoped affected population; a timely, officer-approved Part 573 filing; a safe and available remedy with reimbursement terms; owner and dealer communications cleared for release; a staffed customer response operation; an auditable campaign ledger; and completion reports submitted on the schedule shown in the current NHTSA rules and Manufacturer Recalls Portal.
NHTSA says 894 vehicle safety recalls were conducted in the United States in 2023. It also reports more than 17,000 recalls affecting over 750 million vehicles and pieces of equipment in the preceding decade. The numbers show why recall work is a standing operating capability, not an occasional communications project. In 2024, NHTSA announced a $165 million Ford consent order, then described as the second-largest civil penalty in agency history, following findings about untimely rearview-camera recalls and inaccurate or incomplete reporting. An earlier Hyundai and Kia consent order involved combined penalties of $210 million over untimely Theta II engine recalls affecting more than 1.6 million vehicles and inaccurate reporting. In the related 2014 United States v. Toyota deferred-prosecution matter, DOJ reports a $1.2 billion penalty and an independent monitor over wire-fraud allegations tied to concealed safety information. That criminal matter is not a Part 573 deadline ruling. NHTSA says completion rates vary with factors such as vehicle age, owner contact quality, remedy convenience and parts supply; it does not present one universal completion-rate benchmark.
What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
NHTSA manufacturer safety recall reporting and execution kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Open the safety case and preserve the decision clock · Product safety lead + Field quality + Engineering + Legal + Regulatory [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
What exact dated evidence will show when the company first determined that the condition was safety-related or the product was out of compliance?
Can Quality and Data Science reproduce the affected population, the excluded population and the estimated share actually containing the defect from source records?
Worked scenario
A supplier reports that a fastener may loosen under repeated heat cycles. The vehicle maker opens a restricted safety case, preserves the supplier notice and starts a chronology using dated warranty claims, returned parts, field reports and tests. Quality builds a VIN and component population with inclusion and exclusion logic. Engineering evaluates hazard and interim steps while Legal and Regulatory identify the determination point and filing clock. Once the company makes the reportable determination, the filing owner submits the required initial Part 573 information within five working days, then completes confirmed details on the follow-up schedule. Service engineering proves the remedy, parts operations checks launch capacity, Finance approves reimbursement terms, and Communications prepares owner and dealer notices. The team submits the owner letter to NHTSA at least five Federal Government business days before mailing and tracks owner notice inside the 60-day deadline. A campaign operations room reconciles mail, VIN lookup, parts, repairs, complaints, field incidents, amendments and each due report until the portal shows no open requirement.
Submit the quarterly status report on the statutory schedule
Current § 573.7 requires six consecutive quarterly reports beginning with campaign initiation or until all corrective action is completed, whichever occurs first; follow portal alerts and confirm current annual workflow too.
Initial report no more than 5 working days after the reportable determination; confirmed remaining information within 5 working days after confirmation
Recall program director + Dealer network + Parts supply + Customer care + Communications + Regulatory
Owner notices within 60 days of Part 573 filing; immediate-threat dealer notice within 3 business days after electronic report transmission, or 5 business days by other means
Set a start date
Campaign execution dashboard; communication delivery evidence
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Open the safety case and preserve the decision clock
Who Product safety lead + Field quality + Engineering + Legal + RegulatoryWhen Immediately when credible field information indicates a potential safety defect or noncompliance
Create one access-controlled case number and a single chronology owner. Capture the original complaints, warranty claims, dealer reports, supplier communications, returned parts, test results and relevant design changes with source system, receipt date and custodian. Record separately when each event happened, when the company learned it, when the issue was escalated, and when the company determined the defect was safety-related or noncompliance existed. Preserve unfavorable and contradictory facts. Start interim safety controls and product containment review while the technical investigation proceeds. Do not wait for an injury or a final root-cause analysis to start the regulatory clock assessment.
What to produce
NHTSA safety case chronology and evidence holdRestricted case log
Gather first
Complaint and warranty feeds
Dealer and supplier reports
Test results
Product and design history
Safety escalation procedure
How to prepare it
Create one row per event. Store event date, company receipt date, source system, product scope, reporter, issue summary, evidence location and custodian.
Keep observations separate from hypotheses and decisions. Record contradictory evidence, injuries, crashes, warnings, interim actions, decision meetings and approvals.
Name the owner of the determination clock. Preserve original records, log legal holds and restrict access to privileged or personal information.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional event row
On 4 May the supplier sends a returned component report. The case log records when the supplier observed the failure and when the manufacturer received the report as separate dates.
Fictional review note
Engineering confirms the sample is from an affected lot but cannot yet establish the whole production range. The uncertainty and next data request are recorded.
Check before handing it over
An independent reviewer can reconstruct what the company knew, when it knew it and who authorized each action.
Provide a controlled chronology to Product Safety, Legal and the authorized decision committee.
Reproduce the affected population and risk assessment
Who Quality engineering + Vehicle or equipment data + Manufacturing + Supplier quality + Safety counselWhen In parallel with investigation; review assumptions daily until the first report is filed
Join production, VIN or serial, component, supplier, shipment, warranty, dealer, repair and test records. Define the first and last production dates, part numbers, models, lots, geography and installation paths. Document the denominator and the method used to estimate what share is actually defective. Test positive samples and a defensible sample of excluded units. Explain why close sibling products are included or excluded. For each fact, retain the query, data version, field definitions, transformation and reviewer. If the exact count is not yet known, file the required initial information and continue validation rather than using an unsupported precise number.
What to produce
Affected population and safety-risk analysis workbookData analysis workbook
Gather first
Production and VIN or serial master
Supplier lots
Warranty and repair records
Field reports
Test data
Product engineering definitions
How to prepare it
Define a population query and version it. Record joins, exclusions, duplicates, missing identifiers, source dates and accountable data owners.
Calculate total potentially involved products separately from the estimated percentage actually containing the defect. Show the numerator, denominator, assumptions, uncertainty and validation sample.
Test in-scope and out-of-scope samples, compare sibling models and production changes, then have a second engineer independently reproduce the result.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional population row
An engineering change narrows the suspect production interval. The analyst retains both the earlier broad query and the revised interval, with the change reason and reviewer.
Fictional calculation
The manufacturer reports the affected population and a separate estimated proportion expected to contain the condition, with the sample and assumptions linked.
Check before handing it over
A reviewer can rerun the population logic and explain why nearby products are included or excluded.
Give the approved count, basis and risk analysis to the Part 573 filing owner.
Make the formal decision and file the Part 573 report
Who Authorized safety decision committee + Regulatory filing owner + Product counsel + Quality and EngineeringWhen Initial report no more than 5 working days after the reportable determination; confirmed remaining information within 5 working days after confirmation
Have the decision owner record the determination date and the basis under the Safety Act and current Part 573. Complete the Manufacturer Recalls Portal form for the correct product type: vehicle, equipment, tire or child restraint. The report must identify the manufacturer, product population and selection basis, estimated number and percentage affected, defect or noncompliance, safety risk and chronology. Include noncompliance test dates and results when applicable, supplier or component information, remedy program and reimbursement plan, notification schedule, and copies of directly related notices where required. Submit the minimum information needed for the initial report by the five-working-day deadline; calendar missing fields separately and submit them promptly within the rule. Route every material change to the amendment owner; specified report information must be amended within five working days after the manufacturer learns it has changed. Save the submitted version, portal receipt, assigned NHTSA campaign number and the person authorized to answer questions.
What to produce
Part 573 decision and submission recordSubmission checklist and record
Gather first
Safety case chronology
Counsel’s applicability analysis
Affected population
Defect or noncompliance description
Risk evaluation
Remedy and reimbursement inputs
How to prepare it
Record the reportability question, decision owner, exact determination date, applicable rule, decision rationale and any unresolved facts.
Map each Part 573 field to its source, owner, evidence date and validation status. Mark initial minimum fields separately from additional fields that require follow-up after confirmation.
Have Legal and Quality reconcile the report, submit through the Manufacturer Recalls Portal, retain the accepted submission and receipt, and calendar the five-working-day supplemental and amendment clocks.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional decision
The committee records why the failure mode presents a safety risk and assigns the regulatory owner to file within five working days of the determination.
Fictional open field
The initial filing includes the verified minimum product and risk facts. The exact supplier country of origin is tracked to a named owner and a due date after confirmation.
Check before handing it over
Every reported fact and certification has a traceable source, approver, submission version and follow-up date.
Give the submission record and pending-field tracker to the campaign director and regulatory calendar owner.
Prove the remedy and prepare notice and reimbursement
Who Service engineering + Parts operations + Dealer operations + Finance + Customer care + Legal + RegulatoryWhen Before public notice; send the proposed owner notice and required attachments to NHTSA at least 5 Federal Government business days before mailing
Build a remedy package that states what is repaired, replaced or refunded, how the new part or repair addresses the failure, when parts and software will be ready, technician instructions, labor time and capacity, and any interim do-not-drive or park-outside direction. Confirm that the repair is available without charge as required and that the repair path works across every affected model and geography. Establish the pre-notification reimbursement period, eligible costs, claim steps, proof requirements and appeal owner; document how this follows § 573.13. Draft the owner letter against Part 577 in plain language: identify the affected product, the defect, what can happen, any warnings or precautions, the safety risk, free repair steps, expected remedy availability and a clear contact path. Prepare the envelope and dealer instructions. Obtain cross-functional factual sign-off and submit the draft and reimbursement material to NHTSA in time for the required five Federal Government business-day review window.
What to produce
Validated remedy and reimbursement plan; NHTSA-ready owner and dealer notice packRelease packet
Gather first
Approved defect and risk statement
Remedy engineering validation
Parts and dealer capacity
Owner and dealer populations
§ 573.13 reimbursement rules
Part 577 letter requirements
How to prepare it
Define the repair, replacement or refund, remedy part and software versions, technician steps, labor time, supply forecast, interim precautions and repair locations.
Set reimbursement start and end dates, eligible costs, claim evidence, exclusions permitted by the rule, submission address, service-level target and appeal owner.
Draft the owner notice and dealer bulletin against Part 577. Verify warnings, safety risk, free remedy, who is affected, how to act, contact details, accessible formats and envelope markings. Schedule NHTSA review at least five Federal Government business days before mailing.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional remedy check
A test repair confirms the new bracket prevents the fastener movement. Parts Planning confirms stock by region and records the first dealer ship date.
Fictional notice review
The draft explains the risk before the technical description, tells the owner what to do now and gives a staffed number to book the free remedy.
Check before handing it over
The remedy is technically effective and operationally deliverable, and the notice passes regulatory and plain-language review.
Obtain release approval from the safety decision owner, Legal, Service and Regulatory before submitting the notice to NHTSA.
Launch the campaign and run the owner response operation
Who Recall program director + Dealer network + Parts supply + Customer care + Communications + RegulatoryWhen Owner notices within 60 days of Part 573 filing; immediate-threat dealer notice within 3 business days after electronic report transmission, or 5 business days by other means
Use NHTSA’s accepted notice process and release on the approved dates. Confirm NHTSA has the proposed owner letter at least five Federal Government business days before the mailing start, and mail the owner notice within the 60-day limit. If the remedy is not available, issue the required interim communication and send the follow-up notice when the remedy is available. Submit copies of the final notices and other covered recall communications within the required five-day window. If either reported notice start or completion date will slip by more than two weeks, promptly advise NHTSA with the reason and revised dates. Reconcile eligible owners, returned mail, digital contact, dealer receipt, VIN lookup and repair transactions. Track parts fill rate, appointment wait, remedies completed, units that do not need repair, unreachable units and customer complaints. Escalate any new injury, fire, crash or remedy failure to the safety decision owner immediately.
What to produce
Campaign execution dashboard; communication delivery evidenceCampaign dashboard
Gather first
Accepted Part 573 report
Approved owner and dealer notices
VIN or serial population
Mail vendor receipts
Dealer and parts feeds
Call center cases
Repair transactions
How to prepare it
Reconcile the approved population to each communication channel and record start and completion dates, returned mail, failed digital delivery, dealer acknowledgement and follow-up.
Track daily remedy availability, parts by region, appointments, repairs, no-repair inspections, unreachable units, complaints and new safety signals. Tie each count to its source and snapshot date.
Route a greater-than-two-week notification schedule delay to Regulatory immediately with a reason and revised estimate. Record interim and final notices, NHTSA uploads and any revised owner lists.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional daily metric
The campaign dashboard shows 18,400 owner records mailed, 6,200 repairs booked, 310 notices returned and 12 dealers below the parts fill target, each linked to source data.
Fictional schedule escalation
A supplier delay moves the mailing completion estimate by three weeks. Regulatory sends the agency the reason and revised date, then logs the submission receipt.
Check before handing it over
The campaign director can see who has been notified, who can obtain the remedy, where the plan is slipping and what NHTSA has been told.
Use the dashboard in daily safety reviews and in the quarterly reporting reconciliation.
Submit completion reports and close the campaign with evidence
Who Recall program director + Regulatory reporting + Data governance + Internal audit + Executive sponsorWhen Quarterly on the current federal calendar while required; retain all open portal alerts until each is resolved
Build each report from reconciled cumulative counts, not a manually copied snapshot. Tie repaired and inspected units to repair orders, parts records and VIN or serial population. Classify items that were exported, stolen, scrapped, not notified or otherwise unreachable and retain the supporting basis. Current § 573.7 sets six consecutive quarterly reports beginning with the quarter the campaign was initiated or until corrective action is complete for all affected items, whichever occurs first, with quarter due dates of April 30, July 30, October 30 and January 30, adjusted when a date falls on a weekend or federal holiday. The 2025 portal guide also describes annual completion-report screens and portal alerts. Before closing, reconcile the current rule, the campaign’s MRP eligibility and every upcoming or overdue alert; submit any portal-required annual report rather than assuming the screen is optional. Reconcile amendments, rejected documents and missing-information alerts. Close only after the portal status, financial reserve, returned parts, customer cases, supplier corrective actions and records-retention owner are documented.
What to produce
Cumulative completion report package and campaign closeout decisionRegulatory report and closeout memo
Gather first
NHTSA campaign identifier
Current MRP alerts
Repair-order and VIN data
Dealer returns
Export, theft and scrapping data
Open complaints and remedy issues
How to prepare it
Reconcile cumulative counts for affected, repaired, inspected with no repair needed and unreachable products. Explain exclusions and carry forward prior accepted totals.
Prepare the report due for the current reporting period. Compare the federal calendar, current § 573.7 schedule and all campaign-specific quarterly or annual reports surfaced by the portal.
Resolve rejected or overdue reports, missing-information requests, supplier actions, remedy failures and customer cases. Have Internal Audit sample source transactions before the executive closeout decision.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional quarterly row
The report adds this quarter’s verified repairs to the cumulative total and separately counts products that were exported, scrapped or could not be contacted.
Fictional closeout
The team leaves the campaign open while an annual MRP alert and several remedy cases remain. The closure memo lists each issue, owner and final evidence required.
Check before handing it over
The MRP has no unexplained alerts, cumulative completion figures reconcile to transaction data and the company can defend its closeout decision.
Submit the approved completion report, retain the portal receipt and obtain executive sign-off on the campaign record.
A hands-on operating guide for manufacturers, importers, distributors, retailers and brands selling consumer products in the United States. Use it to collect safety signals, make and document the reporting decision, submit a complete Section 15(b) report, and run a corrective action or recall with clear owners and evidence.