> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/activities/general-settings/neien.md).

# NEIEN

<figure><img src="https://2238918414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FatQfu0bk7aRHUPp2fz19%2Fuploads%2FGpVW0FZIrfzCe4Vth2P1%2FScreenshot%202025-03-25%20at%203.37.47%E2%80%AFPM.png?alt=media&amp;token=9de41805-5521-45bd-8453-6d3c3e774d30" alt="" width="563"><figcaption></figcaption></figure>

IN THIS ARTICLE

FieldDoc make it easy to map your activity records to the NEIEN schema. This is especially helpful for organizations conducting their own NEIEN reporting or grantees that must meet NEIEN reporting requirements through awards received.

***

## NEIEN

Align activity metadata and implementation measurements with Environmental Information Exchange Network specifications. This information enables implementation tracking and crediting by state governments and the U.S. Environmental Protection Agency.

### Step-by-step instructions

1. Open the NEIEN tab.
2. Click the `+ measurements`button.&#x20;
3. Search to select the NEIEN best management practice from the available list.
4. Find and save your selection.
5. Enter the measurement value for one or more of the options. If you are unsure, you can reach out to <support@fielddoc.org> or your state reporting lead.

### Dig in! Interactive Tutorial&#x20;

{% @arcade/embed flowId="CSQk2eOYEssNMdoDt75a" url="<https://app.arcade.software/share/CSQk2eOYEssNMdoDt75a>" %}


---

# 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://help.fielddoc.org/essentials/activities/general-settings/neien.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.