> 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/academy/guides/build-a-data-management-plan.md).

# Build a Data Management Plan

<figure><img src="/files/Fv0YCWKktskYcKn6HL6D" alt="" width="287"><figcaption><p><a href="https://drive.google.com/uc?export=download&#x26;id=1gpBxdu-tzdKibXtHdO2rQ_0gP5I_LA4D">Download the article (PDF)</a></p></figcaption></figure>

Learn how to build a simple, repeatable data management plan that keeps conservation and restoration data accurate, reusable, and ready for reporting—inside FieldDoc and beyond.

This guide walks through how to design a data management lifecycle—from defining standards and workflows to reviewing and maintaining records over time. It is designed for nonprofit and practitioner-led organizations managing conservation and restoration data who need approaches that fit real-world constraints. Rather than prescribing a single system or tool, the guide focuses on practical habits and shared conventions that help data remain usable, trustworthy, and adaptable as programs, staff, and reporting needs evolve.


---

# 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:

```
GET https://help.fielddoc.org/academy/guides/build-a-data-management-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
