Vendor scorecard template for PO performance

Use one scorecard row per supplier and review period

Create a row for each supplier in a defined monthly, quarterly, or rolling period. Record the number of POs and lines reviewed so decision-makers can distinguish a score based on two simple orders from one based on hundreds of lines. Keep the review period, buyer owner, review date, and data-coverage percentage visible beside the result. The included sample rows are illustrative and should be deleted or replaced with your own attributable records.

Score response performance with a clear denominator

Response performance can combine the percentage of required acknowledgments completed within the agreed window and median response hours. Define the clock before calculating: when it starts, which business calendar applies, how corrected contacts are handled, and when a response is complete. A sent email alone is not evidence of receipt or acknowledgment. If delivery or view evidence is unavailable, disclose that limitation instead of assigning an automatic failure.

• POs sent and lines requiring acknowledgment
• Complete responses within the stated service window
• Median time to first view and complete response
• Reminder dependence and contact-delivery failures

Measure change stability without punishing transparency

The template includes lines accepted as ordered and lines with proposed date changes. Those measures expose planning volatility, but a prompt, honest proposal can be more useful than silent acceptance followed by a miss. Review the timing, magnitude, cause, and recurrence of changes before assigning the stability score. Keep price, quantity, and date proposals distinct, and do not treat a buyer-approved change as if the supplier silently altered the source PO.

Measure commitment reliability from the current commitment

Commitment reliability compares the supplier's buyer-approved commitment with the observed result. It should not compare delivery against an original requested date after the buyer accepted a different commitment without showing both. Define how partial deliveries, buyer-caused holds, cancellations, expedite requests, and unavailable receipt data are handled. If Pacteva supplies acknowledgment evidence but another system owns receipt or delivery facts, join the datasets through stable PO and line identifiers.

Keep internal buyer decision time out of the supplier score

When a supplier proposes a change, the exception may wait on an internal buyer. The template records buyer decision median hours as a diagnostic but does not include it in the sample weighted supplier score. This prevents internal delay from lowering the supplier rating and gives procurement leaders a separate improvement signal. Review stalled decisions before using a scorecard in a supplier conversation.

Set weights and thresholds before reviewing results

The sample weighted score uses 40 percent response, 25 percent change stability, and 35 percent commitment reliability. Those weights are examples, not universal benchmarks. Agree on definitions, weights, minimum sample size, missing-data treatment, and red-amber-green thresholds before seeing supplier results. Changing a model after seeing the outcome undermines comparability. Retain the prior model and review date when governance changes.

Turn the scorecard into a fair improvement process

A score should lead to a documented review, not an unexplained penalty. Share the underlying events, allow factual corrections, record context, agree on one or two improvement actions, assign owners, and set a follow-up date. Use append-only or superseding corrections so the team can explain why a historical result changed. Avoid publishing sensitive supplier performance data outside authorized procurement and operations roles.

Move from a spreadsheet when evidence becomes fragile

A spreadsheet is appropriate for designing the scorecard and reviewing modest volumes. Move to structured software when multiple buyers edit concurrently, status depends on inbox searches, supplier lines are omitted, reminders are inconsistent, corrections overwrite history, or nobody can trace a metric back to its source event. Pacteva provides the post-PO acknowledgment and commitment evidence that can feed this scorecard while leaving quality, risk, receiving, and financial facts in their existing systems.

Validate the workflow with one real purchase order

Before buying or replacing software, run one representative multi-line PO from reviewed source through supplier response and buyer resolution. Include at least one accepted line, one proposed date or quantity change, and one delivery or reminder edge case. Confirm that every participant can identify the current owner and next action, that the original order remains unchanged, and that the final commitment can be exported and traced to its response and decision. Also verify the supplier experience on a normal phone and desktop browser, revoke and reissue a response link, inspect a failed delivery, and test the role boundary with a non-owner buyer. This evidence is more useful than a feature checklist because it exposes adoption friction, hidden authority, and incomplete system boundaries before the workflow reaches production volume.