PMO-06.09 Phase 06: Monitoring and Controlling

Vendor Performance Scorecard

بطاقة أداء المورد

tasleemat asset PMO-06.09 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 06: Monitoring and Controlling

Sizing Tier Requirements

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-06.09 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders
 based on project context.

Context and Definition:
A vendor performance scorecard records how an external supplier performed
against measures the project agreed in advance. The order of the columns is
the order the decisions happen in: the metric, the target that was agreed
for it, what was actually measured, the gap between them, and what is
being done about the gap.

The target is what makes the form worth completing. A score with no target
behind it cannot be argued with in either direction - the supplier regards
it as good, the project regards it as adequate, and nothing in the
document settles the disagreement. Agreeing the target first is the entire
discipline, and a target written after the result is known is not a target.

A scorecard is a period record rather than a running judgement. It is kept
per supplier per period, compared against the previous period, and read by
whoever owns the contract. A supplier that is performing well is left
alone, and a supplier that is not gets a corrective action with a name on
it and a date attached.

It can receive information from:
*   The contract or statement of work
*   Acceptance records, which are the raw material for quality measures
*   Issue and change logs raised against the supplier

It provides information to:
*   Contract closeout report, which reads the record across all periods
*   Procurement audit
*   Project status report, where a supplier shortfall is a schedule risk

Tailoring Tips:
*   Agree the target before the period starts. Every target written
    afterwards is a description of what happened, and the variance column
    then computes a gap between the outcome and itself.
*   State the measure with the score. A number whose measurement method
    changed between periods cannot be compared to one that did not, and
    the comparison is the only reason the number exists.
*   Write a corrective action only where there is a shortfall, and name
    who owns it. A variance with no response is recorded again next period,
    because the only thing that changed in between was the number.

Alignment:
The vendor performance scorecard should be aligned and consistent with:
*   The contract or statement of work, because the measures are contract
    measures and not the project's preferences
*   Procurement audit, which reads the period records as its evidence
*   Contract closeout report, which needs the trend rather than one period

Section Instructions:
*   Vendor Performance Scorecard Entries: for each measure the project
    tracks for this supplier, give the metric named so both sides would
    recognise it, the target agreed for the period, the score actually
    measured and how, the variance with its direction, and the corrective
    action with an owner and a date where the variance is a shortfall.
-->

<h3 dir="ltr" align="right">{{Company_Name}}</h3>
<h2 dir="ltr" align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 dir="ltr" align="center">VENDOR PERFORMANCE SCORECARD</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- | :--- |

---

## Vendor Performance Scorecard Entries

| Metric/KPI | Target Score | Actual Score | Variance | Corrective Action |
| :--- | ---: | ---: | ---: | :--- |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Procurement Manager** | {{Procurement_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Vendor Representative** | {{Vendor_Representative_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div dir="ltr" align="right" style="margin-top: 20px; font-size: 12px; color: #7
f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> VENDOR PERFORMANCE SCORECARD | <strong>Ref:</strong> PMO-06.09 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fak
hruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Project Artifact: Vendor Performance Scorecard

Document Reference: PMO-06.09

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Vendor Performance Scorecard in alignment with the Tasleemat framework.

1. What?

A table of the measures the project tracks for one supplier, one row each: the metric named so that both sides would recognise it, the target agreed for the period, the score actually measured together with the method, the variance from that target with the direction that matters, and the corrective action with an owner and a date where the variance is a shortfall.

2. Why?

Because a score with no target behind it cannot be argued with in either direction. The supplier regards it as good, the project regards it as adequate, and nothing in the document settles the disagreement. Agreeing the target beforehand is what converts the form from a record of an opinion into the basis for a decision, and it is also what makes the variance column worth computing at all.

3. When?

Once per period, per supplier, and kept rather than overwritten, because a single period says almost nothing and the trend is what identifies a supplier that is drifting. Reviewed by whoever owns the contract, and read again at closeout, where the question is not how the last quarter went but whether the supplier would be chosen again.

4. Who?

Owned by the procurement manager, who holds the contract and is the only party with standing to act on what the numbers show, with the project manager supplying the schedule and quality context the measures come from. The supplier representative signs the record, and that signature is worth having precisely because it means both sides are working from the same figures rather than from two accounts of the same period.

Tailoring Tips

Agree the target before the period starts. A target written afterwards is a description of what happened, and the variance column then computes a gap between the outcome and itself.
State the measure with the score. A number whose method changed between periods cannot be compared with one whose method did not, and the comparison is the only reason the number exists.
Write a corrective action only where there is a shortfall, and name who owns it. A variance with no response is recorded again next period, because the only thing that changed in between was the number.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Approved Project Baselines (PMO-04.01.01)
- Work Performance Data & Logs (PMO-05.01 - 05.12)
Optional / Contextual:
- Risk Register (PMO-04.08.02)
- Vendor Agreements (PMO-04.09.04)

2. Downstream Dependents

Mandatory:
- Change Requests (PMO-05.03)
- Project / Phase Closeout (PMO-07.03)
- Lessons Learned Summary (PMO-07.01)
Optional / Contextual:
- Transition to Operations Checklist (PMO-07.04)
- Value Realization Register (PMO-01.03)

5. How?

To accurately complete the Vendor Performance Scorecard, populate the following sections based on the project context (ensuring reference to parameters.md for the general project variables):

Metric/KPI: What is being measured, named so that both sides would recognise it. "Quality" is not a metric; "defects found in acceptance, per hundred items delivered" is, because a word cannot be measured twice and compared across periods.
Target Score: The level agreed in advance, with the period it applies to. A target written after the result is known is not a target, it is a description, and this column is the one that makes the variance column mean anything.
Actual Score: What was measured, and how. The measure is stated with the score so that a later reader can tell whether the same method was used in both periods; a number whose method has changed is not comparable to a number whose method did not.
Variance: Target minus actual, with the direction that matters. Whether a positive number is good or bad depends on the metric, and stating it here is what stops the sign being argued about instead of the performance.
Corrective Action: What happens because of the variance, and by when. Written only where there is a shortfall, and naming who does it: a scorecard that records a variance and no response produces the same variance next period, because the only thing that changed in between was the number.

Associated Templates

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 06_09_Vendor_Performance_Scorecard_Example.md

LLM Generation Prompt & Agent Instructions

Vendor Performance Scorecard - LLM Generation Prompt

SYSTEM INSTRUCTIONS: This document is the detailed instruction set for generating the Vendor Performance Scorecard. When asked to populate the template, follow the guidance for each section below to produce the requested content. Refer to parameters.md for the general project variables.

Context and Definition: A record of how an external supplier performed against measures the project agreed in advance. The columns are in the order the decisions happen in: the metric, the target agreed for it, what was actually measured, the gap between them, and what is being done about the gap.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Approved Project Baselines (PMO-04.01.01), Work Performance Data & Logs (PMO-05.01 - 05.12) * Optional: Risk Register (PMO-04.08.02), Vendor Agreements (PMO-04.09.04) * Downstream Dependents: * Mandatory: Change Requests (PMO-05.03), Project / Phase Closeout (PMO-07.03), Lessons Learned Summary (PMO-07.01) * Optional: Transition to Operations Checklist (PMO-07.04), Value Realization Register (PMO-01.03)

Vendor Performance Scorecard Entries

Metric/KPI

Instructions: What is being measured, named so that both sides would recognise it. "Quality" is not a metric; "defects found in acceptance, per hundred items delivered" is, because a word cannot be measured twice and compared across periods.