How Do I Describe Workforce Wellbeing Incidents in My Value Chain?

What is this section actually about?

This section is easy to confuse with your own internal workplace incidents, so it is worth being clear about the distinction upfront. This part of the report asks about incidents affecting workers in your value chain, typically at suppliers, communities impacted by your company, or consumers and end users of your product. Your own employees' workplace incidents belong in a different section.

For most SMEs, this section is primarily about suppliers. This could be a labour standards issue at a manufacturing partner, or a health and safety concern at a facility you source from. If your company has a simple, direct supply chain, or barely any physical supply chain at all, as with many software or professional services firms, this section may be short, and that is appropriate.

‍

‍

If you've identified no incidents, say so clearly

For many SMEs, particularly those with limited or low-risk supply chains, the honest answer here is that no incidents have been identified. That is a perfectly valid response, but it is stronger when paired with a brief note on how you would find out if something occurred. For example:

"No workforce wellbeing incidents affecting our value chain, communities, or end users were identified during the reporting period. Our supplier relationships are reviewed periodically, and any concerns raised would be investigated using the process described below."

This shows the absence of incidents reflects genuine monitoring, not simply a lack of visibility.

‍

If you have identified an incident, use a consistent structure

Where a genuine incident has occurred, most commonly a labour, health and safety, or wage-related issue at a supplier, describing it with a consistent structure makes the account far easier to follow and more credible. Useful elements include:

• What happened: A factual description of the incident.
• Where and with whom: Which supplier, location, and roughly how many workers were affected.
• How it was identified: Audit, grievance mechanism, worker complaint, internal review, or another route.
• Immediate response: What was done right away.
• Corrective actions required: The specific changes demanded, ideally with deadlines.
• Support provided: What you did to help the supplier or affected workers actually fix the problem, not just comply on paper.
• Verification and follow-up: How you confirmed the corrective action actually worked.
• Current status: Closed, or under ongoing monitoring.
• Lessons learned: What this revealed about your own due diligence or purchasing practices.

This structure works whether the incident is a machine safety issue, excessive working hours, wage payment delays, or something else entirely.

‍

How the incident was identified matters

It is worth being specific about how you found out about the issue, whether through a scheduled audit, a worker grievance hotline, an anonymous tip, a routine business review, or something else. This detail matters because it shows whether your due diligence is proactive, such as regular audits catching issues before they escalate, or reactive, such as only learning about problems when something goes wrong or a worker speaks up. Both are legitimate ways of identifying issues, but naming the actual mechanism shows the process is real, not assumed.

‍

Look at root causes, not just the immediate violation

A stronger disclosure looks past the immediate violation to understand what allowed it to happen. It is often useful to distinguish:

• The immediate cause: What directly happened, like missing machine guards.
• Contributing factors: Conditions that made it more likely, such as cash flow pressure or tight deadlines.
• Your own role, where relevant: Whether your own purchasing practices, like tight lead times or cost pressure, contributed to conditions that led to the violation.

This last point is particularly important and often overlooked. If your company's own ordering patterns or pricing contributed to a supplier's difficulties, acknowledging that honestly is far more credible than presenting the incident as entirely the supplier's failing.

‍

Corrective action should include real support, not just demands

A list of requirements alone can look like a compliance checkbox exercise. A stronger response also explains what your company did to actually help the supplier fix the problem. This could involve financial support, connecting them with technical expertise, adjusting your own order timing or pricing, or providing training resources. This distinction matters because sustainable fixes usually require more than a demand letter; they often need genuine support alongside it.

‍

Verification shows the fix actually worked

Describing corrective actions without confirming they were followed through leaves a reader unsure whether anything really changed. Where possible, briefly note follow-up checks, such as a later audit, worker interviews, or ongoing monitoring, that confirmed the issue was actually resolved, and whether the case is now closed or still being monitored.

‍

Summarising across multiple incidents

If your company has identified more than one incident in a reporting period, it can help to summarise patterns across them. This could include common root causes, total workers affected, or how many cases are closed versus still being monitored. This is not necessary if you have just one incident or none, but it can show a company learning at a broader level when there are enough cases to draw a pattern from.

‍

Keep it proportionate to your business

Not every SME has the visibility or scale to conduct formal third-party audits or maintain grievance hotlines across a global supply chain. If your company has a small number of direct suppliers, a proportionate description might simply explain how you communicate with them directly, what you would do if a concern were raised, and any informal checks you already carry out. The goal is an honest description of your actual due diligence, not a copy of a large enterprise's supply chain compliance programme.

‍

Common mistakes to avoid

• Confusing this with internal workplace incidents: This section is about value chain, community, or consumer impacts, not your own employees.
• Listing corrective demands without support: Requirements alone can look punitive rather than collaborative. Explain what help was actually provided.
• Skipping verification: Without follow-up, a reader cannot tell whether the corrective action actually worked.
• Ignoring your own contribution: If your purchasing practices played a role, acknowledging this honestly is more credible than presenting the incident as solely the supplier's fault.
• Fabricating incidents or detail: If your company genuinely has no incidents to report, a brief, honest statement is far better than an invented case study.

‍

How Wardn helps

Wardn provides a structured template with example wording to help you describe value chain incidents consistently, whether you're reporting a specific case or explaining your process when none has occurred. The same structure can be reused each year, making it easier to track patterns across incidents and show how your due diligence process develops over time.

‍

Frequently asked questions

Does this section cover our own employees' workplace accidents?

No. This section covers workers in your value chain, typically suppliers, affected communities, or consumers and end users. Your own employees' workplace incidents belong in a separate section of the report.

What if we have no visibility into our suppliers' labour practices?

Describe that honestly, along with any steps you do take, even informal ones, like direct communication with key suppliers. Acknowledging limited visibility is more credible than implying a level of oversight that doesn't exist.

How should we describe corrective action if we're a small company with limited leverage over suppliers?

Describe what you realistically can do, such as raising the issue directly, requesting changes, or reconsidering the relationship if problems aren't addressed. It doesn't need to match a large enterprise's formal corrective action process to be a genuine response.

Do we need to name specific suppliers when describing an incident?

This is a business decision depending on your relationship and any confidentiality considerations, but describing the type of supplier, general location, and nature of the incident is usually sufficient even without naming the company specifically.

What if we identified an issue but it's still being resolved?

Describe it as under active monitoring, explaining what's been done so far and what verification is still pending. It is fine for a case to be open rather than closed, as long as you're transparent about its current status.

‍