Use vendor lead time variance to find the suppliers driving schedule slippage

For procurement teams, a long vendor list can make every delay look equally urgent. A supplier-level ranking gives a more useful first view: which vendors account for the largest share of accumulated late days? That is a practical way to focus a supply chain delay analysis before a performance review, escalation or corrective-action plan.

There is a distinction worth keeping clear. Lead time variance can describe how delivery dates differ from plan, including both early and late arrivals. A Pareto ranking of delay totals answers a narrower question: where did the most schedule slippage accumulate? It can identify concentration. It cannot tell you what caused it.

Choose a delay measure before ranking suppliers

Start with shipment-level records that include a supplier, a promised delivery date and an actual delivery date. Calculate the difference consistently. For a schedule-slippage review, one workable measure is late days per shipment: actual date minus promised date, with early or on-time deliveries recorded as zero late days. Sum those late days by supplier.

That choice intentionally excludes early deliveries from the delay total. If early arrivals matter—for example, because they create receiving or storage costs—track them as a separate measure. Netting early and late deliveries together can make a supplier with substantial schedule disruption appear close to plan.

Decide, too, whether each shipment should count equally. If a two-day delay on a critical component is more consequential than a two-day delay on a routine item, a simple late-day total will not capture that difference. You can create a separate weighted measure if your team has a defensible weighting rule. Keep the unweighted view available so reviewers can see what the calculation represents.

Build a supplier-level Pareto view

1. Prepare the shipment log. Check that promised and actual dates use the same conventions, and settle how to handle missing dates, partial deliveries and cancellations. Do not silently treat missing records as zero-delay shipments.
2. Calculate late days. Apply the chosen rule to each shipment. If you want to compare suppliers by total slippage, add the late days for all included shipments from each supplier.
3. Aggregate by supplier. Create one row per supplier with its total late days. This avoids confusing a shipment-level list with a supplier-level comparison and makes the unit of analysis explicit.
4. Paste or upload the summary. ParetoScope accepts spreadsheet paste, CSV upload or manual input. Provide supplier names alongside the delay totals, then review the resulting ranking and cumulative percentages.
5. Read the concentration, not just the first row. Note the suppliers with the largest totals, how much of all late days they represent, and where the cumulative share begins to flatten. The vital-few cutoff is a clue for prioritization, not a universal threshold that procurement must adopt.

A free ParetoScope calculation runs locally in the browser and does not require an account. Its calculations include ranking, cumulative percentages, concentration and a vital-few cutoff. The output can help structure the review, but it does not validate the source dates or establish whether a supplier caused a delay.

Turn the ranking into a review agenda

Use the highest-impact suppliers as a starting point for investigation. Compare their late-day totals with shipment counts: a supplier with many shipments may accumulate more late days simply because it handles more volume. A useful review may also compare the share of shipments late, median lateness, and the distribution of delays. Those measures answer different questions, so avoid treating one Pareto chart as a complete vendor scorecard.

Bring the underlying records into the conversation. Ask whether delays cluster around a product, route, season, order size or change in forecast. Check for repeated partial deliveries and for differences between promised dates and the dates your organization actually uses for planning. The ranking tells you where to look first; the shipment history and operational context are needed to explain the pattern.

This is the same basic discipline used in other operational triage: rank a consistent measure, then investigate the largest contributors before assigning work. ParetoScope’s earlier warehouse picking-delay analysis makes a related point about choosing impact totals rather than relying on event counts. Supplier delay totals need the same care: a count of late shipments is not equivalent to total days lost.

Keep supplier defect tracking separate

Late delivery and supplier defects can both warrant corrective action, but they are different measures. Combining defect counts with late days into one ranking obscures what the score means. Run supplier defect tracking as its own analysis, with a defined defect measure and consistent denominator where rates are being compared. Then review whether the same suppliers appear in both views.

The useful result is not a declaration that a small group of vendors is responsible for every supply problem. It is a shortlist grounded in the selected metric, plus a clear next question for each supplier. A procurement Pareto can make that first prioritization step faster; schedule decisions still depend on validating the records and understanding the causes behind them.