Use the framework disclosure requirement and related information when creating a metric from the ESG Explorer
We like the ability to directly create metrics from the ESG Explorer (when identifying a disclosure requirement as material, e.g.).
Right now, when one creates a metric using this approach, the new metric is created with a generic name (like "(Topic Name) - Metric (1)") and without any content except for the reference in the "Related ESG Content" field.
It would help if it populated these metrics with a bit more information already available from the framework, for example (possibilities):
- A default metric name based on the disclosure requirement
- A description copied from the requirement (and probably identified as such)
- Metric type and units from the requirement
The thinking is twofold. First, some of this information is directly related to, or implied by, the framework. Even while there is room for customization, it would save time and effort to start with the metric essentially "pre-configured" and just modify what you want. Second, as part of assessing materiality, it may be helpful to be able to quickly create a larger number of metrics in relatively quick succession and then come back later to configure further details. As it is, if you take that approach, the metrics are almost unrecognizable (e.g., by name) and one must re-open the ESG content reference to even remember what a metric is linked to or what it is supposed to represent. With a sensible automatically generated name and description, even if they are later customized/updated, you have a more usable set of starter metrics.
-
Hi Andrew! Just to clarify, are you referring to the ability to create a metric when connecting content in ESG Explorer to a metric?
Thanks!
0
Thanks for the great feedback, Andrew! I'll passed your idea on to the team, which is already looking at ways to improve connecting ESG Explorer content to ESG Program metrics in general (as well as other opportunities to automatically create metrics based on ESG Explorer content — but more on that later). Thanks again!
0
Thanks Steve Stegelin (and, yes, this is in reference to the behavior triggered by the "+ Add metric" button in the screenshot you shared).
0請登入寫評論。
評論
3 條評論