BOM scrub: finding EOL risk before it finds you

What a BOM scrub is

A BOM scrub is a systematic pass through every line of a bill of materials, checking each component's actual lifecycle status against manufacturer and distributor data, rather than assuming a part is fine because it was fine the last time anyone looked. For each part, that means checking for product change notices (PCNs), last-time-buy dates, recommended-replacement guidance from the manufacturer, and distributor-reported stock trends, then flagging anything that's discontinued, nearing end-of-life, or showing early warning signs like a single remaining distributor or a manufacturer that's gone quiet on a product line.

The point of a scrub isn't to react to the EOL notice that already landed in your inbox, it's to find the ones that haven't been announced loudly yet: a part with no formal PCN but declining stock across every distributor, a manufacturer quietly steering customers toward a newer package on datasheet revisions without ever issuing a discontinuation notice. A reactive process only catches what a supplier decides to tell you, on their timeline. A scrub finds it on yours.

Done well, a BOM scrub isn't a one-time event before a big program milestone, it's a recurring check against a design that's already in production, because component lifecycles keep moving whether or not anyone's watching.

What triggers a scrub

• Before a design transfer to a new supplier or contract manufacturer, since inherited BOMs are often years out of date on lifecycle status
• Before a significant production volume commitment, when the cost of discovering an EOL part mid-ramp is highest
• On a recurring schedule for any product still in active production, typically quarterly or semi-annually depending on how volatile the component set is
• Immediately after a PCN or discontinuation notice arrives for any part, to check whether the same root cause, a fab consolidation, a material shortage, might affect other parts on the same BOM
• Before a new product's design is frozen, to avoid designing in a part that's already showing risk signals at the point of selection

How a scrub actually works

1. Compile the full BOM with manufacturer part numbersNot just the internal part number, the actual manufacturer and MPN for every line, since lifecycle data is tracked against the real part, not your internal numbering.
2. Cross-reference against lifecycle data sourcesCheck manufacturer PCN databases, distributor lifecycle flags, and any subscription lifecycle-tracking service available, for every line. A part with no red flags from one source can still show early warning signs in another, so single-sourcing the check is itself a risk.
3. Score each flagged part for real risk, not just statusStatus alone (active, NRND, EOL) isn't the whole picture. Weight it against how critical the part is to the design, whether it's single-sourced, and how much stock or lead time is actually left. A low-criticality passive with six qualified sources is a very different risk than a single-source connector with no announced replacement.
4. Identify and qualify alternates for anything above thresholdFor each high-risk line, find candidate alternates, check them against the original part's electrical, mechanical, and footprint requirements, and flag anything that would require more than a drop-in substitution.
5. Decide the disposition per partNot every flagged part needs the same response: some get a qualified drop-in alternate added to the approved BOM immediately, some get a last-time-buy to bridge until a redesign is scheduled, and some genuinely require a layout change, which should be scoped, not just noted.
6. Document and schedule the next passRecord what was found, what was decided, and why, and set the next scrub date. A scrub that isn't repeated eventually becomes exactly as stale as the BOM it was meant to fix.

Scoring risk: status alone isn't enough

A part that's technically still "Active" but single-sourced, hard to substitute, and sitting in a safety-critical path can be a higher real priority than a part that's formally EOL but has years of verified stock and three drop-in alternates already on the market. Scoring on status alone misses this distinction constantly.

Worked example: finding an alternate for an EOL connector

The detail worth generalizing from this example: the PCN's own discontinuation window (9 months) wasn't actually the real constraint, distributor stock depletion was tighter, because the rest of the market was reacting to the same notice at the same time. A scrub that only tracks the manufacturer's stated timeline, and not real-time stock trend, would have found this risk months too late.

Common mistakes

• Treating a BOM scrub as a one-time event. Component lifecycles keep moving after the scrub is filed away; a design still in production needs a recurring cadence, not a single pass.
• Scoring on lifecycle status alone. A part's formal status is one input, not the whole risk picture, ignoring sourcing, criticality, and substitution difficulty misses real risk hiding in "Active" parts.
• Checking only the manufacturer's stated timeline. Distributor stock can deplete faster than a PCN's official window once the broader market reacts to the same notice.
• Qualifying an alternate on datasheet specs alone. Footprint, mating force, thermal behavior, and mechanical fit can differ in ways a datasheet comparison alone won't catch; real qualification matters even for a "drop-in" candidate.
• Waiting for the PCN to arrive. By the time a formal notice lands, the best window for an unhurried, well-qualified alternate is often already closing.

Frequently asked questions