Zurück zur Bibliothek

Supplier performance scorecard

Calculates a supplier scorecard from orders, deliveries, quality cases, prices, and service records, then explains period changes and proposes improvement actions. Use for quarterly supplier reviews, vendor performance management, procurement negotiations, and supplier escalation.

von adlass TemplatesVersion 1Nutzt adlass-ToolsUniversell

Veröffentlicht 21. Aug. 2026 · Aktualisiert 26. Aug. 2026

Hilfreich · 0Rohes SKILL.md ansehen

Voraussetzungen

Map operational fields and add metric definitions, weights, targets, and exclusions. Define score bands, cadence, and improvement ownership. Set like-for-like period comparison rules.

Skill-Dokument

Das vollständige SKILL.md, das dein Agent liest und befolgt.

Supplier performance scorecard

Purpose

Measure supplier performance on a common basis and turn the result into evidence-backed review priorities. Preserve the difference between a calculated metric, a target, and a recommendation.

Scope

Purchase orders, promised and actual delivery, quantities, inspection or complaint records, prices, service cases, criteria, weights, and prior scorecards. Excluded: changing supplier ratings in a system, negotiating, or terminating a supplier.

Data basis

  • Order, delivery, receipt, and quality tables.
  • Price agreements, service cases, and response records.
  • Scorecard criteria, weights, targets, and prior period.

Result

A scorecard sheet, review agenda, and improvement-request document with calculations and citations.

Quality criteria

  • Denominators and exclusion rules are visible for every metric.
  • Weighted score reconciles to component scores.
  • Period comparison uses like-for-like definitions.
  • Every recommendation links to a finding.

Instructions

Do not count missing delivery dates as on-time. Separate supplier-caused and internally caused exceptions when evidence permits. Use supplied weights and targets; if missing, report metrics without inventing a grade. Preserve order and case identifiers for traceability.

The review should make the population, calculation basis, and exception treatment understandable to a second operator. Preserve source identifiers in every working table, and state the effect of missing evidence on the decision. A reviewer must be able to reproduce each material result from the cited rows, clauses, dates, or policy rules. Where two sources disagree, show both values and explain which source was treated as authoritative.

Use the outputs as review workpapers: retain the source locator beside every material value, and keep planned action separate from completed evidence. The final document must identify the consequence of each gap for the relevant operational or control decision.

Adapt before use

  • Map order, delivery, receipt, quality, price, and service fields.
  • Add metric definitions, weights, targets, and exclusion rules.
  • Define score bands, review cadence, and improvement-owner conventions.

Verwandte Skills

  • 8D problem-solving report

    Builds a traceable 8D problem-solving report from a manufacturing complaint, defect record, and process evidence. Use for customer complaints, recurring production defects, containment records, corrective action reports, and structured root-cause investigations.

  • Capacity resource plan

    Converts demand forecasts, staffing calendars, work hours, absences, and throughput assumptions into a capacity plan with bottleneck dates and quantified staffing options. Use for workforce capacity planning, resource allocation, utilization review, and delivery-load analysis.

  • Construction punch list

    Converts inspection notes, photos, room data, and project requirements into a prioritized construction punch list with trade grouping and verification fields. Use for substantial completion, handover inspections, snagging, closeout walks, and defect follow-up.

  • Construction RFI draft

    Converts a construction field question or document conflict into a precise request for information with evidence, options, and schedule or cost implications. Use for RFIs, design clarifications, plan conflicts, specification gaps, and field coordination questions.