Map activities, value chain and affected stakeholders

Do not begin a sustainability topic list with the unqualified question, “What matters to you?” The answer depends on whom you ask and can miss impacts beyond the organization's fence. First map activities and business relationships: what the organization purchases, what it does on site, how its product or service reaches users, and what happens during use and after use. At each stage identify people or environmental systems that might be affected, then seek initial evidence of actual or potential impacts. GRI 3 places this within understanding an organization's context and identifying impacts across activities and business relationships. The map organizes inquiry; an item on it is not automatically a material topic.

Consider a hypothetical cooling-appliance maker. Upstream there are metals, refrigerants, suppliers and transport workers. Within the factory there are energy, water, employees and maintenance contractors. Downstream, appliances consume power in use and refrigerant may be lost or recovered during repair and at end of life. A map limited to factory invoices would miss the use phase. Yet one cannot claim its impact is large without quantities, usage patterns, life spans and electricity context. The purpose is to locate data requests and potentially affected parties before judging significance.

Separate a stakeholder who uses information from a person who experiences an impact. An investor or customer may request disclosure, while workers at a subcontractor may bear an impact without any direct channel to the company. Use two columns: users of the decision or disclosure and parties potentially affected. Some parties belong in both, but merging them can make voice or purchasing power a proxy for severity. In this example procurement owns the supplier contract, supplier workers may be affected, and a union or local organization may help reveal conditions. Silence in a complaints register does not establish absence of harm; examine whether people can safely use the channel.

For each impact hypothesis make a five-field record: value-chain stage; activity or relationship; who or what may be affected and how; initial evidence; and verification gap. For instance: “Appliance end of life; contracted service network; possible refrigerant loss; recovery logs from two contractors; third contractor's log absent.” That wording does not assert that the third contractor released gas. It is more actionable than an unsupported line reading “climate,” because the verification path is visible. Distinguish a direct record, such as a measurement or injury log, from a signal, such as a report or complaint, and from an assumption still to test. Do not aggregate quantities from incompatible periods or boundaries.

Stakeholder interviews need a purpose. Are you trying to detect an impact absent from existing records, assess its severity, or test whether a remedy works? Ask an open question and then request a concrete event, time and place without steering the interviewee toward the organization's preferred answer. Handle sensitive personal information under the organization's rules. Five interviewees describing heat on an evening shift provide a signal to inspect temperature records and work patterns, not a prevalence estimate for all workers. If management and workers disagree, preserve both accounts and identify a test; an average of conflicting accounts would hide the question.

Mark the map's limits. A business relationship may involve a supplier or distributor outside the organization's operational control. A value-chain impact link is not by itself a legal liability conclusion or an inventory consolidation decision. Record what the organization knows, its potential influence, and who owns investigation or remedy. Escalate a high-stakes allegation, such as a supplier rights violation, to the appropriate team before public wording, while preserving evidence and not suppressing the signal. The specialist produces a reviewable impact register rather than a legal verdict.