INSR 2026 Full Proposal Applications

Your goal at the Full Proposal stage is to use FieldDoc to create a credible, generalized scenario of your proposed work and estimated expected sediment and nutrient load reductions.

Once awarded, you will have the information needed to accurately say what BMPs were implemented, where, and to what extent. Armed with this information, you will return to FieldDoc to replace those early estimates with more detailed records of your actual implementation activities and their resulting impact.

Before You Begin

FieldDoc is organized around organization workspaces. Your proposal’s Pact has been created in the workspace of the lead organization.

That means your first job is to make sure you are working in the correct organization workspace before entering or reviewing information.

circle-info

The Full Proposal stage is about creating a generalized scenario of the proposed work.

Later, during the period of performance, you will return to FieldDoc to create and refine records that reflect actual implementation locations, activities, and outcomes. You do not need to create activity records in this pact.

Full Proposal Pact Set Up Steps

Step 1: Log in to FieldDoc.

Because FieldDoc is organized by organization, confirm that you are in the workspace of the lead organization for the application.

Step 2: Find Your pact

A Pact has already been created for your Full Proposal.

This Pact is the place where you will enter the information needed to represent your proposed work for the application.

Step 3: Draw the area of implementation

Add Pact geometry to represent the general project area.

At the pact stage, this geometry can be broad. It does not need to show final implementation footprints. A larger generalized area is appropriate, if that best represents the proposed work.

Step 4: Estimate Your Modeled Impact

Run the appropriate model at the Pact level to estimate the sediment and nutrient load reductions associated with your proposed work. You can run this step multiple times.

This step is intended to generate a planning-level estimate for the application.

Step 5: Add non-modeled metrics

If you would like to add non-modeled programmatic metrics, enter those totals in the Pact.

For example, if you are tracking a land-based metric such as trees planted, enter the proposed total for the project. If acreage is the required reporting unit for a metric, enter the total acreage associated with that metric.

Step 6: Click submit

When you are ready to begin, use the tutorial for step-by-step instructions on where to click and what to enter.

Dig-in! Use this tutorial for step-by-step guidance.

spinner

Commonly asked questions

Account management and collaboration

chevron-rightWho should use FieldDoc?hashtag

The Pact for your application has been created in the lead application organization. All members of the organization can access the pact. If you have collaborators outside of your organization, they must be given access to the pact in order to assist in the data entry and management.

spinner
chevron-rightHow do I add someone from outside of my organization?hashtag

All FieldDoc users must register as part of their own organization. You can invite collaborators to have full access to your workspace, or access to a specific pact. This tutorial shows how to invite a collaborator to your pact.

spinner
chevron-rightI can't log in to my account. hashtag

Reach out to [email protected]. If you have not logged into FieldDoc in a long time, we may need to restore your access.

If the registration button is unresponsive when you are trying to create a new account, get in touch with your network IT contact. They will need to place FieldDoc.com on a "safe list".

FieldDoc Data Management

chevron-rightWhat is a pact?hashtag

A Pact is a container in FieldDoc that allows an organization to package information and share it with a funder or other third party. It represents a formal reporting relationship, such as a grant application or award, where information created by a practitioner organization can be submitted in a structured way.

Pacts were introduced in 2024 as part of an expansion of FieldDoc’s features. They were designed to support organizations using FieldDoc for multiple purposes. Pacts honor the basic use of FieldDoc - to share implementation records with funders; as well as support broader data management by allowing organizations who choose to use FieldDoc for data management to maintain their own portfolio structure, while easily sharing a selected subset of records for a specific funding program or reporting requirement. This increases flexibility and allows organizations to report the same activity records to multiple funders.

chevron-rightWhere did my projects go?hashtag

Before 2024, Projects were the primary container used in FieldDoc for both organizing records and sharing them with funders for applications and reporting - because the system had a single use case. In FieldDoc 2.0, those functions were separated through the introduction of Pacts, which are now used for data sharing.

Because Projects have multiple connotations to users, the term became confusing. In 2026, FieldDoc’s portfolio structure was updated to better distinguish between organizing work and sharing it.

As part of this change, existing Projects were converted into top-level folders within the Activities tab. Standard users can create additional folders and use them to organize records in the way that best fits their workflow.

chevron-rightWhat should my activity records represent?hashtag

New in 2026, your INSR Full Proposal does not need any activity records. You will add general modeled estimates at the pact level.

Without exception, all of these INSR full proposals will be prospective sites. No one need sartificially created records. Use the Pact level model runs, pact level programmatic metrics too. The goal will be to add the implementation locations as installation occurs.

Application data

chevron-rightWhat "counts" as a pact geometry?hashtag

NFWF is expecting this to be relatively large. With the pact set up, the only geometry displayed should be one that gives an overall project area. You can be very imprecise and draw a large polygon that generalizes the entire footprint of your proposed implementation area.

You will add a geometry input to your model runs. These are not your pact geometry nor are they captured in any maps.

chevron-rightWhat do I model?hashtag

Use the Adapted CAST model in FieldDoc to create generalized estimates of the sediment and nutrient load reductions associated with your proposed BMPs.

The Adapted CAST model uses geography to determine model inputs, so you will need to provide either a location or a general footprint as part of the model setup.

chevron-rightWhy can't I use a large polygon for my model run?hashtag

If you draw a polygon, it may cross multiple land-river segments. If that occurs, FieldDoc will ask you to enter input values for each segment included in the polygon. Because this can make setup more complex, FieldDoc limits the size of polygons that can be added to a model run.

For most application-stage estimates, we recommend using a representative county-level point rather than a polygon.

chevron-rightCan I add multiple BMPs to one model run?hashtag

Yes! New in 2026, multiple BMPs associated with the same geometry can be added to a single model run. The outputs will be aggregated into a single calculation to appear on the overview page.

chevron-rightWhat do I enter for my application versus reporting during my period of performance?hashtag

At the application stage, you need:

  • Pact level geometry

  • Create one or more model runs that capture the general scope of the work proposed in your application.

    • For example, if your proposal includes work at seven farms to install grass buffers with exclusion fencing, for a total of 60 acres and 0.5 miles of fencing, create a model run using a generalized point, choose the appropriate BMP, and enter 60 acres as the model input.

    • This is different from earlier versions of FieldDoc. Previously, applicants often needed to create activity records for each farm, or build a demonstration farm scenario, during the application stage. In this workflow, you are creating a generalized proposal-stage estimate, not a farm-by-farm implementation record.

    • Use your discretion on what the appropriate resolution and number of model runs you choose to include.

chevron-rightDo I need to add non-modeled, programmatic metrics?hashtag

The main use of FieldDoc is to createcredible, consistent load reduction calculations. The FieldDoc system is also important for NFWF in order to collect the precise geographic information that is needed to report to the jurisdictions at the end of your period of performance.

New in 2026, the models run to calculate the load reduction metrics differ between the application and award stages.

  • Application stage - pact wide

  • Reporting stage - verifiable activity level

Programmatic Metrics will be entered into Easygrants. Unless the grantee would like to enter them into FieldDoc, it is not necessary to hand-enter programmatic metric data.

Last updated