> 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/program-guides/delaware-watershed-conservation-fund.md).

# Delaware Watershed Conservation Fund

### Program Contacts

Erin Lewis, NFWF Delaware River Program Director - <erin.lewis@nfwf.org> &#x20;

Ragan Smith, NFWF Coordinator, Northeastern Regional Programs - [ragan.smith@nfwf.org](http://ragan.smith@nfwf.org/)&#x20;

## DWCF Awards: Tracking Implementation&#x20;

DWCF applicants and grantees are no longer required to track implementation of their activities for NFWF funded work in FieldDoc.&#x20;

Access your pact and activities linked to the pact will be frozen after November 30, 2026.&#x20;

If you would like to retain access to your NFWF funded records and the FieldDoc modeling features, you can upgrade to a FieldDoc Standard account.&#x20;

## FAQs - Creating an proposal

<details>

<summary>Do I have to use FieldDoc for my Proposal?</summary>

**No**. Delaware River Program applicants are not required to use FieldDoc for their applications. FieldDoc Standard users are invited to use the National Model to calculate sediment and nutrient load reductions to share as part of their proposals.&#x20;

</details>

<details>

<summary>Which BMP should I select as my Activity Type?</summary>

Choose the activity type that best aligns with the work that you are doing. Use the `description` field to provide more detail.

</details>

<details>

<summary>What should the geometry represent?</summary>

Each Activity record should have a single geospatial file associated with it. This file represents the installation footpring. You can use a point, line, or polygon to delineate your activity area. Aim to have one record represent a single installation footprint.

FieldDoc has lots of options for how to delineate geometries to activity records. Here are a few:

1. If you have a .csv, shapefile, or GeoJSON file, use **import.**&#x20;
2. Within the Activity record, navigate to the **Edit Activity** modal and select the **Geometry** tab and use FieldDoc's **Map editor** tools to delineate your point, line, or polygon within your activity record.

</details>

<details>

<summary>I don't think FieldDoc is providing an accurate model output for TN, TP, or TSS?</summary>

FieldDoc supports a National Model powered by EPA's PLET tool and and adapted CAST model for the Chesapeake Bay. We recommend reviewing their user documentation for specific details.&#x20;

</details>

<details>

<summary>How do I turn on the models? </summary>

Standard users can access models through the **Tools/Models** tab.

</details>

<details>

<summary>I don't know where I'm working yet. Do I need to put in geometry types?</summary>

At the planning stage, you can run models based on a generalized geography. Make sure to indicate in the activity name field that this is a representative site. Once implemented, we recommend that you update your FieldDoc records to delineate actual installation sites for restoration work.

</details>

<details>

<summary>I have a technical service provider creating my records. How should we proceed?</summary>

FieldDoc is optimized for collaboration! Activity records are owned by the organization that owns the workspace where they were created. Organization subscription levels also determine which features you can access.&#x20;

An organization user can invite collaborators from outside of their organization to their workspace. Once in the organization's workspace, collaborators can create, edit, and delete records on behalf of the organization.&#x20;

</details>

## FAQs - Sharing data to NFWF

<details>

<summary>How do I create a PDF of my Pact?</summary>

FieldDoc does not have an in-app PDF generation function. If you need to capture any views from FieldDoc, we recommend using your browser's print function and printing to pdf. Alternatively, capture the screen with a **Print Screen** command.

</details>

<details>

<summary>How do I get my FieldDoc geospatial data into NFWF's Easygrants system?</summary>

Easygrants will only accept shapefile imports. Because FieldDoc projects can include geospatial data in point, line, and polygon geometry types, we do not export data in the shapefile package. The .csv, .GeoJSON, and Geopackage formats which allow for more analytical flexibility.

NFWF has [created guidance](https://www.nfwf.org/sites/default/files/2025-04/dwcf-2025-fielddoc-to-ezg-guides_0.pdf) on how to convert a FieldDoc GeoJSON files for use in Easygrants. You can reach out to <Michael.Lagua@nfwf.org> for assistance.&#x20;

</details>

## FAQs - Tracking Implementation

<details>

<summary>How do I replace representative records with my actual work?</summary>

You can create or link new activity records to your Pact at any time during your period of performance. Make sure to follow the activity configuration steps for any newly created records. You will also want to de-link or delete the representative records once you no longer use them.

TIP: It is better to create a new activity record than to try to update an existing record to reflect a changed location.

</details>

<details>

<summary>Do I need an activity record for every location where we conducted work?</summary>

Yes. The activity records in FieldDoc should represent on-the-ground installation locations. If you feel this is unachievable, reach out to your Program Officers for guidance.&#x20;

</details>

<details>

<summary>How do I update the TN, TP, and TSS measurements?</summary>

Re-run the model that is associated with an activity record.&#x20;

</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 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/guides-1/program-guides/delaware-watershed-conservation-fund.md?ask=<question>&goal=<endgoal>
```

`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.
