Supplier Scorecard & Monthly Review Agenda

Purpose

This template helps procurement, operations, and quality teams run reproducible, constructive supplier reviews that move beyond numeric reporting into joint problem-solving and sustained improvements. Use the scorecard to measure reliability, quality, lead times, and responsiveness; use the agenda to keep meetings focused and timeboxed; use the tracker to make improvements owned and visible.

How to use this template

1. Set the measurement period (calendar month, rolling 3 months, or MTD).
2. Connect each metric to a single authoritative data source (ERP, shipping logs, incoming inspection records, supplier portal).
3. Populate the scorecard before the meeting and share it with supplier reps 48 hours in advance.
4. Run the monthly review using the agenda and update the joint improvement tracker in the meeting. Assign owners and due dates.
5. Escalate only when triggers in the escalation ladder are met. Prefer joint corrective actions before penalties.

Scorecard metrics (recommended)

Include 4–6 focused KPIs. Keep the scorecard compact so the conversation is about root cause and action, not data translation.

Standardized data sources & calculation rules

• Designate one system as the authoritative source for each metric (ERP shipments for OTD, incoming inspection records for quality escapes, supplier-confirmed lead time logs for lead time).
• Use consistent time windows (e.g., month, rolling 3-month average) and state which is shown on the scorecard.
• Document rounding, handling of partial shipments, and rules for cancellations or expedited orders.
• When manual data is used, include a data owner responsible for validation before the meeting.

Monthly review agenda (60 minutes — adapt as needed)

Keep the meeting tight, constructive, and focused on the few things that matter.

1. Welcome & goals (5 min) — Facilitator states the meeting goal: joint improvement and risk mitigation.
2. Scorecard headlines (10 min) — Review top-level RAG status and any metrics that moved to Red since last review.
3. Top 1–2 issues deep dive (20 min) — Each deep dive follows a mini-structure: describe the issue, show the data/trend, propose root causes, confirm countermeasures. Use 5 Whys or quick cause mapping.
4. Improvement tracker updates (12 min) — Review open actions, status, owners, due dates, and measured impact.
5. New actions & commitments (8 min) — Agree on new actions, owners, due dates, expected outcomes, and follow-up dates.
6. Escalation & contingency check (5 min) — Review triggers; confirm if escalation is required or contingency activated.

Recommended meeting roles

• Facilitator: neutral meeting lead (procurement or operations lead).
• Supplier representative: accountable contact with decision authority.
• Scribe: records actions in the joint improvement tracker.
• Technical/Quality SME: explains inspection or defect data when needed.
• Escalation owner: named person to notify when triggers are met.

Joint improvement tracker (use this table in the meeting)

Keep the tracker as the single source of truth for actions. Update it in the meeting and circulate the updated version within 24 hours.

Escalation ladder & contingency triggers

Escalation should be clear, predictable, and focused on restoring performance and business continuity rather than immediate punishment.

Common escalation triggers

• Any Red metric for two consecutive months.
• Critical quality escape (customer-impacting defect) requiring a recall or stop-ship.
• Lead time variance exceeding 50% for a critical SKU.
• Failure to meet agreed immediate containment actions within the committed window.

Example escalation path

1. Operational discussion and joint containment (current monthly review).
2. Procurement manager intervention: formal joint corrective action plan (JCAP) with root-cause analysis required within 10 business days.
3. Supply chain director: review and evaluate alternative suppliers, inventory contingency, and financial implications.
4. VP Operations / Commercial: decide on contract remedies, strategic supplier actions, or transition plans if improvement is insufficient.

Facilitation & language tips to avoid blame

• Start with facts and patterns: show the data and trend lines.
• Ask "what happened?" and "what process allowed this to happen?" instead of "who made the mistake?"
• Prefer joint problem statements and shared ownership of actions when internal processes (forecasting, quality checks) play a role.
• Celebrate improvements to keep supplier engagement high — call out where the supplier has reduced defects or improved delivery.

Quick start checklist

• Confirm metric definitions and data owners.
• Automate data pulls where possible (ERP, inspection system).
• Share the populated scorecard 48 hours before the meeting.
• Use the agenda timeboxes; keep deep dives to top 1–2 issues.
• Record actions in the joint tracker and circulate within 24 hours.

Common pitfalls & how to avoid them

• Pitfall: Scorecards that punish individuals. Fix: Focus on systems and processes; link corrective actions to process changes.
• Pitfall: Meetings that become status dumps. Fix: Limit metrics and deep-dive only the highest-impact issues.
• Pitfall: Missing data lineage. Fix: Document authoritative sources and calculation rules.
• Pitfall: Overuse of penalties instead of remediation. Fix: Use escalation for unresolved risks; prefer joint corrective actions first.

Customization suggestions

• Adjust metrics and thresholds by supplier criticality and product risk.
• For strategic suppliers, add collaborative improvement KPIs such as cost-reduction plans or lead time reduction projects.
• For high-volume transactional suppliers, automate scorecards and use weekly mini-reviews for urgent items.

Export & automation tips

Copy this template to your platform (Excel, Sheets, or THE interactive form). Where possible, automate the KPI pulls and flag RAG status automatically so meeting time is spent on analysis and action.

End of template — recommended next step: Copy this content into your team's supplier review workspace, map each metric to the authoritative data source, and run the first facilitated review using the agenda.