Warranty stories
How to write a good warranty story
The repair is finished. Can someone else follow the evidence?
The car is gone. The injector is in the scrap bin. Now the warranty administrator is at your toolbox asking why you replaced it.
You remember the misfire. You remember proving it. The repair order says four words: "Replaced injector. Runs good." The work happened, but the evidence never made it onto the page.
Write the story while the vehicle can still answer questions.
Three gaps that send a story back
1. The complaint becomes a finding. An advisor records a cold-start rattle; the story says "verified" even though the technician only ran a warm engine. Fix: state when and how you duplicated it. If you could not, say so and record the checks you completed.
2. The replaced part becomes the diagnosis. "Replaced injector" explains a purchase, not the decision. Fix: show the path from symptom to failed component, including tests that ruled something out. A code identifies a condition; it does not prove every part named in its description failed.
3. The repair has no ending. "Cleared codes" records an action, not whether the fault returned. Fix: repeat the relevant operating conditions, record the result, then close with the systems function check. Keep pending work out of the completed correction.
Bad vs. good: a warm-idle misfire
This fictional adaptation of our DMS demo compares bad and good cause and correction notes for the same concern. Its readings, specification, and added diagnostic steps belong to this example only. Use current service information and your own findings on a real vehicle.
Notice the coil swap: the misfire stayed on cylinder 3. That result explains why the technician continued investigating instead of replacing a coil. The injector reading then supports the recommendation. Every sentence advances the account.
- Bad cause
- ENGINE RUNNING ROUGH. FOUND MISFIRE.
- Bad correction
- REPLACED INJECTOR. CLEARED CODES. OK NOW.
- Concern (advisor)
- CUSTOMER STATES ENGINE IDLES ROUGH AT STOPS AFTER WARM-UP AND CHECK ENGINE LIGHT IS ON. CHECK AND ADVISE.
- Good cause
- VERIFIED CUSTOMER CONCERN OF ROUGH IDLE AT STOPS WITH ENGINE AT OPERATING TEMPERATURE DURING ROAD TEST. CHECK ENGINE LIGHT ON. SCANNED PCM AND FOUND CURRENT DTC P0303, CYLINDER 3 MISFIRE. MONITORED MISFIRE COUNTERS AT WARM IDLE AND FOUND MISFIRES ON CYLINDER 3. SWAPPED IGNITION COILS BETWEEN CYLINDERS 2 AND 3 AND RECHECKED; MISFIRE REMAINED ON CYLINDER 3. MEASURED CYLINDER 3 FUEL INJECTOR RESISTANCE AT 9.4 OHMS AGAINST THE 11 TO 14 OHM SPECIFICATION IN SERVICE INFORMATION. FOUND CYLINDER 3 INJECTOR WINDING RESISTANCE BELOW SPECIFICATION. RECOMMEND REPLACE CYLINDER 3 FUEL INJECTOR.
- Good correction
- RETURNED IGNITION COILS TO THEIR ORIGINAL CYLINDERS. REMOVED FAULTY CYLINDER 3 FUEL INJECTOR AND INSTALLED NEW INJECTOR WITH NEW SEALS. PERFORMED FUEL LEAK CHECK; NO LEAKS FOUND. CLEARED DTCS. ROAD TESTED 5 MILES AND RECHECKED AT STOPS WITH ENGINE AT OPERATING TEMPERATURE. IDLE STEADY AT 650 RPM, NO ROUGHNESS, AND CYLINDER 3 MISFIRE COUNTER REMAINED AT ZERO DURING RECHECK. RESCANNED PCM; NO CURRENT OR PENDING MISFIRE DTCS RETURNED. PERFORMED SYSTEMS FUNCTION CHECK. ALL OPERATION NORMAL AS FACTORY DESIGN.
A number needs its conditions
A reading without units or a comparison leaves the next person guessing. Put the observed value beside the specification you actually used. Identify the component and test conditions, especially when temperature, load, or location changes what the number means.
This is a record of the fictional example, not a specification sheet for other vehicles.
| Check | Recorded result | Why it belongs |
|---|---|---|
| Injector resistance | 9.4 ohms; example specification 11 to 14 ohms | Shows how the failed winding was identified. |
| Coil swap | Misfire stayed on cylinder 3 | Preserves the diagnostic step that ruled out the swapped coil. |
| Warm-idle recheck | 650 rpm; zero cylinder 3 misfires observed | Records the outcome under the original symptom conditions. |
Keep this beside the RO, or just get Bayworks
Bayworks turns your spoken repair notes into a cause and correction for you to review and save.
Copy this review card into your shop notes. It is a reminder of what to check, not a ready-made story. Each line needs the facts from the repair in front of you.
An archived Ford warranty manual emphasizes repair-specific comments and test results even when a menu supplies the wording. It is historical guidance; the current OEM requirements control the claim.
Warranty story review card
Select and copy this checklist into your shop notes.
[ ] Correct vehicle, RO, repair line, and component location confirmed. [ ] Customer symptom verified under stated conditions, or not duplicated clearly recorded. [ ] Diagnostic steps, actual readings, units, and applicable specifications included. [ ] Failed component and repair recommendation supported by those findings. [ ] Completed repair separated from proposed or waiting work. [ ] Final test addresses the original concern and records the outcome. [ ] Required time records, approvals, and attachments checked before submission.
Reference: Ford warranty manual archived by NHTSA, section 1, page 11.
Common questions
How long should a warranty story be?
Long enough to explain the evidence, repair, and result. A straightforward repair can take a few sentences. A repeat visit or complex diagnosis may need more. Length alone does not make a claim complete.
What if I cannot duplicate the concern?
State that clearly. Record the checks performed, relevant conditions, and results. Do not turn an unconfirmed symptom into a verified fault or claim a repair that did not happen.