# Management reporting

{% hint style="info" %}
*This part of the iSHARE Trust Framework is considered normative and is therefore compliant with RFC 2119.*
{% endhint %}

The management reporting process describes the steps that parties MUST take to deliver management information about the use and working of the iSHARE network.

### Goal <a href="#managementreporting-goal" id="managementreporting-goal"></a>

The goal of the management reporting process is to monitor compliance to service level agreements, and to distribute info about the use of the iSHARE network.

### Responsibilities <a href="#managementreporting-responsibilities" id="managementreporting-responsibilities"></a>

Several parties have responsibilities and tasks in the management reporting process:

* The **Scheme Owner** is responsible for delivering its own management information on a quarterly basis, and to process received management information into a report that does not include commercially sensitive information;
* The **Data Space Governance Body** is responsible for delivering management information timely on a monthly basis to the Scheme Owner.
* The **Certified Party** is responsible for delivering management information timely on a monthly basis to the Data Space Governance Body for their data space.

### Sequence <a href="#managementreporting-sequence" id="managementreporting-sequence"></a>

1. On a monthly basis, Certified Parties and the Data Space Governance Body collect management information about:
   1. the use of the data space;
   2. compliance with the service level agreements.
2. Certified Parties and Data Space Governance Body deliver the collected management information to the Scheme Owner in compliance with the standard format and service level;
3. The Scheme Owner processes the received management information on compliance, and, if non-compliance is detected, follows the [warnings, suspension and exclusion process ](https://framework.ishare.eu/version-2.1/detailed-descriptions/operational/operational-processes/warnings-suspension-and-exclusion)to assess whether this is an incident or structural non-compliance;
4. The Scheme Owner verifies whether each party's management information on the use of the *Trust Framework* is correct:
   1. If correct, step 5 follows directly.
   2. If incorrect, a maximum of 5 working days are available for the party to rectify. If 5 working days are not enough, step 5 follows without the incorrect information;
5. Quarterly, the Scheme Owner processes and anonymises (if necessary) the management information on the use of the *Trust Framework* into a report containing:
   1. Number of Certified Parties (also compared to last month and this month previous years);
   2. Number of Adhering Parties;
   3. Other information deemed necessary (to be decided); If incorrect information was found and could not be rectified within 5 days in step 4, a description of the missing management information.
6. The Scheme Owner distributes the management report.


---

# Agent Instructions: 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:

```
GET https://framework.ishare.eu/version-2.1/detailed-descriptions/operational/operational-processes/management-reporting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.