> For the complete documentation index, see [llms.txt](https://sexytrees.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sexytrees.savimbo.com/appendices/fpic.md).

# FPIC: Free, Prior, and Informed Consent in Sexy Trees project design

Effective free, prior, and informed consent (+ongoing which we really like!)

**Free, Prior, and Informed Consent (FPIC) is not an optional step, but a mandatory one.** &#x20;

For certifiers and buyers of any climate project involving grassroots communities, it's also a compliance and legal risk issue. In short, do it. Do it right. And get someone to [double-check that you did it properly](https://savimbo.com/fpic) privately, because it will definitely happen publicly at some point.&#x20;

We would be remiss not to address FPIC, but equally remiss to present ourselves as defining its requirements when there are far more authoritative sources. What follows are *operational answers from a working organization*, not conceptual contributions to the literature or policy. We have added some [practice recommendations](https://sexytrees.savimbo.com/practice-guide/fpic/fpic-tips-and-tricks.md) we adhere to, refer externally to [definitive sources](#authoritative-sources-on-fpic), and strongly recommend our place-based [peer-nominated FPIC validation service](https://www.savimbo.com/fpic) for your jurisdiction.&#x20;

It cannot be emphasized enough that FPIC, like any type of consent, is ongoing. Projects must make provisions early in their design for what happens if consent is revoked and how [data will be handled](https://sexytrees.savimbo.com/foundations/data-sovereignty.md) in that scenario. &#x20;

### Authoritative sources on FPIC

Some guides for effective FPIC we recommend include, but are not limited to:&#x20;

* Roundtable on Sustainable Palm Oil (RSPO) [FPIC Guide](https://rspo.org/wp-content/uploads/RSPO-Free-Prior-and-Informed-Consent-FPIC-Guide-2022_RSPO-GUI-T08-002-V2-ENG.pdf)
* First People's Worldwide FPIC [Due-diligence questionnaire](https://www.colorado.edu/program/fpw/sites/default/files/attached-files/fpic_due_diligence_questionnaire-2.pdf)
* Forest People's Program [Good faith negotiation guide](https://www.forestpeoples.org/sites/fpp/files/publication/2010/09/fppkeyelementsgoodfaithdec08eng.pdf)
* Sirge Coalition [FPIC guide](https://www.sirgecoalition.org/fpic-guide)
* Convention on Biological Diversity[ Mo’ otz Kuxtal Guidelines](https://www.cbd.int/doc/publications/8j-cbd-mootz-kuxtal-en.pdf)


---

# 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://sexytrees.savimbo.com/appendices/fpic.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.
