A shared production bottleneck can cause downtime even when you buy from different suppliers. To assess supply chain concentration risk in manufacturing, start with a critical component and trace the upstream sources, locations and transport handoffs behind each supplier. Use the record below to separate confirmed dependencies from questions that still need an answer.
A supplier count cannot establish whether supply paths are independent. For a small manufacturer, a useful first assessment is a component-by-component record: what you buy, where it is actually made or processed, which route it takes, whether an alternative is approved for the job, and who can verify the missing details. Leave unknowns visible.
This guide provides a copyable worksheet and a hypothetical example. It requires your own supplier records; it supplies no company risk score, safe purchasing percentage or prediction of a disruption.
What does supplier concentration mean for a critical part?
For this worksheet, concentration means that a component’s supply depends on the same source, place or transport node across the purchasing routes you are considering. The question is whether a disruption at that dependency could affect those routes together.
The NIST MEP supply-chain mapping article, published in January 2024, describes mapping critical parts, suppliers’ suppliers, geography and transport routes. Those are the starting fields here. A seller’s billing address is a different piece of information from the location where a part is made.
Choose a component whose absence would interrupt a named production step. Ask the production planner which product or operation needs it, then record the relevant part number and revision. Begin there rather than trying to audit the whole purchasing ledger at once.
For each supply path, distinguish the seller from the manufacturer and any processor you can confirm. A distributor may be a useful commercial alternative; that alone does not answer the upstream-dependency question. Likewise, a small purchase can warrant attention if the part is required to finish a product. Record the operational consequence rather than treating purchasing value as the verdict.
What should go in the shared-dependency worksheet?
Copy this record for each supplier of the component, including an alternative under consideration. Keep the component identifier the same across those records so you can compare the paths. The vertical format lets you add evidence without squeezing it into a wide supplier list.
The last column is deliberately blank. Enter your own information or write Unknown; an empty cell is not evidence of independence.
| Field | What to enter or ask for | Your record |
|---|---|---|
| Critical component | Internal part number, revision and description | |
| Production consequence | Product or operation affected if this part is unavailable; confirm with planning | |
| Direct supplier | Seller’s legal name and the site fulfilling this part | |
| Confirmed upstream source | Manufacturer, material source or processor relevant to the part; distinguish each role | |
| Production location | Actual manufacturing or processing site, where confirmed; do not substitute headquarters | |
| Transport handoffs | Confirmed dispatch point, gateway, warehouse or other node on this route | |
| Shared dependency | Source, site or handoff also named in another record; cite both pieces of evidence | |
| Alternative source | Candidate supplying this exact part and revision, or Unknown | |
| Alternative approval | Applicable internal or customer approval record; outstanding checks | |
| Availability evidence | What the alternative has confirmed about capacity and delivery for your requirement | |
| Unknown information | Exact missing fact, such as processor identity or dispatch gateway | |
| Evidence and date | Document or written confirmation, issuer, scope and confirmation date | |
| Confirmation owner | Person responsible for obtaining or reviewing the evidence | |
| Next question and review date | One specific request, recipient and agreed follow-up date |
Mark a dependency confirmed only when the evidence identifies the relevant component or supply path. If a supplier says it uses several factories but does not identify which makes your part, keep that location unknown. Save the original reply alongside your record rather than turning a broad assurance into a precise fact.
How do you check shared locations and transport routes?
Ask about the actual path for the selected component. Different office addresses do not answer where processing occurs, and a different forwarder does not establish a different gateway.
Use these questions to complete the relevant worksheet cells:
- Which site makes or processes this part, and which site only dispatches it?
- Does a specialist subcontractor perform a required operation? Can the supplier identify that dependency for this part?
- Which warehouse, port or other handoff does the current route use?
- If the named site or handoff becomes unavailable, what alternative has actually been arranged, and what remains to be checked?
Compare the replies at the same level of detail. A named factory on one record and only a country on another leave an unresolved comparison. Record the difference and ask for clarification; do not label the paths separate because their paperwork uses different descriptions.
For the stages a shipment can pass through, see why port and logistics infrastructure matters to smaller exporters. Use it to identify questions for your route, then confirm the route from your own shipment records.
What would a shared-dependency example look like?
Consider a hypothetical mounting bracket bought through a primary seller and an alternative seller. These are roles in an example, not companies or an observed case. At first, you have separate seller details but no upstream processing information. Both upstream cells should say Unknown.
Suppose subsequent component-specific confirmations identify the same heat-treatment processor behind both sellers. Record that processor as a shared dependency and attach both confirmations. The extra seller offers another purchasing contact, but the records now show an upstream point to investigate.
| Point in the example | What the record supports | Next evidence request |
|---|---|---|
| Seller details only | Different commercial contacts; upstream relationship unknown | Ask who performs the required processing for this part |
| Both replies identify the same processor | A confirmed shared processing dependency | Ask whether an approved alternative processing route exists |
| Another route is proposed without approval evidence | A candidate response, with readiness still unresolved | Ask the quality owner what approval is needed and who will complete it |
The conclusion changes when the evidence changes. If the processor information remains unavailable, retain Unknown and assign a follow-up owner. Do not rewrite it as either “independent” or “confirmed shared.”
When can an alternative count as usable?
For this record, describe an alternative as usable only after the responsible people have checked its fit for the exact requirement. A quotation belongs in the file, but it does not by itself establish part approval, available capacity or an executable transport route.
Ask your quality or engineering owner which drawing, material and approval requirements apply. Ask the supplier what it can actually provide for the requirement under review, and ask logistics to confirm the proposed route. Put outstanding checks in the record with an owner. This is an evidence-recording recommendation; it does not replace your industry’s or customer’s qualification process.
Keep cost comparison alongside readiness. Our industrial equipment import-cost worksheet separates quoted, additional and unknown charges for equipment purchases. It answers a cost question; your component record still needs its own dependency and approval evidence.
How should you turn the record into an action?
Choose an action that addresses the dependency you actually found, or obtains the evidence you still lack. The UK Department for Business and Trade’s resilience framework, published in November 2022, places visibility underneath resilience decisions. Its options include alternative supply, stock or surge capacity, and changes in demand or substitutes. Those are options to assess, not automatic prescriptions for every part.
| Finding in your record | Practical next step |
|---|---|
| Upstream source or location unknown | Send a component-specific evidence request and name the person following it up |
| Shared processor confirmed | Investigate an alternative processing path and the approvals it would require |
| Shared transport handoff confirmed | Ask logistics to verify whether a workable alternative handoff exists |
| Alternative proposed but checks incomplete | Record each outstanding approval or availability question before relying on it |
| Dependency cannot currently be changed | Ask planning to assess the production consequence and feasible response; retain the unresolved exposure |
Finish the assessment by naming the next request, its recipient and its owner. Set a review date appropriate to the unresolved question, and revisit the record when the part, supplier site or route changes. The useful output is a traceable decision about a specific component, with uncertainty still visible.
Method, sources and limits
Updated 15 October 2026. This is an editorial worksheet built around public mapping and resilience guidance, not an official NIST or DBT form. Both primary pages were opened and retrieved on that date. NIST supplies the mapping context; DBT supplies the visibility and response context. The blank record, question list and hypothetical bracket sequence are this article’s practical organization of those ideas.
No manufacturer’s supplier data was collected, no alternative part was tested, and no disruption probability or recovery time was calculated. The worksheet does not provide a regulatory opinion, supplier audit or universal safe concentration threshold. Fill it with your own evidence, and leave a cell unknown when that evidence is missing.
