How to Keep a Supplier Shortlist Current When Requirements Change

A supplier shortlist is a conclusion built on requirements

If the requirements change, the shortlist may no longer be valid.

That sounds obvious, but evaluations often preserve the ranking while the criteria that produced it disappear into an old spreadsheet, meeting note, or AI conversation. A supplier marked “not suitable” may become viable after a requirement changes; a preferred supplier may no longer qualify.

Keep four records

For a professional evaluation, maintain:

Current requirements: The criteria suppliers must meet now

Shortlist decisions: Why each supplier advanced, paused, or was rejected

Open checks: Security, legal, commercial, or implementation questions

Replaced criteria: Earlier requirements that explain old decisions

This is different from a personal major purchase. Supplier evaluation may involve due diligence, internal approval, contractual terms, and multiple stakeholders.

Re-run only affected decisions

When a requirement changes:

identify which supplier decisions relied on it;
reopen those decisions;
record the new conclusion and rationale;
keep unresolved checks open;
mark the effective date of the change.

Do not silently edit a score. A future reviewer should be able to understand why the shortlist changed.

Using Giraffe for the evaluation state

Giraffe keeps useful conclusions from AI work in a human-readable Project. A person can explicitly save current supplier requirements, decisions and rationale, open due-diligence questions, notes, and supporting documents.

When a requirement changes, the current value can be updated and earlier values remain available in dated history. A rejected decision can be reversed with a reason where the documented workflow supports it.

Giraffe does not perform supplier due diligence or make the procurement decision. It keeps the conclusions the user chooses to preserve; the authoritative evidence remains in the relevant contracts, security documents, and source materials.

Example: data residency becomes mandatory

An early evaluation treats regional data residency as a preference. Procurement later makes it mandatory.

The record should now show:

Current requirement: approved regional data residency is mandatory.
Affected decisions: recheck every shortlisted supplier.
Open checks: verify contractual commitment and hosting region.
Replaced criterion: data residency preferred but not required.

The shortlist should be updated only after the open checks are resolved.

A shortlist that remains explainable

A professional supplier decision needs more than a ranking. It needs current requirements, explicit rationale, and visible unresolved checks.

Review Giraffe use cases and the product model on How Giraffe works.

Verified sources