For Grant Reporting
A common use of FieldDoc is for grant recipients to use FieldDoc to meet implementation and tracking grant compliance requirements. For specific program guidance, refer to the Guides section.
Last updated
A common use of FieldDoc is for grant recipients to use FieldDoc to meet implementation and tracking grant compliance requirements. For specific program guidance, refer to the Guides section.
Last updated
FieldDoc allows general users to share activity records from their organization's portfolio to funding program managers. Once the activity records are shared, via a Pact, additional programmatic metrics determined by the Funding Program can be assigned to the Pact. The specific instructions of when to create a FieldDoc Pact and what information to include can be found in the .
Anyone using FieldDoc needs a FieldDoc account. The organization submitting the application should be the "owner" of the related records and Pact within FieldDoc. Collaborators and technical service providers can be added to the organization's workspace to assist with configuring the Pact.
Learn more:
Practitioners will share data from their Portfolio of nature-based activities with funding programs via Pacts. Each application should have a unique Pact. To create a Pact, you'll need the funding opportunity's Unique Pact Code. Reach out to your funding program manager or support@fielddoc.org for that information.
Learn more:
Throughout your period of performance, you will use FieldDoc to meet grant compliance requirements. Specific requirements for the cadence of reporting can be found in your grant agreement. The following provides an overview of the steps that you will take to track implementation, and assumes that you have already created a FieldDoc Pact with your funder.
Once you have installed an activity to specification, such as installing a BMP or completing a series of planning sessions, that activity can be marked as complete. You will add the completed_on
date and the system will log the user who entered the date as the verifier. This helps track that no more work will be done for this activity which may trigger other actions, such as reporting to States or conducting inspections for verification of functioning