> 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.fielddoc.org/help-center/activity-records/what-is-an-activity-record-exactly.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.