A supplier should not score well because the final invoice was low or poorly because one defect was visible. The scorecard must preserve baseline, scope changes, actual outcomes, recovery and confidence in the evidence.
A project ends with three competing memories. Procurement remembers a low tender price. The site remembers late replacement sashes. The supplier remembers dozens of buyer changes and an accelerated shipment. A single five-star rating would flatten all three into opinion. A useful scorecard rebuilds the authorised baseline, separates supplier-controlled and external changes, measures promised and actual events, traces quality findings to affected populations, evaluates recovery as well as occurrence, and shows when the evidence is too weak for a confident conclusion.
1. Approve the scoring design before opening the outcome data
Name the decision the scorecard will inform: preferred-bidder status, conditions for another order, due-diligence depth, development actions, order-size cap or no automatic consequence. Identify review owner, contributors, supplier fact-check opportunity, approval authority, retention, confidentiality and challenge route. The scorecard should inform governance, not secretly make an award decision.
Define dimensions and evidence before seeing performance. Common lanes are commercial control, delivery, quality, recovery/claims, communication/document control and compliance/safety where relevant. The buyer sets weights, critical overrides and thresholds according to its risk appetite. A weighted total must not allow an unsupported safety, fraud or certification concern to be neutralised by low price unless approved governance expressly permits that treatment.
Use score descriptors anchored in observable states rather than adjectives. For every band, state required evidence and boundary. Record ‘not applicable’, ‘unknown’ and ‘insufficient evidence’ separately from zero performance. Do not reward missing records by excluding difficult metrics after the project.
| Control | Approved entry | Why it matters |
|---|---|---|
| Decision use | [next-order decision and limits] | Prevents score becoming automatic award |
| Dimensions/weights | [buyer-approved before review] | Controls hindsight bias |
| Critical overrides | [named risks and authority] | Prevents average hiding fatal concern |
| Evidence hierarchy | [primary records and confidence rule] | Separates fact from recollection |
| Review/challenge | [roles, supplier fact check, approval] | Corrects data without bargaining criteria |
| Unknown treatment | [not applicable/unknown/insufficient] | Avoids false precision |
2. Rebuild baseline budget, approved changes and final cost
Start with the accepted quotation/contract and line-item scope—not the first enquiry or final invoice. Reconcile opening marks, quantities, systems, glass, hardware, finish, screens/accessories, samples/tests, packing, freight, services, exclusions, Incoterm/named place, currency and taxes. Record provisional or buyer-supplied items separately.
Create a change ledger linking each authorised variation to trigger/date, affected marks and baseline revision, initiator, reason, added/omitted work, agreed price/time treatment, evidence and status. Separate buyer/design changes, supplier proposals, unforeseen verified conditions, error correction, acceleration and disputed items without converting category into legal fault.
Compare final authorised cost with the adjusted baseline, then isolate unapproved, disputed, avoidable rework, duplicate freight, credits and unresolved claims. Currency and index movements need their contract-defined basis. A low final total can reflect omitted scope; a high total can reflect buyer additions. Score commercial control from transparent causation and forecast discipline, not raw variance alone.
| Cost/scope state | Amount/currency basis | Authority/evidence | Supplier-control question | Scorecard treatment |
|---|---|---|---|---|
| Original baseline | Contract line items | Signed sources | Were scope/assumptions clear? | Baseline only |
| Approved additions | Change IDs | Authorised records | Was pricing timely/transparent? | Adjusted baseline |
| Approved omissions/credits | Change/credit IDs | Authorised records | Were savings returned? | Adjusted baseline |
| Rework/recovery cost | NCR/claim/cost records | Causation/entitlement separate | How was exposure controlled? | Evidence lane |
| Disputed/unapproved | Notice/decision status | Open authority | Do not assume outcome | Unknown/open |
| Final authorised cost | Ledger reconciliation | Finance approval | Forecast versus final | Commercial result |
3. Compare promised and actual delivery through prerequisite-aware milestones
Freeze the authorised programme baseline and revisions. For each group record prerequisite dates—deposit, drawings, samples/colour, glass/hardware decisions, compliance evidence and site inputs—then promised material, first-off, production, inspection, packing, booking, shipment and delivery events. Distinguish forecast, commitment and actual evidence.
Measure by opening group or shipment, not one project completion date. Record missed events, duration and downstream consequence only from evidence. Separate supplier-controlled production/logistics, buyer/design input delay, carrier/customs, force-majeure or unresolved causes according to approved project analysis; this is not a contractual entitlement decision.
Evaluate forecast quality and communication: Was the plan logic visible? Were risks disclosed before commitment failed? Did revised dates include cause, affected marks and recovery plan? A supplier can be late yet manage recovery transparently; another can meet a final date through unsafe compression or repeated unreported slippage. Preserve both outcome and control behaviour.
| Milestone/group | Baseline/revision | Prerequisites closed | Promised forecast | Actual evidence | Variance/cause confidence/recovery |
|---|---|---|---|---|---|
| Technical release | [marks/rev] | [inputs] | [date] | [record] | [classified] |
| Material/first-off | [group] | [release] | [date] | [record] | [classified] |
| Production/inspection | [group] | [holds] | [date] | [record] | [classified] |
| Packing/shipment | [shipment] | [release/booking] | [date] | [record] | [classified] |
| Delivery/replacements | [destination] | [customs/site] | [date] | [record] | [classified] |
4. Score quality and recovery from populations, recurrence and verified closure
Build a quality denominator: total units/parts, inspected population and method, characteristics accessible, shipment/site populations and uninspected scope. Reconcile NCRs, shortages, damage, wrong configuration, documentation and service cases by unique ID and affected opening marks. Raw issue count without denominator or duplicate control is misleading.
Classify only under the approved quality plan. Record requirement source, observation, affected population, containment, disposition, reinspection and closure. Separate isolated damage from common process or repeat failure. A repaired unit can close locally while recurrence control remains open; a large shipment with few inspected units should not receive a confident low-defect claim.
Evaluate recovery as a distinct dimension: acknowledgement, containment, evidence preservation, root-cause quality where required, technically authorised remedy, replacement/configuration accuracy, freight/site coordination, communication, verified closure and claim/credit resolution status. Fast unsupported action can worsen evidence or repeat the wrong part. Score response from approved expectations and actual records, not a universal clock.
| Measure | Population/baseline | Observed outcome | Recovery evidence | Confidence/score basis |
|---|---|---|---|---|
| NCR incidence | Defined inspected/produced population | Unique NCRs and affected units | Containment/disposition | Coverage stated |
| Recurrence | Common requirement/process/time groups | Repeated characteristic | Corrective effectiveness | Cause confidence |
| Shortage/wrong item | Packing/order/opening baseline | Reconciled identities/quantities | Replacement/credit closure | Custody evidence |
| Transit/site damage | Condition/custody baseline | Events by package/unit | Carrier/supplier/site actions | Causation open/closed |
| Response/recovery | Contract/project expectations | Actual milestones | Verified technical/commercial closure | No claim outcome invented |
5. Apply confidence, review contradictions and convert scores into bounded actions
Assign evidence confidence separately from performance: high when primary records reconcile and coverage matches the claim; medium when evidence is partial but corroborated; low when based on recollection, selected messages or unclear populations; unknown when missing. The buyer approves definitions. Never multiply numbers mechanically if the method obscures a critical missing denominator.
Triangulate buyer, supplier, inspector, carrier and site records. Invite correction of factual identities, dates and documents, preserving the audit trail. Supplier disagreement belongs in the final record with evidence and disposition; it does not automatically raise or lower the result. Separate disputed facts from different commercial interpretations.
Issue a signed outcome containing dimension results, weights, confidence, critical overrides, strengths, weaknesses, open matters and authorised next-order controls: smaller first order, extra evidence gates, revised packaging, named project lead, corrective plan, credit review or other buyer decision. Do not publish allegations or blacklist without legal/procurement authority. Revalidate current supplier facts before a future award.
| Finding | Confidence | Critical override? | Next-order control candidate | Approver/status |
|---|---|---|---|---|
| Commercial scope drift | [level] | [rule] | Stronger line-item/change gate | [decision] |
| Forecast reliability gap | [level] | [rule] | Milestone evidence/escalation | [decision] |
| Recurring NCR route | [level] | [rule] | Corrective effectiveness/first-off | [decision] |
| Strong recovery | [level] | [rule] | Retain proven response route | [decision] |
| Unknown financial/certification issue | Low/unknown | Possible hold | Refresh specialist due diligence | [decision] |
FAQ
What weights should price, delivery and quality receive?
The buyer must approve project- and risk-specific weights before reviewing outcomes. This guide supplies none.
Should one major defect fail the supplier?
Use approved critical-override rules, consequence, evidence and authority. A weighted average should not decide this silently.
How should buyer-caused changes affect delivery scoring?
Rebuild prerequisite and programme evidence, separate causes and confidence, and avoid deciding contractual entitlement in the scorecard.
Can defect rate be calculated from NCR count divided by total order?
Only if numerator, denominator, inspection coverage and duplicate/population rules support that claim. Otherwise report bounded counts and unknowns.
Should fast replacement erase the original quality issue?
No. Record occurrence and recovery separately; both matter.
Can the supplier challenge the score?
A fact-check route improves data quality, but criteria and weights should not be renegotiated after results. Preserve disagreements and authority.
Does a high score guarantee the next order?
No. Refresh current capacity, entity, beneficiary, certification, product and market facts and follow authorised sourcing governance.
May the scorecard be shared publicly?
Only under authorised confidentiality, defamation, competition and legal review. It is principally an internal controlled decision record.
Continue the project review
Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.
Official sources used
ISO — ISO 20400:2017 sustainable procurement guidance ↗ISO — ISO 9001 quality management systems ↗ISO — ISO 10007:2017 configuration management ↗World Bank — Rated Criteria procurement guidance ↗UNCITRAL — Model Law on Public Procurement ↗ISO — ISO 31000 risk management guidance ↗Related buyer guides
This article is general procurement-performance, closeout and evidence-control education. It is not legal, accounting, audit, credit, claims, damages, supplier-blacklisting, tender-award, competition, employment or financial advice and does not determine breach, fault, entitlement, causation, liability, suitability or future award. It supplies no score, weight, threshold, rating scale, penalty, defect target, delivery allowance, response period, cost variance limit or disqualification rule and states no Cavorlen project, supplier, price, delivery, defect, claim, score, policy or commercial outcome. The buyer's approved procurement governance, signed contract and changes, reliable project records, applicable law and authorised commercial, legal, technical and finance decision-makers must define dimensions, weights, critical overrides, confidence rules and sourcing consequences before results are scored.