AI Prompts for Supplier Scorecards and SLAs

A supplier scorecard is a measurement system, and it inherits every weakness of one: metrics without definitions get gamed, thresholds without consequences get ignored, and reviews without preparation become relationship chats. The scorecard, the SLA it is anchored to and the review cadence need to be designed together.

These prompts do that in sequence — KPI design with precise definitions and data sources, SLA clauses that reference those definitions so measurement and contract agree, and a quarterly business review built from the data. The SLA prompt drafts commercial language for legal review; it does not replace it.

Before you use these

Have these ready to replace the highlighted [variables]:

• What the supplier delivers and what 'good' looks like for each aspect
• Data you can actually capture (receipts, inspections, invoices, tickets) and where it lives
• Existing contract performance clauses
• Review cadence and who attends

The prompts

• 1. Design the scorecard KPIs and thresholds
• 2. Draft SLA and performance clauses
• 3. Build the quarterly business review from scorecard data

1. Design the scorecard KPIs and thresholds

Act as a supplier performance manager designing a scorecard for [supplier / category].

Scope: [products or services supplied, volume, criticality]
Data available: [e.g. PO and receipt dates, inspection results, invoice accuracy, ticket logs, response times]
History: [known performance problems]
Review cadence: [monthly/quarterly]

1. Select 6–10 KPIs across delivery (e.g. on-time-in-full), quality (e.g. defects per million, first-pass yield, complaints), responsiveness (lead time adherence, issue resolution time), commercial (invoice accuracy, price compliance), and relationship/improvement (corrective action closure, innovation contributions). Justify each against the scope and history.
2. For each KPI: exact formula, numerator and denominator definitions (e.g. what counts as 'on time' — requested date or confirmed date, with what tolerance), data source, owner, frequency, target, and thresholds for green/amber/red.
3. Weight the KPIs into an overall rating with bands and the consequence attached to each band.
4. For each KPI, note how it could be gamed or misread and the control (e.g. supplier-confirmed dates drifting later).
5. Propose the scorecard layout as a one-page table.

Do not include a KPI without a data source we already have or can create within a month. Keep the total under ten.

2. Draft SLA and performance clauses

You are drafting the performance schedule of a supply agreement with [supplier]. This is a working draft for legal review, not final contract language.

KPIs and definitions: [from scorecard]
Commercial context: [contract value, term, our leverage, supplier's likely objections]
Remedy approach: [service credits / rebates / cure periods / termination rights — what we want]

Draft:
1. Definitions clause: each KPI defined exactly as measured, including data source and measurement period.
2. Service levels: target and minimum acceptable level per KPI, and the measurement and reporting obligation on the supplier.
3. Remedies: a graduated structure — cure period for first breach, service credit or price adjustment for repeated breach, step-in or alternative sourcing rights, termination for persistent failure. Make the remedy proportionate to the KPI's importance.
4. Root cause and corrective action obligation with timelines.
5. Governance: review meetings, attendees, escalation ladder with named roles and response times.
6. Change mechanism: how service levels are revised when scope or volumes change.

Flag clauses that will be contentious and offer a fallback position. Note where the remedy depends on being able to prove the measurement — and whether our data can.

3. Build the quarterly business review from scorecard data

Act as a supplier relationship manager preparing a quarterly business review with [supplier].

Scorecard results: [KPI, target, this quarter, last two quarters]
Open issues: [list with status]
Our forward needs: [volume changes, new products, cost pressure, risk concerns]
What the supplier has raised with us: [payment, forecast accuracy, specification changes]

Produce:
1. Performance summary: rating, trend per KPI, the two KPIs that moved most and why (from the data given — do not speculate beyond it).
2. Issue analysis: for each amber/red KPI, the pattern (isolated, recurring, worsening), the likely cause category (their process, our inputs, joint), and the corrective action to propose.
3. Our-side accountability: where our forecasts, specifications, payment or communication contributed. Be honest — this is what makes the review credible.
4. Forward look: changes coming and what we need from the supplier to prepare.
5. Agreed-actions table format: action, owner (their side / our side), due date, KPI it should move.
6. A 60-minute agenda with time per section and the decisions to reach.

Tone: firm on facts, collaborative on solutions. Avoid presenting the QBR as a list of complaints.

Related prompts

• Supplier Evaluation
• Supplier Risk Assessment
• Supplier Negotiation
• Service Level Analysis
• Operational KPI Reviews
• Root Cause Analysis
• Contract risk summary — Legal

Logical next step

After this, most operations teams move on to Supplier Evaluation.

All Operations & Supply Chain prompts · Search the full library