Read-across, sometimes called extend-to-similar, is the requirement to take the root cause and corrective action from one failure and apply it to every similar part, process, tool, and plant where the same failure mode could occur. OEMs ask for it because most repeat escapes are not new problems; they are the same problem on a part nobody checked. A strong read-across is often what closes an 8D and prevents the next spill.
Why read-across prevents repeat escapes
A defect rarely lives on a single part number. The same gauge error, tooling wear, operator instruction, or material issue usually touches a family of parts. If you fix only the part that got caught, the identical failure is still waiting on its siblings. Read-across forces you to ask where else this exact cause exists and to close those gaps before they escape.
How to do a credible read-across
Start from the confirmed root cause, not the symptom. List every part, process, shift, tool, and site that shares that cause, then verify each one with data, not assumption. Where the cause is present, apply the same corrective action and record it. The output is a simple matrix: similar item, is the cause present, action taken, evidence. That matrix is what the customer wants to see.
Documenting it in the 8D
Read-across belongs in the corrective-action and prevention steps of your 8D, D6 and D7. Show the family you reviewed, what you found, and what you changed, including updates to control plans, PFMEAs, and work instructions across the family. A containment and inspection partner can help by checking the similar parts in the field while your engineers confirm the cause, so the read-across is backed by real inspection data.