The Record Type Changes the Repair and Coverage Question Main conclusion Read the remedy and its eligibility rules before deciding who may pay The collection contains 1,200 recall-based files, five extension or support-program files and 16 other manufacturer-path files. Their different purposes create different next steps. The recall-heavy composition reflects the imported library, so it cannot establish how often drivers qualify for a manufacturer-paid remedy. Analysis Why the classification matters more than the largest count The large recall group mainly describes how this collection was assembled. Separate model files can refer to the same campaign, and the import was deliberately recall-heavy. Turning the split into a share of breakdowns repaired by manufacturers would change both the population and the unit being counted. The useful interpretation is at the document level. A recall creates a VIN and current-remedy question. An extension or customer program creates a question about the vehicle, diagnosed condition and printed limits. A bulletin may describe a procedure without deciding who pays for it. Treating all three labels as equivalent would lose the information that changes the next inquiry. Existing remedies and future protection also concern different decisions. A confirmed program can change the payer for a particular fault without establishing coverage for every other repair. Understanding that boundary helps identify what remains to consider under future eligible protection, rather than treating a file count as a recommendation to buy or avoid a contract. Conclusion Resolve the documented remedy before evaluating the remaining gap For a present fault, get the diagnosis and ask the manufacturer whether the VIN and condition qualify under a current remedy. Keep a service instruction separate from a payment promise. Once that answer is clear, evaluate future protection for the remaining eligible systems and failures. This audit explains which inquiry to make; it cannot determine VIN eligibility or the value of a plan from the number of files. Suggested attributed interpretation: “The practical finding from AutoWarranty's selected 1,221-file audit is that record types are not interchangeable. Recalls, qualifying programs and service bulletins create different eligibility and payment questions.” Numeric finding quotation: “AutoWarranty's selected 1,221-file collection contains 1,200 recall-based files, five extension or support-program files and 16 other manufacturer-path files. The collection is recall-heavy, not a representative sample of breakdowns.” Attribution: AutoWarranty.Autos analysis Population: 1,221 selected problem files; repeated campaigns across models are retained Snapshot: 2026-08-03T20:46:23Z Published: 2026-10-12; analysis reviewed: 2026-10-12 Method - Read every retained problem ID once from the migrated source, without expanding its multi-year routes. - Assign safety recall first using the existing sourceKind, evidenceLevel and safety-recall evidence classification. A recall file remains in that group even if it also cites a program. - Among the remaining files, assign extension or customer program where the evidence label or evidence kind names a warranty extension, customer support or customer program. Put all other files in other manufacturer information. - Export every ID, assigned category, original evidence labels, citations and review date so the partitions can be checked. The audit publication date does not refresh those records. Limits - The collection is selected and includes a bulk recall import. Its composition is not the composition of all vehicle faults or manufacturer remedies. - Different model files can cite the same campaign. Unique IDs do not imply unique campaigns. - The classification describes source labels, not independent verification that a particular VIN qualifies for free work. - No owner-feedback, fleet-size, cost, mileage or failure-rate data is used. Sources Retained source and migration method | 2026-08-03 | /car-problem-guides/method Recall, bulletin and extension definitions | 2026-08-02 | /car-problem-guides/service-bulletin-vs-recall-vs-warranty-extension NHTSA VIN recall lookup | 2026-10-12 | https://www.nhtsa.gov/recalls TSB 19-2139 | Nov 21, 2019 | https://static.nhtsa.gov/odi/tsbs/2019/MC-10168739-0001.pdf 21N12 | Jun 9, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10213732-0001.pdf Subaru Bulletin 09-119-24 | Apr 4, 2024 | https://static.nhtsa.gov/odi/tsbs/2024/MC-10253930-0001.pdf Subaru Bulletin 09-80-21 | Feb 28, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10208664-0001.pdf Report: https://autowarranty.autos/research/manufacturer-remedies-before-paid-coverage Data: https://autowarranty.autos/research/manufacturer-remedies-before-paid-coverage/data The 1,221-file collection is heavily recall-based The 1,200 / 5 / 16 split describes this selected collection. It cannot estimate the share of breakdowns repaired free of charge. https://autowarranty.autos/research/manufacturer-remedies-before-paid-coverage/figures/library-composition https://autowarranty.autos/assets/research/manufacturer-remedies-before-paid-coverage-library-composition.png Look closer at the 21 non-recall files A technical bulletin can describe a procedure without promising payment. Program status and VIN eligibility need a separate check. https://autowarranty.autos/research/manufacturer-remedies-before-paid-coverage/figures/non-recall-files https://autowarranty.autos/assets/research/manufacturer-remedies-before-paid-coverage-non-recall-files.png Contact: me@autowarranty.autos Credit AutoWarranty.Autos and link to the report when citing our analysis or graphics. Underlying source material retains its own terms.