Most procurement teams judge suppliers on quality, cost, delivery and compliance, and ask one broad question: is this supplier performing well? The trouble is that a supplier level scorecard usually reacts after a problem has already reached the business.
A sharper question is whether the supplier is performing to the terms you agreed in each contract. Your team negotiated those terms. This guide explains why supplier performance management should start at the contract, which measures to track, and how software turns signed terms into something you can check every week. It has been refreshed for 2026, when AI can read the terms out of every signed agreement instead of relying on someone to key them in.
Why is a supplier scorecard not enough?
A traditional scorecard asks stakeholders to rate a supplier once a quarter, often from memory. It captures sentiment, but it rarely ties back to the commitments the supplier signed. When a score drops, nobody can say which promise was broken, which contract it sits in, or what remedy the contract allows.
For years the contract lifecycle conversation focused on what happens before signature: authoring, negotiation and execution. That work matters, but the real test of a contract starts when you begin transacting under it. Price caps, service levels, delivery milestones and reporting duties only create value if somebody checks them.
That is why the question should move from supplier performance to contract performance. You are not measuring how a contract was managed. You are measuring whether each term the supplier agreed to is being delivered.
Why track terms per contract rather than per supplier?
Large suppliers rarely hold just one agreement with you. A cloud provider might host a mission critical application under one contract with a very high uptime commitment, and a set of internal tools under another with a lower commitment priced accordingly. Both contracts are with the same supplier, and both are legitimate.
If you only score the supplier, a miss on the critical contract can be hidden by good results on the less critical one, or the reverse. Tracking each commitment against the contract it belongs to keeps the picture honest and shows you where a service credit or a remedy is actually owed. The CIO guide to service level agreements makes the same point: a service level is only useful when it is defined, measured and tied to a consequence.
Which contract measures should you track?
Contract level measures fall into four broad groups. Most agreements contain terms in all four, even when nobody has labeled them.
| Category | What it covers | Examples |
|---|---|---|
| Financial | Money owed in either direction | Price caps, rebates, volume discounts, service credits, payment terms |
| Quality | The standard of what is delivered | Uptime, defect rates, response and resolution times |
| Milestone | Dates and deliverables | Go live dates, delivery schedules, phase sign offs |
| Compliance | Rules the supplier must follow | Insurance certificates, audit rights, data protection, regulatory reporting |
Write each measure in plain terms with a clear threshold and a named owner on your side. A measure without an owner will not be checked, however carefully it was negotiated.
How do contract scores roll up to the supplier?
Once you collect performance at the contract level, supplier performance becomes an aggregation of contract performance rather than a separate exercise. The supplier view answers strategic questions: should we renew, consolidate, expand or exit? The contract view answers operational ones: is a credit owed this month, is a certificate about to lapse, has a milestone slipped?
- Extract the commitments from every active contract with the supplier
- Assign each commitment an owner, a check date and the evidence you expect
- Record the result of each check against the contract
- Aggregate results by supplier, category and business criticality
- Use the supplier view in quarterly reviews and renewal decisions
This structure also makes supplier conversations more productive. Instead of telling a supplier that stakeholders feel service has slipped, you can point to the specific term, the dates it was missed and the remedy the contract provides.
How does software make contract performance practical?
The idea of contract level measurement is not new. What held it back was effort: someone had to read every agreement, list the terms and set reminders by hand. That work is now largely automated.
Extraction from signed contracts
Aavenir AI in Aavenir, reads executed contracts and lists the commitments by category, with dates and thresholds. A contract manager reviews and approves the list before anything is assigned, so a person stays in control of what counts as an obligation.
Owners, reminders and evidence
In Obligationflow, each approved commitment goes to an owner with a due date. Owners attach evidence, such as a monthly service report or an insurance certificate, and Avy compares it to the clause and flags gaps for a person to resolve.
Better terms in the next contract
Performance history feeds back into authoring. When a team drafts the next agreement in Contractflow, it can see which service levels and remedies held up in practice and which were never enforced. On ServiceNow, all of this runs inside the instance your teams already use.
Where should a team start?
Pick your most critical suppliers, usually the ones whose failure would stop a service or create regulatory exposure. Extract the commitments from their active contracts, agree on owners and run one quarter of contract level checks. Then compare what you learned with the scorecard you used before. Most teams find commitments they had forgotten, and a few credits they were owed. Read more about contract obligation tracking and service credit recovery.
The bottom line
Supplier performance management is only as good as its link to the contract. Measure each agreed term where it lives, roll the results up to the supplier, and your reviews, renewals and negotiations will rest on what was promised rather than on opinion.