Supply Chain Risk Software

Our fictional pilot follows Hawthorn Components, which buys metal parts through an agent and receives a concern about recruitment practices at a subcontractor site.

The procurement director needs to establish the supply relationship, investigate the concern and decide how to respond without treating an unverified allegation as a final finding.

The UNGP commentary explains that human-rights due diligence goes beyond risks to the company itself to include risks to rights-holders Principle 17 commentary.

The OHCHR publication identifies the UNGP framework and its endorsement; it is not a UK software mandate UNGP publication.

The standards homepage and ESG governance guide help connect the investigation to wider responsibilities without replacing the actual case.

Hawthorn’s first acceptance test is an incomplete relationship map with one uncertain site identity.

The supplier must keep that uncertainty visible rather than present a precise score based on a guessed match.

Hawthorn’s purchasing system contains an agent name, while the concern names a factory in another jurisdiction, so the pilot asks the supplier to connect them with evidence.

A similar trading name is not accepted as proof that the entities are identical, and a group-level assessment is not automatically assigned to every site.

The OECD publication page identifies the 2023 Guidelines as government recommendations to enterprises, rather than a compulsory technology specification Guidelines status.

The buyer asks for relationship history, source references and a way to correct an erroneous match without losing the original investigation trail.

This is an editorial data-quality test and does not prescribe a universal supplier-tier depth.

The fictional test deliberately includes a second factory with a similar name.

The buyer checks whether a reviewer can correct the match before it affects the case or purchasing decision.

Hawthorn’s pilot introduces a report about recruitment fees alongside a supplier response disputing the allegation, asking the system to preserve both sources.

The case reviewer needs dates, source identity, affected location and an explicit confidence assessment rather than a merged summary that removes disagreement.

UNGP Principle 18 includes meaningful consultation with potentially affected groups and relevant stakeholders Principle 18.

The buyer therefore asks how an investigation can record appropriate stakeholder information while restricting access to sensitive personal material.

The demonstration does not establish a particular legal finding or suggest that software should decide whether an allegation is true.

Hawthorn rejects a workflow that marks the concern resolved merely because a supplier uploaded a policy.

The reviewer needs an explanation of the response and its evidence before changing the case status.

The CSDDD application framework was changed by Directive 2026/470, including the removal of Article 22’s climate-transition-plan duty Article 4 amendments.

The consolidated directive identifies the relevant scope and application provisions; a supplier’s old checklist should not be accepted as the current legal basis Articles 2 and 37.

Hawthorn’s fictional procurement brief asks for evidence and case-management support that could be mapped to an approved due-diligence programme, not an assertion that buying software makes the company CSDDD compliant.

The CSDDD guide owns the legal explanation, and this guide incorporates the software buyer task without creating a separate CSDDD-software synonym page.

The supplier must show how a changed source mapping is reviewed and approved rather than silently applied to every open supplier case.

The fictional buyer asks the legal reviewer to approve the mapping before the implementation supplier configures it.

This separates a technology deliverable from an uncatalogued promise about legal compliance.

Hawthorn’s fictional case sets an investigation action and a supplier engagement action separately so that a completed meeting is not confused with a resolved impact.

The buyer asks the software supplier to demonstrate a missed action, a revised deadline and an evidence-based closure review.

The case should preserve why a response changed and which questions remain open, with sensitive records accessible only to appropriate users.

The Modern Slavery Act section 54 statement is a distinct statutory output and should not be replaced by an internal case dashboard section 54.

The ESG questionnaire guide addresses requested answers, while this purchasing brief follows the investigation and response behind them.

Hawthorn’s pilot keeps the supplier’s policy upload as one piece of evidence rather than treating it as a complete outcome.

The reviewer can leave the case open when the evidence does not yet support closure.

Exiger, Intertek and LRQA describe their own supply-chain products in terms that include mapping, risk information and due-diligence workflows owner description owner description owner description.

These references are category examples, not a shortlist, feature guarantee, comparative score or recommendation to purchase one of them.

Hawthorn turns each relevant claim into a pilot question using its uncertain factory identity, disputed concern and incomplete action evidence.

The team asks what data sources are licensed, how a source change is explained and which outputs can be retained after the contract ends.

No independent market ranking, provider price or promised reduction in business risk is invented.

The same fictional case is used for each supplier demonstration so that the buyer compares outputs against one clear brief.

The comparison remains task-specific rather than presenting a universal ranking of platforms.

Hawthorn’s acceptance schedule requires the implementation team to leave usable identity records, case evidence, access settings and the actual reasons for decisions.

The contract separates configuration and migration from specialist investigation, stakeholder engagement and legal interpretation, with dependencies stated explicitly.

The software RFP and software-versus-consultant guide provide broader purchasing structures for that allocation.

The final exit test asks a different reviewer to reconstruct the factory concern and explain why the case remains open without access to the live dashboard.

The useful result is a team able to investigate and act on supported information, not a supplier list decorated with an unexplained green status.