A BOM alternate component approval matrix records which substitute is permitted at each reference designator, why it is acceptable, what verification supports that decision and who approved its use. Treat a cross-reference result as a candidate. Release the alternate only after the responsible engineering owner has reviewed the application and the manufacturing consequences.
This guide is for hardware teams and buyers preparing procurement for a defined assembly revision. It does not declare two unnamed parts interchangeable or set a universal qualification procedure. The aim is a usable approval record that prevents a purchasing suggestion from silently becoming an engineering change.
Identify the replacement precisely
Record the complete manufacturer part number, including suffixes that identify the package, grade or orderable configuration. Also record the approved original, the assembly revision, the fitted variant and the affected reference designators. An internal stock number can be useful, but it should resolve to a controlled manufacturer identity rather than an informal description.
Decide whether approval applies to all placements of a part or only to a specific use. The same component may appear in several circuits with different requirements. An alternate reviewed for one low-demand function should not automatically be treated as approved elsewhere simply because the original part number is the same.
Distinguish matching pins from matching behavior
Texas Instruments’ cross-reference definitions distinguish a drop-in replacement from a pin-for-pin replacement and from parts with the same or similar functionality. In particular, matching function and pinout can coexist with different parameters. These tool categories help describe a candidate; the project owner still needs to determine suitability in the actual circuit.
Use the original and candidate data sheets as the comparison inputs. Identify which parameters matter in the application rather than copying only the first row of each feature list. Record operating conditions alongside limits, and distinguish guaranteed limits from typical values. If a requirement cannot be compared from the available documents, keep it unresolved until the appropriate review or verification closes it.
Create an approval matrix that purchasing can act on
| Record field | Required entry | Decision it supports |
|---|---|---|
| Scope | Assembly revision, variant and reference designators | Where the approval is valid |
| Identity | Original and proposed complete manufacturer part numbers | Exactly what may be ordered |
| Electrical review | Relevant requirements, conditions, limits and document revisions | Whether the candidate meets the circuit’s needs |
| Mechanical review | Package drawing, land-pattern compatibility and assembly constraints | Whether the proposed part fits the released design |
| Software impact | Configuration, identity or behavior differences requiring review | Whether firmware or test code must change |
| Verification | Review or test report, result, limitations and affected build | What evidence supports acceptance |
| Disposition | Approved, conditionally approved, rejected or pending; named authority | Whether purchasing is allowed to proceed |
| Effectivity | Applicable lot, order, date or revision boundary | When the decision applies and how it is traced |
Keep availability and commercial evaluation visible but separate from technical approval. A candidate may be attractive to buy and still lack engineering acceptance. Conversely, a technically approved alternate may be unavailable for a particular order. The matrix should allow these two facts to coexist without compressing them into a single ambiguous “OK.”
Include the assembly and test consequences
Ask whether the candidate changes an orientation reference, marking interpretation, handling instruction or approved process requirement. A package may appear familiar while the assembly team’s visual reference needs updating. Give the assembler the controlled change, not just a purchasing email with a new number in the subject line.
Review the production test at the same time. If the test relies on an identification response, programmed option or characteristic that changes with the alternate, define the necessary update and its verification. Do not weaken an acceptance limit just to make a new part pass. Any changed requirement needs the authority and evidence appropriate to the product.
Example: the same footprint in two different circuits
Consider a hypothetical controller using the same original analog device at two locations. One location serves a slow monitoring function; the other supports a more demanding signal path. A proposed pin-compatible alternate might satisfy one location’s requirements while leaving the other unresolved. The correct record is reference-specific approval, not a blanket addition to the approved parts list.
The engineering reviewer can document the conditions evaluated at each location and identify any required testing. Purchasing then has a clear rule for the affected build. This example illustrates approval scope; it does not assert that a particular substitute is acceptable or that a test has been performed.
Make conditional approval operational
A conditional approval needs a condition someone can enforce. “Approved after review” is not useful if nobody knows which review remains open. A clearer entry identifies the permitted pilot quantity or revision, the report required for closure and the person who can release broader use. Do not interpret permission to obtain evaluation samples as permission to install the candidate in production.
Track the approved change into the BOM, purchasing instruction and assembly documentation. Record which units or lots used the alternate through the project’s agreed traceability method. If the candidate is later removed from approval, the same effectivity information helps determine what was already built and what purchasing instructions must change.
Close the loop after the first affected build
Review the observations from the first build using the alternate against the original approval conditions. Capture unexpected differences without treating every observation as a confirmed component defect. Separate receiving, assembly, firmware, fixture and product findings so the responsible owner can investigate the right cause.
Keep the approval package available with its source documents and revision history. A later buyer should be able to determine why the candidate was accepted and whether that decision covers the new order. Reusing the same spreadsheet row without checking its revision scope can erase the distinction between a controlled alternate and an undocumented substitution.
Prepare the sourcing inquiry
For component sourcing, supply the released BOM, complete part numbers, approved alternatives and any pending candidates clearly marked as pending. Identify who approves substitutions and which documents the supplier must return. Use the assembly quote comparison guide to keep material ownership and approval work consistent across proposals.
When selecting an electronic manufacturing service, agree how a shortage-driven proposal reaches engineering before it becomes a purchasing commitment.