Supply chain due diligence software reads every supplier code of conduct, certificate, and audit on arrival - flagging risk before a CSDDD finding.
Social supply chain due diligence is the practice of hearing supplier and worker voice directly and keeping it on a stable record, so a social concern is review evidence as it arrives rather than assumed from a questionnaire. This page covers the first-party social layer; it is not a legal compliance screening, sanctions check, or audit-certification service. Sopact holds that voice on the Stakeholder Thread, so a finding traces to the worker or supplier who reported it.
Watch · 2 min
Portfolio reporting from every source
Every source in, every investor's report out. CRM, diligence, investee surveys, documents and email — one connected record, personalized reporting per recipient.
Most supply chain due diligence rests on self-reported checklists and periodic audits, which capture what a supplier chooses to declare and little of what workers actually experience. When worker feedback is collected at all, it lands in raw text no one reads until an incident forces it. The gap is that first-party voice exists but is never review evidence as it arrives or held on a record.
Key takeaways
Sopact keeps the supplier profile, diligence evidence, documents, commitments, risk signals, corrective actions, and follow-up on one governed record. A portfolio view can show exposure while opening any finding back to the supplier evidence behind it.
A social audit is a point-in-time snapshot of what a supplier presents on the day, and a self-reported questionnaire captures what a supplier chooses to declare. Neither reads the continuous first-party voice of the workers whose experience is the actual subject of the diligence. Between audits, a concern can build for months in feedback that no system reads on arrival or ties to the supplier record.
Sopact keeps supplier and worker voice on the Stakeholder Thread under a stable ID, read the moment it arrives, so a social signal attaches to the supplier and can be followed over time. Where these signals feed formal risk work, the practice is on ESG risk management, and the direct-collection practice on stakeholder engagement.
Sopact reads the social, first-party layer of supply chain due diligence; it does not perform legal compliance screening, sanctions or watchlist checks, or issue audit certifications. Those are distinct, often statutory services with their own providers, and Sopact does not replace them. What it adds is the worker and supplier voice that audits and screenings do not capture: the lived experience behind a compliance status.
Used that way, Sopact complements a diligence program rather than standing in for its legal components, feeding named, traceable first-party signals into the process a team already runs. The feedback-collection side is covered on feedback tools.
Supply chain teams lean on audit platforms and self-reported supplier questionnaires, social listening or reputation tools such as Meltwater or Brandwatch for external signals, pulse-survey tools such as Officevibe or CultureAmp for a periodic worker read, or a Power BI and Excel stack over exports. Each captures part of the picture, and each reads either a declaration, third-party chatter, or an anonymous snapshot, so none holds continuous first-party worker voice on a supplier record.
a practical buying check that sorts the approach: ask the system to show every worker concern raised at one supplier this quarter in the workers' own words, tied to that supplier's record. An audit or listening tool cannot. Sopact answers from the Stakeholder Thread, because each concern sits on the supplier record that received it.
Collect first-party worker and supplier voice on a stable supplier record and read it on arrival on the Stakeholder Thread, rather than relying only on a periodic audit or a self-reported checklist. The table sets an audit-only approach against an evidence-backed one.
| The question | Audit-only | Evidence-backed |
|---|---|---|
| Whose account? | Supplier declares | Worker and supplier voice |
| Read when? | Point-in-time audit | On arrival, continuous |
| Held on a record? | No, a snapshot | Yes, stable supplier ID |
| Catches issues between audits? | No | Yes, on the Thread |
See formal risk work on ESG risk management, or direct collection on stakeholder engagement.
Counting meetings held and emails sent measures your activity, not your stakeholders’ experience of it. The value of a stakeholder read is highest while a relationship can still be repaired and a plan still adjusted, not in a year-end summary. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment input arrives, improve while there is still time to act.
The Loop is also what makes a stakeholder claim defensible: every theme and trust figure traces back to the responses it came from, the standard detailed in Loop traceability, so “the community’s top concern is access” is backed by the comments, not an impression.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
Use one controlled supplier example with multiple sites, audits, certificates, worker evidence, a social-risk finding, conflicting information, a response, and remediation status. Confirm legal scope with qualified counsel.
Due-diligence teams should update supplier scope, social-risk definitions, evidence rules, review status, and remediation ownership without rebuilding spreadsheets.
How to test it
Supplier, site, audit, certificate, contract, worker evidence, finding, response, and remediation should stay on the correct record.
How to test it
The workflow should handle all in-scope suppliers, long audits, certificates, worker responses, documents, and updates.
How to test it
The team should see findings, responses, corrective actions, repeated issues, closure, and recurrence over time.
How to test it
Worker and community evidence should retain confidentiality, context, and exact passages while protecting people from retaliation.
How to test it
Codes, contracts, audits, certificates, policies, and remediation files should retain source, date, validity, and permissions.
How to test it
An assistant may prepare evidence checks and cited signals but should not make legal-compliance, sanctions, certification, or supplier-termination decisions.
How to test it
A reviewer should reproduce one finding from source through response and remediation.
How to test it
Start with a worker or supplier concern that requires follow-up. A defensible workflow should connect the original voice to the supplier, applicable requirement, investigation, corrective action, and later evidence that the condition changed.
| Check | What must be inspectable |
|---|---|
| Voice | Can an authorized reviewer open the exact worker or supplier evidence? |
| Requirement | Is the applicable policy, standard, or due-diligence requirement explicit? |
| Remediation | Are the owner, action, due date, and evidence of completion recorded? |
| Change | Does follow-up show whether the underlying condition improved? |
It is the practice of hearing supplier and worker voice directly and keeping it on a stable record, review evidence as it arrives rather than assumed from a checklist. Sopact holds that voice on the Stakeholder Thread, so a finding traces to the worker or supplier who reported it.
No. Sopact does not perform legal compliance screening, sanctions or watchlist checks, or audit certification. It reads the first-party social layer, keeping worker and supplier voice on the Stakeholder Thread, and complements a diligence program rather than replacing its legal parts.
A social audit is a point-in-time snapshot of what a supplier presents on the day, and it misses continuous worker experience. Sopact reads first-party worker voice on arrival on the Stakeholder Thread, so a concern surfaces between audits while it can still be acted on.
Sopact collects first-party worker and supplier feedback and keeps it on a stable supplier record, read the moment it arrives. Each concern is tied to the supplier on the Stakeholder Thread, so experience is measured rather than assumed from a declaration.
No. Certification and formal audit are separate services Sopact does not provide. Sopact adds the first-party worker and supplier voice behind a compliance status, kept traceable on the Stakeholder Thread, and feeds it into a team's existing process.
Yes. Every concern is tied to the record and the comment behind it on the Stakeholder Thread, so a social finding can be re-checked against the exact words a worker used rather than taken on trust, within your confidentiality rules.
Because Sopact reads first-party feedback continuously on the Stakeholder Thread, not only at audit time. A concern building at a supplier surfaces the quarter it is raised, tied to that supplier's record, instead of waiting for the next audit.
Sopact provides the first-party worker and supplier layer that feeds formal risk work. The wider practice is on the ESG risk management page, and Sopact keeps each contributing signal traceable on the Stakeholder Thread.
Next: see formal risk work on ESG risk management, or direct collection on stakeholder engagement.
