> 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/completing-gresb-assessments/completing-the-assessment/2026-asset-assessment/nzif-alignment-module/nz4-emissions-performance.md).

# NZ4: Emissions Performance

1. <mark style="color:$primary;">**Does the asset see emissions decline consistent with targets set to converge the asset with a net-zero pathway?**</mark>

<details>

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

This question asks whether observed and expected emissions performance is broadly consistent with the asset’s stated net-zero targets and pathway.

</details>

<details>

<summary><strong>Input</strong>: How do I answer this question?</summary>

Answer “**Yes**” if emissions performance to date and expected future performance are consistent with the targets and pathway used to set the net-zero target.&#x20;

Answer “**No**” if emissions performance is not yet consistent with the stated targets or pathway.&#x20;

</details>

2. <mark style="color:$primary;">**What emissions scopes does this claim regarding emissions performance cover?**</mark>

<details>

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

This question intends to determine what scopes the emissions performance claim covers.

</details>

<details>

<summary><strong>Input</strong>: How do I answer this question?</summary>

Select the Scope option (“**Scopes 1 and 2**” or “**Scopes 1, 2, and material Scope 3**”) that reflects where emissions data exist and a quantitative reference point is available.&#x20;

Where Scope 3 targets are qualitative, emissions performance would generally be expected to cover Scope 1 and Scope 2 only.&#x20;

</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 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://guides.gresb.com/completing-gresb-assessments/completing-the-assessment/2026-asset-assessment/nzif-alignment-module/nz4-emissions-performance.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.