MSP supplier scorecards and tier reviews: the KPIs, release windows, probation and how to dispute your score

An MSP scores each staffing supplier on speed, quality and compliance, typically response rate, time to first submittal, submittal-to-interview and interview-to-hire ratios, fill rate and early turnover, plus hiring-manager feedback, and uses the score to decide tiers (who sees requisitions first) and who stays in the program. As of October 2026, Tennessee's draft MSP contract requires a sub-vendor scorecard with requests-to-submittal, interview-to-submittal and hire-to-interview ratios, reviewed at least semi-annually (Tennessee pro forma contract, RFP 32110-38726). Release windows between tiers are a VMS setting: SAP Fieldglass's training example gives a primary supplier a 72-hour head start, and Beeline's documentation example releases tier two 24 hours after tier one.

This page covers the mechanics: what is measured and how, how tiers and windows are set, the review cycle, and how to dispute your numbers with your own records. What a preferred supplier list is in general is covered in what is a preferred supplier list; winning orders inside a VMS in vendor management systems for staffing agencies.

What goes on an MSP supplier scorecard?

Private programs rarely publish their scorecards, but public ones do. The Tennessee draft contract lists the reports the MSP must produce on sub-vendors and the formulas for the MSP's own service levels, which use the same building blocks. The table uses its definitions where it gives one.

Virginia's survey schedule is in its contingent labor policy (VITA ITCL policy). Compliance items, such as onboarding documents on time, rate card adherence and timesheet accuracy, are also common; Tennessee requires the VMS to track violations of program rules. How fill rate itself should be counted is worked through in fill rate for staffing agencies.

How do tiers and release windows work?

A tier is a group of suppliers that receives requisitions at the same moment. The release window is the delay before the next tier gets them. Both are configured in the VMS:

• SAP Fieldglass. SAP's training material says supplier tiers "specify when suppliers receive notification" of a job posting and are based on the buyer's contract terms with each supplier. Its example gives an MSP supplier under a primary agreement postings 72 hours before any other supplier. Distribution can run automatically when a posting is approved or as a manual step (SAP Learning, job posting distribution lists).
• Beeline. Supplier groups decide who is invited and tiers decide when; an invitation can be sent immediately or later. Beeline's example sends a posting to preferred suppliers in tier one immediately and to tier two 24 hours later (Beeline supplier groups).

Not every program tiers. Tennessee's draft contract says open positions go to all members of the sub-vendor network and the MSP "shall not give preference" to any of them. Arizona's medical staffing program releases each posting to all vendors serving that labor category at the same time, for three business days (State of Arizona vendor training, March 2025). Virginia tiers its SOW suppliers by project size instead: up to $300,000, $1 million or $3 million (VITA policy, linked above).

How often are suppliers reviewed, and how do probation and removal work?

The cycle is whatever the program contract says. In Tennessee's draft, the MSP measures every sub-vendor at least semi-annually, reports quarterly, and the results are used "for the State to determine which Sub-Vendors may continue" to provide staffing. Sub-vendors can be asked to attend the quarterly review, and failing to attend when asked is grounds for removal from the network.

The same contract shows the escalation ladder the State applies to the MSP itself when its score falls below the minimum: a warning and a corrective action plan with one quarter to fix the problem, then probation with one more quarter, then the right to terminate. Your supplier agreement may set a similar ladder for you, or may let the program remove a supplier at will. Ask for the written rule before the first review, not after a bad quarter.

What should you check behind your score?

Most disputes are definitions, not data. Before you argue a number, get the program's answers to these:

• When does the clock start? At requisition approval, at release to your tier, or at the time you were notified? A 72-hour tier delay can count against you if the clock starts at approval.
• Business hours or calendar hours? And in whose time zone?
• What counts as a submittal? Does a candidate rejected for missing compliance documents count? Does a duplicate another supplier sent first?
• Which requisitions are excluded? Cancelled, on hold, filled internally, or changed after release.
• What is the denominator? All requisitions in your categories, or only the ones you were released?
• Over what period? A quarter with three requisitions should not be scored like a quarter with thirty.

How do you dispute scorecard data?

1. Keep your own dated records as you go. Export release, submittal, interview and offer timestamps from the VMS every month, and keep your ATS log and emails with the program office. A record made at the time beats a reconstruction.
2. Ask for the line-level data behind the metric you dispute, not just the score.
3. Compare requisition by requisition and list only the differences you can prove.
4. Send one written dispute before the review closes, with each requisition number, the program's figure, yours and the evidence.
5. Ask for a corrected score in writing, and for the definition to be fixed if it caused the error.

Subject: Scorecard data review: [Supplier name], [Program], [Quarter]

Hi [Program manager],

Thank you for the [Quarter] scorecard. Before the tier review on [date],
we would like to correct the data for [metric].

Our understanding of the definition: [definition as you understand it,
e.g. "time to first submittal, measured in business hours from release
to our tier"]. Please confirm or correct it.

Requisitions where our records differ:

Req #     Program figure     Our figure     Evidence (attached)
[1234]    [no submittal]     [submitted     [VMS submittal confirmation,
                              Oct 3, 10:14]   timestamped]
[1240]    [counted]          [cancelled     [program email of Oct 9]
                              Oct 9; should
                              be excluded]

With these corrections our [metric] for the quarter is [x] rather
than [y]. Could you confirm the corrected figure, or send the
line-level data so we can reconcile any remaining differences?

[Name]
[Title], [Supplier name]

Change the metric, the definition line and the table rows for each dispute; attach the evidence, do not describe it.

How do you move up a tier?

• Respond only where you can fill. A low response rate hurts, but so do weak submittals sent to keep it up. Ask to be removed from categories you cannot serve.
• Send fewer, better candidates. Submittal-to-interview is the ratio managers notice; see how to improve submittal-to-interview ratio.
• Finish compliance before the start date. Late background checks and missing documents become both a compliance mark and a fall-off.
• Watch early turnover. Unplanned departures and performance removals are scored separately in Tennessee's draft; both start with how well you screened.
• Bring your own numbers to the review. The same evidence that wins a dispute makes a good quarterly review; the staffing client QBR template shows a format.

If you are building service commitments for a direct client rather than a program, the staffing agency SLA template turns the same metrics into a contract.