Find Candidate Technical Service Bulletins and Record Their Scope
How to look up technical service bulletins through NHTSA by year, make and model, why a VIN search shows recalls instead, and how to record each bulletin's number, date, revision and stated vehicle scope.
Contents
The short answer
A technical service bulletin (TSB) is a communication from a vehicle manufacturer to its dealers and technicians. It usually describes a known condition and the recommended procedure, part or policy for dealing with it. To find candidate bulletins for a US-market vehicle, search NHTSA's recall and safety-issue lookup by year, make and model rather than by VIN or license plate, and open the manufacturer communications listed in the results. Treat every result as a candidate only. A bulletin turning up in a search for your model does not establish that it applies to your particular vehicle. Each document states its own scope, such as model years, models, market, build ranges or other conditions. Record that scope exactly as written, along with where and when you found the document. Leave applicability marked as unconfirmed until the manufacturer or an authorized dealer confirms it for your VIN.
Why a VIN search is not a TSB search
Many people search for a "TSB lookup by VIN" and expect a list of bulletins for their exact car. NHTSA's lookup does two different jobs. A VIN or license-plate search reports unrepaired safety recalls for that individual vehicle. A year, make and model search returns broader results for the model, and those results include manufacturer communications such as service bulletins. To find bulletins, you need the year/make/model route. To confirm that a bulletin applies to one specific vehicle, you need the manufacturer or its dealer network, because they can check the VIN against the bulletin's stated conditions.
The same applies to brand-specific searches, such as a Honda or Hyundai TSB lookup by VIN. A public model-level search can surface candidates for those makes. A dealer service department can then check whether a candidate covers a given VIN and whether a newer revision exists.
What NHTSA's bulletin collection covers and what it leaves out
NHTSA describes manufacturer communications as covering specified defects, failures, malfunctions and other deviations, whether or not they are safety-related. A bulletin therefore does not mean a recall exists, and a recall is a separate legal process with its own record. Keep the two in separate places in your notes.
NHTSA also publishes its manufacturer communications and TSB data as downloadable files with layout documentation. These are useful if you want to search many records at once. The bulletin summaries are grouped by year, make and model, and sometimes by component.
NHTSA states that this collection does not contain every manufacturer bulletin. An empty search result does not prove that no bulletin exists for your vehicle. If you are chasing a recurring problem and the public search finds nothing, ask the manufacturer or an authorized dealer before concluding there is no relevant bulletin.
Step-by-step: finding and recording candidate bulletins
- 1. Note the search details before you start: the date, the source you used (for example, NHTSA's recall and safety-issue lookup) and the exact year, make and model you entered.
- 2. Run the year/make/model search and list every manufacturer communication that looks relevant to the symptom, component or system you care about.
- 3. Open each candidate and save the full document, not just the search summary. Summaries are short and can leave out the conditions that limit a bulletin's scope.
- 4. From the document itself, transcribe the bulletin number, document date, revision designation (only if the document states one), subject line, listed models and model years, market, and any other stated restrictions such as engine, transmission, equipment or build range.
- 5. Note anything the bulletin says it supersedes or references. Record the exact target it names rather than a general description.
- 6. File related service records, such as repair orders, invoices and inspection reports, alongside the bulletin entry but as separate items. A bulletin does not show that work was done, and an invoice does not show that a bulletin applied.
- 7. Ask the manufacturer or an authorized dealer to confirm two things: whether the copy you have is the current revision, and whether it applies to your VIN. Mark each item confirmed only after you get an answer, and note who confirmed it and when.
Worked example: reading a bulletin's scope
A historical General Motors document in NHTSA's collection shows why the scope should be recorded precisely. Bulletin 14-00-89-003, dated July 2014, concerns US warranty administration for 2015 and earlier GM passenger cars and trucks. It is a policy communication, not a repair procedure. It names a specific policy section that it supersedes and gives a separate reference for Canada. A careful record of this document would include:
- Bulletin number: 14-00-89-003, exactly as printed, with no revision suffix added.
- Date: July 2014.
- Subject type: warranty administration policy, not repair instructions.
- Vehicle scope: 2015 and prior GM passenger cars and trucks.
- Market: United States, with Canada handled under a separate reference.
- Supersedes: the specific policy section the document names, copied word for word.
- Status: historical document, not to be used as current guidance without checking for later revisions.
Leaving out the market restriction or the supersession note would make the record misleading. A reader could assume the bulletin applies in Canada, or that the older policy section is still in force.
A simple bulletin register
The following is an illustrative template, not a real record. One row per candidate keeps the source, the stated scope and the confirmation status separate.
| Field | Example entry (hypothetical) |
| Candidate | A |
| Source | Saved file name and the lookup tool used |
| Lookup date | Date of the search |
| Search query | Year / make / model entered |
| Bulletin number | As printed on the document |
| Document date | As printed on the document |
| Revision | Not stated |
| Subject | As printed on the document |
| Stated scope | Models, years, market and other restrictions, quoted |
| Supersedes / references | Exact targets named in the document |
| Applicability to this VIN | Awaiting confirmation |
| Confirmed by / date | Blank until confirmed |
| Related service records | Repair order or invoice reference, filed separately |
Adding a candidate to this register only records a lookup. Whether the vehicle has the described condition, whether a repair was completed, whether a recall is open and whether warranty coverage applies are separate questions. Each should be answered and documented on its own.
Related articles
Record and Preserve Details from an ADAS Calibration Report
How to read an ADAS calibration report PDF and build a traceable record of vehicle identifiers, dates, system labels, procedure references and outcomes, with open questions sent to the issuer.
Match and File a Vehicle Fluid Analysis Report
How to read a vehicle fluid analysis lab report PDF for record keeping: match it to the right vehicle, component and sample, record results exactly, and link earlier reports.
Identify and Transcribe Vehicle Emission Information Label Fields
How to find and read a VECI label: what the test group, engine family, evaporative family and other fields mean, and how to transcribe them accurately.
Identify Battery Test Report Values, Ratings and Reported Assessments
How to read a battery test report: tell measured voltage and ratings from the selected rating, keep units and test conditions, and record the tester's verdict.
Record Exact Dashboard Messages for a Service Visit
How to capture the exact wording of a dashboard message, plus the warning lights, sounds and driving conditions around it, so a service visit starts from an accurate record.
Identify Wheel Positions, Columns and Units on an Alignment Report
How to read a wheel alignment printout: find each wheel position, separate before, after and specification columns, and record units and symbols correctly.
Verify Extracted Service Invoice Fields Against the Original Scan
A practical method for checking OCR-extracted vehicle service invoice fields against the original scan, reconciling line items and totals, and saving only verified data to your vehicle records.
Identify Brake Inspection Positions, Measurements and Units
How to read brake inspection sheet labels such as LF, RF, LR and RR, tell brake-lining millimeters apart from tire tread and pressure entries, and transcribe each value with its source sheet.
Record Vehicle Parts Purchases, Identifiers and Installation Evidence
A practical template for recording car parts receipts, part numbers and installation evidence, keeping purchases separate from documented installation.
Read Service Paperwork and Record Completed Work
How to read car service paperwork, extract vehicle, date, mileage, work and charge details, and separate recommended work from completed work before updating your service log.