> For the complete documentation index, see [llms.txt](https://guides.gresb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.gresb.com/publicdisclosure/completing-the-assessment/2026-public-disclosure-guidance/operational-performance/d19-waste-data.md).

# D19: Waste Data

<table data-column-title-hidden data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><i class="fa-bullseye">:bullseye:</i> Maximum Score</td><td><strong>3 points</strong></td><td></td><td></td></tr><tr><td><i class="fa-building-columns">:building-columns:</i> Pillar</td><td><strong>Environmental</strong></td><td></td><td></td></tr><tr><td><i class="fa-tag">:tag:</i> Topic</td><td><strong>Implementation &#x26; Measurement</strong></td><td></td><td></td></tr></tbody></table>

***

**Has the entity disclosed waste data of its portfolio?**

{% columns %}
{% column width="66.66666666666666%" %}

<figure><img src="https://content.gitbook.com/content/uN8Fu5f8c1NP0GYJmR6I/blobs/6GpsVODhDG22nqRGQEjk/Screenshot%202025-10-29%20at%2011.32.05%E2%80%AFam.png" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="33.33333333333334%" %}

{% endcolumn %}
{% endcolumns %}

## Assessment Instructions

<details>

<summary><strong>Intent</strong>: What is the purpose of this indicator?</summary>

Disclosure of waste data provides investors with valuable insights into the environmental impacts investment portfolios have.

</details>

<details>

<summary><strong>Input</strong>: How do I complete this indicator?</summary>

Select yes or no. If yes, disclose where the online information can be found.

### Terminology

**Disclosure**

> The act of making information or data readily accessible and available to all interested individuals and institutions. Disclosure does not need to be public, but must be external to the reporting entity and cannot be an internal and/or ad hoc communication within the participating entity.  &#x20;

**Waste production data**

> Data obtained through monitoring the waste production associated with the portfolio. The operational waste production of buildings leads to substantial environmental impact. Monitoring waste data is an important basis for reducing this impact.

</details>

<details>

<summary><strong>Validation</strong>: What evidence is required?</summary>

**Evidence:** URL. Ensure that the hyperlink is not outdated and the relevant page is directly accessible. It is possible to provide multiple hyperlinks.

Best practice disclosures would split up waste production per property type and disposal route and clearly indicate for which percentage of assets data is disclosed/available

</details>

## Scoring

<details>

<summary><strong>Scoring</strong>: How does GRESB score this indicator?</summary>

The answer options are validated by using the hyperlink(s) collected by GRESB or provided by the constituent. Points are contingent upon the validity of the disclosure.

</details>

***

<details>

<summary><em>References</em></summary>

EPRA Best Practices Recommendations on Sustainability Reporting, 3rd version, (September 2017): 5.2, Coverage

RobecoSAM Corporate Sustainability Assessment (2017): 4.2.5, Waste

GRI Sustainability Reporting Standards, (2016): 306-2

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guides.gresb.com/publicdisclosure/completing-the-assessment/2026-public-disclosure-guidance/operational-performance/d19-waste-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
