> 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/help-center/activity-records/what-is-an-activity-record-exactly.md).

# What is an activity record, exactly?

Activity records are the foundational records in FieldDoc. Each Activity is a digital representation of a conservation or restoration action taking place—or planned to take place—on the ground.

Organizations can build portfolios of Activity records to organize and manage their work over time. Activities can also be shared through Pacts for program reporting or used for other tracking, collaboration, and reporting purposes.

Each Activity record can contain a range of information about the work, including its location, implementation details, status, metrics, modeled outcomes, and supporting files. Together, these fields create a structured record of what is planned, what has been implemented, and what the Activity is expected to accomplish.

The key idea is: **one Activity record represents one distinct conservation or restoration action.**


---

# 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/help-center/activity-records/what-is-an-activity-record-exactly.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.