> For the complete documentation index, see [llms.txt](https://docs.bis.org/ellipse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bis.org/ellipse/background/understanding-data-needs-of-stakeholders.md).

# Understanding Data Needs of Stakeholders

A move to machine-executable digital regulatory reporting is closely linked with the need for data standards. There are significant benefits in the medium- to long-term for financial institutions and authorities to move towards a digital reporting framework, for the reasons highlighted in this background section.  

Nevertheless, the initial investment and costs needed to achieve this outcome can steer decisions based on business incentives and risk appetite. While data standards initiatives would ultimately benefit from – and require – financial institutions and authorities to adopt a greenfield approach, the perceived scale of such an exercise could also deter stakeholders from committing to its implementation.  

We propose that in the absence of global or national data standards, alternative options could be explored as a first step to bringing stakeholders closer to a common understanding of data needs. These options can include: 

1. Bringing together authorities that have a mandate to collect data, to see if there are similarities or commonalities in the type of data being collected. <br>
2. Engaging with industry on their use of data models and taxonomies for that specific product to explore wider extensibility.  <br>
3. Establishing small working-level projects using a narrowly scoped and specific use case and agreeing common data attributes and their definitions “in principle”. <br>
4. Exploring ways in which the requirements for the reporting of those data can be published in programming languages.&#x20;


---

# 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.bis.org/ellipse/background/understanding-data-needs-of-stakeholders.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.