> For the complete documentation index, see [llms.txt](https://isbm.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://isbm.savimbo.com/methodology/zh-cn/jian-ce-ji-hua/jian-ce-bao-gao.md).

# 监测报告

监测期内结果摘要

生物多样性信用计算为自动化，并根据观测数据生成报告。 

监测周期和报告频次最短可为1年，最长可为5年，且必须包括： 

* ……的变化 [基线评估](/methodology/zh-cn/ji-xian-ping-gu.md) 如适用
* ……的适应性变化 [实施计划](/methodology/zh-cn/xiang-mu-miao-shu/shi-shi-ji-hua.md)
* 项目边界的任何变化（例如，从一个 [组团项目](/methodology/zh-cn/xiang-mu-miao-shu/xiang-mu-bian-jie/zu-qun-xiang-mu.md)）扩展为.kml格式
* 利益相关方或项目治理的任何变化
* 用于指示物种观测的项目原始数据安全上传
* 当前年份与项目实施前几年之间，信用核算区与泄漏管理区面积（公顷）比较报告（[项目区域](/methodology/zh-cn/xiang-mu-miao-shu/xiang-mu-bian-jie/bcp-de-kong-jian-jie-xian.md#project-area-data-layer))
* 理想情况下，公开可核证的指示物种观测（即iNaturalist）

BCP应在监测报告中包括一份简要的定性总结，概述每个核证周期内开展的活动及其在生物多样性保护方面的有效性。


---

# 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://isbm.savimbo.com/methodology/zh-cn/jian-ce-ji-hua/jian-ce-bao-gao.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.