Kodiak supplier evaluations need period-and-rater provenance

Treat each evaluation as a bounded measurement record

The direct answer is that a supplier rating should identify what was measured, for whom, and when. Kodiak Hub describes 360-degree supplier views, robust audit data, evaluations, ratings, scorecards, and performance monitoring. Those elements can support a measurement program, but a current number cannot stand for every site, product, category, contract, business unit, or period associated with the supplier.

Preserve the supplier legal entity, site, parent or affiliate when relevant, supplied item or service, category, contract and buyer population, evaluation period, event or transaction population, metric name and business definition, unit, direction, target and threshold, numerator and denominator, source system, observation times, exclusions, missing data, transformation, formula version, calculated result, and superseding record. An unresolved scope or denominator should stay visible rather than disappear inside an aggregate rating.

Separate source observations, calculations, and rater judgment

Operational data, supplier self-report, audit evidence, stakeholder feedback, calculated indicators, and reviewer judgment have different provenance. Retain each source value before normalization, the authorized source owner, collection method, applicable period, validation state, correction history, and link to supporting evidence. Then preserve weighting, scale, rounding, missing-value rule, benchmark or target version, and calculation output separately. A formula result should not be edited to express a reviewer concern.

For human assessments, record the rater's identity and role, training or qualification where the buyer requires it, assigned scope, questions and rubric version, evidence visible at review time, conflicts or recusal, response, rationale, confidence or uncertainty, comments, sign-off, and review time. Supplier disagreement should create a linked challenge and disposition, not overwrite the original observation. Where AI helps summarize or rate information, retain the inputs, output, model or feature version when available, reviewer action, edits, and limits rather than presenting generated analysis as source evidence.

Improvement work needs an accepted baseline and decision owner

Kodiak Hub links performance monitoring with supplier collaboration and continuous improvement. The handoff should begin only after an accountable role accepts the bounded result or identifies the evidence gap. Keep the observed issue, baseline metric and period, affected scope, materiality rationale, supplier response, proposed action, buyer and supplier owners, resources, milestone, due date, success measure, escalation, contract consequence where applicable, approval, and change history. A shared task or supplier promise is not evidence that performance improved.

Follow-up needs a new observation under a stated method and period, comparison to the retained baseline, exception analysis, reviewer, supplier response, and decision about continuation, adjustment, closure, or escalation. Do not backfill a prior score when corrected source data arrives; issue a versioned recalculation and identify decisions that relied on the earlier value. This evaluation decision is distinct from whether an external sustainability score authorizes a supplier award: the question here is whether an internally used performance measurement is reproducible and actionable for its bounded scope and period.

Test one supplier across sites, metrics, raters, and periods

Use a representative supplier serving two sites and two categories across adjacent quarters. Combine delivery, defect, audit, responsiveness, cost, and innovation measures; include a supplier self-assessment, two buyer raters, a missing denominator, late ERP correction, changed target, disputed audit result, rater conflict, improvement action, missed milestone, and later recovery. Verify that each displayed score can be reproduced, differences remain attributable, legitimate scopes do not merge, challenge rights work, and follow-up compares like populations without rewriting the baseline.

Kodiak Hub's official page supports the attributed provider positioning about supplier views, audit data, evaluations, ratings, scorecards, performance monitoring, collaboration, continuous improvement, and AI-enabled supplier insight. It does not establish a customer's metric definitions, source completeness, formula accuracy, rater independence, AI accuracy, supplier response, audit validity, performance change, sourcing or contract decision, savings, compliance, or outcome. Qualified procurement, category, quality, operations, finance, sustainability, compliance, data-governance, supplier, and legal owners retain those decisions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Procurement Technology Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.