> 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/guides-1/user-guides/technical-service-providers-grant-application-guide.md).

# Technical Service Providers - Grant Application Guide

Your guide to assisting a partner organization with an upcoming grant application in FieldDoc. Updated 11/2026

There have been significant changes to the application workflow in FieldDoc 2.0.  Whether you're reviewing data, entering activities, or guiding another team through their submission, it’s important to ensure that your FieldDoc setup is right from the start. We've put together this reference to help you support your clients in creating and maintaining records for their grants.

{% hint style="danger" %}
**What's changed?**&#x20;

* Use a pact to shared records with a funder.
* **Modeled metrics** are accessible from a new tab and must be activated manually.
* Use **Transfer** to move records to the appropriate lead applicant account.&#x20;

And more!&#x20;
{% endhint %}

If you're collaborating to support an applicant or grantee organization, this guide is for you.

***

## Watch the webinar

This webinar walks you through five key areas:

* Setting up a FieldDoc account
* Switching between workspaces
* Supporting clients in building pacts
* Prepare and use imports
* Access and running models

{% embed url="<https://youtu.be/yUT8oN8DDCc>" %}

## Understanding the FieldDoc Data Model

We recommend familiarizing yourself with the FieldDoc data model to best understand how the different components fit together.&#x20;

### Each Organization has a workspace.

