Keep shared ESG actions linked to separate issue decisions

Divya Khatwani

Oct 14

5 min read

When one action supports two ESG issues, record the action once and link it to both. Keep the decision about each issue separate, because the same completed task can leave different questions unanswered.

This guide is for teams whose issue lists have grown into repeated task rows. It shows how to preserve the relationships between issues, shared actions and decisions. It is an internal record design, not a materiality assessment or a disclosure-approval procedure.

Separate the question, the work and the decision

Issue record: the precise question, affected population, source reference, current state and accountable issue owner. Keep one ID for the continuing question even when several tasks are created.
Action record: the promised work, one coordinating owner, due date, output reference and current task state. Contributors can be listed without creating another copy of the same task.
Decision record: the issue being decided, evidence considered, conclusion, remaining question, decision owner and date. Identify the action outputs used, but do not copy an action’s status into the issue decision.

Add an issue–action link for each relationship. Give the link a short explanation of what that action is expected to contribute to that issue. A link is a relationship, not another task. The four kinds of record can be separate sections of a small register; specialist software is not required.

GRI 3 distinguishes actions to manage impacts from information about their effectiveness. Its Disclosure 3-3 guidance also permits a shared management approach to be reported once when the covered material topics are clearly identified. That is reporting context, not a requirement to use this register. The ordinary data questions below are not asserted to be GRI material topics.

Follow a shared action through two issues

All records, roles, dates and results in this example are invented. Two sites are preparing an internal monthly electricity schedule. The team defines two narrow evidence questions; it is not deciding whether the sites have achieved an environmental target.

Fictional map: Q01 links to A01 and shared A03; Q02 links to A02 and A03. Three actions create four links. D01 resolves Q01; D02 keeps Q02 open. — Fictional issue map. A03 is one shared action with two links. Q01 is resolved by D01; Q02 remains open under D02. The complete example and limits are in the article.

Q01: Can Site A’s September schedule be supported by the twelve expected source files?
Q02: Can Site B’s September schedule be supported by its eight expected source files?

The team agrees three actions:

A01: Site A coordinator gathers and indexes its twelve source files.
A02: Site B coordinator gathers and indexes its eight source files.
A03: Reporting coordinator issues a shared index form for locating the source files. Both sites use the same form version.

Record four links: Q01 → A01; Q01 → A03; Q02 → A02; Q02 → A03. A03 appears in two links but remains one action with one owner and one output, form V2. Creating “A03 for Site A” and “A03 for Site B” would conceal that shared dependency.

For Q01, the A03 link means “organise Site A’s source references using V2”. For Q02, it means the same task supports Site B’s references. Neither link says that issuing the form supplies a missing source file.

Use the output without inheriting a conclusion

At the fictional review on 8 October, A01 and A03 are complete. Site A’s twelve files are present and its reviewer has checked the stated question. A02 remains open: Site B has supplied seven of eight expected files. The shared form exists for both sites, but the eighth B file is still missing.

D01, linked to Q01, records: “Resolved for the defined September source-file question; twelve expected files checked using index V2.” The decision identifies the files, reviewer and review date. It does not approve a public electricity disclosure or an emissions calculation.

D02, linked to Q02, records: “Open; source file B08 remains missing.” It assigns the follow-up to the B coordinator and retains the agreed next review date. D02 cites A03’s V2 output while explaining why it is insufficient to resolve Q02.

The register contains two issues, three actions, four issue–action links and two decision records. Two actions are complete, but only one of two issues is resolved under the stated test: 50%. Counting A03 twice would report three completed link rows out of four, instead of two completed actions out of three.

Both fractions can be reconstructed, but they measure different objects. Label any summary with the object being counted and the test applied. Neither 75% of linked rows nor 66.7% of actions complete means 75% or 66.7% of ESG issues have been resolved.

Keep priority separate from confidence

Q02 can be urgent because the schedule is due tomorrow while the missing file leaves confidence low. Q01 can have better evidence and a later deadline. Do not average urgency and evidence confidence into one unexplained green status. Record the next decision needed in words.

If A03 is delayed, its owner updates the action once. Use its two links to notify both issue owners about the affected work. Each issue owner decides the effect on that issue. One owner may have an adequate alternative record, while another cannot proceed.

When a shared output changes, inspect every linked decision

Suppose the team later finds that form V2 omitted the source-period field and replaces it with V3. Retain V2 and the reason for revision. Query the A03 links to find Q01 and Q02, then ask each decision owner whether the omission affects their evidence.

Q01 may remain resolved if the retained files and review already establish the correct period. Q02 may still be open for B08 and need the new field as well. Record the review outcome against each issue; do not automatically reopen or close every issue simply because the shared form changed.

Keep D01 and D02 as dated history. Add a new decision that references the earlier one when the conclusion changes. Updating the current-state field is useful, but overwriting the old explanation would remove the trail a later reviewer needs.

Make the next review easy to navigate

For each open issue, show its current question, linked actions, latest decision and next evidence request. For each shared action, show every linked issue owner. Check for an action with no issue, a link to a deleted ID, or a decision with no evidence reference before circulating the register.

This record design helps navigate relationships. Use the corrective-action closure guide when you need to test whether a process fix worked, and the management sign-off guide when you need approval for a disclosure. Urgent safety or legal concerns must follow the organisation’s immediate escalation route rather than wait for this register.

Primary source checked 14 October 2026. The model, IDs, record counts and example are original teaching material. Task status does not establish legal compliance, assurance, certification or completion of GRI reporting.