Stakeholder and value-chain mapping

Stakeholder mapping begins with the organization's relationships, not a generic list of employees, customers, and community. The consultant maps value activities from inputs to end use and asks at each node who is affected, who knows what the system misses, and who can influence the decision. A rights-holder who may bear harm is distinguished from a commercially powerful stakeholder; weak influence does not make an impact unimportant. Indirect relationships that connect a product or service to impacts beyond operational ownership are also identified.

The map combines relationship, impact or dependency, location, and available knowledge channel. A tier-two supplier may carry labor risk absent from direct purchasing records. A nearby community may observe water change before an annual indicator. A temporary worker may avoid a channel controlled by a supervisor. Engagement is therefore not ranked by contract size alone. Risk determines depth of inquiry, while accessibility shapes the channel, with confidentiality and retaliation safeguards where needed.

The engagement plan distinguishes listening, consent, and partnership. An interview provides information but does not automatically transfer decision authority. Good consultation explains purpose, use of comments, and what the organization cannot change, then reports the result back. It need not promise every requested outcome, but should show how evidence affected the decision. Do not collect personal data unnecessary to analysis. If the intermediary is a source of fear, use an independent channel or safe sample instead of maximizing response rate at the cost of safety.

A node matrix contains product or service, relationship type, location, affected group, risk signal, and knowledge quality. A signal is not a verdict; it identifies the next question. Compare contracts, audits, complaints, and interviews, checking whether apparently separate records derive from one source. Mark blind spots such as informal labor or product end of life. Rather than claiming value-chain coverage, report the share of spend or volume, tiers reached, and what remains unknown.

Leverage analysis distinguishes theoretical capacity from capacity actually used. A long contract, purchasing volume, or collective action may create leverage, but its existence does not demonstrate results. Record action, date, expected outcome, and consequence of no improvement. Immediate termination can end a relationship while worsening worker harm, so compare prevention, use of leverage, and remedy, except where safety or applicable rules require urgent suspension. Continued engagement must not become an excuse for inaction.

The communication map assigns an owner and return point. Suppliers know what data are requested and why; rights-holders know how to comment and what confidentiality protection applies; procurement knows when to escalate. Evaluate engagement quality, not meeting count: did the channel reach the most exposed groups, change a decision, address retaliation risk, and return an answer? If not, the completed calendar does not make the activity effective engagement.

Update the map when a supplier, country, product design, distribution model, or complaint signal changes. Preserve versions so coverage movements can be explained. A useful measure combines coverage and priority, such as the proportion of high-risk-category spend subject to suitable verification together with unresolved severe nodes. Spend coverage alone is insufficient because a small node may carry high severity. At delivery, state that the map supports decisions; it is not proof that the value chain is impact-free.

Value-chain lab: the consultant selects one product and traces it from raw material through use and end of life. At every node the map records the activity, location, business relationship, affected group, available leverage, and existing evidence. A direct supplier and a remote mine are not treated as equivalent, but the mine is not erased because there is no direct contract. Control, influence, and linkage are distinguished, after which the suitable engagement route is chosen: a worker interview, purchasing records, incident data, or dialogue with an independent community representative.

The map is challenged with a deliberate-absence test. Who is missing because access is difficult? Who could face retaliation for speaking? Who can represent future generations or ecosystems that have no direct voice? The plan adds safe channels, reasonable compensation for time, interpretation, and separation from management where needed. Meeting counts are not evidence of meaningful engagement; the record shows how input changed a diagnosis or decision, or why it did not. Conflicting testimony is retained and investigated rather than erased through a numerical vote.

The delivery pack contains a numbered value-chain map, a stakeholder register showing interest, exposure, and influence, an engagement plan with owners, timing, and safeguards, and a gap memo. Procurement, operations, and a reviewer independent of the examined relationship test it. Failure signals include stopping at tier one, using a vague category such as “community,” consulting only after the decision, or promising confidentiality that cannot be protected. Quality is demonstrated when every contact has a defined question, participant identity is safeguarded, and new evidence causes the map to be revised rather than forced into the original picture.