The Manufacturer's Repair Path Can Change Which Job an Estimate Should Price

Main conclusion
The system named in a complaint does not determine the replacement scope
A transmission or electronic-system symptom does not automatically identify a complete assembly replacement. In these files, the first official path may instead involve software, adjustment or diagnosis of a smaller component. The inference is to establish the applicable path before applying a replacement benchmark.

Analysis
What the procedure adds beyond the name of the system
The two software procedures demonstrate an important scope distinction. A documented transmission-related condition can direct a matching calibration, and a matching infotainment condition can direct a software update. A price for replacing the full unit would describe a different job from the retained instruction for that stated condition.
The three service or adjustment files and six mixed or diagnosis-dependent files add another distinction: the procedure can depend on the test result. A mixed path may still lead to hardware work, and an adjustment path may contain small parts. The ten specified-component files also do not automatically identify the largest possible assembly; the retained Mazda and Honda examples concern valve seals and a compressor shaft seal.
The categories explain how a repair scope is determined, rather than which type of repair is common in the market. These are 21 selected files with no observed outcome or price comparison. They support asking whether the estimate follows the applicable procedure, but they cannot establish a software-versus-hardware frequency or a saving from choosing a smaller repair.

Conclusion
Require a diagnostic reason for the proposed replacement scope
Ask which condition was confirmed, which manufacturer procedure applies and why the proposed component matches that path. A smaller procedure should not be assumed to solve an unrelated hardware fault, and a complete replacement should not be inferred from a symptom alone. The analysis identifies a scope check to make before using a price; it does not substitute for diagnosis or estimate repair savings.

Suggested attributed interpretation: “The system named in a complaint does not determine the replacement scope. AutoWarranty's review of 21 selected non-recall files shows why the confirmed condition and manufacturer procedure must identify the job an estimate prices.”
Numeric finding quotation: “A review of AutoWarranty's 21 retained non-recall manufacturer files identifies two software procedures, three service or adjustment paths, six mixed or diagnostic paths and ten specified component repairs. The selected files do not measure breakdown frequency.”
Attribution: AutoWarranty.Autos analysis
Population: All 21 non-recall files in the retained collection; manual editorial classification
Snapshot: Source records reviewed 2026-08-02; classification published 2026-10-12
Published: 2026-10-12; analysis reviewed: 2026-10-12

Method
- Select every non-recall record under the retained source classification, yielding 21 files.
- Manually classify the first official path into software procedure, service or adjustment, diagnosis or mixed path, or specified component repair.
- Keep one mutually exclusive category per file. Hardware paths can still be conditional on diagnosis; adjustment paths can contain small or conditional replacement parts.
- Export the source ID, category, affected scope, original review date, retained official-path text and primary citations. The classification is editorial analysis, not a manufacturer-issued taxonomy.

Limits
- The selected collection is not a representative sample of vehicles, failures or repair visits.
- Classification reflects retained descriptions and their first path, not observed outcomes or comparative prices.
- A software entry does not rule out unrelated hardware faults with similar symptoms. No repair savings are estimated.

Sources
TSB 19-23-39 / 2070349/1 | May 17, 2023 | https://static.nhtsa.gov/odi/tsbs/2023/MC-10236572-0001.pdf
SIB 51 21 19 | Aug 16, 2019 | https://static.nhtsa.gov/odi/tsbs/2019/MC-10165284-9999.pdf
SIB 17 03 20 | May 7, 2020 | https://static.nhtsa.gov/odi/tsbs/2020/MC-10176366-9999.pdf
NHTSA MC-10212631 | Feb 2, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10212631-9999.pdf
20-NA-142 | May 2, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10213032-0001.pdf
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
Service Bulletin 21-018 | May 28, 2021 | https://static.nhtsa.gov/odi/tsbs/2021/MC-10194961-0001.pdf
Service Bulletin 23-040 | May 19, 2023 | https://static.nhtsa.gov/odi/tsbs/2023/MC-10237039-0001.pdf
NHTSA MC-10186656 | Jan 27, 2021 | https://static.nhtsa.gov/odi/tsbs/2021/MC-10186656-0001.pdf
L-SB-0032-19 Rev1 | Sep 26, 2019 | https://static.nhtsa.gov/odi/tsbs/2019/MC-10166041-9999.pdf
L-SB-0003-23 | Feb 2, 2023 | https://static.nhtsa.gov/odi/tsbs/2023/MC-10235210-9999.pdf
L-SB-0014-22 | Jun 24, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10224115-9999.pdf
NHTSA MC-10206952 | Jan 31, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10206952-0001.pdf
Mazda TSB 01-011/22 | Nov 17, 2022 | https://static.nhtsa.gov/odi/tsbs/2022/MC-10226816-0001.pdf
LI54.10-P-069698, Version 20 | Mar 25, 2025 | https://static.nhtsa.gov/odi/tsbs/2025/MC-11016221-0001.pdf
NTB19-076 | Oct 8, 2019 | https://static.nhtsa.gov/odi/tsbs/2019/MC-10167398-0001.pdf
Subaru Bulletin 15-261-20R | Oct 1, 2024 | https://static.nhtsa.gov/odi/tsbs/2024/MC-11009683-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
Customer Support Program 20TE04 | Oct 29, 2020 | https://static.nhtsa.gov/odi/tsbs/2020/MC-10182953-9999.pdf
T-SB-0109-20 Rev1 | Mar 3, 2021 | https://static.nhtsa.gov/odi/tsbs/2021/MC-10190473-9999.pdf
T-SB-0079-20 Rev1 | Dec 9, 2020 | https://static.nhtsa.gov/odi/tsbs/2020/MC-10185772-9999.pdf
Service Action 60E5 | Dec 3, 2019 | https://static.nhtsa.gov/odi/tsbs/2019/MC-10169126-0001.pdf
Technical Bulletin 60-19-04 / 2054353 | Apr 1, 2019 | https://static.nhtsa.gov/odi/tsbs/2019/MC-10158675-0001.pdf

Report: https://autowarranty.autos/research/software-service-replacement-paths
Data: https://autowarranty.autos/research/software-service-replacement-paths/data
Not every manufacturer path starts with a large assembly
Two software, three service or adjustment, six mixed or diagnostic and ten specified component paths. This small selected collection is not a breakdown sample.
https://autowarranty.autos/research/software-service-replacement-paths/figures/official-paths
https://autowarranty.autos/assets/research/software-service-replacement-paths-official-paths.png
Compare the procedure with the assembly on the estimate
The full report retains affected vehicles, review dates and primary citations. Diagnosis and scope checks remain necessary.
https://autowarranty.autos/research/software-service-replacement-paths/figures/path-examples
https://autowarranty.autos/assets/research/software-service-replacement-paths-path-examples.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.