Quick Read
SPK DDMS2000:2026 Section 10.9 distinguishes between two fundamentally different forced labour compliance regimes: rebuttable-presumption regimes, where importers must affirmatively prove goods were not produced with forced labour before entry, and strict-liability regimes, where forced labour prohibitions apply regardless of importer due diligence. Organizations cannot treat these regimes interchangeably, as rebuttable-presumption compliance requires supply chain traceability documentation extending potentially beyond Tier 1 suppliers and cannot rely on probabilistic risk narratives alone. The distinction materially changes how an organization must construct its evidence file and operationalize its due diligence posture.
Why This Whitepaper Exists
Forced labour and import compliance regimes are often discussed as a single category of risk, when in practice two genuinely distinct regulatory logics sit underneath that label, and treating them as interchangeable is one of the more consequential mistakes an organisation can make in its supply chain due diligence. SPK DDMS2000:2026 addresses both within Section 10.9, but is explicit that the two regime types shall not be treated as interchangeable, because the evidentiary posture each requires is fundamentally different. This whitepaper sets out the distinction in full, and what it means for how an organisation actually builds its evidence file.
Organisations shall not treat these two regime types as interchangeable; the evidentiary posture required differs materially.
Two Regime Logics, Not One
Section 10.9 identifies two distinct regime types operating on entirely different legal mechanisms.
Rebuttable-presumption regimes
Under a rebuttable-presumption regime, the law presumes that goods from a defined category, geography, or entity list were produced with forced labour, and places the burden on the importer to affirmatively prove otherwise before the goods may enter. The organisation is not required to have done anything wrong to trigger this presumption — the presumption arises from the category itself, and the organisation's task is to rebut it with evidence.
Strict-liability product-ban regimes
Under a strict-liability regime, the law prohibits placing a product made with forced labour on the market outright, regardless of the importer's own due diligence. There is no presumption to rebut, because there is no due diligence defence built into the mechanism at all — the prohibition applies to the fact of forced labour in the product's history, independent of what the importing organisation knew or did.
Rebuttable-presumption regimes | Strict-liability regimes | |
|---|---|---|
Independent DD obligation | Not the mechanism itself — the burden falls on the importer once the presumption is triggered | None — the regulation prohibits the product outright regardless of due diligence |
Role of voluntary DD | Central: DD evidence is what rebuts the presumption | Mitigating: DD is taken into account by authorities and can help avoid or shorten an investigation, but does not change the underlying prohibition |
Evidentiary bar | Traceability sufficient to affirmatively prove the absence of forced labour, potentially beyond Tier 1 suppliers | Documentation sufficient to demonstrate risk identification and mitigation, aligned to the OECD six-step framework |
What triggers organisation action | A presumption arising from geography, entity, or product category | A public risk database match, or an authority's own risk-based investigation |
Rebuttable Presumption: Proving a Negative
Section 10.9.2 requires that, where a rebuttable-presumption regime applies, the organisation maintain supply chain traceability documentation to the depth required to rebut the presumption — potentially extending beyond Tier 1 suppliers — and states plainly that the organisation shall not rely on a general risk narrative alone in these cases. This is a meaningfully higher bar than most supplier due diligence practice operates to, and it is worth being specific about why a risk narrative fails this test even when it is thorough and well-written.
A risk assessment that concludes a supply chain is “likely low risk” based on supplier attestations and general sector knowledge is, at its core, a probabilistic judgement — an estimate of likelihood. Rebutting a legal presumption requires something categorically different: affirmative, traceable evidence tracing the specific goods in question back through the specific supply chain that produced them. The regime does not ask whether forced labour is unlikely; it asks the organisation to prove it did not happen, for this shipment, in this supply chain. No amount of general risk-narrative confidence substitutes for that specific, traceable proof.
Strict Liability: Where Due Diligence Still Matters, Differently
Strict-liability regimes work on a different logic entirely: the underlying prohibition applies regardless of what due diligence the organisation performed. This can create a misleading impression that due diligence is pointless under this regime type. Section 10.9.3 corrects this directly: voluntary due diligence records remain genuinely valuable evidence to present to an enforcing authority, and can meaningfully reduce the likelihood of an investigation being opened, or shorten its duration, even though the underlying prohibition itself is one of strict liability rather than a due-diligence defence standard.
Section 10.9.3 requires these voluntary records be maintained consistent with the OECD six-step due diligence framework — embed, identify and assess, cease/prevent/mitigate, track, communicate, remediate. This is a deliberate choice: it connects the standard's own risk-based methodology directly to what a strict-liability regime's enforcing authority will actually look for when deciding how much scrutiny to apply, even though that authority is not evaluating a due diligence defence in the legal sense.
Watching for the Trigger, Not Waiting for the Investigation
Section 10.9.4 requires the organisation to monitor any public forced-labour risk database maintained by a relevant authority for products or geographies matching its supply chain, and treats a match as a mandatory trigger for enhanced due diligence under this module. This is a proactive requirement, not a reactive one, and it connects directly to the general ongoing due diligence obligation established elsewhere in this standard: the organisation is expected to be watching the relevant public risk indicators continuously, rather than discovering exposure only once an investigation or import action has already begun.
When Enforcement Happens: Deadlines and the Path Back
Section 10.9.6 requires a documented process for responding to detention, seizure, import-denial, or product-ban actions, including evidence retrieval procedures capable of meeting the enforcing authority's evidence-request deadlines — which can be as short as 30 working days under some regimes' guidance — and a documented pathway for demonstrating elimination of forced labour from a supply chain sufficient to support a product's return to market where the regime permits this.
The return-to-market pathway connects directly to the remediation discipline addressed elsewhere in this standard. Section 10.18.7 requires that, where an enforcement authority requires evidence of remediation as a condition of restoring market access, the organisation maintain documentation sufficient to demonstrate the remedy was effective and sustained, not merely initiated. A product cannot return to market on the strength of a stated intention to fix the underlying labour conditions — the standard requires sustained, evidenced remediation, tracked the same way any other remediation case is tracked under Section 10.18.4.
Building One Evidence File, Not Two Weaker Ones
Organisations exposed to both regime types for overlapping supply chains should resist the temptation to build a single, generic forced-labour evidence file intended to serve both purposes equally well. A file built to rebut a presumption — deep, traceable, affirmative, extending as far into the supply chain as the presumption requires — will generally also serve a strict-liability authority's interest in voluntary due diligence evidence, because it exceeds what that authority is looking for. The reverse is not reliably true: a file built only to demonstrate general risk awareness for a strict-liability context will usually fall well short of what a rebuttable-presumption regime requires to actually rebut anything, because general risk awareness is precisely what a presumption regime does not accept as sufficient.
A practical building principle
Where an organisation is uncertain which regime type applies to a specific supply chain, or where both may apply, building to the rebuttable-presumption standard as the default is the more defensible choice — it is the more demanding standard of the two, and evidence built to that standard degrades gracefully into strict-liability sufficiency, while the reverse does not hold.
Common Misconceptions Worth Correcting
“If a strict-liability regime doesn't require due diligence, doing it is optional.” Voluntary due diligence remains genuinely valuable evidence under a strict-liability regime, even though it is not a legal defence to the underlying prohibition.
“A thorough risk narrative should satisfy a rebuttable presumption.” Section 10.9.2 requires affirmative traceable evidence, not a well-reasoned risk assessment, however thorough.
“We only need to watch for enforcement action once we have reason to suspect a problem.” Section 10.9.4 requires proactive, ongoing monitoring of relevant public risk databases, not reactive investigation.
“Once a remediation commitment is made, the product can return to market.” Section 10.18.7 requires the remedy be shown to be effective and sustained, not merely initiated or promised.
Common Gaps Worth Checking
The organisation treats all forced labour regimes it is subject to as requiring the same evidentiary depth, rather than distinguishing rebuttable-presumption from strict-liability exposure.
Supply chain traceability stops at Tier 1 suppliers even where a rebuttable-presumption regime's evidentiary demands may extend further.
No process exists for monitoring the relevant public forced-labour risk database for product or geography matches.
Evidence retrieval procedures have never been tested against the short response deadlines some regimes' enforcement guidance imposes.
The same generic evidence file is used across both regime types, built to neither standard's actual requirements.
How Speeki Sentinel Certification Assesses This
Certification against SPK DDMS2000:2026 tests whether an organisation's forced labour due diligence evidence is calibrated to the specific regime type it faces — traceability sufficient to rebut a presumption where one applies, and OECD-aligned voluntary due diligence records where a strict-liability regime applies — rather than a single undifferentiated approach applied across both. An assessor will specifically test whether traceability documentation would actually rebut a presumption, not merely whether a general risk narrative exists.
Speeki Sentinel is the certification product through which this assessment is delivered. Organisations may build their own regime-specific evidence approach on a self-assessed basis, without ever seeking Speeki Sentinel certification. Speeki Sentinel certification — the independent verification of that DDMS against the standard — is available once an organisation believes its approach is ready to be independently tested.
Speeki is an accredited certification body. For current information on the specific accreditations Speeki holds and their scope, please refer to speeki.com rather than relying on this whitepaper, as accreditation status and scope are maintained centrally and can change.
Closing Note
Forced labour due diligence is not one discipline with two names. It is two distinct evidentiary tasks that happen to share a subject matter — proving an absence in one case, and demonstrating genuine, sustained effort in the other. Section 10.9 exists because conflating them produces a file that does neither job particularly well, and an organisation that discovers the distinction only after an enforcement action has already begun has discovered it too late to matter.