* A workspace contains all of an organization's records. Users can belong to multiple workspaces, but only one organization. This means that external partners or contractors are invited to join and work within a workspace without joining the organization account.
* Within an organization workspace, you can view the organization's portfolio. The portfolio provides a list of pacts and a list of activities. The structure for organizing activities is similar to how you would use Google Docs or any file manager.&#x20;
* When applying for a pact or completing a pact report, we recommend that all work be started from within a pact, not the activities file structure.&#x20;
* If you want to organize records within a workspace, you can make use of the nested folder structure to organize activity records. All activity records that are created within a pact are added to the portfolio but are not automatically organized into folders.
  * [Activity](https://help.fielddoc.org/essentials/portfolio/activities-records.md) records each represent a single, trackable restoration or conservation action. They serves as the core unit of nature-based work, capturing detailed information about what was done, where, when, and what outcomes are expected.

### Sharing Activity Data to a funder

* To share data with funders, or other third parties, you must use Pacts. Pacts allow a third-party program manager to view the activity records and provide access to programmatic-metrics.&#x20;
* Activity records are the only portion of your workspace portfolio that can be shared via Pacts.&#x20;
* A single activity record can be shared to multiple pacts.

#### Data model

<div align="center" data-full-width="false"><figure><img src="https://1728742785-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoqGpBtiTp05bHUD7Z3m%2Fuploads%2FATh0WWvtcCrRp905Z26k%2FFD-Data-Model-Diagram.png?alt=media&amp;token=3a624b21-5208-4eeb-8d61-cc00460ae662" alt=""><figcaption></figcaption></figure></div>

***

## Account Management

{% stepper %}
{% step %}

#### Create your Account

Each user must create an account within their own organization in FieldDoc. However, if you are not the lead applicant for the grant, do not create any records or start a Pact in your own workspace. [Account Management ](https://help.fielddoc.org/manage-your-organization/user-account.md)

{% hint style="danger" %}
The organization applying for funding must be the Pact owner in order to submit the application. This means the applicant organization must have a FieldDoc account set up and active.
{% endhint %}
{% endstep %}

{% step %}

#### Joining Your Client’s Workspace

If you're assisting another organization (e.g., a grantee or client), they must invite you to join their FieldDoc workspace. Once you've accepted the invitation, you can switch to their workspace using the workspace selector in the upper left hand corner. Once in their workspace, all of the records that you create or edit will be owned by your client. This means that you can create a Pact and activity records on their behalf.
{% endstep %}

{% step %}

#### **Configure the Pact details correctly.**&#x20;

* Make sure you use the **Pact opportunity code** for the correct funding opportunity.  Check out the [Program Guides](https://help.fielddoc.org/guides-1/program-guides/chesapeake-bay-stewardship-fund.md) to find available codes.
* The “**Pact recipient**” field is automatically set based on the workspace you're in. This field cannot be edited. Therefore, the Pact must be created within the workspace of the lead applicant—the organization applying for funding.
* You will not enter the Start Date, End Date, Funding Amount, or Unique Identifier fields.
  {% endstep %}

{% step %}

#### Linking Activities to the Pact

Only activity records from the workspace where the pact was created can link records to a pact. In other words, records from multiple workspaces cannot be added to the same pact. Make sure you are creating all project records, activities, and metrics from within the lead applicant’s workspace. [Pact Overview](https://help.fielddoc.org/essentials/pacts.md)
{% endstep %}
{% endstepper %}

***

## Completing the FieldDoc portion of a funding application&#x20;

### Pacts

Funding Opportunities that use FieldDoc to collect applicant information or reports on grants collect that information through pacts. Pacts also provide basic FieldDoc users with some advanced features, like Models.&#x20;

If you're applying for funding, follow these tips to get started:

1. **When you are applying for funding, Do not create individual activity records to start, create a Pact.** Funding program managers cannot view records in your portfolio unless they are shared via a pact. You also cannot access the model feature as a basic user unless you are in a pact view.&#x20;
2. **Finding your pact code**. Each finding opportunity has a unique Pact code for this funding cycle. Check in the Help Doc [Program Guidance](https://help.fielddoc.org/guides-1/program-guides/chesapeake-bay-stewardship-fund.md) for your code.
3. **Naming your Pact**. The Pact name must match the name of the title used in your grant application. If you use any alternative, the program managers may not be able to align it with the correct application.
4. **Remember to click submit**. Funding program managers cannot view Draft pacts.
5. **Uploading your Pact to a Grants Management System**. FieldDoc does not have an in-app print report function. Use the browser’s file>print commands or take a screenshot of your Pact page (including the URL) to upload to another system.&#x20;

***

### How to create your activity records

Activity records were formerly called practices. How you create these records and share your activity records to a funder has changed in FieldDoc 2.0.&#x20;

{% hint style="warning" %}
Records that you create in a Project are not visible to Program Managers until they are linked to the Pact. Programmatic metrics are not available to add to records until they are linked to a Pact.&#x20;
{% endhint %}

#### Create individual activity records.&#x20;

Only use the “**+ create**” button if you will be using the FieldDoc draw tools to delineate your activity footprint. Once you have created your activity record shell, open the “Edit Activity” modal via the upper right hand corner. You will add:

1. [**Activity Type**](https://help.fielddoc.org/essentials/activities/general-settings/activity-type.md)**.** Select what you are implementing via the standard list.&#x20;
2. [**Geometry**](https://help.fielddoc.org/essentials/activities/geometry.md). Draw your activity footprint to indicate the location and extent of the installation using a point, line, or polygon.
3. [**Models**](https://help.fielddoc.org/essentials/activities/models.md). Calculate associated sediment and nutrient load reductions by entering the required fields. :exclamation:  Models in FieldDoc don’t turn on by themselves. To use a model and see estimated environmental benefits, you'll need to manually activate it by completing the required input fields and running the calculator.
4. [**Metrics**](https://help.fielddoc.org/essentials/activities/activity-metrics.md). Select programmatic metrics based on the funding program’s list and add planned values. These should match the work proposed in your grant application. :exclamation:Programmatic metrics only appear if you have linked your activity record to a Pact.

#### Use the Import File option.&#x20;

Use the Import File button if you have geospatial files on hand, whether you are importing them individually or in batch format.&#x20;

FieldDoc can import [.csv](https://help.fielddoc.org/essentials/import.md#file-type-csv), [.GeoJSON](https://help.fielddoc.org/essentials/import.md#file-type-geojson), or [Shapefiles](https://help.fielddoc.org/essentials/import.md#file-type-shapefile), as long as the files meet the FieldDoc requirements.

With Import, you can create a single activity record or batch create up to 1,000 records.&#x20;

:seedling: Learn more: [Import](https://help.fielddoc.org/essentials/import.md)

## Using Transfer

If you created a pact for a client in your own workspace rather than in theirs, we have created a fail safe option. In order to use Transfer, you must be a member of both participating workspaces.

* From the upper right hand corner of the pact, click on the horizontal ellipses.&#x20;
* Choose **Transfer**.&#x20;
* Select the workspace where you want to transfer the pact.&#x20;
* Step through the prompts and click OK

This transfer moves the pact and all related activity records into the new workspace. Nothing is left behind. You will need to navigate to the new workspace to continue working on the pact.

## Frequently Asked Questions

<details>

<summary>Where do I find the Pact Code? </summary>

If your funding application manager publicly shares the Pact code, you will find it in theRFP’s specific help documentation via the [FieldDoc Help Guides](https://help.fielddoc.org/guides-1).

</details>

<details>

<summary>Can I move activity records between workspaces? </summary>

Yes. Use the transfer option to move records between workspaces.

</details>

<details>

<summary>Can I add activity records from multiple workspaces to one pact?</summary>

No. Workspaces are siloed. Activity records are 'stuck' within their workspace.

</details>

<details>

<summary>Where do I go for more help?</summary>

For more details, check out our expanded help center. For technical support, send an email <support@fielddoc.org>. Remember that the support desk is open 9:00-5:00 Monday through Friday. Expect a 24 hour response time for your ticket.

</details>


---

# 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/guides-1/user-guides/technical-service-providers-grant-application-guide.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.
