Quick Read
SPK DDMS2000:2026 Section 10.18 establishes remediation as a distinct operational discipline separate from prevention and mitigation, requiring organisations to maintain documented policies that honestly assess their degree of involvement and actual leverage in addressing harm that has already occurred. The standard mandates grievance mechanisms meeting UN Guiding Principles effectiveness criteria—legitimate, accessible, predictable, equitable, and transparent—and requires these mechanisms to be designed and periodically reviewed through genuine engagement with the stakeholder groups they serve, rather than treated as a compliance checkbox. This approach shifts remediation from an afterthought to a core governance function with defined accountability and continuous learning built into its operation.
Why This Whitepaper Exists
Prevention and mitigation address exposure to harm that has not yet occurred. Remediation addresses harm that already has. Due diligence programmes routinely invest heavily in the first and treat the second as an afterthought — a grievance inbox that exists in policy but is rarely tested, and a vague commitment to “work with suppliers” that has no defined mechanism behind it. SPK DDMS2000:2026 treats remediation as its own dedicated, cross-cutting discipline at Section 10.18, distinct from prevention and mitigation, and this whitepaper sets out why that separation matters and what genuine remediation capability looks like.
Remediation is a distinct discipline from prevention and mitigation, and this standard treats it as such. Preventing harm and mitigating identified risk address exposure going forward; remediation addresses harm that has already occurred.
What the Standard Actually Says
Section 10.18 is cross-cutting: it applies across all modules in Sections 10.5 through 10.16 where adverse impact on a person, community, or the environment is identified, not solely within the supplier human rights and environmental due diligence module at Section 10.8. Section 10.18.1 requires the organisation to maintain a documented remediation policy that distinguishes its obligation according to its degree of involvement in an identified harm.
This distinction is drawn directly from the UN Guiding Principles' access-to-remedy pillar, and it matters because the correct response differs depending on which side of the line an organisation sits.
Organisation's relationship to the harm | Remediation obligation | Governing clause |
|---|---|---|
Caused the harm | Provide for, or cooperate in, remediation directly | Section 10.18.1(a) |
Contributed to the harm | Provide for, or cooperate in, remediation directly | Section 10.18.1(a) |
Directly linked to the harm through a business relationship, but did not cause or contribute to it | Use leverage to encourage the responsible party to provide remedy; assess and document the limits of that leverage | Section 10.18.1(b) |
The “directly linked” category is the one organisations most often get wrong — either by assuming no obligation exists because the organisation did not cause the harm, or by assuming full remediation responsibility regardless of actual influence. Section 10.18.1(b) requires neither extreme: it requires the organisation to use whatever leverage it genuinely has, and to document honestly where that leverage runs out, rather than either overstating its power to fix the problem or disclaiming responsibility entirely.
A Grievance Mechanism Built With the People It Serves
Section 10.18.2 requires a grievance mechanism meeting the effectiveness criteria recognised under the UN Guiding Principles — legitimate, accessible, predictable, equitable, transparent, and a source of continuous learning — extending the alert and grievance mechanism at Section 10.8.3 across all applicable modules, not confined to supplier human rights and environmental due diligence alone.
The clause goes further than most comparable standards on one specific point: the mechanism's design and periodic review must be based on genuine engagement and dialogue with the stakeholder groups it is intended to serve, and the organisation must document how their input shaped the mechanism — channel format, language, anonymity options, accessibility — rather than simply asserting that the effectiveness criteria have been met. A grievance mechanism designed entirely by the organisation, with no evidence that the people expected to use it were ever consulted on whether it actually works for them, does not satisfy this requirement.
Remedy Is Not One-Size-Fits-All
Section 10.18.3 requires the organisation to determine and document the range of remedy appropriate to the nature and severity of the harm — which may include an apology, restitution, rehabilitation, financial or non-financial compensation, prevention of further harm through changed practice, or cooperation with a judicial or non-judicial remedy mechanism. The clause explicitly prohibits assuming a single remedy type is adequate for all cases. An organisation whose remediation policy defaults to financial compensation regardless of what actually happened has not built the range of response Section 10.18.3 requires.
Closing a Case Properly, Not Just Quickly
Section 10.18.4 requires the organisation to track each remediation case from identification to closure, recording the harm identified, the remedy provided or facilitated, the affected party's engagement in determining the remedy, and the basis for considering the matter resolved. Critically, the clause prohibits closing a case solely on the basis that a payment or action was made, without evidence that the affected party considers the harm addressed, where feasible to obtain.
This is a materially higher bar than most organisational remediation practice operates to. A payment made and a case marked closed is not, on its own, evidence of remedy under this standard — the affected party's own view of whether the harm has actually been addressed is part of the record the organisation is required to keep.
Protecting the People Who Come Forward
Section 10.18.5 requires that no person who raises a grievance, seeks remedy, or participates in a remediation process be penalised, retaliated against, or disadvantaged as a result, consistent with the non-retaliation protections at Section 7.4.3 and Section 9.4.2. A grievance mechanism that is technically accessible but where those who use it face informal consequences will not generate the case volume, or the honest engagement, the rest of Section 10.18 depends on.
Feeding the Pattern Back Into the System
Section 10.18.6 requires the organisation to report remediation activity — case volume, remedy types provided, closure rates — as part of the performance monitoring at Section 12.1, and to escalate any pattern of recurring harm from the same subject or root cause to the corrective action process at Section 14.2, rather than treating each case as isolated. A supplier that generates repeated, unrelated grievance cases over time is showing the organisation something about that relationship the case-by-case view alone will not surface.
Section 10.18.7 connects remediation directly to regulatory consequence: where an authority requires evidence of remediation as a condition of restoring market access, licensing, or ceasing an investigation — including the return-to-market pathway under forced labour import regimes addressed at Section 10.9.6 — the organisation must maintain documentation sufficient to demonstrate the remedy was effective and sustained, not merely initiated.
Common Gaps Worth Checking
A grievance mechanism exists, but was designed entirely internally, with no documented stakeholder input into its format, language, or accessibility.
Remediation cases are closed once a payment is made, with no evidence the affected party considers the matter resolved.
The organisation's remediation policy does not distinguish between harm it caused or contributed to and harm it is only directly linked to — or assumes the same response applies regardless.
Remediation case data is not reported as part of performance monitoring, so recurring patterns from the same subject or root cause go unnoticed.
How Speeki Sentinel Certification Assesses This
Certification against SPK DDMS2000:2026 tests remediation case files directly against Section 10.18: whether the caused/contributed/directly-linked distinction was applied correctly, whether closure required evidence of the affected party's own view where feasible to obtain, and whether the grievance mechanism itself shows genuine evidence of stakeholder-informed design rather than an assumed-adequate default.
Speeki Sentinel is the certification product through which this assessment is delivered. Organisations may build and operate a genuine remediation capability independently of Sentinel; certification is a separate, optional step available once an organisation believes its capability 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
A due diligence management system that only ever looks forward — preventing and mitigating exposure to future harm — has no answer for the harm that has already occurred on its watch. Section 10.18 exists because access to remedy is not a lesser obligation than prevention; it is the obligation that determines whether the people actually affected by an organisation's activities experience the standard as something real, or as a document that was never really about them.