11.2 Reviewing Performance Against SLAs (Task 1-E-8)

Service level agreements (SLAs) translate negotiated expectations into measurable commitments—on-time delivery percentages, response times, uptime, defect rates, fill rates, or resolution times—usually with defined remedies when targets are missed. Task 1-E-8 on ISM CPSM Exam 1 asks you to review supplier performance against negotiated SLAs. Within Domain 1-E, this task is scored at roughly four exam questions, so candidates must handle measurement mechanics, credits, disputes, and improvement—not just “check the green dashboard.”

SLA Versus KPI: Do Not Conflate Them

A KPI (key performance indicator) is any metric the organization uses to monitor performance. An SLA is a subset of commitments that are contractually binding (or formally incorporated into the agreement) with targets, measurement methods, and consequences. A supplier scorecard may include KPIs such as innovation submissions, sustainability scores, or relationship health. Those KPIs matter for SRM—but missing an innovation KPI is not automatically an SLA breach unless the contract says so.

When reviewing performance, first ask: Is this metric an SLA, a KPI, or a stretch goal? Applying SLA remedies to non-SLA KPIs creates disputes and erodes trust. Ignoring true SLA misses because “the overall relationship feels good” creates operational and legal risk.

Anatomy of an Enforceable SLA Measure

A review-ready SLA definition usually specifies:

• Metric definition — exact formula (for example, on-time = receipts by promise date ÷ total receipts in window)
• Data source of record — ERP receipts, ticket system timestamps, carrier EDI, or joint portal
• Measurement window — calendar month, rolling 90 days, per shipment, per incident
• Exclusions — buyer-caused delay, force majeure, approved change orders, forecast volatility beyond agreed bands
• Reporting cadence — who calculates, who validates, when published
• Remedies — service credits, re-performance, cure periods, escalation ladder

Ambiguous SLAs produce “we hit 97%” versus “you hit 91%” arguments that waste governance time. Supply professionals strengthen reviews by insisting definitions are unambiguous before performance periods start—and by documenting any mid-period definition changes in writing.

Measurement Windows and Aggregation

Measurement windows change outcomes. A supplier may miss five days badly yet still meet a monthly average; conversely, a strong month can mask a catastrophic week that stopped a production line. Reviews should examine both the contractual window (what triggers credits) and operational granularity (what protects the business). Some contracts use tiered windows: incident-level for critical failures, monthly for credits, quarterly for executive reviews.

Aggregation rules matter equally. Does a late partial shipment count as late for the whole order? Are early shipments scored the same as late? Are cancelled lines removed from the denominator? These details are not pedantry—they are the difference between a fair credit claim and an unenforceable one.

Example: A 3PL SLA promises 99% on-time delivery measured monthly by delivery scan versus customer appointment. The buyer’s plant tracks “dock arrival by start of shift.” Without aligning the data source of record, monthly reviews become debates about clocks rather than performance. The fix is a joint definition workshop and a single system of record for SLA calculation.

Service Credits and Remedies

Service credits are contractual reductions or rebates when SLA targets are missed, often expressed as a percentage of fees for the period or a fixed amount per incident. Credits are not free money and not unlimited: contracts typically cap credits per period, require timely claim notices, and may treat credits as the exclusive remedy for the covered miss (or as one remedy among several).

Professional review practice:

1. Calculate attainment using the contract formula and source of record
2. Apply agreed exclusions before declaring a miss
3. Compute credits per the schedule; document the claim within the notice window
4. Route through AP/finance so credits appear as credit memos or invoice adjustments—not informal “price breaks”
5. Escalate chronic misses through the cure and termination ladder even when credits are paid

Paying or accepting credits does not automatically waive termination rights unless the contract says so. Conversely, chasing credits while ignoring root cause is poor SRM: credits compensate; they do not by themselves restore capability.

Disputing Metrics

Metric disputes arise when parties disagree on data, exclusions, timestamps, or formula application. A sound dispute process includes:

• Freeze the period’s raw data extract
• Recalculate with both parties present or via independent audit
• Apply only documented exclusions
• Escalate unresolved items to the contract governance forum within defined days
• Record the resolution and update the measurement playbook if ambiguity caused the fight

Do not “split the difference” on a credit as a habit—that trains both sides to negotiate every month. Split only when ambiguity in the definition is real, then fix the definition going forward.

Continuous Improvement Linkage

SLA review is incomplete if it ends at green/yellow/red. Continuous improvement uses trends to drive corrective action plans (CAPs), process changes, capacity investments, or renegotiation of unrealistic targets. If an SLA is chronically missed despite CAP effort, the relationship may need exit planning (Task 1-E-7) or contract redesign. If an SLA is always crushed with huge margin, the target may be too soft to protect the business—or the supplier may deserve volume growth and preferred status.

Business reviews should separate: (1) contractual SLA attainment and credits, (2) broader KPI dialogue, and (3) forward improvement commitments with owners and dates. That separation keeps legal remedies clean while still enabling collaborative development.

Exam Lens

Expect questions that test whether you enforce SLAs as written, distinguish them from soft KPIs, respect measurement windows and exclusions, process credits through formal channels, and escalate recurring failure. The best answers are process-disciplined and continuity-minded—not punitive for its own sake, and not casually forgiving of contractual misses.