> For the complete documentation index, see [llms.txt](https://docs.orbitfin.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbitfin.ai/part-3-use-cases/3.7-esg-and-stewardship.md).

# 3.7 ESG and stewardship

The ESG and stewardship use cases cover the sustainability and engagement work that sits alongside fundamental research — and they have a distinct character, because some of them carry a compliance dimension that the others do not. Producing a regulatory disclosure or a standards-aligned scorecard is not just useful research; it is output a firm may have to stand behind to an auditor or a regulator. That makes the traceability established in 2.9 not a convenience here but a requirement: every figure traceable to its source, the whole path auditable after the fact. These use cases draw on the same connected data and the same backbone as everything else — ESG is not a separate system, but the same companies seen through a sustainability lens.

**17 · SFDR PAI reporting.** What it produces is the principal adverse impact data assembled across a portfolio in the form the SFDR disclosure regime calls for — gathering the required indicators across holdings into a structured, sourced output ready to feed a firm's reporting. The outcome is that a reporting obligation that is otherwise a heavy, manual collation exercise becomes largely assembled by the platform, with each data point traceable to where it came from. It runs naturally on the reporting cycle. On the value chain it is access and extraction in service of a structured deliverable. A necessary note on accountability: Orbit assembles and sources the data, but the firm remains responsible for what it discloses — the platform supports the reporting and shows its work; the sign-off stays with the firm. Run it against the standard indicator set, or customise it to your firm's reporting template and methodology.

**18 · Controversy monitoring.** What it produces is a standing watch for ESG controversies across a portfolio or universe — surfacing the incidents, allegations, and developments that bear on the sustainability profile of held names, tied to the right company through the entity master. The outcome is that reputational and ESG risk is caught as it emerges rather than discovered late, across the whole book at once. It is an automate-mode use case by nature, running continuously. On the value chain it is access and extraction with a layer of judgment about materiality. Run it on Orbit's sense of what constitutes a controversy, or define the categories and severity that matter to your mandate.

**19 · SASB scorecard.** What it produces is a sustainability scorecard for a company built around the industry-specific metrics that the SASB standards identify as financially material for its sector — drawn from the company's own disclosures and organised against the framework. The outcome is a consistent, framework-aligned ESG read on a company, comparable across a universe because it is produced the same way each time. It runs on demand for a single name or on a schedule across a universe. On the value chain it spans extraction into analysis. Run it on the standard framework, or adapt the metric set and weighting to your firm's own ESG methodology.

**20 · Engagement priority list.** What it produces is a ranked view of where stewardship attention is most warranted — the holdings where engagement would matter most, on the issues where it would matter most, prioritised across the portfolio. The outcome is that a stewardship team directs its finite engagement capacity to where it can have the most effect, rather than spreading it evenly or reacting to whatever surfaces. It runs as a standing list, recomputed as circumstances change. On the value chain it reaches toward decision support — surfacing where to engage and why, with the evidence attached, while the decision to engage and how stays with the team. It is, in effect, the stewardship counterpart to the portfolio attention list in 3.5. Run it on Orbit's prioritisation, or shape what "warrants engagement" means for your stewardship approach.

What sets this group apart is the audit dimension. Two of these — SFDR PAI reporting and the SASB scorecard — produce output measured against external frameworks, where being able to show the source of every number is the difference between a deliverable a firm can file and one it cannot. This is where the platform's grounding in primary sources, kept traceable end to end, stops being a quiet virtue and becomes the point. The other two — controversy monitoring and the engagement priority list — mirror use cases seen elsewhere in the library (the standing watch, the attention list), applied to the stewardship side of a firm's work. Together they let a firm run its sustainability and engagement research on the same foundation, with the same rigour, as its fundamental research — rather than treating ESG as a separate exercise on separate tools.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.orbitfin.ai/part-3-use-cases/3.7-esg-and-stewardship.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.