> 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/intro-to-pacts.md). # Intro to pacts A **Pact** is the way an organization shares selected FieldDoc records with a funder, program manager, or collaborative initiative. You can think of a Pact as a shared connection between records in your organization’s Workspace and an outside program. The Pact identifies which records your organization is submitting and allows the external program manager to review information needed for a grant, reporting requirement, or other shared effort. Your organization continues to manage the original records in its own Workspace. ### What Is Included in a Pact? A Pact can include: * Activities * Activity locations and implementation footprints * Metrics and progress updates * Modeled environmental benefits * Documents, images, and supporting files * Information required by the program A Pact may represent a grant award, funding agreement, reporting relationship, or participation in a collaborative program. ### How a Pact Works A Pact connects your organization to an **Opportunity** created by a FieldDoc Program Manager. The Opportunity represents the program, grant, or other reason records are being collected. Your organization uses the Pact to share the Activities connected to that Opportunity. For example, a funder may create an Opportunity for a restoration grant program. Each funded organization can then create a Pact connected to that Opportunity and add the Activities supported by its award. ### Activities Stay in Your Workspace Adding an Activity to a Pact does not move the Activity out of your Workspace or create a second copy. The original Activity remains part of your organization’s portfolio. Your organization can continue to update and use the record for its own planning, tracking, reporting, and communication. The Pact gives the Program Manager access to the selected record for the purpose of the program. This is similar to sharing a file from Google Drive. The file stays in your drive, but the person you share it with can access it based on the permissions you provide. ### Pacts Share Selected Records A Pact does not give the Program Manager access to every record in your Workspace. The Program Manager can access the Activities that are connected to the Pact. Activities that are not added to the Pact remain outside that program relationship. Before adding an Activity, confirm that it belongs to the correct grant, award, or reporting program. ### Program Requirements Some Pacts include requirements set by the Program Manager. These may include: * Required fields * Specific Activity Types * Programmatic metrics * Environmental models * Reporting dates * Implementation or completion updates * Supporting documents Requirements can vary from one Opportunity to another. [Find your program guidance ](https://help.fielddoc.org/guides-1/) to review the Pact instructions before entering or submitting information. ### One Pact for One Agreement In most cases, a Pact should represent one award, agreement, or defined reporting relationship. For example, if your organization receives two separate grants from the same funder, each grant may have its own Pact. Keeping these agreements separate makes it easier to understand which Activities, metrics, and reports belong to each award. ### Who Can Work in a Pact? Users with access to the Workspace can work with the Pact based on their assigned permissions. Depending on their role, users may be able to: * View the Pact * Add or remove Activities * Update required information * Review progress and metrics * Submit information to the Program Manager The Program Manager can review the records shared through the Pact and may also manage certain program-specific fields. ### Pacts and Folders Serve Different Purposes Folders organize records inside a Workspace. Pacts share selected records with an outside program. An Activity can be stored in a folder for your organization’s internal use and also connected to a Pact for reporting to a funder or partner. For example, an Activity might be stored in a folder called **2026 Stream Restoration** and also be added to a Pact for the grant that funded the work. ### Keep Pact Information Current Update the Activities connected to a Pact as the work moves from planning through implementation, completion, and monitoring. Keeping records current helps your organization and the Program Manager work from the same information. It also reduces the need to rebuild data when reports are due. A well-managed Pact makes it easier to share progress, meet program requirements, and maintain a lasting record of the work in your organization’s own FieldDoc portfolio. --- # 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/getting-started/quickstart/intro-to-pacts.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.