Vendor performance management: scorecards, reviews, and records

Reference article · 5 min read

Most of what a technology contract delivers is decided after award. An evaluation team scores proposals once, then the agency lives with the vendor for years: through releases, outages, turnover on both sides, change orders, and renewals. Vendor performance management is watching that period deliberately rather than by complaint, so problems surface while there is still time and leverage to correct them.

A workable program is smaller than most agencies expect. A short scorecard tied to contract language, a standing review with an agenda and minutes, and a file a future evaluation team can read will outperform a framework nobody maintains.

Build the scorecard from contract obligations

Every measure should trace back to something the vendor agreed to do. If a measure cannot be tied to a service level, a deliverable, a staffing commitment, or a warranty term, it is either a preference rather than an obligation or a sign the contract is missing a clause.

• Cite the source. Each measure names the contract section it comes from, so a score applies the agreement rather than an opinion.
• Name the data source. The ticketing system, the project schedule, invoices, or the vendor's monitoring. Decide in advance whose numbers count and whether the agency can verify them.
• Name the scorer. One accountable person, usually the contract administrator, gathering input from named reviewers rather than from whoever complained most recently.
• Fix the scale first. A short rating scale with a written description of each level keeps scores comparable across quarters and across scorers.

Keep the measure set small

Five to eight measures is usually enough, and fewer is better than a list that goes unscored. Most technology contracts are covered by a handful of categories: availability and incident response against the agreed service levels, delivery against schedule and acceptance criteria, quality of work such as defect and rework rates, staffing continuity including key personnel, accuracy of invoices and reports, and security obligations including timely notification and patching.

Weight the measures if some matter more, but resist elaborate arithmetic. The score exists to force a conversation and leave a record, not to produce a precise number. Write a short narrative beside each score describing what happened, because the narrative is what a later reader will use.

Run the review as a meeting of record

Set a standing cadence in the contract, commonly quarterly in steady state and monthly during implementation. Send the scorecard and agenda in advance so the meeting discusses known material rather than a first reading.

A durable agenda is short: performance since the last review, measure by measure; open action items; risks and upcoming milestones; administration items such as amendments, invoices, and key personnel changes; and anything either party wants to escalate. Ask the vendor for a brief self assessment in the same format. Differences between the two views are the most informative part of the meeting.

Keep minutes: attendance, the scores, the vendor's response, decisions, and each action item with an owner and a due date. Send them to the vendor, invite written corrections within a set period, and file the final version in the contract record. Minutes like these turn recollection into a documented pattern.

Escalate in steps, before it becomes a legal matter

Most performance problems are recoverable if raised early and in writing. Build a ladder and follow it in order rather than moving from patience to a termination letter.

1. The scorecard note and action item in the minutes.
2. A written request for a corrective action plan with dates and named owners.
3. Escalation to vendor management above the account team.
4. Formal notice under the contract's notice and cure provisions.
5. Contract remedies such as withholding, service credits, or termination rights.

Involve counsel and your procurement office before the fourth step, and earlier if you are considering withholding payment. Notice and cure requirements, the availability of liquidated damages, and the remedies a state procurement code imposes or limits vary by jurisdiction and contract, so confirm the sequence with counsel. Suspension and debarment are separate processes with their own due process requirements, not substitutes for contract administration.

Write past performance so it can be cited later

Performance information is worth collecting only if a future solicitation can use it. Federal agencies record past performance in a government wide system and consider it in source selection. State and local practice varies: some jurisdictions allow past performance as an evaluation factor or a responsibility consideration, some constrain its use, and some are silent. Confirm what your code and policy allow before telling a vendor that scores will travel.

However the information is used, write it so it survives scrutiny:

• Factual and specific. Describe what was required, what was delivered, and when. Avoid adjectives that cannot be traced to evidence.
• Contemporaneous. Score each period at the time rather than reconstructing it at closeout.
• Fair on its face. Give the vendor notice of the assessment and a chance to respond, and file the response beside it.
• Written for disclosure. Assume public records law may make the file disclosable and that the vendor will read it.

Starting on a contract already underway

Read the contract and list the obligations measurable today. Draft the scorecard and agenda, send both with the first meeting invitation, and score the first period as a baseline. At the next amendment or renewal, add what was missing: a defined review cadence, a vendor obligation to participate and report specified data, key personnel provisions with substitution approval, a notice and cure sequence, and language allowing the agency to use documented performance in later procurements to the extent its law permits.

HQT works with state and local agencies on technology delivery and contract administration, including performance measures and review structures.

Frequently asked questions