A contract scorecard is a structured, regular review of how a single agreement is performing against its commitments, using a short set of measures, each with a target, a result, supporting evidence and a next action. It answers a simple question: is this contract delivering what was agreed, and what should we do about it?
Why contract scorecards matter
After signature, performance information is scattered. Operations sees service levels, finance sees invoices, procurement sees renewal dates. A scorecard brings them into one view so problems are spotted, raised with the supplier and fixed, and so renewal decisions rest on evidence rather than impressions.
It also connects performance to contract rights. A missed service level may earn a credit; an overbilled invoice may be recoverable. A scorecard that stops at a rating misses both.
Three to seven measures tied to what the contract actually requires.
Target
The contractual requirement, or a clearly labelled internal goal.
Result and evidence
The verified result, with the report, invoice or record behind it.
Score or status
A rating on an agreed scale, such as 1 to 5 or red, amber, green.
Action and owner
What happens next, who does it and by when, including any credit or recovery.
Keep contractual targets separate from internal goals. Missing an internal goal is a conversation; missing a contractual one may trigger a remedy.
How contract scorecards are scored
Most scorecards use either a red, amber, green (RAG) status or a numeric scale. Numeric scorecards often weight each measure by importance:
Weighted score = sum of (weight × score), with weights adding up to 100%
Whatever method you choose, define the thresholds in advance. Scottish public sector guidance from Procurement Journey, for example, illustrates RAG thresholds of green at 97% on-time delivery, amber at 92% and red below 92%.
Contract scorecard example
An illustrative software services agreement costs $20,000 a month. Its quarterly scorecard uses a 1 to 5 scale (5 exceeded, 4 met, 3 minor miss, 2 major miss, 1 failed) and five weighted measures:
Service availability (30%): 99.70% in one month against 99.9%. Score 3.
Report timeliness (20%): two of three monthly reports on time. Score 3.
Obligations met (15%) and responsiveness (10%): both met. Score 4 each.
The weighted score is 0.90 + 0.60 + 0.50 + 0.60 + 0.40 = 3.0 out of 5, which looks satisfactory. But the detail shows $5,600 owed to the buyer: a $2,000 service credit (10% of one month’s fee under the SLA) and $3,600 of overbilling to recover, plus a corrective plan for late reports.
Convention used: 1 to 5 scores, weights summing to 100%, and a weighted average. Agree the method with the supplier before the review period starts.
An illustrative weighted scorecard, and the money behind an average score.
Contract scorecards in federal contracting
U.S. federal agencies formalize contractor evaluations. Under FAR 42.1503, performance assessments cover factors including technical quality, cost control, schedule, management and small business subcontracting, each rated “exceptional, very good, satisfactory, marginal” or “unsatisfactory” with a supporting narrative. The narrative requirement is a useful model: a score without evidence is hard to act on.
Contract scorecard vs. related terms
Term
How it differs
Supplier or vendor scorecard
Rates a supplier across all its contracts and relationship factors. A contract scorecard covers one agreement.
Service-level agreement (SLA)
Sets the service targets and remedies. The scorecard reports performance against them and others.
Key performance indicator (KPI)
A single measure. A scorecard combines several KPIs with targets and actions.
Contract performance report
A broader narrative report; a scorecard is a compact, repeatable summary.
Common mistakes
Too many measures. A dozen measures dilute attention; keep the ones the contract and business care about.
Averages that hide problems. Always read the measures behind the score.
No evidence. Ratings without reports or records are hard to defend with a supplier.
No follow-through. Credits unclaimed and actions unowned make the scorecard a formality.
How teams use contract scorecards
Procurement: runs supplier reviews and builds the case for renewal or exit.
Operations: supplies service and delivery results.
Finance: checks invoices and confirms credits and recoveries.
Legal and compliance: confirm obligations, certificates and remedy rights.
Frequently asked questions
How often should a contract scorecard be reviewed?
Monthly or quarterly for important contracts, with a final review well before the renewal notice deadline.
Who should own the contract scorecard?
Usually the contract or supplier relationship owner, with inputs from operations, finance and legal.
Should the supplier see the scorecard?
Usually yes. Shared measures and evidence make review meetings productive and corrective actions easier to agree.
What is the difference between a contract scorecard and a vendor scorecard?
A contract scorecard covers one agreement; a vendor scorecard rates the supplier across all its contracts.
Where ObligaAI fits
ObligaAI describes its platform as helping teams search key terms across contracts, track obligations and key dates, and spot missed value and recovery opportunities.