ESG Programme Issue Log
This is a practical guide to building a issue log for an esg programme project — a register of problems that have occurred and need resolving, adapted to the realities of delivering an environmental, social and governance programme.
What a Issue Log is
A issue log is a register of problems that have occurred and need resolving. For the full concept and how it works in general, see Issue Log. On an esg programme project it plays the same role, tuned to this kind of work.
Why it matters for an ESG Programme project
ESG Programme projects live or die on delivering an environmental, social and governance programme. A well-built issue log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how esg programme projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
ESG Programme-specific considerations
Tailor the issue log to the risks that most often derail esg programme projects:
- Data availability
- Evolving standards
- Stakeholder scrutiny
Example
On a real esg programme project, the issue log would be shaped by delivering an environmental, social and governance programme. In particular, it should explicitly account for the project’s biggest risks — data availability, evolving standards, stakeholder scrutiny — rather than treating them as afterthoughts.