> 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/id/rencana-pemantauan/laporan-pemantauan.md).

# Laporan pemantauan

Ringkasan hasil selama periode pemantauan

Perhitungan kredit keanekaragaman hayati dilakukan secara otomatis dan menghasilkan laporan dari data observasi.&#x20;

Periode pemantauan dan laporan dapat sesering 1 tahun, dan paling jarang 5 tahun, dan harus mencakup:&#x20;

* Perubahan dalam [penilaian garis dasar](/methodology/id/penilaian-garis-dasar.md) jika berlaku
* Perubahan adaptif dalam [Rencana pelaksanaan](/methodology/id/deskripsi-proyek/rencana-implementasi.md)
* Setiap perubahan pada batas proyek (seperti penskalaan dari suatu [Proyek gabungan](/methodology/id/deskripsi-proyek/batas-proyek/proyek-gabungan.md)) dengan format .kml
* Setiap perubahan pada pemangku kepentingan, atau tata kelola proyek
* Unggah aman data mentah proyek untuk observasi spesies indikator
* Laporan perbandingan area Pemberian Kredit vs area pengelolaan kebocoran dalam hektare untuk tahun berjalan vs tahun-tahun sebelumnya dari pelaksanaan proyek ([Area proyek](/methodology/id/deskripsi-proyek/batas-proyek/batas-spasial-bcp.md#project-area-data-layer))
* Idealnya observasi spesies indikator yang sudah divalidasi secara publik (misalnya iNaturalist)

BCP harus mencakup, dalam laporan pemantauan, ringkasan singkat kualitatif tentang kegiatan yang dilakukan selama setiap periode verifikasi dan efektivitasnya dalam hal konservasi keanekaragaman hayati.


---

# 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/id/rencana-pemantauan/laporan-pemantauan.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.
