Supplier performance dashboard: layout and checks

A supplier performance dashboard puts delivery, quality, lead time, and spend beside the same supplier and site so the next action is clear. Build it from purchase schedules, receipts, inspection results, and invoices, with a visible denominator and baseline for every rate. A chart is useful only after its totals agree with those files.

Start with the decision and the reporting period

The first screen should answer: which supplier needs a review, at which site, and on what evidence? Separate that job from ranking suppliers for a sourcing award. The supplier KPI framework defines the measures; the dashboard arranges them for a recurring conversation.

Choose one reporting period and a cutoff date. Delivery belongs to schedules due during that period, including schedules still open after their due dates. Quality belongs to the declared inspection cohort. Lead time belongs to completed receipts, with open orders shown separately. Invoice spend belongs to the posting period. Label these differences rather than implying every measure covers identical transactions.

Keep the supplier ID and site as filters. A supplier's performance at one receiving location may say little about another location with different materials, routes, or receiving procedures.

Prepare the exports without duplicating spend

Use a schedule identifier, not just the purchase order number. One purchase order can contain several lines and promised delivery dates. Combine partial receipts against their original schedule before testing whether the full quantity arrived on time.

The working files need these fields:

Summarize the files separately before putting their measures alongside each other. Joining every receipt to every invoice can repeat both quantities and dollars. The small example below uses an already reconciled allocation with one invoice amount per schedule; that assumption should never be silently applied to a real export.

Lay out the dashboard around evidence

Use a compact comparison table as the main view. Keep the same supplier order across trend charts so readers can find the same business quickly.

Avoid a shared axis for dollars, days, and percentages. A broader performance dashboard can show company objectives, while this screen stays focused on supplier evidence. Do not turn the design exercise into a complicated composite scoring system.

Work a supplier comparison from the rows

An Ohio distributor reviews its September due schedules. Every schedule has now completed, and every unit has been inspected. Received-by-due units are the units physically received on or before the original promised date, before later inspection disposition. This delivery test is separate from the quality rejection rate. Lead days are calendar days from purchase release to completed receipt.

Use columns A through I in this order, with headers in row 1 and records in rows 2 through 7:

The OTIF flag in I2 is =--(D2>=C2), filled down. Require positive due quantities and complete receipt checks before applying it. Missing evidence is an exception to resolve, not proof that delivery succeeded. The full supplier and site OTIF method covers the delivery definition in more detail.

Round OTIF to one decimal place, rejection rates to two, and mean lead time to one. Keep unrounded values for calculations. The same mean lead time does not mean the suppliers have identical consistency; the lead-time variability method examines that separate question.

Use formulas that retain the denominators

Put the supplier being summarized in K2. These Excel formulas work on the displayed rows:

OTIF: =SUMIFS($I$2:$I$7,$A$2:$A$7,K2)/COUNTIFS($A$2:$A$7,K2)
Rejection rate: =SUMIFS($F$2:$F$7,$A$2:$A$7,K2)/SUMIFS($E$2:$E$7,$A$2:$A$7,K2)
Mean lead days: =SUMIFS($G$2:$G$7,$A$2:$A$7,K2)/COUNTIFS($A$2:$A$7,K2)
Spend: =SUMIFS($H$2:$H$7,$A$2:$A$7,K2)

Microsoft documents SUMIFS for summing values that meet specified criteria and COUNTIFS for counting records that meet the criteria. Add the same site and period criteria to both numerator and denominator in a larger workbook. The lead-time formula assumes every displayed row has a completed lead time; use a completed-observation count when some are open. Covirage is not affiliated with Microsoft.

Add the baseline and prove the totals

The prior-period records summarized below use the same site and definitions:

Summit's OTIF fell from 100.0% to 66.7%, a decline of 33.3 percentage points. Rejection rose from 1.00% to 1.50%, while mean lead time increased from 9.0 to 10.0 days. Harbor improved OTIF from 66.7% to 100.0%; its other displayed service measures were unchanged. These small counts support a follow-up conversation, not a confident general claim about future performance.

Check the dashboard against its inputs: supplier spend totals $8,800, due schedules total six, inspected units total 800, and rejected units total ten. Company rates divide these summed counts. Preserve an exception list for anything excluded. For a deeper investigation after a flag appears, use the supplier deterioration worked example.

Where it goes wrong

• Counting only receipts. Late open schedules disappear, making delivery look better.
• Changing the promise date. Replacing the original commitment can erase lateness.
• Repeating invoice dollars. Receipt joins can inflate purchasing exposure.
• Treating no inspection as perfect quality. Missing inspection evidence is not a zero rejection rate.
• Comparing partial periods. A new month with little completed work can look artificially strong or weak.

Build the comparison on your own file in Covirage

Bring a sample of your own purchase schedules, receipt, inspection, and invoice exports; Covirage maps the columns, and its tools compute and check the supplier measures. The external AI model explains the comparisons with every figure traced to its rows. Create a free Covirage account, which takes about a minute, and set up your business with your own data.

See Covirage for procurement teams for the purchasing context.