Governance
Identify responsible officers, board oversight, and cross-functional committees. Describe decision-making authority, reporting lines, and how often governance bodies review modern slavery risk and remediation outcomes.
A clear HR Modern Slavery Statement demonstrates organizational awareness of modern slavery risks, supports supplier due diligence, helps meet stakeholder and investor expectations, and documents controls for audits. It reduces legal and reputational exposure and provides a reference point for training and remediation efforts.
HR, compliance, procurement, and legal teams typically lead preparation of the HR Modern Slavery Statement for workforce and supplier oversight.
Ensure cross-functional review and approvals so the statement reflects operational realities and accountability across departments.
| Document Workflow Field Name and Use | Configuration settings and recommended options for each field |
|---|---|
| Upload the source statement file (PDF or DOCX) | Auto-detect fillable fields and preserve layout |
| Map fields to HR data sources and tables | Use Magic Fields or manual mapping to populate templates |
| Define signer roles and review sequence | Set sequential reviewers and signature order for approvals |
| Choose signer authentication and verification methods | Select email, SMS, KBA or stronger options based on risk |
| Configure retention, export, and archival settings | Auto-archive signed PDF/A to secure storage with audit log |
Digital signing and storage should meet security and accessibility needs for the HR Modern Slavery Statement.
Conduct review at least once per fiscal year; set fixed calendar date.
Allow two to four weeks for legal and board review before publication.
Require corrective actions within 30 to 90 days after a reported breach.
Publish online within 30 days of board approval if external disclosure required.
Preserve records from statement effective date for retention period.
Identify responsible officers, board oversight, and cross-functional committees. Describe decision-making authority, reporting lines, and how often governance bodies review modern slavery risk and remediation outcomes.
Explain methodology for identifying high-risk operations and supplier tiers, risk scoring criteria, data sources used, and how frequently assessments are updated to reflect evolving conditions.
Detail onboarding checks, contractual clauses, audit processes, escalation triggers, and expectations for corrective action including timelines and consequences for noncompliance, plus monitoring and documentation requirements.
Summarize employee and contractor training programs, frequency, training materials, target audiences, and how training completion and effectiveness are measured, including assessment methods and records retention for proof of compliance.
Describe anonymous reporting mechanisms, whistleblower protections, internal investigation procedures, and how reports are documented and escalated, along with expected response timelines and confidentiality safeguards, plus external reporting triggers.
Outline steps for addressing confirmed issues, timelines for corrective action, supplier termination thresholds, and monitoring to verify remediation effectiveness, including recordkeeping and follow-up audits and performance metrics.
A mid-size manufacturer created a statement after supplier mapping revealed high-risk sourcing in overseas subcontractors; the HR team led remediation planning.
A regional healthcare network incorporated HIPAA-aligned privacy controls into its HR Modern Slavery Statement to address contractor labor and vendor risk in clinical supply chains.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |