--- title: "Manufacturer communications vs safety recalls" description: "Separate manufacturer bulletins from safety recalls, read NHTSA communication metadata, and prepare reference questions for a qualified repair planner." canonical: "https://scalewithsearch.com/articles/manufacturer-communications-recall-repair-planning" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Manufacturer communications and recalls: read the difference before repair planning When a document reference enters a repair-planning discussion, identify its class before drawing a conclusion. A bulletin reference can prompt further reading. A safety recall raises a different applicability question. An uncertain reference needs clarification before either label belongs in the plan. NHTSA's manufacturer-communications collection covers defect and malfunction communications concerning safety and non-safety matters. Its recall guidance defines a safety recall around an unreasonable safety risk or failure to meet safety standards. Read the [collection description](https://www.nhtsa.gov/nhtsa-datasets-and-apis#manufacturer-communications) alongside the [recall explanation](https://www.nhtsa.gov/recalls). The collection's breadth means that finding a communication does not, by itself, identify a recall campaign. Treat the document class as an evidence question. This guide proposes a reference card for that question, without copying repair procedures or resolving technical work. The [collision shop overview](/for/auto-body-and-collision-shops) explains the larger office boundary. Qualified staff direct the repair. Public-source reading should help them locate and assess the right material. ## Start with the reference someone supplied Ask what the person has: an official link, a document identifier, a search summary, or an informal mention. Preserve that distinction on the reference card. An identifier without a source is a starting clue. Do not improve an uncertain reference through confident wording. If someone says “there may be a bulletin,” write that a bulletin reference remains unconfirmed. Avoid turning the sentence into “manufacturer repair required” before a qualified reviewer examines the controlling material. First, find the official source that supports the reference. Next, compare its document identity and product scope with the question under review. Then ask the planner what further evidence is needed. Keep each step visible in the card. For example, a synthetic planning note might mention “the body-system communication discussed last week.” That phrase cannot identify a document on its own. The next useful action is to locate the reference, rather than guessing its content from the topic. ## Read the current layout before choosing fields The [NHTSA manufacturer-communications layout](https://static.nhtsa.gov/odi/ffdd/tsbs/TSBS.txt) distinguishes CSV and TSV files. CSV records represent document/product combinations. TSV can repeat a document across multiple-valued elements. Repeated rows therefore need interpretation before anyone treats them as separate communications. The layout names NHTSA ID Number, TSB/Document ID, Mfr Communication Date, Date Added to File, Make, Model, and Model Year. It defines the two dates differently: manufacturer dissemination versus addition to the file. Preserve both meanings when preparing a reference card. Those field names come from the published layout. The proposed card below adds local review labels. Keep that distinction clear: a review owner or unanswered question is your shop's working note, rather than a claim about the source dataset. Avoid calling every row a separate bulletin. Equally, do not merge records merely because their summaries look similar. Compare the published identities and scope first. If the distinction remains unclear, bring the records to the reviewer as an unresolved question. ## Make a compact reference card This example is synthetic. It describes no real communication, vehicle, customer, or repair. It shows how to keep a reference traceable without importing a technical procedure into an office worksheet. | Card field | Hypothetical entry | | --- | --- | | Source collection | Manufacturer communications | | NHTSA identity | Copy the NHTSA ID Number after confirming the record | | Manufacturer identity | Copy the TSB/Document ID after confirming the record | | Vehicle scope | Example Make, Example Model, model year 20XX | | Manufacturer date | Copy the stated communication date with its label | | File date | Copy Date Added to File separately when available | | Official source link | Confirmed public reference URL | | Access date | 2026.10.28, illustrative research date | | Research summary | Document reference located; technical applicability unresolved | | Planner question | Does the current document apply to this planning question? | | Additional evidence | Current controlling manufacturer material, as identified by the planner | | Review owner | Assigned qualified repair-planning role | | Recorded outcome | Pending review | Leave unknown entries blank with a clear label such as “not established.” Do not fill a manufacturer identity with the NHTSA identity because only one number was available. Keep both slots so the reviewer can see the gap. Write the research summary in your own narrow language. “Reference located” says what happened. “Required repair confirmed” would need a separate technical determination. The card should make that difference visible without requiring someone to read every attachment. ## Keep four decisions in separate rows Document retrieval, procedure access, warranty coverage, and repair authorization answer different questions. The following separation is an editorial planning recommendation. It does not describe any particular manufacturer's terms or a universal repair process. | Decision | Useful evidence question | Responsible review | | --- | --- | --- | | Document retrieval | Which official reference did we locate? | Researcher and planner check identity | | Procedure access | Which current manufacturer material controls the technical question? | Qualified planner identifies the required source | | Warranty coverage | Who can confirm applicable terms for this situation? | Authorized coverage reviewer | | Repair authorization | What approval controls the proposed work? | Person authorized under the shop's process | A successful retrieval closes only the retrieval row. Do not copy that success into the other three rows. Their owners may need additional information, different sources, or a direct answer from an authorized party. For instance, a publicly accessible summary may help locate a reference. The planner still needs to decide whether the current controlling material has been obtained. A readable summary does not answer that decision on the planner's behalf. Similarly, the presence of a document supplies no shop-specific authorization. Record who must decide and where the resulting approval belongs. Keep the reference card focused on evidence and unresolved questions. ## Compare a bulletin reference with a recall reference Imagine two synthetic notes on the same planning desk. One points to a manufacturer communication. The other points to a safety recall result. Preserve them as separate references, even if both mention a similar component. For the communication, ask the planner to confirm document identity, scope, and the current controlling material. For the recall, ask who will confirm campaign applicability through the approved vehicle-specific process. Neither research note should choose a repair method. If the documents appear related, record that as a question: “Does this communication relate to the campaign under review?” Ask the qualified reviewer to establish the relationship. Do not create a relationship from matching words alone. The [make, model, and year recall guide](/articles/nhtsa-recall-search-make-model-year-limits) covers the campaign search question. Use it when the research task concerns general recall results. Keep this card for document classes and reference evidence. Suppose the reviewer confirms that the communication is useful background but does not resolve the recall question. Record both outcomes. That answer prevents the background reference from being mistaken for completed applicability review during the next handoff. ## Read dates as dates with specific meanings Preserve the labels beside each source date. Add your access date in a different field. These distinctions let the reviewer ask a precise question about document age without guessing what “updated” means in a copied note. In a synthetic example, a card could show a manufacturer date in one month and a file-addition date in another. Write both observations exactly as sourced. Do not label the later date as a technical revision unless the controlling source establishes that meaning. If two references conflict, keep the conflict open. Ask the planner which current material controls the decision. Record the reviewed answer with its source. Avoid choosing the newest-looking date as a shortcut for resolving document authority. When a later review replaces a reference, preserve the reason. “Planner identified different controlling material” is useful if supported by the recorded decision. “Old document invalid” requires its own evidence and should not appear as an automatic conclusion. ## Turn a vague technical concern into a useful question A reference card should help the planner respond without guessing what research has already occurred. Specify the evidence found, the evidence missing, and the decision requested. Leave technical interpretation with the person responsible for it. Consider this synthetic question: “We found an official communication reference for the selected model combination. Please confirm its relevance to the current planning question.” Attach the identity, source link, and dates. Keep the underlying repair record in the approved shop system. If the planner requests another source, record that request as the next research action. Do not broaden the search into unrelated vehicles or collect customer information because a field is empty. The task remains locating the evidence the reviewer named. If the document cannot be accessed, record the access failure separately from the reference's identity. A missing document and a disproven reference are different outcomes. Ask the reviewer which approved access route should be used next. Keep any description of a technical concern short and within the material approved for the card. Link to the proper record when needed. Avoid duplicating private notes into a general research folder. ## Close the reference question with a reason Choose a closing label that describes the review performed. Useful examples include “reference confirmed,” “different document required,” and “insufficient evidence.” Ask the reviewer to supply the reason and source. Avoid a generic “done” when it hides an unresolved technical question. In a synthetic case, the researcher locates the correct communication identity, but the planner needs another document for the technical decision. Close the retrieval task as complete. Keep the separate request for controlling material open with its own owner. If the reference proves unrelated, retain the rejected identity and the review reason. This gives the next person an explanation for excluding it. Do not remove the reference and leave a blank card that invites the same search again. When someone reuses the card, ask them to compare the new question with the recorded review scope. Preserve the earlier answer as historical evidence. Request a fresh decision if the new question exceeds what the reviewer previously established. ## Preserve the review without copying the procedure Retain document metadata, official links, the question submitted, and the reviewed outcome. Do not reproduce technical instructions in this worksheet. Let qualified staff use the approved sources and systems for repair planning. The [business memory guide](/articles/business-memory-for-ai-agents-guide) covers keeping records and accepted corrections. Here, a useful correction might say that two references have different product scopes. Preserve the evidence supporting that correction so it can inform the next research task. Review the card when the planning question changes. A reference accepted for one question should not silently become authority for another. Ask the new reviewer to state what carries forward and what needs fresh confirmation. The [collision shop intelligence overview](/intelligence/auto-body-and-collision-shops) places public-source research within broader planning work. A document card remains a source-reading aid. It does not diagnose damage, interpret an insurance policy, or authorize a repair. Bring Scale With Search a synthetic handoff example if your shop needs help organizing approved references. Identify the person who will review them. Define any paid engagement through the existing written scope process. [Discuss the work](/work) ## Source note Sources reopened on October 28, 2026: [NHTSA datasets and APIs](https://www.nhtsa.gov/nhtsa-datasets-and-apis#manufacturer-communications), [manufacturer-communications layout](https://static.nhtsa.gov/odi/ffdd/tsbs/TSBS.txt), and [recall guidance](https://www.nhtsa.gov/recalls). The inspected layout's latest change-log entry is September 15, 2026. The web guidance has no edition number stated in the inspected sections. No procedure text, real vehicle record, or live campaign count appears in the examples. Continue the website review: [AI-native auto body and collision shops: first functions to build](/articles/ai-native-collision-shop-first-functions); [Auto marketing: a website plan for body shops](/articles/auto-body-marketing-website-local-search); [Auto Body Estimate Emails Missing: Trace the Request](/articles/auto-body-shop-estimate-email-delivery-check); [Auto Body Shop FAQ Schema: Check the Current Rules](/articles/auto-body-shop-faq-schema-current-rules); [How Auto Body Shops Can Ask for Google Reviews](/articles/auto-body-shop-google-review-requests); [Hail Damage Pages for Auto Body Shops: Define the Work](/articles/auto-body-shop-hail-damage-service-page); [Auto Body Shop Photo Estimate Form: What to Ask](/articles/auto-body-shop-photo-estimate-form); [Auto Body Shop Tow-In Pages: Explain the Arrival](/articles/auto-body-shop-tow-in-directions-page); [Collision shop AI rules: data, approvals, and spend](/articles/collision-shop-ai-data-approval-spend-rules); [Collision Shop Certifications: What Your Site Can Say](/articles/collision-shop-certifications-website); [Collision Shop Google Appointment Links: Check the Path](/articles/collision-shop-google-appointment-link); [Collision Shop Insurance FAQs: Separate Each Promise](/articles/collision-shop-insurance-website-faq); [Collision Shop Location Pages: Route Each Inquiry](/articles/collision-shop-multiple-location-website-inquiries); [Collision Shop Repair-Time FAQs: Explain the Stages](/articles/collision-shop-repair-time-website-faq); [NHTSA recall searches: what make, model, and year tell a collision planner](/articles/nhtsa-recall-search-make-model-year-limits). [auto body and collision shops](/for/auto-body-and-collision-shops): website and search resources. ## Related: auto body and collision shops - [NHTSA recall searches: what make, model, and year tell a collision planner](/articles/nhtsa-recall-search-make-model-year-limits) - [AI-native auto body and collision shops: first functions to build](/articles/ai-native-collision-shop-first-functions) - [Auto marketing: a website plan for body shops](/articles/auto-body-marketing-website-local-search) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```