> 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/getting-started/quickstart/start-here.md). # Start here FieldDoc Data Manager helps organizations create and manage digital records of their conservation and restoration work. Each record is called an **Activity**. An Activity represents work happening in a specific place, such as planting trees, restoring a stream, improving wildlife habitat, or monitoring environmental conditions. An Activity can include: * A name and description * A map showing where the work is happening * Details about what is planned or completed * Metrics used to measure progress * Environmental models that estimate benefits * Status updates from planning through completion and monitoring * Documents, photos, and other supporting files ### Why Use FieldDoc? FieldDoc is designed specifically for conservation and restoration work. It provides a consistent way to describe, organize, and manage information about work happening on the ground. We like to say that FieldDoc does the “dirty work” of managing real-world data. It turns information about your work into organized digital records that your organization can use to: * Plan and prioritize future activities * Track implementation progress * Organize work across projects and programs * Estimate and report environmental benefits * Share results with funders and partners * Analyze and communicate your organization’s impact ### Build Records You Can Keep Using Your organization owns and manages the FieldDoc records that represent its work. Instead of entering the same information again and again into different systems, you can create a lasting record in your own FieldDoc portfolio. These records become more useful over time. As you add maps, progress updates, metrics, model results, documents, photos, and monitoring information, each Activity becomes part of a larger history of your organization’s work. Your organization can use this information for planning, project management, reporting, analysis, and communication. ### Share Records Without Starting Over When a funder, program manager, or partner needs information about your work, you can share selected FieldDoc records with them. You can also connect FieldDoc data to other software tools. This allows your organization to share information without rebuilding the same records in someone else’s system. It can reduce duplicate data entry, preserve important organizational knowledge, and keep the people doing the work connected to the data that describes it. --- # 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/getting-started/quickstart/start-here.md?ask=&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.