# Hello! How can we help you?

### Popular topics
Find Pact CodeA Pact code is unique to each funding opportunity/spaces/uoqGpBtiTp05bHUD7Z3m
Manage AccountConfigure your account and workspace access/pages/kop1DqciIJnwvVsk3YLj
Run a ModelLearn about the models supported in FieldDoc and how to run them/pages/jerKiul18dSx9wvElWzo
Track Program MetricsAdd programmatic metrics to your pact and track implementation progress/pages/VvN6dkKf2WkZpLFtL5UY
CollaborateShare records with partners/pages/kop1DqciIJnwvVsk3YLj
Upgrade your PlanUnlock additional features and functionalityhttps://www.fielddoc.com/pricing
### Applying for funding? Check out available guides for some funding programs:
Cover image
Chesapeake and Atlantic Coastal Bays Trust Fund/spaces/uoqGpBtiTp05bHUD7Z3m/pages/RT99lMhwLU2f1upS2ttz/files/Ub3bFqISkG8pVlIOsdOE
NFWF Chesapeake Bay Stewardship Fund/spaces/uoqGpBtiTp05bHUD7Z3m/pages/LJvOZxLAdAXBMZ4kruKH/files/DxJ0nLGMstVIgVpnSfxy
NFWF Delaware River Program/spaces/uoqGpBtiTp05bHUD7Z3m/pages/2lpmknqDRwI9Ziw6VwOp/files/pcHbXSjM2S3H4Wo5vAU4
## Still have questions? ### Email our team Reach out to our team with any questions, comments, or great ideas: ### Hire The Commons Work with a FieldDoc expert via the The Commons's Data Concierge program. Get personalized help, set up your workspace and folders, and accomplish all of your FieldDoc goals. To learn more and get started, email # FieldDoc Basics # Start here FieldDoc Data Manager helps organizations create and manage digital records of their conservation and restoration work. Each record is called an **Activity**. An Activity represents work happening in a specific place, such as planting trees, restoring a stream, improving wildlife habitat, or monitoring environmental conditions. An Activity can include: * A name and description * A map showing where the work is happening * Details about what is planned or completed * Metrics used to measure progress * Environmental models that estimate benefits * Status updates from planning through completion and monitoring * Documents, photos, and other supporting files ### Why Use FieldDoc? FieldDoc is designed specifically for conservation and restoration work. It provides a consistent way to describe, organize, and manage information about work happening on the ground. We like to say that FieldDoc does the “dirty work” of managing real-world data. It turns information about your work into organized digital records that your organization can use to: * Plan and prioritize future activities * Track implementation progress * Organize work across projects and programs * Estimate and report environmental benefits * Share results with funders and partners * Analyze and communicate your organization’s impact ### Build Records You Can Keep Using Your organization owns and manages the FieldDoc records that represent its work. Instead of entering the same information again and again into different systems, you can create a lasting record in your own FieldDoc portfolio. These records become more useful over time. As you add maps, progress updates, metrics, model results, documents, photos, and monitoring information, each Activity becomes part of a larger history of your organization’s work. Your organization can use this information for planning, project management, reporting, analysis, and communication. ### Share Records Without Starting Over When a funder, program manager, or partner needs information about your work, you can share selected FieldDoc records with them. You can also connect FieldDoc data to other software tools. This allows your organization to share information without rebuilding the same records in someone else’s system. It can reduce duplicate data entry, preserve important organizational knowledge, and keep the people doing the work connected to the data that describes it. # Create an organization and account ### Create Your User Account To use FieldDoc or any FieldDoc-powered application, you need to create an individual user account. Each person must have their own login. Do not share your username, password, or account access with anyone else. When creating your account, please use accurate information, including your real name and a valid work email address. You are responsible for keeping your account details, including your email address, up to date. ### Join the Correct Organization All FieldDoc users must be connected to a verified Organization. You should only join an Organization if you are authorized to act on its behalf. This usually means you are an employee, officer, member, or direct representative of that Organization. External partners, such as contractors, consultants, collaborators, technical assistance providers, funders, agency partners, or volunteers, should not join another Organization’s account as a member. Rather, external partners may have their own Organization account and collaborate can through FieldDoc features such as workspaces, Pacts, shared records, application-specific permissions, or other available tools. ### Collaborate Across Organizations FieldDoc welcomes collaboration! If you work with more than one Organization, use FieldDoc’s collaboration features instead of joining multiple Organization accounts. As explained above, each user account can only be a member of to one Organization at a time. However, users can access records, workspaces, or other shared areas across Organizations when they are invited through the appropriate FieldDoc permissions. Organization Owners and authorized administrators may invite external users to collaborate within an Organization workspace only through the permissions available in FieldDoc and only when they are authorized to provide that access. # Onboard your team IN THIS ARTICLE Start by creating your own account. Then, connect with colleagues and collaborators. Both internal team members and external partners can work together through a shared Workspace tied to your organization. This article outlines the different ways you can invite the right people to the right place, ensuring everyone has access to the data they need. *** ## Create your user account Configuring your account is a three-step process. ### Step 1. Register with your professional email address. All user accounts must be assigned to an organization. 1. Navigate to fielddoc.org/register 2. Enter in your name and professional email address. 3. Click Complete. 4. Open your inbox and verify your email address. Tip! Use the available prompts if you need to update the email that you originally entered or you need to re-send the email verification. 5. Once confirmed, it's time to select an organization or create a new one. {% @arcade/embed flowId="8mZMhnph8NDsrZXQ3CKk" url="" %} ### Step 2. Join an organization #### Option 1. Join an existing organization If your organization already exists in FieldDoc, you will be able to add your account to that organization. 1. FieldDoc will look at your email domain and match you to the organization in FieldDoc with the same domain (if one exists). 2. Click to join the organization. 3. FieldDoc will automatically confirm your membership and bring you to your home page. Welcome! {% @arcade/embed flowId="xM5lSs8yfAFd2vGGXTHG" url="" %} #### Option 2. Create a new organization If you are creating a new organization as you set up your account, you will be presented with a screen where you can create a new organization. {% @arcade/embed flowId="AC1ArMh8aZ66nu1sgFsi" url="" %} {% hint style="info" %} If you believe your organization is already in the system but you need a separate section, please contact to discuss options. {% endhint %} *** ## Invite your colleagues FieldDoc works great for collaboration. ### Invite from FieldDoc You can jumpstart the on-boarding process for colleagues at your organization by inviting them to join your organization Invite your colleagues (staff with the same email domain) to join your organization. During the invitation process, they will complete the steps to create their own FieldDoc account. {% @arcade/embed flowId="Fp4yblnlBJTrPrzrazvt" url="" %} {% hint style="warning" %} Do not invite colleagues outside of your organization to join your organization. All external partners and technical service providers can be joined to your organization via **workspaces**. {% endhint %} ### Self-onboarding colleagues You can also ask colleagues to create their own FieldDoc account and join your existing organization. They will follow the same process as [Create your User Account](#create-your-user-account) up above. After they verify the account, the system will prompt them to join your organization, based on your email domain. *** ## Invite Collaborators and Technical Service Providers ### via Workspaces FieldDoc makes it easy to let collaborators from *outside* of your organization help you manage your FieldDoc portfolio. Any member of a workspace with administrator access can perform all tasks, such as setting up Pacts and Activity Records on behalf of your organization. **Workspaces** are the feature within each organization through which all users create and manage data. Collaborators will need to switch workspaces before getting started on any work being. {% @arcade/embed flowId="0LLjfTTGsNdP3sfzoINl" url="" %} ### Via Folders If a collaborator needs narrower access, you can invite them to a folder, pact, or even an activity record. This will allow them to make edits and complete work within a contained area in your workspace. Collaborators will access these records from the **Shared with Me** tab on the lefthand panel. They do not need to switch workspaces. # Intro to workspaces ## Introduction to Workspaces A **Workspace** is a shared area in FieldDoc where a group of people manages conservation and restoration records. You can think of a Workspace as similar to a shared Google Drive. It brings records, folders, and users together in one place. The main difference is that FieldDoc is designed to manage structured conservation and restoration data rather than standard documents and files. A basic organization subscription will use one Workspace for all of its work. Standard Subscriptions can create up to three separate Workspaces to separate folders, such as to differentiate disparate teams, regions, programs, or groups of records. ### What is managed in a Workspace? A Workspace contains the records your team manages together, including: * Activities * Folders and subfolders * Pacts * Metrics * Models * Documents, images, and supporting files * Integrations Users can create, review, organize, and update these records based on their permissions. ### How Users Get Access There are two ways a user can become a member of a Workspace. #### Members of the Organization People who belong to the organization are added to its Workspace by default. Their assigned role determines what they can view, create, edit, or manage within the Workspace. #### People Outside the Organization A person who is not part of the organization can be added manually to a Workspace. For example, an organization might add a: * Consultant * Contractor * Project partner * Technical advisor * Other outside collaborator Adding someone to a Workspace gives that person access to the records in that Workspace. It does not make the person a member of the organization or automatically give them access to other Workspaces in your organization. ### Workspaces Help Manage Access Like a shared drive, a Workspace allows a specific group of people to work with the same set of records. A user’s role determines what they can do. Depending on their permissions, a user may be able to: * View records * Create Activities * Edit records * Organize records into folders * Manage Workspace members Organizations should add only the people who need access and remove members when that access is no longer needed. ### Each Workspace Has Its Own Folders Folders belong to the Workspace where they were created. A folder created in one Workspace will not appear in another Workspace, even when both Workspaces belong to the same organization. For example: **Chesapeake Bay Workspace** * Maryland * Virginia * West Virginida * DC * Pennsylvania * New York **Lake Erie Workspace** * Ohio * Michigan * Pennsylvania * New York The Chesapeake Bay folders are available only in the Chesapeake Bay Workspace. The Great Lakes Workspace has its own separate folder structure. This is similar to having two shared drives. Each drive can contain its own folders and be shared with a different group of people. ### Switching Between Workspaces Users who belong to more than one Workspace can switch between them in FieldDoc. Before creating or organizing records, check that you are in the correct Workspace. New folders and records will be created in the Workspace that is currently open. ### Workspaces and Folders Serve Different Purposes Use a **Workspace** to manage a separate group of records and the people who can access them. Use **folders** to organize related records inside that Workspace. For example, a regional team might have its own Workspace because it manages a separate group of records and users. Within that Workspace, folders could organize Activities by watershed, project, funding source, or year. A clear Workspace structure helps people find the right records, understand where new records belong, and work together without giving everyone access to every part of the organization’s portfolio. # 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. # Create folder Folders help you organize Activity records in your FieldDoc portfolio. You can use folders to group related work by project, location, program, funding source, year, or any other system that works for your organization. Creating a folder does not create a new Activity or change the information in an existing Activity. It simply gives you a place to organize related records. ### Before You Begin Think about how your team will use the folder. A clear and consistent naming system will make records easier to find later. For example, you might organize folders by: * Project or initiative * Watershed or geographic area * Grant or funding program * Calendar or fiscal year * Type of conservation work * Planning, active, or completed work Avoid creating too many layers of folders. A simple structure is usually easier for your team to understand and maintain. ### Create a New Folder 1. Open the **Folders** section of your FieldDoc workspace. 2. Select **Create Folder**. 3. Enter a clear name for the folder. 4. Add a description, if available, to explain what belongs in the folder. 5. Select **Save**. Your new folder will now appear in your workspace. ### Add Activities to the Folder After you create the folder, you can add existing Activities to it or create new Activities within it. Adding an Activity to a folder does not create a copy of the record. The folder simply helps you organize and find the Activity. An Activity can continue to be shared through a Pact or used in reports and integrations, even when it is stored in a folder. ### Create a Subfolder You can create a folder inside another folder to organize your records in more detail. This is called a **subfolder**. For example: **Chesapeake Bay Projects**\ → **West Virginia Projects**\ → **Delaware Projects** Use subfolders only when they make the records easier to find. Too many levels can make a portfolio harder to navigate. ### Keep Your Folder Structure Useful Your organization can update its folder structure as its work changes. Review folders from time to time and rename, move, or archive them when needed. Remember that folders are an organizational tool. The Activity record remains the main record for documenting what happened, where it happened, and what results are expected. # What's an Activity? An **Activity** is the main record used to document conservation and restoration work in FieldDoc. Each Activity represents one trackable action happening in a specific place. For example, an Activity might describe planting a riparian buffer, restoring a stream, installing green infrastructure, monitoring water quality, or leading a community engagement effort. You can think of an Activity as the digital record of work happening on the ground. ### What Can an Activity Include? An Activity can include: * A name and description * An Activity Type * A mapped location or implementation footprint * Planned and completed dates * Implementation status * Metrics used to track progress * Environmental models that estimate benefits * Documents, images, and supporting files * Monitoring results and updates Not every Activity will include all of this information. Add the details that are useful for managing, understanding, and reporting the work. ### One Activity Represents One Trackable Action Each Activity should represent a clear piece of work that can be described and tracked. For example, a larger restoration project might include several Activities: * Planting a five-acre forest buffer * Restoring 1,000 feet of stream * Installing a stormwater practice * Monitoring water quality after construction Keeping these actions in separate Activity records makes it easier to map locations, track progress, calculate results, and report outcomes. ### Name Activities Clearly Give each Activity a name that helps people understand what the record represents. A useful name may include: * The location * The type of work * The project or site name * A tracking number used by your organization For example: * **Smith Farm Riparian Buffer** * **Pine Creek Stream Restoration** * **Main Street Rain Garden** * **RC-104 Water Quality Monitoring** Avoid vague names such as “New Activity,” “Project 1,” or “Site Work.” ### Choose an Activity Type The **Activity Type** describes the kind of work being completed. Examples may include: * Riparian buffer planting * Stream restoration * Wetland restoration * Green infrastructure * Conservation planning * Monitoring or research * Community engagement Choosing the correct Activity Type helps organize records and may make environmental models available. FieldDoc manages a standard list of Activity Types so similar work can be described consistently across organizations and programs. ### Map Where the Work Is Happening An Activity can include a mapped location or implementation footprint. Depending on the work, you may use: * A point for one location * A line for work along a stream, trail, or shoreline * A polygon for an area such as a field, wetland, or planting site You can draw the location in FieldDoc or import geospatial data created in another system. The map should show where the Activity is planned or where the work was completed. ### Track Progress and Results Activities can be updated as work moves from planning through completion and monitoring. You can use the Activity record to track: * What is planned * When implementation has been completed * Metric tracking against implementation status * What outcomes are expected For example, an Activity may begin with a planned value of five acres. After the work is completed, the record can be updated with the number of acres actually planted. You can track the number of trees planted and the number of volunteers that assisted. ### Use Metrics and Models Metrics describe the size, amount, or result of an Activity. Examples include: * Acres restored * Feet of stream improved * Trees planted * People engaged * Water samples collected Environmental models can estimate benefits such as reductions in pollution or improvements in habitat. Models are not turned on automatically. Select the models that are appropriate for the Activity and the reporting needs of your organization or program. ### Organize Activities in Folders Activities can be placed in folders and subfolders within a Workspace. Folders help your organization group related Activities by project, region, year, funding source, or another useful category. Adding an Activity to a folder does not change the Activity itself. It only helps users organize and find the record. ### Share Activities Through Pacts An Activity can also be connected to a Pact. A Pact shares selected Activities with a funder, Program Manager, or collaborative initiative. Connecting an Activity to a Pact does not move the record or create a second copy. The Activity remains in your organization’s Workspace, where your team can continue to manage and update it. An Activity can be organized in a folder for internal use and shared through a Pact at the same time. ### Build a Lasting Record An Activity can grow as the work progresses. You may begin with a name, description, and planned location. Later, you can add implementation dates, completed metrics, photographs, model results, reports, and monitoring information. Over time, your Activities become a lasting digital record of your organization’s conservation and restoration work. These records can support planning, project management, reporting, analysis, and communication. # Build your Portfolio IN THIS ARTICLE Portfolios provide the organizational structure for an Workspace's activity records and supporting data. They also include organization metrics and Pact overviews. The structure of your content in FieldDoc is organized through project folders, sections and activities. Pages live inside of spaces, and collections are groups of spaces. *** ## Build your Portfolio Think of your portfolio like your a Google Drive full of folders and sub-folders in which you organize your files. Activity records are the core of your portfolio. They can be added directly or sorted into Project Folders and Sections. ## Adding data to your portfolio All data that you add to a FieldDoc workspace will be added to your portfolio. The following are a few ways that you can put data into your portfolio. ### Create Folders > Sub-Folders > Activity Records Using the **+ Create** button, you can manually add individual folders and then nest data within those folders. For example, you can create a *Folder* for a Program that your organization manages. You can create *Sub-Folders* within the Project folder for each of the farmers that you are working with. And then within each section, you can create the *activity records* to track the sustainability practices that will be installed across that farmer's landholdings. ### Import Data FieldDoc lets you import data in .csv, shapefile, and .GeoJSON formats. You can import single files or batch import. The importer from the Home page allows you to select the destination table, which means that you can import Metrics, Project folders, Section sub-folders, or Activity records. The really cool thing is that, if you batch import activity records, you can include fields for Folders and sub-folders This means that you can build out your entire portfolio from one import! :seedling: Learn more: [Import](/essentials/import) ### Create a Pact When you create a pact in an Opportunity, you have the option to create new activity records within the pact *or* link them from your portfolio. Any activity records that you create within your pact will also be added to your workspace's portfolio. # Model environmental benefits IN THIS ARTICLE FieldDoc makes it easy to estimate the sediment and nutrient load reductions that will result from implementing a BMP. Inputs must be met in order for the models to calculate. *** ## Model environmental benefits At this time, the calculator supported in FieldDoc requires the following inputs: 1. An activity type 2. A location based on the geospatial data. 3. A unit input. The data required from the activity type and location are collected from your activity record. On the models tab, you will be prompted to enter in the unit input manually. In most cases, the calculator is asking for the footprint of the activity in acres; however, in some cases you will need to input an alternative extent, such as animal units.
:seedling: Learn more: [Models](/essentials/activities/models) # Find Your Program ## Find your program
Cover image
Chesapeake & Atlantic Coastal Bays Trust FundMaryland Department of Natural Resources/spaces/uoqGpBtiTp05bHUD7Z3m/pages/RT99lMhwLU2f1upS2ttz/spaces/uoqGpBtiTp05bHUD7Z3m/files/sFcpuSox7zro6EhYGFqk
Chesapeake Bay Stewardship FundNational Fish and Wildlife Foundation/spaces/uoqGpBtiTp05bHUD7Z3m/pages/LJvOZxLAdAXBMZ4kruKH/spaces/uoqGpBtiTp05bHUD7Z3m/files/qpt3dz6aM1Z3HgyjdEGj
Delaware River ProgramNational Fish and Wildlife Foundation/spaces/uoqGpBtiTp05bHUD7Z3m/pages/2lpmknqDRwI9Ziw6VwOp/spaces/uoqGpBtiTp05bHUD7Z3m/files/r3bhaT4umIEZZp1iJP54
A **Program** is a program, collaborative effort, or investor opportunity that uses FieldDoc to collect information from participating organizations. Finding the correct Funding Program is an important first step when you are using FieldDoc to meet an application or funding requirement. {% hint style="info" %} Not all Programs provide user guidance in FieldDoc. If you have been asked to use FieldDoc but do not see the associated program listed here, contac or your program manager for assistance. {% endhint %} ### What Is a Program? A Program is managed by a funder, government agency, partnership, or other organization using FieldDoc to collect, review, or aggregate conservation and restoration data from other organizations. A Funding Program may use FieldDoc to: * Collect proposed Activity information * Review mapped locations * Track implementation progress * Collect required metrics * Estimate environmental benefits * Support grant reporting * Combine results across many organizations Each Funding Program may have its own instructions and data requirements. ### Funding Programs, Opportunities, and Pacts structure Funding Programs use **Opportunities** and **Pacts** to collect information. An **Opportunity** represents a specific grant round, award year, reporting effort, or other reason that organizations are being asked to share records. Each opportunity has a unique code and period where users can create pacts within it. A **Pact** connects your organization to that Opportunity. For example: **Program:** Chesapeake Bay Stewardship Fund\ **Opportunity:** 2026 Implementation Awards\ **Pact:** Your organization’s individual award You use the Pact to share selected Activities with the Program Manager. ## Create Your Pact In reality, users need a **pact code** and that will create a pact within the correct opportunity. Basic and Standard users will never start by looking for a Program. {% hint style="info" %} **Missing your pact code?** Reach out to the Program Manager of your Program or contact if you do not know who that is. {% endhint %} ## Managing your Pact The Pact is where you will create or link the Activities being supported by the award or included in the reporting effort. Pacts are accessible and organized within their own tab on your workspace portfolio. ### Review the Program Requirements Each Program sets different data management expectations for the information that they are collecting in FieldDoc. Requirements may include: * Specific naming conventions * Available Activity Types * Requirements for what to delineate as a geometry (ie general point, implementation footprint, county, etc.) * Planned and Completed Programmatic metrics * Environmental models * Status and implementation dates * Documents or images * Application or reporting deadlines {% hint style="warning" %} Review your program's unique Pact instructions before entering information. Requirements for one program may not apply to another. {% endhint %} # Introduction to Models FieldDoc offers a curated set of analytical models to help you estimate the environmental impact of your conservation and restoration activities. Our team integrates established, peer-reviewed models from trusted sources. When needed, we also build or connect to external APIs to generate dynamic, location-specific impact estimates. ## Models Overview FieldDoc offers a curated set of analytical models to help you estimate the environmental impact of your conservation and restoration activities. Our current lineup covers parameters such nutrient and sediment load reductions and carbon sequestration gains. FieldDoc integrates established, peer-reviewed models from trusted sources. When needed, we also build or connect to external APIs to generate dynamic, location-specific impact estimates. {% hint style="warning" %} **An important note about model behavior.** Models are mathematical simulations of the real world that represent how various changes or actions could affect ecosystems. These simulations are not a perfect forecast of on-the-ground outcomes. Due to variations among model techniques and versions, FieldDoc's results may differ from those generated by other systems. Do not use FieldDoc model outputs for legal compliance. FieldDoc models are only intended to provide additional context and insight about conservation and restoration activities. {% endhint %} ## Available Models ### Adapted Chesapeake Nutrient and Sediment Load Reduction Model ![Chesapeake Bay Program logo](https://app.fielddoc.com/images/logos/cbp-logo.svg) Estimate load reductions based on Phase 6 best management practice isolation run outputs provided by the Chesapeake Bay Program. ### COMET-Planner ![USDA Natural Resources Conservation Service logo](https://app.fielddoc.com/images/logos/nrcs-color-lockup.svg) Estimate the carbon sequestration and greenhouse gas impacts of NRCS conservation practices for initial planning purposes. ### National Water Quality Model
Estimate potential nutrient and sediment load reductions produced by best management practices (BMPs) supported by the EPA's Pollutant Load Estimation Tool (PLET). ### Shoreline Restoration Load Reduction Estimates ![Chesapeake Bay Program logo](https://app.fielddoc.com/images/logos/cbp-logo.svg) Estimate load reductions using data and algorithms from the 2019 Shoreline Management Expert Panel Report. ### Stormwater performance standard - Treatment depths other than 1 inch ![Chesapeake Bay Program logo](https://app.fielddoc.com/images/logos/cbp-logo.svg) Estimate nutrient and sediment load reductions using data and algorithms from the October 26, 2020 Consensus Recommendations to Improve Protocols 2 & 3 for Defining Stream Restoration Pollutant Removal Credits. ### Stream Restoration Load Reduction Estimates (Protocols 1 - 5) ![Chesapeake Bay Program logo](https://app.fielddoc.com/images/logos/cbp-logo.svg) Estimate nutrient and sediment load reductions using data and algorithms from the October 26, 2020 Consensus Recommendations to Improve Protocols 2 & 3 for Defining Stream Restoration Pollutant Removal Credits. ### Oyster Aquaculture ![Chesapeake Bay Program logo](https://app.fielddoc.com/images/logos/cbp-logo.svg) Estimate nutrient and sediment load reductions using data and algorithms from the October 26, 2020 Consensus Recommendations to Improve Protocols 2 & 3 for Defining Stream Restoration Pollutant Removal Credits. ### Virginia Runoff Reduction Method (Runoff Only)
Estimate the volume of stormwater infiltration and storage based on site-specific conditions. # Tutorial: Set up your organization {% hint style="info" icon="circle-user" %} **Tier:** Basic, Standard, Aggregator {% endhint %} This tutorial will teach you how to set up and manage your organization's FieldDoc organization by: * Creating your organization * Create additional workspacesStandard * Assigning different roles to organization staff and external collaborators * Set up your portfolio folder structure In this tutorial, you are the first user to create an account at a non-profit organization, ***Westmarch Conservation Society***. This organization uses FieldDoc to track work across three distinct regional programs. Westmarch Conservation Society has the following staff, collaborators, and structure: * Executive Director: You - Elanor Fairbairn * Two Managers: * Rowan Underhill * Perry Tooker * Three Programs: * Silverlode Watershed Restoration Program * Longbottom Meadow Conservation Initiative * Greenway Forest and Stream Resilience Program * Two Technical Service Provders: * Elanor Greenbank, Greyhaven Geospatial Services * Sam Groundwell, White Tree Environmental Consulting You're going to: * Create a FieldDoc Organization Standard Account * Workspaces for each Program to manage work * Assign Staff and Collaborators to the respective workspaces * Prepare a portfolio file structure. ## Before you begin Make sure you are using your professional email address. If your organization already exists in FieldDoc, this process may be slightly different. ## Create your user account First, you will create your user account. As the first user to enter the FieldDoc system, you will be invited to create a new organization and you will be listed as the owner of this organization. Only owners can access billing. To create your account: 1. Open fielddoc.com/register 2. Fill in the provided fields with your first `Elanor` and last name: `Fairbain`, professional email address `fairbain@WSC.ME` , and a secure password. 3. Click **Create Account**. 4. Open your email inbox to retrieve the six-digit verification code. Enter it into the provided box. 5. The system will confirm your verification. ## Create your organization 6. During the same registration flow, the system invites you to join an existing organization or create a new organization. 7. Type in your official organization name, `Westmarch Conservation Society`. 8. Click **Continue**. 9. All organizations start with free, `Basic` Subscription. ## Upgrade to Standard `Westmarch Conservation Society` must upgrade to **Standard** to create multiple workspaces, add an expanded group of users, access the available models, and integrate their records with third-party systems. 1. Elanor Fairbain has an `owner` level account. Only owners can upgrade accounts from basic. 2. In the bottom left hand corner, select the three elipses next to your name. 3. Choose **Organization** from the pop up menu. All of the Organization settings appear in the main view. 4. Scroll down to **Billing**. 5. Choose the **Standard** Plan and preferred billing cycle (Monthly or Annual). Click **Upgrade**. 6. Enter in your payment information. Click **Start trial.** ## Create Workspaces for your Programs By default, each organization has one workspace. Organizations on the Standard Plan can configure up to three separate workspaces. Workspaces are independent containers for records; they are not nested within one another. Organizations commonly use multiple workspaces to separate distinct programs, teams, or geographic areas. 1. To add additional workspaces to your account, contact . In the body of the email, include your organization name and the names you would like to assign to your workspaces. ## Invite Staff to your Organization FieldDoc users join the organization that directly employs them. Contractors and consultants join their own “home” organization, then receive access to client workspaces as collaborators. Staff can self-onboard and join your organization, as long as your emails have the same domain. Alternatively, you can invite your staff to your organization. 1. In the bottom left hand corner, select the three elipses next to your name. 2. Choose **Organization** from the pop up menu. All of the Organization settings appear in the main view. 3. Scroll to **Members**. Click the button to **+ Invite member**. 4. Enter the email address of your staff. 5. Select the accessibility level that they need: **Read Only** or **Admin**. {% hint style="info" %} User levels explained: **Read only:** When they accept the invitation, the user will have read-only access to this organization’s data and settings. **Admin:** When they accept the invitation, the user will have full access to create, modify, and delete this organization’s data and settings. They will also have permission to create, modify, or delete any type of record within this organization. **Owner**: Same level of permissions as Admin, but can access billing information. If you want to upgrade an additional user to **Owner**, reach out to for assistance. {% endhint %} 6. When you hit **Send invitation** we'll deliver a message to their inbox with a private link to create a FieldDoc account. 7. The user will click on the link and the system will invite them to choose a password. 8. Once in the system, the new user can click the ellipses in the bottom left hand corner to update their account settings with their real name. ## Assign Staff and Collaborators to Workspaces By default, all organization members are assigned to the original workspace. Workspaces are independent containers for records; they are not nested within one another. You can invite members of your staff and external collaborators to any of your workspaces. 1. In the upper right hand corner click the expand button and switch to the workspace that you want to add users to. 2. Once that workspace is active, select **workspace settings**. 3. Click the button **+ Invite member**. 4. Enter the user's email address and select their access level: **Read-only** or **Admin**. 5. The user will receive an email inviting them to the workspace. 6. After following the email prompts, the user will be able to switch between workspaces when logged into their FieldDoc account. ## Set up your portfolio structure An Activity record represents a single, trackable conservation or restoration action and captures what is planned or completed, where it occurs, and its expected outcomes. Within a Workspace, organize Activity records into folders to group related work by program, project, location, grant, or another structure that supports collaboration and reporting. {% hint style="info" %} **Basic.** Users in a Basic Organization create Activity records within Pacts. Each Activity remains linked to the Pact where it was created and is also added to the organization’s Portfolio. When Activities are added to the Portfolio, they appear as unorganized records. You can create folders and move Activities into them to keep your records organized. **Standard.** Users in a Standard Organization are encouraged to organize Activity records in folders within each Workspace’s Portfolio. Activities created within a Pact are also added to the Portfolio as unorganized records. After creating an Activity in a Pact, move it into the appropriate folder in your Workspace. Alternatively, create records in your portfolio and link them to your pact. {% endhint %} 1. Open the **Activities** tab. 2. Click :file\_folder: **New Folder**. This creates a folder in which you can organize activity records. 3. Within the folder on the main viewer, click the **Activities** tab. 4. You can add a sub-folder by clicking **New Folder**. This folder will be nested within your original folder. 5. When you are ready to create activity records, click **+ Create activity** within the final folder. 6. Add in your activity record data. Repeat. # User Account To access FieldDoc, you must have an active user account. ## Create your user account All user accounts must be assigned to an organization. 1. Navigate to fielddoc.org/register 2. Enter in your name and professional email address. 3. Click Complete. 4. Open your inbox and copy the six digit verification code. 5. Enter the code into the verification field on your screen. 6. Once confirmed, select an organization or create a new one. {% hint style="info" %} If you belong to a large organization, government body, or institution, you may need to contact for assistance completing your account registration. {% endhint %} ### Join an existing organization If your organization already exists in FieldDoc, you will be able to add your account to that organization. 1. FieldDoc will look at your email domain and match you to the organization in FieldDoc with the same domain (if one exists). 2. Click to join the organization. 3. FieldDoc will automatically confirm your membership and bring you to your home page. Welcome! ### Create a new organization If you are creating a new organization as you set up your account, you will be presented with a screen where you can create a new organization. ## Invite your colleagues New in 2025, you can invite your colleagues (staff with the same email domain) to join your organization. During the invitation process, they will be able to create their own FieldDoc account. ## Join external workspaces If you collaborate with another organization in FieldDoc, a member of that organization can add you to one of its Workspaces. Workspace access allows you to work within that organization’s Portfolio, including creating, editing, and deleting records or building Pacts on its behalf. You will use the features available through that organization’s plan while working in its Workspace. *** {% hint style="success" %} **User Account Management best practices** * Every FieldDoc user needs their own account — do not share log-ins! * Make sure you are using a current email address. Email addresses that bounce back will be archived. * Use your work email account and real name. {% endhint %} # User Roles Your account type and roles determine which actions you're allowed to take in FieldDoc. Explore the different user types and roles to help you decide which setup is right for you. ## Organizations Stewarding data for an organization is a multi-person, multi-year effort so it's important that data is accessible across an organization and not limited to single-viewer accounts. FieldDoc organizations represent real-world entities, such as companies or non-profits, whose employees and/or volunteers manage data using the platform and its associated tools. All data and activities in FieldDoc are linked to an organization. As the users within an organization change over time, the data remains constant. All users within an organization are categorized as standard or general users. All users are assigned to an organization, regardless of their user type or role. *** ## User Types ### Standard Users Standard FieldDoc users can create a portfolio of activities and metrics, collaborate on activities created by other users, or share their activities through a Pact. Users are associated with an organization, which allows all members to view records within that organization. If you're using FieldDoc for grant reporting, a Standard account is required. Within an organization, users can be assigned either Admin or Read-Only access to a portfolio. {% hint style="info" %} ### At Registration Upon registration, all FieldDoc users start with **Standard** access. Through the registration process, you'll complete your standard account setup. Once you have created an account and assigned yourself to your organization, you will be able to add, edit, and delete data within your organization's portfolio. If you would like to upgrade your account to one of the user types listed below, please reach out to for assistance. {% endhint %}
Organization/pages/tbdSBOvHRPkpL9fKkFIw
Workspaces/pages/wnEQnufXPb0BGpA1iojB
### Technical Service Providers This work is nothing if not a team effort! We want to make sure that your full team — both within your organization and those outside of it — can access the relevant information in FieldDoc. Collaborators are **Standard** users that have been given access to a **Workspace**, **Project**, **Pact**, or **Activity** outside of their organization. Collaborators are often Technical Service Providers (TSP) who support a grant recipient on everything from data management to sharing of detailed engineering designs. Collaborators looking to use FieldDoc to support their partners and clients must configure their own organization and a standard user account, just like the organizations that they are service - even if you are only working with one other organization in FieldDoc. Your collaborators can add you to their workspaces or projects *after* you have created your account.
Collaboration/pages/HrcOJTtykilgmJakRZYI
### Funding Program Managers Programs hosted in FieldDoc have a curated list of **activity types**, metrics, models, and target outcomes. Programs collect Activities from their constituents via Pacts. Program Managers are assigned by FieldDoc staff to the Program(s) that they manage. Once we configure a Program Manager account, that user can see all **Pacts** assigned to their program. *** ## User Roles FieldDoc offers two types of user roles: **Admin** and **Viewer**. These roles are available at various entry points, including **Organizations**, **Workspaces**, **Projects**, **Pacts**, and **Activities**. This enables you to share and collaborate on FieldDoc records at your preferred scale. For example, you may work with a contractor who needs broad access to your workspace. Adding that person as a Workspace Admin will grant them full permissions on all Project, Pact, and Activity records within your workspace (but *not* your organization settings). By contrast, sometimes you might need to invite a third-party to assist on a *subset* of your Activity records. In that case, a sound approach is to add those activities to a Project and share the Project with one or more of your external collaborators. ### Organization #### Admin Organization Admins have unrestricted access to an organization’s data and settings. They can add, modify, and delete records (e.g. projects, activities, metrics, pacts) and members. #### Viewer Organization Viewers have read-only access to an organization’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete any records within their organization's account. ### Workspace #### Admin Workspace Admins have **unrestricted** access to a workspace’s data and settings. They can add, modify, and delete records (e.g. projects, activities, metrics, pacts) and members within the workspace. #### Viewer Workspace Viewers have **read-only** access to a workspace’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete any records within the workspace. ### Project #### Admin Project Admins have **unrestricted** access to a project’s data and settings. They can add, modify, and delete records (e.g. projects, activities, metrics) and members within the project. #### Viewer Project Viewers have **read-only** access to a project’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete the project or any records that it contains. ### Pact > #### 🚧Pact roles **do not** have access to the pact's **program-level**, **workspace-level**, or **organization-level** members or other settings. #### Admin Pact Admins have **unrestricted** access to a pact’s data and settings. They can add, modify, and delete records (e.g. activities, metrics) and members within the pact. #### Viewer Pact Viewers have **read-only** access to a pact’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete the pact or any records that it contains. ### Activity #### Admin Activity Admins have **unrestricted** access to an activity’s data and settings, including collaborators, metric values, and all activity metadata. #### Viewer Activity Viewers have **read-only** access to an activity’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete the activity or any records that it contains (e.g. files, metric values, model outputs). # Organization ## Organizations An **Organization** represents the real-world entity you work for or represent in FieldDoc. It is the primary account structure that connects your users, Workspaces, records, and FieldDoc subscription or access. Organizations may include nonprofit organizations, government agencies, funders, universities, businesses, watershed groups, land trusts, technical assistance providers, and other entities involved in conservation and restoration work. Every FieldDoc user is associated with an Organization. ### How Organizations work Your Organization establishes the organizational home for your work in FieldDoc. Within an Organization, users can: * Access the Organization's Workspaces based on their permissions. * Create and manage Activities and other Organization records. * Organize records within the Organization's Portfolio. * Participate in Programs by linking Activities through Pacts. * Collaborate with people from other Organizations through Workspaces and sharing. Records created on behalf of an Organization remain associated with that Organization unless they are transferred, deleted, archived, or otherwise reassigned. This means FieldDoc records belong to the Organization's body of work rather than to the individual user who created them. ### Organizations and Workspaces Organizations and Workspaces serve different purposes. An **Organization** represents the real-world entity responsible for the account and its records. A **Workspace** is a working area used to manage a distinct collection of that Organization's records. An Organization on a Standard plan may use Workspaces to separate different programs, partnerships, teams, or bodies of work. Each Workspace has its own folder structure and provides a defined place for users and collaborators to work with records. Think of the relationship this way: **Organization → Workspaces → folders and records** Your Organization provides the overall home for your data. Workspaces help organize and manage that data. ### Organization membership Each FieldDoc user is assigned to one Organization. You should join the Organization that you are authorized to represent. Your Organization might be your employer, agency, nonprofit, business, university, or another entity for which you are authorized to work in FieldDoc. People who work with your Organization but represent a different entity do not generally need to become members of your Organization. For example, a: * Consultant * Technical service provider * Partner organization * Funder * Agency partner can maintain their own FieldDoc Organization and collaborate with yours through **Workspace access, sharing, Pacts, or other available collaboration tools**. This keeps Organization membership accurate while still allowing people from different Organizations to work together. ### Organization Owners Each Organization has at least one **Organization Owner** responsible for managing the Organization's FieldDoc account. Organization Owners are responsible for administrative tasks such as: * Managing subscription level and billing. * Maintaining Organization membership. * Adding, removing, or updating users. * Assigning appropriate roles and permissions. * Monitoring collaborator access. * Managing Organization records. * Maintaining applicable account and billing information. Organization Owners should periodically review membership and remove or update users who no longer represent the Organization. Removing a user does not remove records they created on behalf of the Organization. Those records remain part of the Organization's data unless they are otherwise managed in FieldDoc. ### Organizations and record ownership Organizations are an important part of how FieldDoc maintains responsibility for conservation and restoration data. When a user creates a record on behalf of an Organization, that record becomes part of the Organization's body of data. Users should therefore create records within the Organization that is responsible for managing that work. For example, if a technical service provider is creating Activities on behalf of a partner organization, the appropriate collaboration method may be to give the provider access to the partner's Workspace rather than creating the Activities under the technical service provider's Organization. This helps preserve the connection between the record and the Organization responsible for the underlying conservation or restoration work. ### Collaborate with other Organizations You do not need to belong to another Organization to work with its FieldDoc records. FieldDoc provides several ways for Organizations to work together: * **Workspace access** gives an external user ongoing access to work within a particular Workspace. * **Sharing** gives another user access to selected records. * **Transfer** moves responsibility for a record to another Organization. * **Pacts** link Activities to a Program for reporting, review, or Program participation. These options allow users to collaborate across organizational boundaries without changing their Organization affiliation. ### Organizations and Programs An **Organization** and a **Program** represent different relationships in FieldDoc. Organizations create and manage conservation and restoration records. Programs provide a structure for funding, reporting, review, aggregation, or other coordinated work managed by a Program Manager. Organizations participate in Programs through **Pacts**. A Pact links selected Activities from an Organization to a Program and makes that information available for Program purposes. Linking an Activity to a Program does not move the Activity into the Program or change the Organization responsible for the underlying record. It also does not automatically give the Program Manager permission to edit the Activity. ### If you work with multiple Organizations Your user account is associated with one Organization, but you may work with records managed by other Organizations through FieldDoc's collaboration features. For example, a technical assistance provider might belong to their consulting Organization while also being given access to Workspaces managed by several partner Organizations. In these situations, check which **Workspace** you are working in before creating or editing records. The active Workspace determines the organizational context in which you are working. ### If you are in the wrong Organization Accurate Organization membership is important because it affects record responsibility, access, and account administration. If you joined the wrong Organization or believe your Organization assignment needs to change, contact your Organization Owner or FieldDoc support. If records were created under the wrong Organization, do not delete them simply to recreate them elsewhere. Contact FieldDoc support to determine whether the records should be reassigned or transferred. # Workspaces IN THIS ARTICLE Workspaces allow organizations to manage their FieldDoc records and invite team members, collaborators, and technical service providers to help with their work. By giving trusted collaborators access to a Workspace, organizations can coordinate record creation, data management, Pact development, and reporting throughout the data lifecycle. *** ## Workspaces {% hint style="info" icon="circle-user" %} **Tiers**: Basic (1 workspaces), Standard (3 workspaces), Aggregator (custom) {% endhint %} Workspaces organize records in FieldDoc. Each Workspace contains a distinct set of Activities, folders, Pacts, Metrics, and related records that users with access can create, organize, review, and update. Because each Workspace is separate, the same user can work in multiple Workspaces without combining the records or folder structures within them. This is useful when an organization needs to manage different collections of work or when users need access to records managed by another organization. ### How Workspaces organize records Think of a Workspace as a shared working area for a particular collection of FieldDoc records. Within a Workspace, you can: * Create and manage Activities. * Organize Activities into folders and subfolders. * Manage Pacts connected to funding or reporting Programs. * Review Metrics and other information associated with your records. * Work with other users who have access to the same Workspace. The way records are organized in one Workspace does not determine how they are organized in another. **Folders are specific to the Workspace where they are created.** This distinction is important when you work across multiple Workspaces. A record may be shared or made available elsewhere, but its organization within one Workspace does not automatically carry over to another Workspace. ### Workspace access Users can have access to more than one Workspace. Your access will depend upon the following conditions: * You are part of the Organization associated with the Workspace. * You were added to the Workspace so you can work with another Organization's records. This allows organizations to give collaborators or technical service providers access to the records they need without requiring all work to be managed in the same Workspace. Workspace access is different from sharing an individual folder or record. **Workspace access allows a user to work within that Workspace, while folder and record sharing makes selected records available outside their original Workspace.** ### Determine which Workspace you're in Before creating or organizing records, check which Workspace you are currently using. The active Workspace determines where new records and folders are created and which existing records you can see and manage. If you have access to multiple Workspaces, switch to the appropriate Workspace before beginning your work. This helps keep Activities, folders, Pacts, and other records organized in the correct location. ### Workspaces and Organizations A Workspace belongs within an Organization's FieldDoc account structure and provides a defined place for managing records. Organizations may use Workspaces to separate collections of records that need their own organization or group of collaborators. For example, an Organization might use separate Workspaces for different programs, partnerships, or bodies of work. How an Organization should divide its records among Workspaces depends on how the records need to be managed and who needs access. ### Workspaces and Pacts Workspaces help your Organization manage its own records. **Pacts serve a different purpose: they allow Activities from within your workspace to be shared with a Program for a defined purpose, such as funding, grant tracking, or reporting.** An Activity can therefore be managed within your Workspace while also being included in a Pact for review by a Program Manager. Activity records in your workspace can be shared to multiple pacts that are within the same workspace. Just remember, records do not move between workspaces - each workspace is a contained space. Keeping this distinction clear helps maintain record ownership and organization while still allowing information to be shared for program reporting and collaboration. ### Important notes * Each Workspace has its own folder structure. * Users may have access to multiple Workspaces. * Workspace access and record sharing are different forms of access. * Pacts provide a way to share Activities with Programs without changing where those Activities are managed. * Before creating new records, confirm that you are working in the correct Workspace. ## Accessing multiple workspaces FieldDoc Users do not have a limit on the number of workspaces that they can belong to. This is especially helpful for technical service providers who join organization workspaces to work on behalf of their clients. #### Users that may have access to multiple workspaces * **Standard** plan member. Organizations with a standard plan can create up to three workspaces as part of their base subscription. You may be given access to one or many workspaces by the organization admins. * **Collaborators**, such as technical service providers. Your clients can invite you to be an admin of their workspace so that you can add, edit, delete records on their behalf. #### Switching workspaces 1. Log in to FieldDoc. 2. Locate the Workspace switcher in the upper-left corner. 3. Select the vertical arrows icon to view your available Workspaces. 4. Select the Workspace you want to open. 5. Confirm that you are in the correct Workspace before creating or changing records. After you switch, FieldDoc displays the Portfolio, features, and permissions associated with the selected Workspace. Any records you create while working in that Workspace are owned by that Workspace’s organization. They remain there when you switch to another Workspace. Records and folders are not automatically shared or searchable across Workspaces. {% hint style="info" %} Any work that you complete in this workspace is owned by that workspace and will remain in that workspace when you switch to a different workspace. Records are not searchable across workspaces. {% endhint %} ### Invite a new member to a workspace Invite someone to a Workspace when they need to create, review, organize, or manage records on behalf of the organization. Before inviting an external collaborator, confirm that the person has a FieldDoc account connected to their own home organization #### Step-by-Step Instructions 1. Log-into your FieldDoc account. 2. Open your **Account Settings**. 3. Click **workspace settings**. 4. Navigate to **Members**. 5. Click **Invite member**. 6. Enter in the email address. 7. Choose the Permission level. 8. Click **send**. {% hint style="info" %} Invitations are time sensitive. If an invitation expires, you can re-send it. {% endhint %} ### Important notes * Adding someone to a Workspace does not make them a member of the organization that owns the Workspace. * Records created in a Workspace are owned by that Workspace’s organization. * Folders and folder structures are unique to each Workspace. * Records are not automatically visible or searchable across Workspaces. * Give users only the level of access they need to complete their work. * Confirm the active Workspace before creating, editing, moving, or deleting records. # Members ## Members Members are the people who have access to work in your FieldDoc Workspace. Membership allows organizations to give staff, partners, and other collaborators access to the records and tools they need to manage conservation and restoration work. Members may receive access because they belong to the Organization associated with the Workspace or because they have been added directly to a Workspace. ### Types of members There are two common ways someone can have access to a Workspace: * **Organization members** are users who belong to the Organization that manages the Workspace. Organization membership provides access based on the Organization's configuration and the user's permissions. * **Workspace members** are users who have been given access to a specific Workspace. This is useful when someone outside your Organization needs to work directly with records in that Workspace. For example, an Organization might add a technical service provider to a Workspace so they can help create, organize, or update Activities without making that person a member of the Organization. ### Membership and record access Adding someone as a member is different from sharing an individual record. A member has access to the Workspace and can work with records available there according to their permissions. Sharing, by contrast, can give another user access to selected records without giving them general access to the Workspace. This distinction is useful when deciding how much access someone needs: * Use **membership** when someone needs ongoing access to a Workspace and its records. * Use **sharing** when someone only needs access to specific Activities, folders, or other records. * Use a **Pact** when Activities need to be shared with an external Program for a defined purpose, such as funding, review, or reporting. ### Add a member to a Workspace Add members when someone needs ongoing access to work within a Workspace. \[Confirm current navigation and who has permission to add Workspace members.] To add a member: 1. Open the Workspace Settings where you want to provide access. 2. Open **Members** tab. 3. Select **Invite member** button. 4. Enter the user's email address. 5. Review the access level that you are providing. 6. Select **Send invitation**. The person you add must use their own FieldDoc account. FieldDoc accounts can not be shared between users. ### View Workspace members Review your Workspace members periodically so you know who has access to your organization's records. To view members: 1. Open the Workspace settings. 2. Open **Members** tab. 3. Review the list of users with access. The member list can help you identify staff, external collaborators, and other users who can work within the Workspace. ### Remove a member Remove or update a user's access when they no longer need to work in the Workspace. \[Confirm whether removing a Workspace member affects Organization membership or only the selected Workspace.] Removing a user does not necessarily remove records they previously created on behalf of the Organization. Organization records remain part of the Organization's portfolio unless they are otherwise managed through FieldDoc. ### Members and collaborators Membership and collaboration provide different levels of access. A Workspace member is given access to work within a Workspace. A collaborator may instead receive access only to particular records or areas that have been shared with them. When deciding which approach to use, consider what the person actually needs to do. A consultant helping manage an entire collection of Activities may need Workspace access, while a partner reviewing a small set of records may only need those records shared with them. ### Manage membership carefully Workspace access can expose users to records beyond the individual Activity they are currently working on. Before adding someone, make sure they should have access to the Workspace and the records it contains. Organizations should also review membership when: * A staff member leaves the Organization. * A consultant or technical service provider completes their work. * A collaborator's responsibilities change. * Someone appears to have access to the wrong Organization or Workspace. If membership or record ownership appears incorrect and cannot be resolved through the available Workspace controls, contact FieldDoc support. # Collaboration ## Collaborating in FieldDoc FieldDoc is designed to support conservation and restoration work that involves multiple people and organizations. You can collaborate by **sharing records**, **giving someone access to a Workspace**, **transferring a record**, or **linking records to a Program through a Pact**. The right option depends on what you are trying to accomplish: **Who should manage the record, who needs access to work on it, and who only needs to receive it for Program reporting or review?** ### Ways to collaborate FieldDoc supports several different ways to work across people, Organizations, and Programs: | Collaboration method | Best for | What happens | | -------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Share** | Giving another user access to selected records | The existing record remains where it is managed while the collaborator receives access to the shared record. | | **Workspace access** | Ongoing collaboration across a collection of records | The collaborator works within the Workspace and can access records available there according to their permissions. | | **Transfer** | Moving responsibility for a record to another Organization | Responsibility for managing the record moves to the receiving Organization. \[Confirm exact access behavior after transfer.] | | **Pact** | Linking Activities to a Program for reporting, review, or participation in a Program | Activity information is made available to the Program through the Pact, but the Program Manager is not invited to make changes directly to the Activity. | These options are not interchangeable. Choosing the right one helps maintain clear record ownership, access, and reporting relationships. ### Share records for focused collaboration Use **sharing** when another person or Organization needs to work with specific records but does not need general access to your Workspace. For example, you might share records with: * A technical service provider helping complete Activity information. * A partner organization collaborating on a restoration project. * A colleague who needs access to a specific group of Activities. Sharing gives collaborators access to the selected records while allowing the rest of your Workspace to remain separate. #### Sharing folders When several related Activities need to be shared, you can share a folder instead of sharing each record individually. This can make it easier to provide access to an existing collection of records. **Important:** Sharing a folder provides access to the records contained in the folder when it is shared. New Activities created in that folder later are automatically shared with the collaborator. Your collaborator can create new records in the folder and they will remain in the folder owner's [workspace](/manage-your-organization/workspaces). ### Use Workspace access for ongoing collaboration Use [**Workspace**](/manage-your-organization/workspaces) **access** when someone needs to participate more fully in managing a collection of records. A Workspace is a discrete working area with its own Activities, folders, Pacts, Metrics, and related records. Adding someone to a Workspace allows that person to work within the Workspace according to their permissions. Workspace collaboration can be useful for: * Technical service providers managing records on behalf of another Organization. * Long-term project partners. * Consultants who need to create, organize, or update multiple Activities. * Collaborations where several people need to work from the same record structure. #### Workspace access versus sharing The main difference is **scope**. Sharing gives someone access to selected records. Workspace access gives someone access to the Workspace and the records available within it according to their permissions. If someone only needs to review or update a few Activities, sharing may be the better choice. If they are helping manage a larger body of work over time, Workspace access may be more appropriate. ### Transfer records when responsibility changes Use a **transfer** when the Organization responsible for managing a record needs to change. Unlike sharing, a transfer is intended for situations where the receiving Organization should become responsible for the record rather than simply collaborate on it. For example, a transfer may be appropriate when: * One Organization created a record that should be managed by another Organization. * Responsibility for managing an Activity moves from one Organization to another. * A partner created initial records and is handing ongoing stewardship to the Organization responsible for the work. Before transferring a record, confirm whether the originating Organization should continue to have access and whether additional sharing is needed after the transfer. Transfers should be used carefully when records are connected to a Pact, Program, award, or reporting requirement. ### Use Pacts to report or participate in a Program A **Pact** links Activities to a Program Opportunity for a defined purpose, such as grant reporting, Program review, or participation in a collaborative Program. Pacts are different from sharing or Workspace access because the relationship is **uni-directional**. When you link an Activity to a Pact, you make that Activity available to the Program according to the Program's reporting and configuration requirements. The Pact does **not** invite the Program Manager to become a collaborator on the underlying Activity. This means a Program Manager can review and use information submitted through the Pact without automatically receiving permission to edit or manage the Activity itself. If a Program Manager or another user needs to work directly on the Activity, you must use a separate collaboration method, such as **sharing** the record or providing appropriate **Workspace access**. #### Pacts versus direct collaboration Use a Pact when the goal is to: * Report Activities to a funding or reporting Program. * Submit records for Program Manager review. * Connect Activities to Programmatic Metrics, Activity Types, Models, or other Program requirements. * Participate in a Program while continuing to manage the underlying Activities within your own Workspace. Use sharing or Workspace access when another person needs to **work directly on the record**. A Pact establishes a reporting and Program relationship. It does not, by itself, establish a collaborative editing relationship. ### Sharing is not the same as transferring responsibility This distinction is central to collaboration in FieldDoc. When you **share**, you give someone access to an existing record while the record remains managed in its current context. When you **transfer**, responsibility for managing the record moves to another Organization. When you use a **Pact**, you link the record to a Program for reporting or review without giving the Program Manager collaborative access to the underlying record. ### Choose the right collaboration method A simple way to decide is to ask what the other person or Organization needs to do: **Do they need access to specific records?**\ Use **sharing**. **Do they need ongoing access to work across many records?**\ Use **Workspace access**. **Should another Organization become responsible for managing the record?**\ Use **transfer**. **Do the records need to be reported to or reviewed within a Program?**\ Use a **Pact**. If a Program Manager also needs to work directly on the record, use a separate sharing or Workspace collaboration method in addition to the Pact. ### Manage collaboration carefully Periodically review collaboration when: * A consultant or technical service provider finishes their work. * A partner's role changes. * Responsibility for an Activity changes. * A user no longer needs access to a Workspace. * A Program relationship ends. * A record appears in the wrong Organization or Workspace. Keeping collaboration methods distinct helps users understand who manages a record, who can work on it, and where its information is being reported. # Activities The base unit for FieldDoc data. {% embed url="" %} IN THIS ARTICLE FieldDoc Data Manager provides a digital portfolio where your organization can document, manage, and track nature-based work. The foundational unit in FieldDoc is the **Activity record**. These records can represent conservation, restoration, or other nature-based work that your organization plans, implements, monitors, or reports. Each Activity record can store a range of information about the work it represents. This may include a mapped location or footprint, implementation dates, descriptive details, progress status, and environmental model results that estimate benefits. You can use Activity records to track work from early planning through installation, completion, and long-term monitoring. Within your portfolio, you can organize Activity records using Folders. You can also share records with funders or program managers, export data, and use integrations to connect FieldDoc with other applications. {% hint style="info" %} In Legacy FieldDoc, Activities were called Practices. The change in FieldDoc 2.0 reflects the expanded list of nature-based work that can be tracked in FieldDoc. Restoration BMPs like cover crops, tree plantings, and wetland restoration are still supported as Activity\_Types. The expanded list includes additional work such as convenings, monitoring, and research. {% endhint %} *** Each activity record is accessible by a tile in your portfolio. Each record contain a wealth of qualitative, quantitative, geospatial, and standardized information about your nature-based work. Activity records help you track where you're implementing conservation and restoration activities, what you're implementing, and their impact. ## What is an activity record? An activity record should represent a single implementation or a representative example of a single implementation. Each activity record should be verifiable, if required, by the activity owner or by other authorized FieldDoc users, such as Program Managers or Collaborators. Keep this in mind when creating an activity record and delineating its geospatial boundary. For example, activity record geometries should not be delineated at the scale of an entire watershed, county, or state. Doing so may disrupt FieldDoc’s functionality. :seedling: Learn more about delineating the [geometry ](/essentials/activities/geometry) ## Create Activity Records FieldDoc makes it easy to create activity records within the platform, but if you already have data ready to port into the system, we have options to get that data into the system too! {% hint style="warning" %} **To use geospatial data when creating an activity:** If you have a shapefile or other geospatial file with multiple records, start from the **"File Import" option**. If you have a single shapefile, you can import it directly to a geometry. {% endhint %} {% tabs %} {% tab title="In-App Creation" %} ### When to use in-app Create Activity? Use the Create Activity button if you do not have a geospatial file for this record or a spreadsheet with prepared data. This will allow you to use FieldDoc's Map Editor to delinate the activity footprint. ### Where to find Create Activity? You can create an activity from multiple entry points: on **Home Page**, within a **Project**, or within a **Pact**. ### Step-by-Step Instructions 1. Open the Workspace where you want to create the activity record. 2. Enter a Name for the Activity. 3. From the **Activity Overview** Page, open the **three vertical ellipses** and select **Edit Activity**. This opens up the **Edit Activity Modal**. 4. Now you can enter in all of the attribute information that you have for this record. * **Activity Type** - Choose from the universal list. Click Save once you have selected the activity type. * **Geometry** - use the point, line, or polygon draw tools to delineate the activity location on the map. TIP - if you draw a line or polygon, you can grab the `extent`or set a custom extent on the **Extent** tab. * **Organization Metrics -** If you have a list of organization metrics, you can select metrics and set `planned_values` for all relevant metrics. (TIP - the activity must be assigned to a Pact before you can add programmatic metrics!) * **Models -** If you selected an Activity Type and there is an associated model, you can calculate model outputs on this tab. Most models require a geographic component, taken from the geometry, and an **Unit Value**. ### Dig in! Interactive Tutorial {% @arcade/embed flowId="2f5oGeYxLt3PmdvXVZmw" url="" %} For more information on any individual section, please visit the corresponding article. {% endtab %} {% tab title="File Import" %} ### When to use Batch Import Use the batch import option if you have geospatial file(s) or a spreadsheet of multiple activity records that you would like to create simultaneously. You can batch import a file with projects, activities, or metrics. If you have a single geometry, you will use the Batch Import feature to create the activity record and add the geometry to it in one step. ### Where to find Batch Impact? You can batch import from multiple entry points: on **Home Page**, within a **Project**, on the **Activity** page, or within a **Pact**. Once in the Batch Import modal, check the upper left hand-corner to confirm what the system thinks that you are importing. ### Step-by-Step Instructions 1. Prepare your source file. 2. Select the **File Import** button. 3. Select your source file and drop it in the modal. 4. Map your source file field names to the **FieldDoc Field Names**. 5. Click **Save.** The system will tell you how many records were imported. 6. If you were importing activity records, open the **Activities** within your **Portfolio**. 7. Since you cannot import the `activity_type:name`field, now is a good time to associate that FieldDoc managed data with your activity records. A "fast" way to add the `activity_type:name` is to toggle your activities to the grid view. 8. Select the field `activity_type:name` . A drop down appears. Search for the appropriate option, select it, and save. Repeat for all records. 9. If you are adding [Metrics](/essentials/activities#activity-metrics) or [Models](/essentials/activities/models) to your records, check out the corresponding articles for options for how to add those in expedited actions, like using table views. ### Dig in! Interactive Tutorial {% @arcade/embed flowId="ARE2dXl7n6sxPU4nEhmq" url="" %} {% endtab %} {% tab title="Table View" %} ### When to use Table Views to create Activities? You can create new activity records from the table views in FieldDoc. You will treat the table view like a spreadsheet to enter in an activity record within a single row. ### Where to find Table Views Table views for **Activities** are available within the **Activity Portfolio** as well as individual **Projects** and **Pacts**. ### Step-by-Step Instructions 1. Switch to the Table view. 2. In an empty row, type in the `Activity_Name` 3. Select the associated `Project_name`, if applicable. Tip! Activity records can only be organized in one Project. 4. Select the associated `Section_name`, if applicable. Tip! Activity records can only be organized in one Section, which is a sub-folder of the Project. 5. Select the `Activity_Type:Name`from the universal list. 6. Add your `Activity_Description`. This is a text field. This is a great place to add details for you and your team about the record that you are documenting. 7. Type in the `Practice:extent`. This is a number field. 8. Use the `practice:extent_unit`to define the extent. Select from the available drop down list. 9. Return to the **Tile** View. Open the **Edit Activity** modal to add a geometry and activate the model. 10. Open the **Geometry** tab. Use the draw tools to [delineate the geometry](/essentials/activities/geometry) for this record. 11. To activate a model, you need both an `activity_type` and a `geometry`.\ Keep in mind that not all `activity_types` have models, and some models may not work in all locations. ### Dig in! Interactive Tutorial {% @arcade/embed flowId="BeMDdwYMLwWdxl7OBjLh" url="" %} {% endtab %} {% tab title="Map Editor" %} ### When to use Map Editor to create Activities? We do not recommend using the Map Editor to create mulitiple activity records. If you want to create all of your records via a digital map editor tool, there are some excellent third party tools availble. We recommend using third party applications like ArcGIS Online, GeoJSON.io, or Placemark.io and then using our Import feature to add them to FieldDoc. ### Where to find Map Editor The Map editor view is available from the **Activity Portfolio** view as well as within individual **Projects** and **Pacts**. Please use the Map Editor to edit existing geometries. {% endtab %} {% endtabs %} ## Editing an Activity {% tabs %} {% tab title="In-App Editing" %} To edit an existing activity record, open the **Edit Activity** modal. From this view, navigate to the area that you would like to update and make your change. Remember to click save! {% endtab %} {% tab title="Import File" %} Currently, you cannot edit existing records by importing a file. {% hint style="warning" %} Any records in the imported file will be treated as new entries. {% endhint %} {% endtab %} {% tab title="Table View" %} Edits are easy in FieldDoc table views. We recommend using the **Activity Table** to edit `activity_type`, `extent`, `extent_unit`, and `completed_on`date. To edit **Metrics** associated with **Activities**, we recommend using the **Metric Table** and **Implementation** **Table** available in the **Project**, **Activity**, and **Pact** views. {% endtab %} {% tab title="Map Editor" %} If you would like to edit a geospatial feature for an **Activity** record, you can do that from the Map Editor view. You have the option of editing or deleting a geometry. You have the option of deleting an entire feature record too. {% hint style="warning" %} FieldDoc's Map Editor is not intended to be used for editing multiple records. If you want to make changes to multiple activity record geometries, we recommend using the Edit Activity>Geometry tools. {% endhint %} {% endtab %} {% endtabs %} *** ## Activity Attributes Overview ### General Settings The following provide a brief overview of the different attributes that you can attach to each Activity record. {% hint style="info" %} **What fields are required?** All fields in the activity record are *optional;* however, some Program Managers may have specific data standard requirements that must be met. Find your [Program Guide](https://help.fielddoc.org/guides-1/) for specific instructions. When building your organization's portfolio, we recommend creating your guidelines for your organization and collaborators to clearly indicate how you want to structure and name your data and what fields you want to include. {% endhint %}
Activity Type FieldDoc provides a universal Activity Type list of standard names. Users have the option to attach an activity type from this list to their activity record. This is helpful if you want to turn on environmental models or participate in funding programs with curated activity type lists. :seedling: Learn more: [Activity Type](/essentials/activities/general-settings/activity-type)
NEIEN Map this Activity to NEIEN best management practice specifications. Align activity metadata and implementation measurements with Environmental Information Exchange Network specifications. This information enables implementation tracking and crediting by state governments and the U.S. Environmental Protection Agency. :seedling: Learn more: [NEIEN](/essentials/activities/general-settings/neien)
Extent FieldDoc calculates extent based on the dimensions (area, length, etc.) of an activity's geometry. Many models and activity types use this number to calculate estimated nutrient and sediment reductions and other parameters. FieldDoc uses the World Geodetic System (WGS84, EPSG:4326) as its reference coordinate system. Note that the estimated extent value generated by FieldDoc may differ from values produced by other systems that process geospatial data. If necessary, fill out the "User-defined extent" inputs below to override the FieldDoc-generated extent. :seedling: Learn more: [Extent](/essentials/activities/general-settings/extent)
Completion Status Completion status indicates the date when the activity was fully installed by clicking the **Mark activity as completed** button. We recommend marking an **activity** as complete when all work is done to specification - this may The activity completion date is never generated by FieldDoc. It must be entered manually. :seedling: Learn more:[ Completion Status](/essentials/activities/general-settings/completion-status)
State Reporting For use by users that are submitting their Activities to State Reporting Leads for crediting. :seedling: Learn more: [State Reporting](/essentials/activities/general-settings/state-reporting)
Inspection Log Demonstrate ongoing functionality of an installed Activity, or BMP. :seedling: Learn more: [Inspection Log](/essentials/activities/general-settings/inspection-log)
Pacts Look at the Pacts associated with this record, or connect the record to a new/existing Pact. :seedling: Learn More: [Pacts](/essentials/pacts)
Project Project folders provide organizational structure to individual activity records. Activity records can only be associated with a single project. Project folders can also include sections, which provide even further organizational options. :seedling: Learn more: [Project](/essentials/activities/general-settings/project)
Privacy The privacy setting indicates that the geometry from this record should be generalized if shared via a Pact with a third party. It does not protect the data from being shared. :seedling: Learn more: [Privacy](/essentials/activities/general-settings/privacy)
### Geometry [➜](/essentials/activities/geometry) The geometry tab opens the Map Editor. From this view users can draw a geometry type to delineate the activity record footpring. FieldDoc provides basic draw tools for points, lines, and polygons.
:seedling: Learn More: [Geometry](/essentials/activities/geometry) ### Activity Metrics [➜](/essentials/activities/activity-metrics) Both Organizational Metrics and Programmatic Metrics can be added to individual activity records. Metrics will include a `planned_value`and `implemented_value`to track progress towards organizational goals.
:seedling: Learn More: * [Metrics - Organization](/essentials/metrics/metrics-organization) * [Metrics - Programmatic](/essentials/metrics/metrics-programmatic) ### Models [➜](/essentials/activities/models) Where available, you can choose to turn on environmental models that are associated with the selected `Activity Type` .
:seedling: Learn More: * [Models](/essentials/activities/models) * [Model Outputs](/essentials/model-outputs) *** ## Share Activity Records to Funder All activity records that you create become part of your portfolio. You can share some activity records to one or many third parties via [Pacts](/essentials/pacts). There are two pathways that you can take to share an Activity with a funder: ### Create an new activity record within a Pact. Within a Pact, navigate to the **Activities tab**. You can create new records by clicking **Create** or **Import File**.
{% hint style="info" %} **Tips about creating activity records within a Pact** * The benefit of creating records within a Pact is that the programmatic metrics will be available without any further action needing to be taken. * When you create an activity record within a Pact, it is not assigned to a Project Folder or Section in your Portfolio. You can organize your records from within the edit activity modal or from the Activity table view in your portfolio. {% endhint %} ### Link an existing activity record to a Pact All activities that you create are placed into your portfolio. All of these activities can be linked to one or many Pacts. Once an activity is linked to a Pact, [programmatic metrics](/essentials/metrics/metrics-programmatic) from that Program can be added to the activity record. #### Link records from within your Pact If you open an activity record, you can link it to a Pact without leaving the record from two locations: within the **Edit Activity** modal or from the **Overview>Pact** tab. From these views, you can create a new Pact or manage your Pact connections. You can also jump over to the Pact overview page using the hyperlink. {% @arcade/embed flowId="VvOHs1d363varM5l152n" url="" %} # Tutorial: Create your activity record IN THIS ARTICLE Learn how to create an Activity Record in FieldDoc, from naming the record and adding core details to mapping its location and attaching supporting files. This article also covers when to use activity types, models, and metrics so records support both internal tracking and program reporting. {% hint style="info" %} **Standard users** can create and manage Activity records within their organization’s portfolio. These Activity records belong to the organization’s workspace and can be organized in the organization's preferred structure using folders and subfolders. **Basic users** create Activity records within a Pact. We recommend finding the appropriate [Program Guide](/guides-1/program-guides/chesapeake-bay-stewardship-fund) for specific instructions on configuring a Pact. A Pact is used when a funder, program manager, or other third party has invited an organization to submit or share records for a specific Opportunity. In this case, the Pact provides the structure for creating, organizing, and sharing the required Activity records. Records will be added to a basic user portfolio so that they can be used for future funding opportunities and remain available if the organization upgrades to Standard. {% endhint %} *** ## Create an Activity Record Activity Records are the foundation of FieldDoc. They are digital representations of on-the-ground work that enable you to document restoration, conservation, planning, outreach, implementation, monitoring, and other nature-based work in a clear and trackable way. Use Activity Records to describe what work is happening, where it is happening, who is responsible, and what outcomes are expected. *** ### Before You Begin Before creating an Activity Record, make sure you are working in the correct Organization and workspace. If you are a **Standard user**, you create Activity Records within the desired workspace. If you are a **Basic user** working through a funding program or reporting process, you will usually create Activity Records inside a **Pact** connected to that program. If you have been invited to a workspace, pact, or folder from outside of your organization, make sure to switch to that workspace before creating the record. {% hint style="info" %} Some Programs may require specific Activity Types, Metrics, Models, or reporting fields. These requirements are managed by the Program Manager. If you are a basic user working on a pact, we recommend using the appropriate [Program Guide](https://help.fielddoc.org/guides-1) to set up your records. {% endhint %} *** ### Step 1: Create a New Activity From your FieldDoc workspace, click the **Activities** tab. Select **+ New Activity**.
{% hint style="info" %} You can actually create an activity record from many locations: * From your workspace's home page * Within a folder in your activity list * Within a **Pact** connected to a funding program or reporting opportunity {% endhint %} *** ### Step 2: Name Your Activity Each Activity Record should have a unique name.
{% hint style="info" %} We recommend that you create a system for naming all of your activity records and apply it to all records created in your workspace. A clear name makes the record easier to find, review, and report on later. This is part of the process of coming up with and using a data management plan. Check out our resources on [data management plan creation](/academy/guides/build-a-data-management-plan) for more details. Example: Smith Farm Loafing Lot {% endhint %} ### Step 3: Add attribute data to your record After you create the Activity Record, you can add more information to it. Wherever you see a pencil icon, you can add data or make edits.
*** #### Activity Type FieldDoc manages a universal list of **Activity Types**. Activity Types represent on-the-ground and real-world work completed for nature-based solutions, including: * Restoration * Conservation * Sustainability measures * Community engagement * Research * Monitoring * Observation Assigning an Activity Type is not required to create an Activity Record. However, activity types provide valuable standardization for future analysis and visualizations. Search and filter the available list of activity types to choose the option that best matches your work. If no Activity Type accurately matches your work, you can leave the field blank and describe the work using the Activity Name and Activity Description fields.
#### Add a Description and Status Use the Activity Description field to briefly explain the work and its status. Consider your future self and your collaborators when writing your description. Consider including information that is not captured in the standardized and quantitative fields, such as: * What work is being done * Where it is happening * Why is it being done * What outcome is expected * Who is involved? #### Edit Geometry In an activity record, the geometry represents the implementation footprint. FieldDoc provides drawing tools so users who do not have access to an existing shapefile can draw the footprint directly in the system.
You can use a: * **Point** to mark a specific location * **Line** to show a linear feature, such as a stream segment or trail * **Polygon** to show an area, such as a planting site, restoration footprint, or treatment area You can only add **one geometry** per Activity Record. {% hint style="info" %} **Import existing records.** If you already have geospatial data, you do not need to use FieldDoc’s drawing tools. If you have a file with multiple features, use the importer to batch create your Activity Records. During the import process, FieldDoc will map the attribute data fields to the FieldDoc schema and automatically assign the geospatial data to each new record. If you have a file for a specific activity, you can upload it via the **Edit Geometry** prompt. *** **Multi-polygons.** If you draw your footprint in FieldDoc, you can only have one polygon or geometry per activity record. If you are importing a shapefile or geoJSON, you can import a multi-polygon to one record (if the source file has configured the polygons to be one geometry). {% endhint %} ### **Extent** Once an activity record has a geometry, the system will estimate the geometric extent. You can use the User-Defined extent field to set a different extent, if desired.
### Step 4: Calculate Environmental Benefits Models estimate environmental outcomes, such as nutrient or sediment reductions or carbon sequestration capacity, based on the information entered into a model run. To calculate environmental benefits, open the **Models** tab. Multiple model runs can be added to a single activity record.
Review the inputs required for the selected Model. Once the correct inputs are entered, click **Run**. The model results will appear on the overview page of the activity record.
These outputs are saved to the Models tab and can be re-run at any time. {% hint style="warning" %} Models must be manually run. No models are automatically run in FieldDoc. {% endhint %} *** ### Step 5: Add Organization Metrics Metrics allow you to manually track progress toward target outcomes. If your organization has a curated list of metrics, you can select from that list to add to your activity record. Open the **Metrics** tab to add or review metrics connected to the Activity record.
### Step 6: Add Images or Attachments You can add images, documents, or other attachments to support the Activity Record. Attachments may include: * Site photos * Design files * Permits * Monitoring documents * Maps * Reports * Other implementation documentation Use attachments when they help explain, verify, or support the work described in the Activity Record. # General Settings Edit Activity modal contains a lot of editable fields associated with the Activity record.
IN THIS ARTICLE This tutorial walks you through the fields in the Edit Activity > General Settings view. Each field is tied to a single activity record and helps track progress toward installation and ecosystem outcomes. *** ## General In this view, you can enter in a unique name for your activity record. We recommend making sure that you're name is unique so that you don't end up with multiple records with the same name.
FieldDoc Field NameImport Field NameDescriptionTips
Namepractice:nameThis name appears throughout the system and is visible to anyone who can see the record.Make your name unique! If your organization has a unique identifier, you can use that; otherwise, make sure you avoid having seven records named "Forest Buffer - Narrow"
Descriptionpractice:descriptionThe description is a text field that allows you to add a narrative about your activity.Your description field may be useful for collaboration and for any program managers that you share the record with. Think, what would our future selves want to remember about this record?
# Activity Type
IN THIS ARTICLE Activity Types provide all users access to a standard list of activities that may be implemented for nature-based work. The list is extensive and continually growing. This article walks through how to add an Activity Type to a record and how to best navigate the list of options. *** ## Activity Types In FieldDoc, **activity types** represent the kinds of restoration or conservation practices being implemented. They define *what* kind of work is being done—such as **tree planting**, **cover cropping**, **stream restoration**, **wetland creation**, **monitoring**, or **convening**. Each activity type typically includes: * **Unit types** for measurement * Optional **modeling support**, depending on the geography and practice * Optional **NEIEN BMP** code. * **A suggested set of standard metrics** (like acres, feet, number of trees, etc., provided by the program funder) They help organize and categorize projects so that outcomes can be consistently tracked, compared, and reported across programs and geographies. ## Set your Activity Type Activity Types can only be added to a record from within FieldDoc. 1. Click the button to select an Activity Type, you open the universal list. 2. Use the search or scroll features to find the appropriate option to associate with your activity record. 3. Click save. ### Dig In! Interactive tutorial {% @arcade/embed flowId="iL64trXzjvGVpyS5Gty4" url="" %} *** ## Explore using search fields
#### Name Search by the Activity Type name. Some Activity Types include an NRCS code, so you can also search by that code. #### Group Some of the Activity Types supported in FieldDoc have been grouped by the leading scientists, modelers, or conservation professionals that created the list. Where possible, FieldDoc honors those groupings and lists them as a search option. #### Description Some activity types include descriptions provided by program managers and the guides that they reference. When available, FieldDoc displays these to help guide all users in their selection. To view the full description, click the **“More”** link. Descriptions may also include instructions on how to properly map the footprint for that activity type. #### Model(s) You can see which Activity Types are supported by available models in the FieldDoc system. #### Program(s) Some of the funding programs that use FieldDoc to collect application or grant recipient data have suggested lists of activity types. When these have been provided by program managers, all users can benefit by sorting by the programs. {% hint style="warning" %} Selecting an activity type associate with a funding program does not automatically create a pact or load the associated programmatic metrics to your activity record! {% endhint %} ## Commonly asked questions
Can I access a list of activity types without entering my activity records? To review the list of **Activity Types** available in FieldDoc, open the **Activity Types** tab on your left hand panel. The FieldDoc team is routinely updating this list, so please check back often.
I don't know which activity type to choose, can you help? While the team at FieldDoc consists of professionals with decades of experience in environmental sciences, we strongly recommend that you research available documentation or reach out to your technical service providers and funding program managers to discuss which activity types to choose.
Do the models work in every geography? For example, can I select an activity type with the CAST model in Missouri? Some models are universal while others are geography specific. We recommend looking at the Model(s) field to confirm that you are choosing an activity record that may have an available model.
The Activity Type used to be associated with a model, but it's not there anymore. FieldDoc partners with leading modeling experts to provide access to sediment and nutrient reduction calculations. Recently, access to a regional model used in the Delaware River Basin was discontinued. As a result, activity types linked to Delaware River programs in FieldDoc are currently unable to generate load reduction estimates. Our team is actively working to restore this functionality by integrating a new model, ensuring that practitioners in the region can once again access these important calculations.
# NEIEN
IN THIS ARTICLE FieldDoc make it easy to map your activity records to the NEIEN schema. This is especially helpful for organizations conducting their own NEIEN reporting or grantees that must meet NEIEN reporting requirements through awards received. *** ## NEIEN Align activity metadata and implementation measurements with Environmental Information Exchange Network specifications. This information enables implementation tracking and crediting by state governments and the U.S. Environmental Protection Agency. ### Step-by-step instructions 1. Open the NEIEN tab. 2. Click the `+ measurements`button. 3. Search to select the NEIEN best management practice from the available list. 4. Find and save your selection. 5. Enter the measurement value for one or more of the options. If you are unsure, you can reach out to or your state reporting lead. ### Dig in! Interactive Tutorial {% @arcade/embed flowId="CSQk2eOYEssNMdoDt75a" url="" %} # Extent Displays the estimated footprint based on the geometry associated with this activity record.
IN THIS ARTICLE Review the FieldDoc estimated extent, convert it to different units, or enter your own value.\ Note: These inputs are for reference only and are *not* used in any additional calculations or features. *** ## Extent This view allows you to input two types of extent: 1. **Estimated Geometric Extent** – Automatically calculated based on the dimensions (area, length, etc.) of the activity’s geometry. Many models and activity types require a unit input tied to geographic extent, so this value is useful to keep with your activity record. 2. **User-Defined Extent** – If your geometry doesn’t include a measurable extent (e.g., a point location), or if the estimate is inaccurate, you can manually enter an extent and select the appropriate unit. This will override the FieldDoc estimated extent, however the system-generated field will remain visible (you cannot delete it).
FieldDoc Field NameImport Field NameDescription
User Defined Extentpractice:extentEnter in a numerical value for the activity record extent.
Unitpractice:extent_unitEnter in the unit type, such as acres or linear feet.
{% hint style="warning" %} The Extent fields are not automatically used to calculate most models. To run a model, you must enter in the unit input (which may be the extent available from this page) into the corresponding model input field and then press run. {% endhint %} # Completion status Mark the date that your record was installed to specification.
IN THIS ARTICLE The completion status helps track the lifecycle of your nature-based work. Explore how to set your completion status. *** ## Completion Status You only get to enter the completion status for an activity record once. Enter the date when the activity was fully installed by clicking the "Mark activity as completed" button. An activity is complete when all implementation work is finished. Set your completion status. 1. The user setting the completion date will be logged as the attestation person. 2. Open the Completion view. 3. Click the button to open and enter in the date of completion. This can be an estimated date, but it must be a date in the past. 4. Click save. ## Dig in! Interactive Tutorial {% @arcade/embed flowId="2sEA2XYkyh60PYNVypNd" url="" %} # State Reporting
IN THIS ARTICLE State reporting assists stakeholders in tracking the BMPs that are managed in FieldDoc and reported for inclusion in State Reports. *** ## State Reporting The FieldDoc fields for state reporting serve as a data tracking feature. Currently, no data is directly shared with the NEIEN system. However, The Commons has agreements with certain entities to report to state reporting leads, who then include the BMPs tracked in FieldDoc in their templates for submission to the NEIEN data exchange warehouse. These fields are used by The Commons to track confirmed BMPs associated with impacted activity records. Standard FieldDoc users who report directly to their state leads can also use these fields to support their own internal tracking efforts. These fields must be manually inputted within each record. # Inspection Log
IN THIS ARTICLE What happens once a restoration or conservation activity is completed? It's time to monitor it's impact. Use **Inspection Logs** to track visits to the activity site and share observations of the functionality. *** ## Inspection Logs Once your restoration or conservation activity is installed to specification, the next critical step is to monitor its ongoing impact. Completing the implementation phase doesn't mean that the work is done - in fact, it marks the beginning of long-term observation and stewardship. The FieldDoc **Inspection Logs** feature allows the owners of the activity records to systematically track site visits and document post-implementation conditions. This is especially important for ensuring that Best Management Practices (BMPs) are functioning as intended and that any issues are detected early. ## Step-by-Step Instructions 1. Open the **Inspection Log** view within the **Edit Activity** modal. 2. Select '**+ Add inspection report**\`. 3. Enter in the date of the inspection. 4. Select if the BMP was functioning, or not functioning. 5. Type in additional notes. 6. Click Save. The system will log the user who entered the report as "attested by", this is not an editable field. If you have additional documentation, such as photos or pdfs you can add those in the [Documents](/essentials/documents) and [Images](/essentials/images) tabs within the activity record. You can add as many inspection reports as you would like to each activity record. ## Dig in! Interactive Tutorial {% @arcade/embed flowId="Z1sBzs3pVo98AKNORspp" url="" %} # Pacts (via Activity)
IN THIS ARTICLE Pacts are the feature through which standard users can share their activity records to third-parties. These are typically funding opportunities. Activity records can be linked to multiple Pacts, which should help reduce the threat of duplication for this important work. *** ## Pacts via Edit Activity **Pacts** are a key feature in FieldDoc that allow standard users to share their **activity records** with third parties—typically organizations managing **funding opportunities** or broader programmatic initiatives. Think of a Pact as a bridge between your project work and the entities that review, support, and track it. There are multiple connection points between Pacts and individual activity records. From within the Edit Activity, users can: 1. Check to confirm which Pacts are associated with the Pact. 2. Create a new Pact. 3. Link to an existing Pact. ## Dig In! Interactive Tutorial {% @arcade/embed flowId="UDnjmKWEXQ8xieCfvvsO" url="" %} ## Learn more!
Pacts/pages/vVU9tGq2JSsCkXATch0w
# Project
IN THIS ARTICLE FieldDoc Portfolios are organized with Project Folders and Site Sections. Check, edit, and delete the configuration within the Project view. *** ## Projects Activity records are the base unit in the FieldDoc system. Standard user Portfolios include two levels of organization so that you can more clearly organize these records. Project folders and sub-folders called, Sections, allow users to segment the activity records and roll up analytics for the contained records. This view allows you to add, edit, or remove the organization of each activity record. {% hint style="success" %} **Best management practices for organizing your activity records.** Activity records can only be organized within a single Project and Section. Activity records do not need to be associated with a Project or Section. {% endhint %} # Privacy
IN THIS ARTICLE Privacy settings for individual activity records help obscure sensitive geospatial data through Pacts. *** ## Privacy FieldDoc activity data is, by default, only visible to the organization that owns the record. Records shared with Program Managers via Pacts share all of the attribute data. Turning on the privacy toggle indicates to the Program Managers that they should not expose geographic data related to this activity record on any dashboards. Refer to the FieldDoc [Privacy Policy](https://www.fielddoc.org/privacy) for more details about how the system protects your data. # Geometry
IN THIS ARTICLE FieldDoc invites standard users to attach simple geospatial data to each activity record to delineate the area of installation or implementation. This article covers the feature and how to enter data into FieldDoc. *** ## Geometry Each activity record can have a single geospatial data point associated with it, which is used to delineate the footprint of the activity. In this article, we’ll walk through the **Geometry** feature—its purpose, functionality, and how to input geospatial data into activity records. Geospatial data holds immense value for nature-based work. During the prioritization and planning phases, location data helps align potential installation sites with strategic priorities and anticipated impacts. In the implementation phase, it enables a landscape-level view of where work is being carried out. And once projects are installed, accurate location data supports confident monitoring and verification by ensuring activities can be reliably tracked over time. ### The purpose of geometries In FieldDoc, we keep it simple—the geospatial data attached to an activity record should represent the area impacted by the implementation of the nature-based work. This guidance is intentionally generalized, as what you choose to delineate may vary depending on your organization’s intended use of FieldDoc. To support broader and more complex workflows, FieldDoc offers [integrations ](/essentials/integrations-beta)that allow you to share geospatial data with third-party applications like ArcGIS Online and Airtable. This ensures your data can feed directly into prioritization models and tracking tools—without duplication or extra effort. ### Rules for geospatial data * Each activity record can only have one geometry associated with it. In other words, you can have a single point, a line, or a polygon for each record. If you have multiple geometries, then those should be represented by individual activity records. * We recommend focusing on an implementation area for a single location. Large geometries, such as the polygon of an entire state or watershed, may disrupt the functioning on ### Geometry functionality FieldDoc's **Geometry** feature allows users to associate a single geospatial data point—such as a point, line, or polygon—with each activity record. This geometry is intended to represent the physical footprint of the nature-based work being implemented. Users can create or upload geometry directly within FieldDoc, or integrate with external tools like ArcGIS Online to sync data. By capturing geospatial information at the activity level, FieldDoc enables spatial analysis, improved tracking, and seamless integration into broader planning and reporting workflows. The geometry may also be used to determine available environmental models and the inputs used to generate environmental benefits. ## How to input geospatial data into activity records Geometry data is typically added as part of the [Activity](/essentials/activities) record configuration. FieldDoc offers multiple ways to associate a geometry with activity records. {% hint style="warning" %} **To use geospatial data when creating an activity:** If you have a shapefile or other geospatial file, you **must start by using the Import File** button to create a new record. This is the only way to associate your file with a new activity. **Important:** You **cannot** import a shapefile after the activity record has already been created. There is currently no option to upload or link geospatial data from within an existing Activity record. {% endhint %} {% tabs %} {% tab title="Draw in App" %} ## Draw with Map Editor You can draw your geometry directly in the FieldDoc platform. This is the preferred method if you do not have access to GIS software or if you have already created your activity records and you need to add a geometry. ### Step-by-step instructions. 1. Open the Geometry tab. 2. Navigate to your location on the map. 3. Change the base layer to satellite for more precision. 4. Select your draw tool (point, line, or polygon) 5. Delineate your activity footpring. 6. Click on the map but away from the geometry to save your data. This will turn the geometry purple. 7. You're done! ### Dig in! Interactive tutorials #### Draw a polygon {% @arcade/embed flowId="NilvISfP4G3XPOuD2sKZ" url="" %} #### Draw a point {% @arcade/embed flowId="22chsxf6vAiqi9oiZoaU" url="" %} #### Draw a line {% @arcade/embed flowId="MKC9pgLNn6SfAy9dlrZT" url="" %} {% endtab %} {% tab title="Import File" %} ## Import File Using the FieldDoc Import File you can create activity records based on existing geospatial data. The process works for single activity creation and batch record creation. In the import process, you will select your source file, map the source fields to the FieldDoc fields, and click "import". FieldDoc will create an activity record for reach feature in the file. You can learn more about [Import ](/essentials/import)guidelines. ### Step by Step Instructions 1. Prepare your source file. 2. Click the **Import File** Button. 3. Map your source file fields to the FieldDoc fields. 4. Click Import. 5. An activity record will be created for each feature. The geometry will be added to each record. 6. You will need to enter into each activity record in order to complete the configuration. ### Dig in! Interactive Tutorial #### Import a .CSV files A .CSV file typically contains latitudes and longitudes in decimal degrees. These will be loaded as points within each activity record. If you want to batch import a .csv file without coordinates then you will need to use the FieldDoc Map Editor tools in the Edit Activity > Geometry draw your geometries. Below is an example .CSV file for the tutorial. {% file src="/files/1QI0BHsl36nqoNHuV8WB" %} {% @arcade/embed flowId="8r51lTaMCPZSaje1izSR" url="" %} #### Import a .GeoJSON file GeoJSON is an open standard format based on JavaScript Object Notation (JSON) for encoding geographic data, representing simple features like points, lines, and polygons, along with their non-spatial attribute. If you don't have a .GeoJSON file on hand, you can create one and add attribute data from free online platforms like geojson.io and placemark.io. Here is an example .GeoJSON file for the tutorial. {% file src="/files/bcfeeSsnPE8I3ryYW14Y" %} {% @arcade/embed flowId="jBUuWqAIODLQ10LIXgkZ" url="" %} {% endtab %} {% endtabs %} # Activity Metrics
IN THIS ARTICLE Tracking organization and programmatic metrics allow all stakeholders to measure the impact of this nature-based work toward bigger goals. *** ## Activity Metrics FieldDoc tracks metrics at the **activity level** and aggregates them across **Sections**, **Projects**, and **Pacts** using standardized metric lists. In this article, we’ll explore the two types of manually tracked metrics in FieldDoc: **organizational metrics** and **programmatic metrics**. Each metric includes two fields: `planned_value` and `implemented_value`. By the end of the performance period, both fields should be populated to reflect expected and actual outcomes. Although **organizational** and **programmatic** metrics can be linked to the **same activity**, the process for adding and managing each type differs. Understanding these differences is key to accurate tracking and reporting. Let's dig in! ## Organization Metrics In FieldDoc 2.0, organizations can curate their own list of metrics. Once added to your workspace's portfolio, these metrics can be assigned to any activity record. For guidance on curating your list, see the [*Metrics – Organization*](/essentials/metrics/metrics-organization) article. Organization metrics can be assigned to any activity records in your portfolio. These metrics can be assigned via the **Edit Activity** modal or the **Table view within** Project **Folder,** Site **Section, or** Activity **Record** views. Organization metrics are exclusively visible to users within the organization; therefore, they cannot be added via Pact views, because the Pact view only contains metric information provided by the Pact Opportunity Program Manager. ### Add organization metrics to an activity record {% tabs %} {% tab title="Edit Activity" %} ### Add organization metrics via Edit Activity Modal 1. Open your **Edit Activity** Modal 2. Navigate to the **Metrics** tab. 3. Click 'Add Metric' Button. 4. From available list, check the box to select metric(s) and add the `planned_value`. The `planned_value` indicates the intended target will be achieved by the end of the period of performance for this activity. 5. Click Save. {% hint style="info" %} Metrics must have a planned value. If you leave the planned value field blank, the metric will not be added to your activity record. {% endhint %} {% endtab %} {% tab title="Table View" %} ### Add organization metrics via table views Adding activity metrics via Metric table views can significantly speed up your data entry process. Metric table views are available for adding organization metrics within Project Folders, Sections, and Activity Records. The Metric table view is also available via Pacts, however, organization metrics are not available for selection within Pacts. ### Step-by-step instructions to add organization metrics via table views 1. Make sure your organization's Portfolio of Metrics is up-to-date. 2. Open the table view. 3. Add the Activity name to the first row. The actvity key will be automatically populated. 4. Use the drop down field to select a metric. The metric key will be automatically populated. 5. Enter in the `planned_value`. 6. Additional metrics should be reported in additional rows. {% hint style="success" %} **Using keyboard shortcuts in table views** FieldDoc table views operate similarly to other spreadsheets. To speed up populating your metrics table, you can use your keyboard shortcuts to copy and paste cells, such as the `activity_name` and `activity_key` as well as the `metric_name`and `metric_key`. If you copy records, make sure to copy the key as well! {% endhint %} {% endtab %} {% endtabs %} ### Track implementation of organization metrics By the end of your activity's period of performance, you will want to update your organization metrics to track progress towards your goals. You can track implementation at whatever cadence you decide. {% tabs %} {% tab title="Edit Activity" %} Add implementation values via Edit Activity Modal 1. Open your **Edit Activity** Modal 2. Navigate to the **Metrics** tab. 3. All organization metrics assigned to the activity record are available under the **Organization Metrics** section. 4. Click the three elipses next to the metric that you want to update to open the edit option. 5. Enter in your implemented value. 6. Click save. 7. Repeat for other values. {% endtab %} {% tab title="Table View" %} ### Add implementation values via table views As mentioned above, all metrics have two inputs: `planned_value`and `implemented_value`. Adding implemented values via table views can significantly speed up your data entry process. The Implementation table view is available within Project Folders, Sections, and Activity Records. The implementation table view is also available via Pacts , however, organization metrics are not available for selection within Pacts. ### Step-by-step instructions for adding implementation values via the Implementation table view 1. Open the **Implemented** tab. 2. Copy from the Metrics tab or manually enter the `activity_name`, `activity_key`, `metric_name`, and `metric_key`rows. The planned value will appear. 3. In the `implemented_value`field, input your value. 4. Click save. {% hint style="info" %} The organization and programmatic metrics will both appear once they have been added to your activity record in the table views. {% endhint %} {% endtab %} {% endtabs %} ## Programmatic Metrics **Programmatic metrics** are defined by individual **Funding Programs** and are made available to standard users who have created a **Pact**. Once a Pact is in place, the associated activity records can access and assign that program's metrics to their records. Keep in mind: a **single activity** can be linked to **multiple Pacts**, meaning it may be responsible for managing **multiple sets of programmatic metrics**—each sourced from a different Pact or Funding Program. ### Add programmatic metrics to an activity record {% tabs %} {% tab title="Edit Activity" %} ### Add organization metrics via Edit Activity Modal All metrics have two inputs: `planned_value`and `implemented_value`. Even if you are adding metrics at the end of a period of performance to report to a funder, you must add both a `planned_value` and `implemented_value`. Adding implemented values via table views can significantly speed up your data entry process. The Implementation table view is available within Project Folders, Sections, and Activity Records. The implementation table view is also available via Pacts , however, organization metrics are not available for selection within Pacts. 1. Open your **Edit Activity** Modal 2. Navigate to the **Metrics** tab. 3. Navigate to the **Programmatic Metrics** section. 4. Select the appropriate Pact name. A button will appear that says Add Metrics. 5. Click 'Add Metric' Button. All of the metrics associated with the Pact will appear 6. From available list, check the box to select metric(s) and add the `planned_value`. The `planned_value` indicates the intended target will be achieved by the end of the period of performance for this activity. 7. Click Save. {% hint style="info" %} Metrics must have a planned value. If you leave the planned value field blank, the metric will not be added to your activity record. {% endhint %} ### Dig in! Interactive Tutorial {% @arcade/embed flowId="6MxfrpECKfhZpOA9puGY" url="" %} {% endtab %} {% tab title="Metrics Table View" %} ### {% endtab %} {% endtabs %} # Models IN THIS ARTICLE FieldDoc *** ## Models Models in FieldDoc can either be associated with individual activities. Most models require a combination of inputs collected during the activity set-up process ([activity type](/essentials/activities/general-settings/activity-type) and [location](/essentials/activities/geometry) [via geometry](/essentials/activities/geometry)) and unit inputs for the extent. Some models require additional inputs in order to generate outputs. :seedling: Learn more about the models hosted by FieldDoc: [Models](/resources/models) ### Generate outcomes using models The models page changes depending on the [activity type ](/essentials/activities/general-settings/activity-type)that you selected. Let's tour a common view of this page. {% @arcade/embed flowId="rXqb5TMLBpNuOZ1Ob8I4" url="" %} ### Step-by-step tour The model view changes depending on the [activity type](/essentials/activities/general-settings/activity-type) selected and the [model](/resources/models) selected. This tour displays a basic Adapted CAST activity type, `Bioretention/rain gardens - A/B soils, no underdrain`. 1. Select the model that you want to use from the drop down. 2. The **Best Management practice code** is based on the selected `Activity_type` and is uneditable from the model view. 3. The **Land river segment(s)** is based on the delineated geometry and is uneditable from the model view. 4. **Unit type** is populated from the efficienty tables associated with the Adapted CAST model. This is not an editable field. All CAST BMPs have a single selectable unit type. 5. Enter the **Unit value**. 6. Click **Save inputs.** {% hint style="warning" %} ### Model Tips * If you last ran the model prior to 2024, we recommend using the **clear** button to refresh the page and re-calculate the outputs. * The Adapted CAST model does not include efficiencies for every combination of land-river segment and activity type. If the efficiency tables used to calculate load reductions do not contain values for your selected land-river segment, the model view will display a message indicating this. In such cases, you will not be able to generate load reduction estimates based on your inputs. {% endhint %} ## Common questions
How do I clear model calculations? If, for whatever reason, you want to remove the calculated inputs from this activity record, click the **Clear** icon in the upper right hand corner. This will remove the input and associated calculated outputs.
I disagree with the model outputs. Can I use custom values? Yes. Models are representations of real-world scenarios. The outputs generated from these models may not align with your expected outcomes for this activity. As such, you may choose to associate alternative environmental benefit estimates with your activity record. You will do this by using the **Metrics** tabs. #### Organization metric tracking If you are tracking these outcomes for your Organization, please add the associated metrics to your curated Metrics list within your portfolio. Then, you can associate those metrics with this activity record and assign the planned value that better aligns with your intended outcomes. #### Programmatic metric tracking Once you have associated this record with a Pact, you can assign programmatic metrics to the record. If your program allows it, you can select the associated metrics and enter the `planned_value` that you think more accurately represents the expected outcome for your record. Your funder may ask that you upload documentation of how your arrived at your estimated outcomes to your [Documents](/essentials/documents) tab.
Why didn't my outputs change when I completed my activity? The models used to calculate outputs in FieldDoc assume that the activity has already been installed. Think of it this way: *If I install this activity as planned, what would the estimated load reduction be?* The outputs reflect a post-installation scenario based on the inputs you provide. They will **not** update automatically after the work is completed. However, if you change the model inputs—such as the extent, location, or activity type—the calculated outputs will adjust accordingly.
# Atlas
IN THIS ARTICLE Atlases visually represent all of the activity records and associated data from the provided context. View the modeled outcomes, progress toward metric goals, and the activity locations. *** ## Atlases The **Atlas** provides a spatial overview of all activity records within your project, offering a map-based view that brings together geospatial data, metrics, and project structure. It’s a powerful way to explore where work is happening and how different components of your project relate to each other geographically. In the Atlas, users can see the locations of activities alongside their associated metrics—including organization metrics, programmatic metrics, and modeled outputs. This view is especially useful for identifying gaps, visualizing patterns across a landscape, and communicating progress to partners or stakeholders. Whether you're planning next steps or reporting on completed work, the Atlas helps connect your data to place. # Collaborators
IN THIS ARTICLE Collaborators are users outside of your organization that have access to a portion of your organization portfolio. You can invite, view, and manage collaborator permissions from any collaborator view. *** ## Collaborators The **Collaborators** feature allows you to easily manage who has access to your project and what they can do within it. You can invite team members, partners, or funders to collaborate directly in FieldDoc, enabling shared responsibility for creating, editing, and managing activity records and project data. Collaborators have the ability to add new records, update existing information, and contribute to the overall progress of the project. This feature is designed to support transparent, team-based workflows—whether you're working within a single organization or coordinating across multiple partners. Managing access through the Collaborators tab ensures that the right people have the right level of access at the right time. ## Collaborate: Shared with Me When another user invites you to collaborate on part of their FieldDoc [portfolio](/essentials/portfolio), you gain limited access to specific records—without taking ownership of them. Collaborators can be added at the [Project](/essentials/activities/general-settings/project), [Activity](/essentials/activities), or [Pact](/essentials/pacts) levels. ### **What does "Share with Me" Mean?** As a **collaborator**, you can view and contribute to the records you’ve been invited to, but those records remain part of the original owner’s portfolio—not yours. You’ll find these records in the **Shared with Me** tab of your FieldDoc workspace. ### **What can collaborators Access?** * **Pacts** and **Activities** that have been shared with you. * Depending on the level of access granted, you may be able to **view**, **edit**, or **comment** on these records. {% hint style="info" %} You will not see these records in your own **Portfolio** tab because they are not affiliated with your organization’s portfolio. {% endhint %} ### **What can collaborators not do?** * You cannot move shared records into your Portfolio. * You cannot invite new collaborators to shared records unless you are granted permission by the original owner. * You do not have administrative control over shared records. **Why This Matters:** This structure helps ensure that data ownership and reporting responsibility remain with the original record owner, while still allowing for cross-organizational collaboration and support. If you need to work with someone on their data, always check your **Shared with Me** tab. If a record doesn’t appear there, it may not have been shared with you yet—or you may not have the right level of access. ## Sharing workspaces ### Collaborating at the Workspace level in FieldDoc If you need full access to another organization’s portfolio in FieldDoc, **the best option is to be invited directly to their** [**workspace**](/manage-your-organization/workspaces). This kind of access goes beyond individual record sharing and allows you to work across all projects, activities, and Pacts within that organization. ### **What happens when you're invited to a workspace?** #### Once invited, you’ll be able to: * Access the entire [portfolio](/essentials/portfolio) of records in that organization’s [workspace](/manage-your-organization/workspaces). * View and manage [activities](/essentials/activities), [projects](/essentials/activities/general-settings/project), [pacts](/essentials/pacts), and shared [metrics](/essentials/metrics) * Switch between your own organization’s workspace and theirs using the workspace switcher in the top-right corner of your FieldDoc account. You do **not** need a new login—your existing FieldDoc account can be used to access multiple workspaces. **Why this matters:**\ Workspace-level collaboration is especially useful for: * Technical service providers who support multiple grantees * Program managers working across different partner organizations * Organizations that co-manage a shared restoration portfolio **Key difference:**\ Unlike record-level collaboration (where you only see specific items under the “Shared with Me” tab), workspace access gives you a full view of everything in that organization’s account. To gain access, an **administrator from that organization** must send you an invitation. {% hint style="danger" %} The FieldDoc team does not recommend adding collaborators to projects at this time. If you need to add a collaborator to support your portfolio development, we recommend using workspaces. If you only need support to complete a grant application, add the collaborator through [**Pacts**](/essentials/pacts). {% endhint %} ### Collaborating at the Pact level in FieldDoc If you are supporting a grant applicant with their FieldDoc submission and do not want to use workspaces, users can invite collaborators to their Pact. **Once invited collaborators will be able to:** * Access the Pact via *shared with me*. * View, edit, and delete activity records within the Pact. All records will be discoverable via *shared with me* and within the Pact. * Add programmatic metrics to the activity records within the Pact. # Documents
IN THIS ARTICLE Attach documents to your FieldDoc records to different folders in your portfolio. *** ## Documents The **Documents** feature in FieldDoc allows users to upload and store important files within a **Project**, **Pact**, or **Activity**. This centralizes documentation so that relevant materials—such as reports, designs, permits, or data sheets—are easily accessible to all collaborators working on a project. Documents uploaded to a record are only visible to users with access to that specific record, helping ensure that sensitive or project-specific information remains secure. This feature is especially helpful for teams that need to share reference materials or maintain a clear record of supporting documentation over the lifecycle of a project. To add a document, navigate to the **Documents** tab of your chosen record and click the upload button. Supported file types include common formats such as PDF, DOCX, XLSX, and more. # Export
IN THIS ARTICLE Extract you data from FieldDoc using the export feature. *** ## Export The **Export** feature in FieldDoc allows users to download project data for offline use, analysis, or reporting. You can export information from Projects into geospatial packages. You can also export Activities, Metrics, and other tabs into spreadsheet formats (e.g., CSV or Excel), making it easy to work with your data outside of FieldDoc or share it with partners and funders. Exports include structured data such as activity details, metric values, and associated metadata, helping you maintain clear records and perform custom analysis or visualization in external tools. Exporting is especially helpful when preparing reports, submitting documentation, or performing quality control on project data. To export data, look for the **Export** button in the relevant tab (e.g., Activities, Metrics). Once selected, your data will be packaged and downloaded in a convenient, ready-to-use format. ### Step-by Step Instructions 1. Open the context where you want to export activity records. For instance, if you export at the **Project** level the export will include all activities within that Project. 2. Click on the vertical ellipses in the upper right hand corner. 3. Select Export file. 4. Name your file. Click **Create Export**. 5. Open the **Export** tab under tools. 6. Find the export that you just created. 7. The system takes a few moments to generate your export. You may need to refresh the Exports page. 8. Click the Zip file icon, this with download the export to your downloads folder. 9. Open your file manager to extract the file. Data is available in .csv, .geojson, and geopackage format. Reference the README.txt for more information. ### Dig In! Interactive Tutorial {% @arcade/embed flowId="pUjDTbFbtIsKFjvx4qNk" url="" %} ## Export FAQs
How do I export a shapefile? You can export Projects from FieldDoc in .CSV, GeoJSON, or Geopackage formats. If a shapefile is specifically required, your GIS staff can easily convert the Geopackage export to a shapefile using most standard GIS tools. FieldDoc does not support direct shapefile export, but the Geopackage format preserves full geometry and attribute data for seamless conversion
Why does my GeoJSON file display points, not polygons? The exporter outputs centroids for activity collections containing more than 100 records to preserve functionality within the file type.
# Images
IN THIS ARTICLE Import and attach images to different sections of your FieldDoc work: Projects, Sections, Activities, and Pacts. *** ## Images The **Images** feature in FieldDoc allows users to upload and store important visual files within a **Project**, **Pact**, or **Activity**. This centralizes documentation so that relevant materials—such as photos demonstrating progress and functioning—are easily accessible to all collaborators working on a project. Images uploaded to a record are only visible to users with access to that specific record, helping ensure that sensitive or project-specific information remains secure. This feature is especially helpful for teams that need to share visual materials or maintain a clear record of supporting documentation over the lifecycle of a project. To add an image, navigate to the **Image** tab of your chosen record and click the upload button. FieldDoc currently supports PNG, JPEG, GIF, and TIFF formats. # Import
IN THIS ARTICLE Do you have data about your implementation activities prepared in an external file or system? You can use that data to create your FieldDoc records, without to enter everything by hand! By our estimates, import can save you hours of manual data entry for new records. In this article, learn how to build your portfolio using external .csv, .GeoJSON, or Shapefiles. Get existing geospatial data into FieldDoc in a breeze. This article is intended to assist users in batch import of data. If you are looking to import a single geospatial data point, view the [Geometry](/essentials/activities/geometry) article. *** ## Import The Import feature helps you quickly create new FieldDoc records from data you already have—such as spreadsheets or GIS files—without entering information record by record. Import is especially helpful when you are: * Adding a large number of activities at once * Migrating data from another system * Preparing a portfolio or pact to share with a funder * Working with partners who already manage data outside of FieldDoc Rather than rebuilding work you’ve already done, import lets you bring your data into FieldDoc efficiently and consistently. {% hint style="warning" %} **Important limitations to know upfront** * Import is used to **create new records only** * Existing FieldDoc records **cannot be updated via import** If you need to batch-update existing records, email **** and we’ll help you plan the best approach. {% endhint %} ### Quick Start: How Import Works At a high level, importing into FieldDoc follows a simple pattern: 1. **You choose where to start the import** 2. **You upload a source file** 3. **You map your file’s fields to FieldDoc fields** 4. **FieldDoc creates new activity records and places them accordingly** Two things determine *where your records end up*: * **Where you start the import from** (Home, Project, or Pact) * **What information you include in your source file** (such as Project or Section names) Once imported, all activity records become part of your FieldDoc portfolio. ### Important Limitations to Know Up Front Before getting started, it’s important to understand what Import can—and cannot—do. * Import is used to **create new records only** * Existing FieldDoc records **cannot be updated via import** If you have an existing portfolio and need to make large-scale updates using an external source file, please contact us at ****. We’re happy to help you plan the best approach. ### Before You Import: A Quick Checklist Taking a few minutes to prepare will save time later. Before importing, confirm that: * You are logged into the **correct FieldDoc workspace** * You know whether your records should belong to a **Project or Pact** * Your source file includes the required fields for your activity type * Your file format and size meet FieldDoc requirements * You are intending to create **new** records (not updating existing ones) ## Text and numerical fields to import
FieldDoc NameFieldDoc Field NameImportableDescription and tips
Activity Namepractice:name✅Choose a unique name or code as a reference point. This is the label for each activity record.
Activity Typepractice_type:key❌You must choose and assign activity type from the available list within FieldDoc. We recommend appending the activity type to the description during import for a quick in-app reference.
Activity Descriptionpractice:description✅A text field where you can provide narrative about the activity record. A great place to add the activity type for quick reference.
Activity Extentpractice:extent✅Number field. An extent overrides the estimated extent generated from associated polygon or line geometries. This is an especially helpful field if you are relying on point geometries. Tip: the extent will need to be manually entered into any models to run calculations.
Activity Extent unitpractice:extent_unit🟡You can import if you follow the standard FieldDoc vocabulary for extent
Completed on datepractice:completed_on✅The completion date should represent the estimated date that the activity was installed to specification.
Project Nameproject:name🟡A new project folder will be created for all unique names in the file. If all records have the same project name listed, only one folder will be created.
Section Namesection:name🟡Sections are a sub-folder within projects. One folder will be created for all records with the same section name.
### Things to consider #1: Where you start the import matters You can start an import from different locations in FieldDoc. Each option affects where your new activity records are placed. #### Importing from Within a Project or Pact If you begin the import from inside a specific Project or Pact folder: * All activities in your file will automatically be added in that folder so that you do not need to link the records later. This approach works well when you are preparing data for a funder or building out a specific portfolio. #### Regardless of Where You Start No matter where you begin the import: * All activity records become part of your FieldDoc portfolio * You can organize and link them later if needed #### Importing from the Home Page If you begin the import from the Home Page and select Activities as the destination: * Activity records will be created without a Project or Pact association * Unless Project or Pact information is included in your source file This approach gives you more flexibility if you plan to organize records after import. ### Things to consider #2: Use Import to build your folder structure Import can do more than create activity records—it can also help you create **Projects and Sections** automatically. This is optional and considered more advanced FieldDoc usage. If you are new to FieldDoc, you can skip this and organize records later. #### Including Project and Section in Your Source File If your import file includes columns for: * **Project** * **Section** FieldDoc will automatically: * Create new Projects and Sections (if they don’t already exist) * Place your activity records inside them {% hint style="info" %} The "rule" that FieldDoc only creates new records applies to project and sections as well. That means that if you have an existing project in FieldDoc and you import a file with a project name field, regardless of if the names match, FieldDoc will create a new project. This means that if you are importing new activity records to an existing project then you need to import them directly to that project or organize them after import. {% endhint %} ## Supported File Types and Limits FieldDoc follows standard data import practices. If your file meets the requirements below, it will import successfully. #### Supported File Types * `.csv` * `.GeoJSON` * Shapefiles (zipped) #### File Size and Feature Limits * **Maximum upload size:** 10 MB * **Maximum features per upload:** 1,000 For shapefile archives, the 10 MB limit applies to the total size of all uncompressed files. If your dataset exceeds these limits, additional features will be ignored. For larger workloads, please contact **** so we can help you plan your workflow. ### File Type: .CSV #### *When to use a .csv file.* If you have all of your activity records and associated attribute data prepared in a spreadsheet, you can import that spreadsheet into FieldDoc in a .csv format. Every row in the spreadsheet will create a new activity record. Files in comma-separated value (CSV) format may contain spatial data, but it isn't required. If included, geometry values should be provided as coordinates or [well-known text](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry). When your file contains coordinates, columns for latitude and longitude **must** be present. Please refer to the following column header mappings before uploading CSV files with spatial data. If you don't include coordinates, you will be able to draw your geometries in FieldDoc or make use of the import option within each activity record's geometry tab to delineate the implementation location. | **Value** | **Supported column headers** | | --------- | ------------------------------------------- | | geometry | wkt | | latitude |

lat
latitude
y

| | longitude |

lng
lon
long
longitude
x

| #### Sample template: .csv {% file src="/files/4K7Z3rHdzd0B2Rj9k3vO" %} ### **File Type: Shapefile** When importing shapefiles you can quickly configure d You can import a multi-feature shapefile to create many records at once, or import a single shapefile into the geometry tab of a single activity record. The following instructions are provided as general guidance for all shapefile imports; however, the demo template includes multiple features. **Files to include in your archive.** In addition to the mandatory .shp, .shx, and .dbf files, shapefile archives must include a .prj file that describes the coordinate system and projection. The files should be projected in WG84. All files must be compressed into a .zip file before uploading. To ensure that FieldDoc reads the archive correctly, the archive itself and the files it contains should share the same name.

All of the file types to include in your compressed file.

#### Tips and tricks for preparing your shape file for import: * File names must not contain spaces. * FieldDoc will interpret each feature as a unique record. If you are attempting to import multiple polygons into a single record, they must be configured as multi-polygons before import. * Nested ZIP folders are not supported (e.g. example.zip > example > example.shp). All required files must be stored in the top level of the ZIP folder (e.g. example.zip > example.shp, example.shx, …). #### Sample Shapefile {% file src="/files/rWlDK3SjY6y4KsQ3klpD" %} ### **File Type: GeoJSON** GeoJSON files must use the .json or .geojson file extensions and follow the format described in [this specification](https://tools.ietf.org/html/rfc7946). We recommend testing GeoJSON data with [geojson.io](https://geojson.io/) before uploading it to FieldDoc. See [here](https://www.mapbox.com/help/define-geojson/) for more help with the GeoJSON format. ## Step 2. Import your source file 1. Prepare your source file. Review our [source file requirements](#prepare-your-source-file) to make sure that your file will be successfully imported. 2. You can find the **Import File** button in several places across FieldDoc. Before you begin, we recommend reviewing [**How FieldDoc Organizes Your Data**](#how-fielddoc-organizes-your-imported-data) to choose the best place to start your import—whether that’s from the **Home Page**, a **Project**, or a **Pact**. Your starting point helps determine how your data will be grouped and displayed. > **Tip:** Starting your import from the right place saves time and helps keep your activities organized automatically. 3. Open the Import File button. Drop in your source file and click **upload**. 4. Map your source file fields to the FieldDoc fields. 5. Click save. 6. FieldDoc may take a few moments to generate all of the new records. Once it has completed the task the button will turn green and indicate how many records were imported. 7. Some fields cannot be imported. Once you have imported your source file, you must complete the configuration for each activity record. For example, you may need to assign `activity types`, run [models](/essentials/activities/models), and attach [programmatic metrics](/essentials/metrics/metrics-programmatic) in the FieldDoc system. ### Dig in! Interactive Training Tutorial {% @arcade/embed flowId="JOLCfjh94voD5JpBwRX0" url="" %} ### Complete data entry within FieldDoc for the imported activity records FieldDoc's importer cannot import the following fields: * `Activity Typef` * `Model Input` These are critical fields in the FieldDoc system, so users will need to manually input this information. Both Activity Type and Extent fields can be quickly inputted using the [Tables (Grid View)](/essentials/tables-grid-view). Alternatively, you can open the **Edit Activity** modal and enter this information in manually. {% tabs %} {% tab title="Single Activity" %} ### Single Activity: Step-by-Step Instructions For more detailed instructions, visit the [Activities](/essentials/activities) pages. #### Assign Activity Type 1. Open the **Edit Activity** modal. 2. Navigate to **Activity type** view. 3. Select **Choose Activity** type to open the universal list. 4. Search for the appropriate `activity type`. Select it. Save. Close modal. 5. **Save** on the overview page. #### Activate Model(s) 1. Open the **Edit Activity** modal. 2. Navigate to the **Models** view. 3. Follow the instructions to input all required fields and run the model. 4. Click **save**. #### Metrics 1. Open the **Edit Activity** modal. 2. Navigate to the **Metrics** tab. 3. Select the associated Pact to access the relevant Programmatic Metrics list. > **Tips:** > > * Link your activity record to a Pact in order to access the Programmatic metrics. > * Activity records can be assigned to multiple Pacts. ### Dig in! Interactive Tutorial {% @arcade/embed flowId="n1iv1gciMCZHUPUmOgKB" url="" %} {% endtab %} {% tab title="Table View" %} ### Table View: Step-by-Step Instructions Table View is a simple way to see and update many of your activity records at once—kind of like working in a spreadsheet. Instead of opening each activity one by one, you can scroll through a table and edit key details directly from the page. This is especially helpful when you need to review or enter data for multiple records at the same time. Below, we’ll walk you through what you can do in Table View and how to use it effectively. #### Activity types 1. Navigate to the activity types field. 2. Click the drop down arrow. A list of all activity types in FieldDoc pops up. 3. Search, scroll, and select the `activity_type` that matches your work. 4. Close the modal. 5. You can repeat these steps within individual rows/records, or, you can copy (CTRL+C) and paste (CTRL+V) the same activity type and activity type key into other rows/records. #### Extent 1. Navigate to the `extent` field. 2. Enter in a numerical value. 3. Navigate to the `extent_unit` field. 4. Select the unit from the available list. #### Completed date 1. Navigate to the `completed_on` field. 2. Open the calendar tool. 3. Select a date in the past. {% hint style="info" %} At this time, models cannot be activated from the table view. To [turn on a model](/essentials/activities/models) to calculate environmental benefits, you must open the [Edit Activity](/essentials/activities/models) modal within each activity record. {% endhint %} {% endtab %} {% endtabs %} ## Common Import Mistakes (*and How to Avoid Them*) Import is designed to be flexible, but a few common missteps can create extra work. Reviewing these ahead of time can save you from needing to re-import data or reorganize records later.
Importing into the wrong workspace **What happens**\ Activities are created successfully—but they’re in the wrong organization’s workspace and cannot be moved. **Why it matters**\ Records cannot be shared or transferred between workspaces after they’re created. **How to avoid it** * Double-check the workspace name before importing * Confirm that you are working in the **lead applicant’s workspace** when importing for a pact **Tip:**\ If you’re helping a partner or client, pause here and confirm you’ve been invited to the correct workspace before continuing.
Expecting import to update existing records **What happens**\ Duplicate activities are created instead of updating existing records. **Why it matters**\ Import only creates new records; it cannot modify records that already exist. **How to avoid it** * Use import only for **new** activities * If you need to batch-update existing records, contact **** for guidance.
Starting the Import in the wrong location **What happens**\ Activities are created but aren’t linked to the Project or Pact you expected. **Why it matters**\ You may need to manually organize or relink records afterward. **How to avoid it** * Start the import from inside a **Project or Pact** if records should live there * Start from the **Home Page** only if you want unassigned records **Quick check:**\ Ask yourself—*“Where should these records land immediately after import?”*
Missing Project or Section fields in the source file **What happens**\ Activities import correctly, but folders and sections aren’t created because they were not included in the source file fields. **Why it matters**\ You can manually organize records after import from the table views. **How to avoid it** * Include **Project** and **Section** columns in your source file if you want FieldDoc to create them automatically * Ensure values are spelled consistently across rows **Note:**\ This is optional—manual organization is always possible later.
The import "hangs" when you click save. **What happens** When you click save to import all of your data, the save button hangs on saving and the records are not created. **Why it matters** This means that something is interuppting the import process, either in the source file or in FieldDoc. **How to avoid it** * Make sure to follow all of the configuration guidelines based on the file type that you are utlizing. * If everything looks good in your source file, try refreshing your browser and clearing your browser cache, then try again. * If you still cannot import the file, send the file to for assistance.
Skipping field mapping step. **What happens** You import a file and skip the field mapping step, you just click save. FieldDoc will create activity records for all of the rows of data and map the geometries data to individual activity records. All all FieldDoc fields will remain empty. **Why it matters** FieldDoc import will "work" even if you don't map any fields from the source data to the FieldDoc schema; it will simply follow the instructions that you give it. Importing the geospatial data is automated, so the points, lines, or polygons will be imported regardless. If you need to remove these records because you do have field data to map, please delete the records first. Reach out to if you need assistance deleting a failed import.
# Integrations (beta) {% hint style="info" icon="circle-user" %} **Tiers**: Standard and Aggregator. If you would like to begin using FieldDoc integrations, reach out to to discuss your needs. {% endhint %} *** ## Integrations Integrations connect your FieldDoc portfolio to work with external systems, tools, or data sources. This enhances functionality and data management for environmental restoration and monitoring projects. These integrations allow users to: 1. **Pull in Data**: FieldDoc can integrate with existing data systems to streamline the import of real-time data into the platform from ArcGIS Online or Airtable. 2. **Export Data**: Users can export FieldDoc data for further analysis or reporting in other software, like GIS tools (e.g., ArcGIS) or spreadsheet software (e.g., Airtable), for deeper insights or visualization. 3. **API Connections**: FieldDoc can be connected to APIs (Application Programming Interfaces) of other systems, allowing for automatic data exchange between platforms, which can improve efficiency and reduce manual entry. 4. **Mapping Tools**: FieldDoc integrates with ArcGIS Online to create and maintain the integrity of a Feature Service that can be used to provide visual representations of restoration activities and their impacts on the environment. Users can overlay additional data sources, such as satellite imagery, land use maps, or prioritization tools to provide context. 5. **Project Management**: FieldDoc integrates with the project management tool, Airtable, to track project timelines, budgets, and deliverables in conjunction with environmental data collection. These integrations enhance FieldDoc's ability to manage, visualize, and analyze environmental project data, making it a more powerful tool for users working on restoration, conservation, and climate resilience efforts. ## Key Benefits of Integrations in FieldDoc Integrating FieldDoc with other systems and tools offers several key benefits that enhance the platform’s overall functionality and usability, particularly for environmental organizations engaged in restoration, monitoring, and reporting efforts. Here are some of the main advantages: 1. **Improved Data Management and Accuracy**\ ***Seamless Data Import and Export***: Integrations with ArcGIS Online and Airtable allow FieldDoc to pull data from external systems, reducing manual data entry errors and ensuring up-to-date information is always available.\ ***Centralized Data Storage***: Users can consolidate multiple data sources into one platform, making it easier to manage, track, and analyze all project-related data from a single dashboard. 2. **Enhanced Analysis and Reporting**\ ***Automated Data Sync:*** Integrations and triggers ensure that data flows between systems without requiring manual intervention. This allows for real-time analysis, which is crucial for monitoring the impacts of environmental interventions.\ ***Comprehensive Reporting:*** Users can create detailed reports by combining data from various tools, ensuring a more holistic understanding of project outcomes and environmental impacts. 3. **Greater Efficiency and Time Savings**\ ***Reduced Manual Work***: Automation of data collection, syncing, and reporting minimizes the need for manual data entry, freeing up staff time to focus on higher-value activities like analysis, strategy, and decision-making.\ ***Streamlined Workflow***: Integrations with project management tools can improve workflow by aligning tasks, timelines, and outcomes with environmental data collection and impact tracking. 4. **Better Decision-Making**\ ***Real-Time Insights***: Integrations with real-time monitoring tools or sensors (e.g., IoT devices measuring water quality) provide instant feedback on environmental conditions, allowing project managers to make timely adjustments to restoration activities.\ ***Comprehensive Visualizations***: GIS integrations offer sophisticated mapping capabilities, enabling users to visualize the spatial impact of their restoration efforts, track changes over time, and communicate these visually to stakeholders. 5. **Enhanced Collaboration and Transparency**\ ***Data Sharing***: With integrations, FieldDoc can easily share information with other platforms or organizations. This is particularly useful in multi-stakeholder initiatives, where transparency and collaborative data sharing are key to success.\ ***Consistency Across Tools***: Integrations ensure that data is consistent across different tools used by various teams, helping maintain a unified approach to data analysis and project reporting. 6. **Scalability**\ ***Adaptable for Larger Projects***: As project complexity grows, integrations allow FieldDoc to scale alongside the increasing data and reporting needs. For instance, integrating with more advanced data analytics or machine learning platforms can provide deeper insights into environmental trends.\ ***Multi-Site Management***: When managing multiple restoration sites, integrations help keep all data synchronized across locations, ensuring accurate cross-project comparisons and summaries. 7. **Increased Impact Measurement**\ ***Tracking Long-Term Outcomes***: FieldDoc integrations help organizations track not just immediate outputs but long-term environmental and ecological impacts, providing richer datasets to analyze the effectiveness of interventions over time.\ ***Aligning with Goals***: Integrating FieldDoc with larger regional or national datasets can help users align their projects with broader conservation or climate resilience goals, making it easier to measure and communicate impact to funders and stakeholders. Overall, the key benefits of integrating FieldDoc are increased efficiency, improved data accuracy, enhanced decision-making, and the ability to scale projects and impact measurement. These benefits collectively lead to more effective environmental restoration and conservation efforts. ##
# Linked Pages IN THIS ARTICLE What are Linked Pages? *** ## Linked Pages Information applications relevant to FieldDoc-managed data are scattered across the digital world. The breadth of work made possible by data associated with FieldDoc should be connected back to FieldDoc itself. It should not take a digital detective to discover or an information science degree to track. For example, work planned in FieldDoc can be aligned with prioritization models to assess the preferred investments. Users can add a stylized URL to a Project, Pact, or Activity that links to a third-party website. A great use for this is to attach an AGOL prioritization tool that is linked to a Feature Service that hosts FD data so that users can see the connection between the two systems. Another option is to connect to services like [Matterport](https://matterport.com/) or [Coolant](https://coolant.earth/), which provides MRV data collection services. ## Key Benefits of Linked Pages This feature is crucial in making FieldDoc a more dynamic hub for managing and connecting environmental data with various external tools and services. By allowing users to add stylized URLs to [Project](https://help.fielddoc.org/docs/project), [Pacts](https://help.fielddoc.org/docs/pacts), or [Activities](https://help.fielddoc.org/docs/activitives), FieldDoc can serve as a centralized platform, bridging the gap between different applications and data sources that complement its functionality. Here’s how this integration strategy benefits users and enhances FieldDoc’s role in your work: **Streamlined Access to External Resources**: By linking prioritization models or MRV (Monitoring, Reporting, and Verification) tools directly to FieldDoc projects or activities, users can seamlessly access additional insights and data without leaving the FieldDoc platform. This reduces the need to search for tools or platforms and allows users to see the broader impact of their data. **Enhanced Decision-Making:** Aligning FieldDoc’s project data with prioritization models, such as AGOL (ArcGIS Online), enables users to evaluate investment opportunities more effectively. Decision-makers can see real-time data within these tools, assess project priorities, and make informed investment choices based on a comprehensive understanding of environmental impacts. **Improved Data Visibility and Connections:** By linking to third-party platforms like Matterport (for 3D space visualization) or Coolant (for MRV data collection), users gain deeper insights into project sites and their environmental conditions. This visibility can help align planned activities with on-the-ground realities, ensuring that restoration or conservation efforts are well-informed and impactful. **Customizable Integration Options**: Allowing stylized URLs gives users flexibility in connecting FieldDoc with the specific tools they need, whether it’s a data visualization tool, a prioritization model, or an MRV platform. This flexibility encourages users to adapt the system to their unique workflows and project requirements. **Enhanced User Experience**: Centralizing access to third-party tools within FieldDoc improves the user experience by reducing the complexity of managing environmental data across multiple platforms. Users won’t need to be digital detectives to track down data or tools—they can easily access relevant resources through linked URLs directly in FieldDoc. ## Create Linked Pages Linked Pages can be created within [Project](https://help.fielddoc.org/docs/project) or [Activities](https://help.fielddoc.org/docs/activitives). ## Components of Linked Pages
| Component | Description | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | Enter a name for this link. If the link points to a full web page, please consider using the title of that page. The name will be displayed everywhere this record appears in FieldDoc. | | Annotation | Describe this link. If the link points to a full web page, please consider using the description of that page. The description will be displayed everywhere this record appears in FieldDoc. | | URL | Point FieldDoc to the URL for your content. For items that provide embed or share links (e.g. YouTube), please use that URL rather than the URL for the full page. | | Thumbnail (optional) |

Upload a small image that represents your content. For best results, the image dimensions should be at least 400x400 pixels.

FieldDoc supports the following formats for thumbnails: .jpg, .jpeg, .png.

The maximum file size is 1 MB.

|
### Supported third-party content sources FieldDoc currently supports page links from the following domains. \\ > #### 🚧My link is not displaying > > Links from sources not listed here will not be displayed. New domains may be added over time as our team gathers feedback and monitors use of the linked page feature. Please contact support if you have questions or need help creating links. | Name | Domain | Category | | -------------- | ---------------------- | ------------------------------ | | Adobe | adobe.com | Documents | | Airtable | airtable.com | Analytics \| Data | | ArcGIS Online | arcgis.com | Analytics \| Map | | Box | box.com | Documents | | Datawrapper | datawrapper.de | Analytics | | Dropbox | dropbox.com | Documents | | Felt | felt.com | Analytics \| Maps | | Flourish | flo.uri.sh | Analytics | | Google | google.com | Analytics \| Documents \| Maps | | Matterport | matterport.com | Media | | Observable | observablehq.com | Analytics | | OneDrive | onedrive.com | Documents | | QuickChart | quickchart.io | Analytics | | Retool | retool.com | Analytics \| Data | | Vimeo | vimeo.com | Media | | Water Reporter | maps.waterreporter.org | Maps | | YouTube | youtube.com | Media | # Map Editor :construction: COMING SOON # Metrics IN THIS ARTICLE With metrics, users can track progress toward implementation goals. This article examines the process for adding and tracking progress toward stated outcomes. *** ## Metrics In FieldDoc, each activity record can have associated metrics. There are two types of metrics. Automated metrics [model ](/essentials/model-outputs)outcomes. Manual metrics can be attached to activity records from curated lists. The most common lists are associated with a [pact](/essentials/pacts). This flexibility expands what you can analyze, measure, and report through the system. Because FieldDoc standardizes data across every component, you can track metrics at any scale—from a single project, to an organization-wide initiative, to participation in a funding program that spans many partners. Let’s take a closer look at the manual metrics. {% hint style="info" %} **Looking to calculate modeled metrics?** To look closer at how modeled metrics are managed, start [here](/essentials/activities/models). {% endhint %} ### \`Planned\_Values\` & \`Implemented\_Values\` Non-modeled metrics each have two input fields: `planned_value` and `implemented_value`. These values track both the goal and the progress toward that goal. Inputs to each field are manually entered by FieldDoc users. #### Edit activity modal view of metrics
#### Overview view of metrics
FieldDescriptionDetails
'planned_value' The proposed outcome, or target goal, that will be achieved at the end of the performance period.This is a number field. This field is typically set when a record is created and remains the same.
'implemented_value`The amount implemented to date.This is a number field. This field is typically updated during reporting periods, with the final implementation report displaying the final implemented value.
## Enter your metric values Metrics can be entered from within an activity record or from table views within *Project folders* or *Pacts.* Both options have benefits, and our team recommends choosing the pathway that you feel most comfortable with using. {% tabs %} {% tab title="Enter within activity records" %} ### Step-by-step instructions 1. Open an activity record's **Edit Activity** modal. 2. Navigate to the **Metrics** tab. 3. Under **Programmatic Metrics**, select the **Pact** within which you want to add **Metrics**. 4. Click **+ Add Metrics**. A list of all metrics associated with the Pact appears. 5. Select all metrics that you want to add to the record. You must enter in a `planned_value` into the provided field in order to the metric to save. 6. All selected metrics will appear in the metrics view with their `planned_value`. ### Dig-In! Hands-on tutorial to add metrics via *Edit Activity* modal {% @arcade/embed flowId="xuY3LhzHoUd5vv7U7rnc" url="" %} {% endtab %} {% tab title="Enter within table views" %} ### Step-by-step instructions to add a metrics via table view These instructions are designed for users working within a **Pact view**. Once you have added all of your activities to your Pact, follow the steps below to enter planned metrics using the **Metrics** tab: 1. **Navigate to the Metrics Tab**\ Open your Pact and click on the **Metrics** tab. This will display the metrics table view. 2. **Add a New Row**\ Click **“+ Add Row”** to begin entering metrics. 3. **Select the Activity**\ In the first column, choose the corresponding **Activity** from the dropdown. Each row should be tied to **one activity**. 4. **Select the Metric**\ In the next column, use the dropdown to select the **specific metric** you want to track for that activity. Each row should include **only one metric**. 5. **Enter the Planned Value**\ Input the **planned value** (numeric) in the appropriate field. This represents the amount you plan to implement for that metric. 6. **Add Additional Metrics**\ If an activity includes multiple metrics, click **“+ Add Row”** again and repeat steps 3–5. Use the same activity, but select a different metric for each additional row. 7. **Add Metrics for Other Activities**\ Repeat the process for each additional activity in your Pact. > 💡 *Tip: Each row in the metrics table should represent a single activity/metric pair. This structure ensures your metrics are clearly linked to specific implementation activities.* ### Dig in! Hands on tutorial for entering metrics and planned values from the *Pact Metric table view* {% @arcade/embed flowId="mEsJpoKJI0asMgM8RT0U" url="" %} {% endtab %} {% endtabs %} ## Enter implementation progress for metric values for reporting {% tabs %} {% tab title="Enter within activity record" %} ### Step-by-step instructions 1. Open an activity record's **Edit Activity** modal. 2. Navigate to the **Metrics** tab. 3. Under **Programmatic Metrics**, select the **Pact** within which you want to add **Metrics**. 4. Click the ellipses next to the metric that you want to update. A pop up with `planned_value` and `implemented_value` fields appears. 5. Enter in the `implemented_value`. Click Save. 6. The saved metrics will appear in the metrics view with their `planned_value`. The progress will be displayed in the grid view and rolled up within all overview dashboards. ### Dig in! Step-by-step tutorial for reporting implementation via *Edit Activity* modal {% @arcade/embed flowId="kDnOXA54D0PAk2ylTOv9" url="" %} {% endtab %} {% tab title="Enter within table views" %} ### Step-by-step instructions to add a metrics via table view These instructions are designed for users working within a **Pact view**. Once you have added all of your activities to your Pact, follow the steps below to enter planned metrics using the **Metrics** tab: 1. **Navigate to the Metrics Tab**\ Click on the **Metrics** tab. This will display the metrics table view. 2. **Find the activity and metric that you want to add or update an implementation value.**\ Each metric will have its own row, meaning that you may see multiple rows for each activity. 3. **Enter in the \`implemented\_value\`** \ Values must be numeric. 4. **Repeat.** ### Dig in! Hands on tutorial for reporting implemented\_value via *pact table views* {% @arcade/embed flowId="uxTLfnwuowdVzFYPa6dh" url="" %} {% endtab %} {% endtabs %} ## Types of non-automated metrics ### Organizational Metrics (*standard plan*) Standard users can create a custom list of metrics that are important to their organization. After making this list, you can set targets for each metric. These targets will show up in the organization view. As you add activity records to your portfolio, you can link them to your organization’s metrics. During the project timeline, you can track your progress toward each goal at the activity level. That progress is then added up and shown at higher levels—like Section, Project, and Organization views. For example, if an activity is part of a Section and a Project, its contribution to a metric will count toward the totals for the Section, the Project, and the Organization. This makes it much easier to track and share progress on big goals, like the number of trees planted or the number of miles of stream restored. There is a lot of information to explore on how to set up and track your metrics. :seedling: Learn More: [Metrics - Organization](/essentials/metrics/metrics-organization) ### Programmatic Metrics (*all plans*) Program Managers can create a custom list of metrics that are important to their funding program and organization. After making the list, any user that has assigned activity records to a Pact in that Funding Program can add the metrics to their activity record and set a target outcome. The targets will show up in the Pact Overview view. As grantees progress in their work to meet their funding requirements, they can track progress toward implementation for the programmatic metrics within their activity record. That progress is added up and shown on the Pact overview page. All of the Pacts within a Funding Opportunity will roll up and provide an overview of progress toward larger goals, such as Blueprints or Business Plans, for an entire funding program. The process allows Funding Program Managers to: * Align their priorities with individual awards * Track the geospatial and quantitative impact from standard views * Track implementation progress and measure progress toward program goals through a verifiable source. :seedling: Learn More: [Metrics - Programmatic](/essentials/metrics/metrics-programmatic) # Metrics - Organization IN THIS ARTICLE Learn how organizations can create a curated list of metrics. Then, assign metrics to individual activity records and track progress toward stated goals. Outcomes are aggregated throughout FieldDoc and can be pushed to third-party applications through integrations. *** ## Metrics - Organization Organization Metrics help you understand the scale and scope of work being tracked by your organization in FieldDoc. They provide a standardized, scalable snapshot of intended outcomes and progress toward those outcomes that can be used to communicate progress, identify trends, and inform future strategic investment or implementation strategies. Metrics are attached by users within an organization's workspace to the individual activity records you and your collaborators create. As you track progress toward implementation, these values will update in real time. Organization metrics are only visible to collaborators within the organization workspace. They are not visible to funders via pacts. Read the [Metrics - Programmatic ](/essentials/metrics/metrics-programmatic)article for information on how to assign metrics to meet Pact requirements. You can view metrics at different levels: across your entire organization, within specific Project Folders, or within individual Sections. Organization Metrics are especially useful when you are communicating with funders, program managers, and administrators. You can demonstrate your impact via outcomes or understand engagement across multiple implementation locations. {% hint style="info" %} In Legacy FieldDoc, organization metrics did not exit. These are a new feature released in FieldDoc 2.0 and available to all standard users. {% endhint %} # Metrics - Programmatic IN THIS ARTICLE Learn how grantees and standard users can assign programmatic metrics to activity records. Then, assign metrics to individual activity records and track progress toward stated goals. Outcomes are aggregated throughout FieldDoc and can be pushed to third-party applications through integrations. *** ## Metrics - Programmatic Programmatic Metrics help you understand the impact of your work as it aligns to third-party Program goals. These metrics provide a standardized, scalable snapshot of intended outcomes and progress toward those outcomes that can be used to communicate progress, identify trends, and inform future strategic investment or implementation strategies. Metrics are attached by users within an organization's workspace to the individual activity records you and your collaborators create, after they have been linked to a [Pact](/essentials/pacts). As you track progress toward implementation, these values will update in real time. Programmatic metrics are only available to activity records shared with a Pact. Programmatic metrics are uniquely curated by program managers and assigned to Pacts. They are visible to funders via pacts and roll up across all Pacts within the Opportunity to show the impact of the investments across all fund recipients. {% hint style="info" %} In Legacy FieldDoc, all metrics were programmatic metrics. In the FieldDoc 2.0 system, programmatic metrics can be assigned to activity records once they are linked to a Pact. The available programmatic metrics list is based on the selected pact and its funding program. {% endhint %} ## Planned Values Each metric has two inputs fields - `planned_values` and `implemented_values`. T # Model Outputs
IN THIS ARTICLE Models within each activity record allow estimated environmental benefits to be associated with the digital representation of the on-the-ground work. *** ## Model Outputs To activate a model, you must complete the required input fields, which are determined by the **activity type** associated with the record. For most Adapted CAST models, the only required input is the **extent** in acres. However, we recommend reviewing all available input fields to ensure your estimate is as accurate as possible. Keep in mind that the **model output view** will vary depending on the activity type linked to the record, as different practices may produce different types of reduction estimates. ### Tour the Models view {% @arcade/embed flowId="7yYYf7XtebnCnjJoroEa" url="" %} ## Models FieldDoc supports a growing library of model calculators. For detailed information on the supported models, we recommend reading the associated model documentation. * [Adapted Chesapeake Nutrient and Sediment Load Reduction Model](/resources/models/adapted-chesapeake-nutrient-and-sediment-load-reduction-model) * [In-Stream load reduction estimates](/resources/models/in-stream-load-reduction-estimates) * [Shoreline restoration load reduction estimates](/resources/models/shoreline-restoration-load-reduction-estimates) * [Stormwater performance standard - treatment depths other than 1-inch](/resources/models/stream-restoration-load-reduction-estimates-protocols-1-5) * [Stream restoration load reduction estimates (Protocols 1 -5)](/resources/models/stream-restoration-load-reduction-estimates-protocols-1-5) # Portfolio IN THIS ARTICLE Portfolios are the home for your organization's FieldDoc data. *** ## Portfolio Portfolios are unique to each workspace within an organization. Portfolios are the home for your activity and metric data, providing structure that allows your team to stay focused on their work.
Portfolios contain the following organization components: ### Project Folders **Project folders are the top-level organizational units within a Portfolio.** While optional, they can be used to structure your activity records more effectively. For example, if your organization runs multiple conservation or restoration programs, you may choose to create a separate folder for each initiative. This helps organize activity records and track implementation progress more distinctly. ### Sections **Sections are mid-level sub-folders within a Project folder.** They are optional but can be helpful for adding another layer of organization to your activity records. For example, you might use Sections to group activities by landholder, county, or another relevant category within a project. This can support clearer tracking and reporting across different areas or partners. ### Activities **Activities are the core data records within a Portfolio.** Each Activity represents a specific conservation or restoration action, such as planting riparian buffers, installing cover crops, or removing invasive species. Activities are where you enter key implementation details, including location, timeline, and practice metrics. All measurable progress and outcomes are tracked at the Activity level, making them the foundation for reporting and impact assessment. ### Metrics **Metrics are organization-defined, non-automated data types used to track quantitative goals.** Each Metric represents a specific objective your organization has set—such as acres restored, linear feet of streambank stabilized, or pounds of sediment reduced. Users can define planned target values and then track progress toward those targets within each Activity record. Metrics are automatically rolled up to the Section and Project levels, allowing users to view collective progress across their portfolio. **Note:** If you are participating in a Pact, you may also be asked to track *Programmatic Metrics*. These are separate from your Portfolio metrics and are managed at the Pact level. ### Pacts **Pacts are agreements that bring together multiple partners under a shared conservation or restoration strategy.** They provide a framework for aligning efforts, sharing data, and reporting collective progress toward regional or programmatic goals. Pacts as managed by Funding Programs and allow an organization so share activity data for review and participation. Each Pact may define its own set of Programmatic Metrics, which participating users are expected to track in addition to their Portfolio metrics. Pacts allow organizations to link activity records from their portfolio. Once activity records are linked to a Pact, the programmatic metrics and other program-specific information will be made available through the activity records. Once completed, they roll up relevant data from partner Portfolios to support shared analysis and storytelling across the full collaboration. # Project Folders IN THIS ARTICLE Project folders are the highest level organizing unit in FieldDoc Portfolios. Projects are an optional folder in which to organize your activity records. *** ## Project Folders **Project folders are the highest level of organizational structure within a Portfolio.** They are visible only to members of the organization’s workspace and are used to group and manage related activities internally. This structure helps teams organize their work without sharing it outside the organization. ### How to use Projects Organizations should use Projects to organize programs or initiatives. For example, if your organization hosts a *Healthy Trees Program* and a *Forest Buffer Installation Initiative*, you can create a Project Folder for each one. What's really cool is that as you add [activity](/essentials/activities) records to your projects, the data included in each of those records will roll up to appear on the Project Summary Page. **Tip**: We do not recommend using projects to represent individual grants, as you may have overlap in funding opportunities over time. ## Tour a Project Folder Overview Page Project folders contain information that is stored at the Project level and a roll-up of activity record data stored within this project. {% @arcade/embed flowId="HDoSa9qLgjvoBn8VKe0T" url="" %} #### Details from the Project Folder tour #### Navigating a Project in FieldDoc To enter a project, click the **Project Summary** icon. This brings you to the **Overview Page**, which dynamically updates to reflect all the information you build within the project. As you add activity records and associated metadata—such as geospatial data and metrics—this information will populate on the Overview page. #### Activities Activities contain the foundational data in FieldDoc. From the **Activities** tab, you can view all records organized within the project folder. You can open existing activities, create new records, or switch views to manage your data in different formats. FieldDoc offers both a **Table View** and a **Map Editor View** for flexible data management. #### Metrics The **Metrics** tab displays a table of all non-modeled metrics assigned to activity records in the project. You can add organization-specific metrics directly to this table or view metrics added within individual activities. Note: **Programmatic metrics** are created by funding program managers and are only available to activities shared through a **Pact**. When assigned, these metrics also appear in the Metrics table and will include a Pact reference in the corresponding row. #### Implementation The **Implementation** tab tracks progress on the metrics listed in the Metrics tab. Once a metric is added to this view, the **only** field users should edit is `metric:implemented_value`. #### Sections **Sections** allow you to create subfolders within your project to further organize activity records. Each section has its own summary overview page, similar to the main project Overview. This is a great way to parse, manage, and share subsets of your data—especially helpful for managing updates. #### Collaborators Working together is easy in FieldDoc. From the **Collaborators** tab, you can invite and manage who has access to the project. Collaborators can create, edit, and delete activity records within the project. #### Linked Pages Use **Linked Pages** to attach stylized URLs to a Project, Pact, or Activity. This is useful for integrating third-party tools like AGOL prioritization apps or services like Matterport or Coolant that support MRV data collection. These links help bridge FieldDoc data with external systems. #### Documents Upload and store documents directly within a Project, Pact, or Activity. Files are accessible to other users who have access to the corresponding record. #### Images You can also upload **.png** and **.jpg** images to any Project, Pact, or Activity. Images are a great way to share visual context about the work being tracked and are accessible to all users with permission to view the record. #### Atlas The **Atlas** view provides a map-based visualization of all activity records within your project. It brings together organization metrics, programmatic metrics, and modeled metrics with their geospatial context, offering a comprehensive spatial perspective of your work. ## Managing Project Folder Data ### Create a Project Folder These instructions walk through creating a new project folder only. For instructions on how to add activity records to a project, check out the [activity](/essentials/activities) articles. {% tabs %} {% tab title="In-App" %} ### Create new Project From the Home screen or your Project view, click '+ Create' to make a new Project folder in your workspace. {% endtab %} {% tab title="Import File" %} ### Importing Projects via File Import When importing a file, you can create new **Project(s)**—this is especially helpful when batch importing **activity records**. **Steps to Import Projects:** 1. **Add a Project Name column**\ In your import file, include a column labeled for **Project Name**. 2. **Map the Project Name field**\ When configuring your import, map this column to `FieldDoc project:name`. 3. **Save your import**\ Once you click **Save**, the system will automatically create a new **Project** for each **unique Project Name** found in your file. Each activity record row will be placed within its corresponding Project. **TIP:**\ Each time you import a file with a mapped `project:name` field, the system creates a **new Project**, even if a Project with the same name already exists. to import [activity](/essentials/activities) records to an **existing Project**, import the file **from within that Project’s folder**. ### Dig In! Interactive Tutorial Through this file import you will create a new project called *Outer Rim Restoration and Resilience Program* that includes three *Sections* and nine individual activity records. The tutorial will walk you through how to import and navigate the records that you import. {% file src="/files/BUpVKxzIT3OCv99oSjNy" %} {% @arcade/embed flowId="FeckLqRZbrW8NJQcG9W5" url="" %} {% endtab %} {% endtabs %} ### Link or Create Activity records within Project Folders Here, we share how to make sure that activity records already in FieldDoc are correctly organized within the folder structure. Activity records can only be assigned to a single project folder; however, you can move activity records around or assign the project after the activity has been created. {% tabs %} {% tab title="Within Activity Record" %} ### Assign a project to an existing activity record Within an activity record, open the **Edit Activity** modal. Select the **Project** tab. Choose an available project or create a new one. Once you tap save, your activity will be organized and available with the project. {% endtab %} {% tab title="From Activity Table View" %} ### Assign a project from the activity table view From any table view of activities, you can reference or edit the associated project. From the table view, you can use the filter and sort options to organize activities by project. {% @arcade/embed flowId="JAqWB2Xs8lDyHmsK9pOs" url="" %} {% endtab %} {% endtabs %} # Sections IN THIS ARTICLE Sections are optional sub-folders within Projects that allow for further organization of activity records. *** ## Sections **Sections** allow you to create subfolders within your project to further organize activity records. Each section has its own summary overview page, similar to the main Project Overview, offering a clear way to parse, manage, and share subsets of your data. This is especially helpful for organizing updates or segmenting work by geography, implementation phase, or project team. Sections can only be added within an existing project. {% hint style="info" %} In Legacy FieldDoc, Sections were referred to as ***Sites***. The name was updated to provide a more generic and flexible naming structure that better reflects the wide range of ways users organize their nature-based work in FieldDoc. {% endhint %} # Activities records
IN THIS ARTICLE Where do activity records fit within an organization portfolio? How are they shared with funders? When is funder information available within an activity record? *** ## Activities Think of FieldDoc as a growing repository of your nature-based work. The fundamental unit is an **activity record**, which you can create for any action you're taking in support of nature-based solutions. Each activity record can include a wide range of attribute data, such as environmental models to estimate benefits and geometries to map its location on the landscape. You can organize your records within your portfolio using **Project Folders** and **Sections**. When you're ready, you can share records with funders, export them, or use integrations to connect with other applications. Examples of Activities include: * [ ] **Conservation strategies**, such as building wildlife corridors or placing conservation easements on parcels. * [ ] **Restoration strategies**, such as planting cover crops, installing bioretention rain gardens, and expanding urban tree canopies. * [ ] **Sustainability strategies**, such as conserving grasslands, managing forests, or protecting sensitive habitats. * [ ] **Community engagement strategies**, such as implementing monitoring programs, conducting educational series, or leading research initiatives {% hint style="info" %} In Legacy FieldDoc, Activities were called Practices. The change in FieldDoc 2.0 reflects the expanded list of nature-based work that can be tracked in FieldDoc. Restoration BMPs like cover crops, tree plantings, and wetland restoration are still supported as Activity\_Types. The expanded list includes additional work such as convenings, monitoring, and research. {% endhint %} *** ## Activity records Each activity record is represented by a tile in your portfolio. You can switch between views to see activity records as tile, grid, or on a map. Regardless of the view you choose, these records contain a wealth of information about your nature-based work. Activity records help you plan, track, and report progress toward completion, as well as assess the impact of your work in achieving target goals. The first step is to create activity records within your organization's workspace. Activity records are the fundamental unit in FieldDoc. It's the place where all data about the work will be stored. The information here may be visible and moved around FieldDoc to view in different contexts, or pushed to other parties via integrations. For information on the data that is managed within Activity Records, check out the articles in the Activities Essentials section: [**Activities Overview**](/essentials/activities) [General Settings](/essentials/activities/general-settings) [Geometry](/essentials/activities/geometry) [Activity metrics](/essentials/activities/activity-metrics) [Models](/essentials/activities/models) There are some **rules** for how activity records are organized within portfolios that are helpful to understand. ## Organize your activity records Activity records *can* be organized within a single Project folder and Section; however, this is optional. You can access all of your Activity records from the Activities view within your portfolio. ### Add new activity records Regardless of the entry point where you add a new activity record to your FieldDoc workspace, it will be added to your Portfolio. For example, if you add activities directly to a Pact, those records will also be added to your workspace portfolio. ### Sharing Activity Records #### Visibility Any user with Admin or Read-Only access to your Organization's workspace can see all of your activity records while they are looking at the workspace's portfolio. Any records they are linked to a Pact will be visible to the program managers associated with the Pact. Activity records and their accompanying data roll up to the hierarchical contexts, such as within Sections, Project Folders, and Workspaces for Organizations. For Programs, Activity record data is visible within Pacts, Programs, and Funding Sources. #### Managing data Activity record data can be managed within each activity record, through table views, or via [integrations ](/essentials/integrations-beta)and [workflows](/essentials/workflows-beta). ## Activity Record Fields
Field NameInstructions
NameGive each Activity in your portfolio a unique, easily identifiable name. This is a text field.
DescriptionProvide any additional details about your Activity that you'd like to share. The description will be visible through all Pacts.
Activity TypeSelect from the universal list. The Activity Type you select will load any relevant model(s) in the models section.
NEIEN

Map this Activity to NEIEN best management practice specifications.

Align activity metadata and implementation measurements with Environmental Information Exchange Network specifications. This information enables implementation tracking and crediting by state governments and the U.S. Environmental Protection Agency.

Extent

FieldDoc calculates extent based on the dimensions (area, length, etc.) of an activity's geometry. Many models and activity types use this number to calculate estimated nutrient and sediment reductions and other parameters.

FieldDoc uses the World Geodetic System (WGS84, EPSG:4326) as its reference coordinate system. Note that the estimated extent value generated by FieldDoc may differ from values produced by other systems that process geospatial data.

If necessary, fill out the "User-defined extent" inputs below to override the FieldDoc-generated extent.

Completion Status

Track the completion status for this activity.
Enter the date when the activity was fully installed by clicking the "Mark activity as completed" button. An activity is complete when all implementation work is finished.

Note: The activity completion date is not generated by FieldDoc. It must be entered manually.

State ReportingFor use by users that are submitting their Activities to State Reporting Leads for crediting.
Inspection LogFor use by users that choose to demonstrate ongoing functionality of an installed Activity, or BMP.
SectionA mid-level organizing feature to add to multiple Activities.
PrivacyWhen the privacy setting is turn on, the activity can only be viewed and edited by project collaborators and program managers. Geographic data related to this activity will not appear on dashboard maps.
# Metrics (via Portfolio)
IN THIS ARTICLE Within a workspace portfolio, users can curate a custom list of metrics and set organization-wide targets. These targets can then be assigned to individual activity records, enabling progress tracking throughout the implementation period. Metric summaries are available on overview pages across multiple levels—Activities, Sections, Project Folders, and the Organization—offering a clear snapshot of progress toward goals. *** ## Metrics In FieldDoc, users can activate automated modeled outcomes and assign non-automated metrics to their individual activity records. This approach broadens the amount of analysis, measuring, and reporting that can be accomplished through the system. The standardization ubiquitous across components of FieldDoc makes metric tracking possible at all scales: within an organization, within a project, within a Pact, but also across an entire funding program or grant opportunity. Let's take a closer look. ### Organizational Metrics Standard users can create a custom list of metrics that are important to their organization. After making this list, you can set targets for each metric. These targets will show up in the organization view. As you add activity records to your portfolio, you can link them to your organization’s metrics. During the project timeline, you can track your progress toward each goal at the activity level. That progress is then added up and shown at higher levels—like Section, Project, and Organization views. For example, if an activity is part of a Section and a Project, its contribution to a metric will count toward the totals for the Section, the Project, and the Organization. This makes it much easier to track and share progress on big goals, like the number of trees planted or the number of miles of stream restored. There is a lot of information to explore on how to set up and track your metrics. :seedling: Learn More: [Metrics - Organization](/essentials/metrics/metrics-organization) ### Programmatic Metrics Program Managers can create a custom list of metrics that are important to their funding program and organization. After making the list, any user that has assigned activity records to a Pact in that Funding Program can add the metrics to their activity record and set a target outcome. The targets will show up in the Pact Overview view. As grantees progress in their work to meet their funding requirements, they can track progress toward implementation for the programmatic metrics within their activity record. That progress is added up and shown on the Pact overview page. All of the Pacts within a Funding Opportunity will roll up and provide an overview of progress toward larger goals, such as Blueprints or Business Plans, for an entire funding program. The process allows Funding Program Managers to: * Align their priorities with individual awards * Track the geospatial and quantitative impact from standard views * Track implementation progress and measure progress toward program goals through a verifiable source. :seedling: Learn More: [Metrics - Programmatic](/essentials/metrics/metrics-programmatic) # Pacts (via Portfolio)
IN THIS ARTICLE\ View all Pacts that have been created to share activity records from within this workspace portfolio. Each Pact shares a collection of activity records and gives access to the programmatic metrics for that Pact Opportunity. *** ## Pacts **Pacts** are collaborative agreements available from a workspace portfolio that align an external aggregator, such as a funding partner, with an organization's work. Together, all users can track activity data, including shared modeled outcomes and metrics. Pacts allow users to define a common framework for implementation—such as restoration targets, climate resilience outcomes, or equity commitments—and track collective progress over time. Each pact can include: * A curated set of shared metrics * Target values or thresholds * Assigned contributors or member organizations * Timelines and status indicators Pacts provide a pathway for the workspace members to share activity records from within the portfolio, and bring programmatic metrics into the shared activity records. Remember, activity records can be shared across multiple Pacts. This makes it possible to roll up performance data from individual records to assess overall progress toward the pact’s commitments. Overview pages and dashboards provide visibility into how each organization or partner is contributing to the pact goals. # Pacts IN THIS ARTICLE **Pacts** are collaborative agreements available from a workspace portfolio that align an external aggregator, such as a funding partner, with an organization's work. Together, all users can track activity data, including shared modeled outcomes and metrics. Pacts allow users to define a common framework for implementation—such as restoration targets, climate resilience outcomes, or equity commitments—and track collective progress over time. *** ## Pacts **Pacts** are a key feature in FieldDoc that connect restoration professionals implementing critical nature-based work with the partners providing the resources to make that work a reality. Thanks to Pacts, FieldDoc serves as the data system that informs policy action on ecosystem restoration. Each Pact is represented by a tile within your portfolio. You can create Pacts to share collections of your activities with third parties—for example, to report implementation progress to funders. A Pact contains a wealth of information about your nature-based work. By linking activity records from your portfolio, you and the Pact Opportunity owner—such as a funding program manager—can exchange essential data about what work will be implemented, where it will take place, and what impact it is expected to have. Pacts make it easy to share details about your work with investors and partners—any entities that have created a Pact and are ready to receive your data. The first step in sharing your activity records is to locate the **Pact Opportunity Code** and create your Pact. *** ## Pact Actions The following sections walk through actions that you may perform in your pact ### Create a Pact In order to share activity records to a third party, such as a funder, you must create a Pact. Each award or agreement should have its own Pact. For specific details related to open individual Pact Opportunities, visit the FieldDoc [Guides](https://help.fielddoc.org/guides-1/) section. ### Find your Pact code Each funding opportunity has a unique Pact code. Users can find these codes within the [Program Guide ](https://help.fielddoc.org/guides-1/)section for their respective funding opportunity. #### Dig in! Interactive Tutorial on how to create a Pact {% @arcade/embed flowId="4Hkg5IlOq8vuaCETL8ZG" url="" %} #### Step-by-step instructions on how to Create a Pact 1. Select the + Create button from the Pacts Page (Tip! You can create Pacts from other locations too - look below for more options). 2. Enter the **Pact Opportunity Code**. This code is specific to the pact opportunity and may have a timeframe. If you do not know your opportunity code, check the [Program Guide](https://help.fielddoc.org/guides-1/), reach out to your program manager, or email . 3. Give your pact a **Name.** We recommend aligning the name with the title of your project as it appears in grant application or award documentation. 4. Add in a description. This is a helpful field for both the Pact creator, and the Pact Program Manager to reference. {% hint style="danger" %} If you give your Pact a generic name, the program managers will not be able to find it in FieldDoc. It is very important that your Pact name match the title of your application or award, unless otherwise requested by the funding program manager. {% endhint %} ### Tour Pact components While the core data shared via a Pact is activity records, restoration practitioners can enter additional data into the Pact itself. Let's take a tour! {% @arcade/embed flowId="GjCWZxiAuDOwhc1Q0XvO" url="" %} ### Link activity records to a Pact Data can be shared from a Portfolio into a Pact, or organizations can create records within the Pact itself (this data will be added to the workspace's portfolio). This is super helpful for many reasons. Let's take a look at the options to link activity records to a Pact. ### Dig in! Interactive Tutorial {% @arcade/embed flowId="9DXWj9SaEtOhZ5hC67RR" url="" %} #### Step-by-Step Instructions to Link Activity Records 1. Open the **Activities** tab within the Pact. 2. To access your Portfolio of Activities, click the **Link Activities** button. 3. All Activities within your portfolio will appear. You can filter by any of the available fields. Once ready, click the check box to select records to assign to the Pact. 4. Click Save. 5. The activity records linked to this Pact can now be associated with [Programmatic metrics](/essentials/metrics/metrics-programmatic). ### Create new activity records in a Pact To create new activity records, follow the steps in [Essentials: Activity ](/essentials/activities)to [**Create New** ](/essentials/activities#in-app-creation)or [**Import File**](/essentials/activities#file-import)**.** ## Submit a Pact for Review Once you have linked your Activity records and met all of your Program's requirements, make sure you click **Submit**. This gives the Program Managers visibility of your Pact.
{% hint style="info" %} Program Managers can only see data entered into a Pact within their Program. They cannot access or visualize any data that you have not shared via a Pact. {% endhint %} # Tables (Grid View) By switching the **Activity** page to **Table View**, you can quickly enter or update data across multiple activities—without opening each one individually. This makes bulk editing faster and easier. Here are your options for managing data in **Table View**: * **Edit Planned and Implemented values** * **Update Extent or Location information** * **Set Status and Dates** * **Assign to Sections or Projects** * *(Include any other key fields specific to your setup)* > ⚡ **Tip:** Use Table View when you need to review or update many records at once—it’s a big time-saver! # Workflows (beta) {% hint style="warning" %} Workflows are in Beta mode. Training materials and support for workflows will be coming in 2025. If you would like to begin using FieldDoc workflows, we recommed reaching out to to discuss your needs. {% endhint %} # Program Management Overview ## Program Manager Documentation Page actionsCommentShare feedback on the editor**FieldDoc takes the complexity out of managing your funding program, so you can spend less time wrangling grantee data and more time measuring real impact.**CommentShare feedback on the editorProgram Managers unlock a different set of tools in FieldDoc—not just because they oversee the big picture, but because they help shape it. While grantees and standard users enter data from the field, Program Managers define the structure of that data—setting the metrics, activity types, and standards that make it all measurable. By standardizing inputs across many users, they turn scattered details into actionable insights and track progress toward shared goals.CommentShare feedback on the editor ### Aggregator Subscription Program Managers gain access to FieldDoc through an Aggregator subscription. All of the Documentation in the help center for free and standard users applies to Program Managers when you are buiding out your own porfolio of nature-based records. The pages in this section are geared toward setting up and managing Programs to collect data from other FieldDoc users.CommentShare feedback on the editor**Ready to streamline reporting and maximize your program’s potential?**CommentShare feedback on the editorLet's dive into building and managing your program! # Funding Sources IN THIS ARTICLE Program Managers can curate a list of their funding sources and then assign those funding sources to individual Pacts. Demonstrate the impact of the investment to investors. *** ## Funding Sources Program Managers overseeing multiple funding sources can use FieldDoc to track how each investment aligns with specific outcomes. By linking individual awards and contracts to their respective funding sources, FieldDoc enables transparent, organized reporting. All records tied to a funding source can be viewed in the overview dashboard and Atlas views—just like a full Program overview—making it easy to analyze prioritization, demonstrate impact, and share meaningful insights with key investors and stakeholders. ## Configure funding sources Program Managers can coordinate with their FieldDoc account manager to set up funding sources and associate them with a Program. The FieldDoc team will ask for: * Funding Source Name * Provider * Agent * Amount ## Take a tour of a funding source view {% @arcade/embed flowId="ILOu27Xab0g8ICFi4KPE" url="" %} # Programs IN THIS ARTICLE Curate the metrics, activity types, and funding sources that matter most to your program. Launch Opportunities and invite grantees, restoration practitioners, and partners to submit their work using your tailored templates. Watch as a shared dataset comes to life—letting you compare, analyze, and understand impact across every submission. *** ## Programs With FieldDoc, you will manage your restoration or land protection programs’ metrics and targets from one convenient location. Programs are managed by Program Managers - FieldDoc users subscribed at the Aggregator level. ### How Programs work Programs are only visible to their designated Program Managers. With support from The Commons team, Program Managers configure each program with a curated list of metrics and activity types. Within the program, you’ll also create Opportunities—time-bound submission windows that allow other FieldDoc users to share activity records from their portfolios. These Opportunities often align with an RFP application process or serve as a final report deliverable under a grant agreement. :seedling: Learn more: [Opportunities](/program-management/pact-opportunities) To submit activity records to an Opportunity, users create a Pact using a unique Pact Opportunity Code. Once a user creates a Pact, they can begin linking activity records from their portfolio to it. These standardized records may include: * **Activity Types**\ Selected from a standard list. The choice activates relevant metrics and models for consistent, robust analysis. * **Geometries**\ Mapped locations that show where the work will occur. * **Extent**\ The size of the activity—typically in acres or linear feet. * **Modeled Environmental Outcomes**\ Calculated using industry-standard tools to estimate the expected environmental benefits. * **Programmatic Metrics**\ Metrics defined by the Program, along with a planned outcome to be achieved by the end of the project. Once users **submit their Pact**, it becomes visible to you as the Program Manager. You’ll be able to: * Search for submitted Pacts and their activity records * Edit attribute data within the Pact including: * Pact Status * Contract start and end dates * Unique identifiers (eg a Grant ID) * Award Amount * [Funding Sources](broken://pages/gnuqjChFSnojRfzZWd2g) * View data rollups across Pacts in **FieldDoc Atlases** and **Program Overview** Pages * Integrate Pact data with tools like **ArcGIS Online** and **Felt Maps** to support prioritization and align with your business plan or blueprint ## Configure your Program Working with The Commons, Program Managers at the Aggregator level will provide key details to set up your program. These details include: * Program Name * Short program description * Website ### Curate a list of metrics Provide The Commons with a list of all programmatic metrics you want assigned to your Program. This list should include: * Each metric name * Target values * Baseline progress (if available) These metrics will be made available to all activity records linked to a Pact within your Program. Users can assign the relevant metrics to their activity records and track progress toward the targets over time. ### Curate a list of Activity Types Narrow the universal list of Activity Types by selecting only those relevant to the work your program funds. FieldDoc allows you to curate this list during program setup. When users create new activity records within their Pact, they’ll be able to choose from your tailored list—saving time and keeping submissions aligned with your funding priorities. ### Configure your Pact Opportunity Provide The Commons with: * A Pact Name * The Open Date * The Close Date * Funding Sources The Commons will configure the Pact Opportunity and generate a unique Pact code to share with users. Pacts are not discoverable without this code.
### Review submitted Pacts Program Managers can view any Pacts that have been submitted by users to the available opportunity. # Pact Opportunities IN THIS ARTICLE Allow third parties to share implementation they plan to achieve with your support. *** ## Pact Opportunities **Pact Opportunities** allow third-party users—such as grant applicants and awardees—to share their activity data with your Program. Each Program can have multiple Pact Opportunities, making it easier to organize and manage data by specific funding rounds or opportunities. Think of a Pact as the agreement between two parties of what will be accomplished through an agreed upon scope of work, such as through a contractual vehicle like a contract or grant agreement. Program Managers who have multiple agreements with third parties, such as a slate of grant awards, can ask their recipients to create Pacts within the Opportunity to represent the work that will be accomplished. The grant recipients will link activity data from their Portfolio via a Pact. These general FieldDoc users will be able to share single activity records to multiple Pacts, which helps reduce desk time reporting across multiple systems, increases standardization for analysis and decision-making, and solves concerns of redudancy and duplication. ### Configure a Program's Pact Opportunity One Program can have multiple Pact Oppportunities. In fact, The Commons expects Program Managers to configure a new Pact Opportunity for each funding cycle. In order to configure a Pact Opportunity, the Program Managers must provide The Commons with: * A Pact Name * The Open Date * The Close Date * Funding Sources The Commons will configure the Pact Opportunity and generate a unique Pact code to share with users. Pacts are not discoverable without this code. ### Managing a Pact Opportunity FieldDoc users who have the Opportunity code can create Pacts within the Opportunity. Once they have linked their activity records and added the associated attribute data they will click **Submit** on their Pact overview page. They must click submit in order for Program Managers to have access to the Activity record data. Once a Program Manager has access to a Pact, it will appear in Programs> Pacts. As this list grows, use the filter tools to manage the individual Pacts. Within a Pact, Program Managers have access to fields that the general users cannot manage: * Pact Status * Start Date * End Date * Funding Sources * Unique Identifier Managing these fields should be part of your QA/QC standard operating process. The General Users who own the Pact will be in charge of managing data specific to their activity records: * Completion Date * Geometry * Activity Type * Extent * Model outputs * Programmatic metric implementation progress # Models ## What are Models? In FieldDoc you may want to use the available models to populate useful information regarding the proposed environmental benefit of your conservation and restoration efforts. You can calculate estimated benefits by associating and turning on available models within your Activity records. For example, if you use FieldDoc to prepare a NFWF [Chesapeake Bay Innovative Nutrient and Sediment Reduction Grant](https://help.fielddoc.org/docs/nfwf-innovative-sediment-and-nutrient-reduction-insr) applications, you can enter metric inputs for the stream restoration practices, and the system will calculate nitrogen, phosphorus, and sediment load reductions based on the practice type, geographic location, practice extent, and additional inputs. All of the math is made available thanks to FieldDoc's provision of leading, customized algorithms provided by our modeling experts and implemented by our development team. > #### 👍**We define an algorithm as:** > > A process or set of rules to be followed in calculations or other problem-solving operations, especially by a computer. The inputs users provide when creating practice records in FieldDoc power the math required to turn BMP data into calculated load reductions. This greatly benefits our users because it means we can automate important metric information about your project without you needing to know exactly how to calculate complex metrics such as pounds of nutrients reduced. Instead, grantees and applicants simply enter project information and our algorithm handles the rest. ### How do I know what practices and metrics are modeled and which ones are not? There are a few quick and easy ways to know if the practice and its respective metrics are tied to an algorithm developed by one of our partners. First, on all metric summary pages, metrics tied to an algorithm will appear on top. You will also be able to see a handy block of text linking you to algorithm's detail page where you can get more information about the assumptions, how it was developed, who created it, and the practices it encompasses. ## Models in FieldDoc * Adapted Chesapeake Nutrient and Sediment Load Reduction Model * In-stream Load reduction Estimates *(more detailed information coming soon)* * Stream Restoration *(more detailed information coming soon)* * Stormwater Performance Standards *(more detailed information coming soon)* * Shoreline Restoration Load Reduction Estimates *(more detailed information coming soon)* * Stormwater performance standard - Treatment depths other than 1 inch *(more detailed information coming soon)* ## Using Models Step-by-Step instructions on how to use Models can be found on the [Modeled Outputs](/essentials/model-outputs) page. # Adapted Chesapeake Nutrient and Sediment Load Reduction Model **Load reduction estimates** in FieldDoc are based on data from the Chesapeake Bay Program's Phase 6 model. These estimates are calculated by combining the type of [best management practice (BMP)](/essentials/activities/general-settings/activity-type), the **size** or area it treats, and its **location** within a specific land-river segment. The system then applies the corresponding nutrient or sediment reduction efficiency. To simplify this process, FieldDoc uses the **Adapted Chesapeake Nutrient and Sediment Load Reduction Model**, which relies on standard efficiencies. This model is designed to make data entry easy while still maintaining scientific credibility. It’s important to note that this tool is not intended to replace official Chesapeake Bay Program scenario tools or provide exact numbers for TMDL targets. Instead, it offers a general estimate of nutrient or sediment reductions based on the size, type, and location of a practice—helpful for understanding potential environmental benefits before implementation. ## Source Documentation
Chesapeake Assessment Scenario Toolhttps://cast.chesapeakebay.net//files/N6RuwmufeTPtKI6BQjsY
BMP documentationhttps://cast.chesapeakebay.net/Documentation/BMPs/files/N6RuwmufeTPtKI6BQjsY
### Activity model view
: # Stream Restoration Load Reduction Estimates (Protocols 1 - 5) This model estimates nutrient and sediment load reductions using data and algorithms from the October 26, 2020 Consensus Recommendations to Improve Protocols 2 & 3 for Defining Stream Restoration Pollutant Removal Credits. You can find more information about the protocols used to derive these estimates at the links in this page.
Visit website/files/FuYPIomXIZfEone4TW5fhttps://chesapeakestormwater.net/
View Documentation/files/FuYPIomXIZfEone4TW5fhttps://chesapeakestormwater.net/resource/a-unified-guide-to-crediting-stream-and-floodplain-restoration-practices-in-the-chesapeake-bay-watershed/
## Getting started: Inputting data into the stream restoration load models ### Associated \`activity\_types\` The Stream Restoration models load when the `Activity_type` selected is `Stream restoration`. ### Activity model view When you open your Stream Restoration Load Reduction estimates, you first must indicate if the project design meets the completion percentage. If your project does not yet meet the >90% design requirement, you can enter in the linear length and click save inputs. The system will generate estimated load reductions based on the linear feet.
In order to get higher accuracy in the model outputs, you will need to use the >90% design threshold. Let's look at each of the protocols. ## Protocol 1: **Prevented sediment**
Protocol 1: Prevented Sediment Qualifying Conditions The stream reach must be greater than 100 feet in length and be still actively enlarging or degrading in response to upstream development or adjustment to previous disturbances in the watershed (e.g., a road crossing and failing dams). Most projects will be located on first- to third-order streams, but if larger fourth and fifth order streams are found to contribute significant and uncontrolled amounts of sediment and nutrients to downstream waters, consideration for this BMP would be appropriate, recognizing that multiple and/or larger scale projects may be needed or warranted to achieve desired watershed treatment goals. The project must utilize a comprehensive approach to stream restoration design, addressing long-term stability of the channel, banks, and floodplain. Special consideration is given to projects that are explicitly designed to reconnect the stream with its floodplain or create wetlands and instream habitat features known to promote nutrient uptake or denitrification. Each project must comply with all state and federal permitting requirements, including 404 and 401 permits, which may contain conditions for pre-project assessment and data collection, as well as post-construction monitoring. Stream restoration is a carefully designed intervention to improve the hydrologic, hydraulic, geomorphic, water quality, and biological condition of degraded urban streams, and must not be implemented for the sole purpose of nutrient or sediment reduction. There may be instances where limited bank stabilization is needed to protect critical public infrastructure, which may need to be mitigated and does not qualify for any sediment or reduction credits. A qualifying project must meet certain presumptive criteria to ensure that high functioning portions of the urban stream corridor are not used for in-stream stormwater treatment (i.e., where existing stream quality is still good). These may include one or more of the following: * \- Geomorphic evidence of active stream degradation (i.e., BEHI score) * \- An IBI of fair or worse * \- Hydrologic evidence of floodplain disconnection * \- Evidence of significant depth of legacy sediment in the project reach
### Steps to enter data for qualifying conditions **Enter the estimate stream sediment erosion rates and annual sediment loadings.** *To add a set of measurements, click the "Add a set of bank measurements" button below the table. To remove a set of measurements, delete the bank ID and click the "Save inputs" button below the table.)*
{% file src="/files/u7fUrFnRslVTFztVQnhJ" %} ## **Protocol 2: Denitrification in the hyporheic zone**
Protocol 2: Denitrification in the hyporheic zone Qualifying Conditions Project must meet applicable floodplain management requirements in the stream corridor. Any individual stream restoration project should be assessed with hydrologic and hydraulic models to demonstrate whether it increases water surface elevations or has adverse downstream flooding impacts. In general, these analyses are based on design storm events and flood risk conditions established by the appropriate local or state floodplain management agency (e. g., the 100-year storm event). Project must evaluate the duration of floodplain ponding in the context of the restoration goals. Micro pools and long-duration ponding of water on the floodplain is essential for amphibian habitat, but large open water features may adversely impact the desired riparian vegetative community. In evaluating a potential restoration site and design, consider the potential adverse effects of extended open water ponding based on the soil characteristics, plant community, amphibian and other aquatic habitat goals. Project must demonstrate consideration of potential unintended consequences of the restoration. The project should document that a site impairment exists and that the interventions or restoration work proposed are appropriate to address the impairment. The proposed design should demonstrate that a positive ecological functional uplift (or change) for the stream and associated riparian system will result. Project must demonstrate that it either provides, or is tied into existing upstream and downstream grade controls to ensure the project reach can maintain the intended stream access to the floodplain. Project must clearly define the boundary of the effective hyporheic zone. For Floodplain Restoration and Raising the Streambed projects the effective hyporheic zone is a maximum of 18 inches deep in the floodplain soil profile, and extends only to those areas that are regularly inundated after the streambed is raised. The actual dimensions must be confirmed by site investigations that define stream flow conditions, root zones, aquifer conditions and the pre-project water table conditions. Project must demonstrate that baseflow conditions are not reduced as a result of the restoration (ex. change from perennial to seasonal intermittent flow). Presence of legacy sediment deposits or other floodplain impairment. Legacy sediments must be present in the project reach to a depth that has impaired aquatic ecosystem function. Legacy sediment includes any deposits that have occurred since European settlement, including very recent sediment deposits, often created by features such as mill dams, road embankments, floodplain fill and other kinds of stream corridor impairment. Floodplain connection to valley bottom aquifer. The design objective is to restore a plant/groundwater connection within the floodplain, so that most of the root mass of the floodplain vegetation is in direct contact with the underlying hyporheic aquifer. In cases where the historic hyporheic aquifer cannot be accessed due to modern controls (i.e., culverts or utility crossings), the objective is to plug the flow of the underlying aquifer so as to create a new hyporheic zone using cobbles, gravel and/or sandy materials. Defined boundaries for the channel(s), floodplain and valley bottom. The restored channel and floodplain dimensions are based on field testing that define the key vertical and lateral sediment boundaries of the existing floodplain and the hyporheic aquifer beneath it. Raising the stream bed and removal of legacy sediments are the primary means to restore floodplain reconnection at most sites. Meet applicable floodplain management requirements in the stream corridor. Any individual stream restoration project should be assessed with hydrologic and hydraulic models to demonstrate whether it increases water surface elevations or adverse downstream flooding impacts. In general, these analyses are based on design storm events and flood risk conditions established by the appropriate local or state floodplain management agency (e.g., the 100-year storm event).
### Steps to enter data for qualifying conditions **Define the effective hyporheic zone and apply the denitrification rate.**
**Enter the site specific discount factors using the table below.**
**Floodplain factors** {% hint style="warning" %} Values from 0-1 **must** be entered for both pre-restoration and post-restoration inputs. Use the drop-down selections to set discount factor values (see the table above). {% endhint %}
## Protocol 3: Floodplain Reconnection
Protocol 3: Floodplain reconnection Qualifying Conditions Project extended hyporheic zone and floodplain treatment zone boundaries must be assessed with hydrologic and hydraulic models to demonstrate whether it increases water surface elevations or has adverse downstream flooding impacts. Project must avoid extended ponding / inundation of the floodplain to assess the potential adverse effects of extended open water ponding based on the soil characteristics, plant community, amphibian and other aquatic habitat goals. Project must demonstrate consideration of potential unintended consequences of the restoration, such as aquatic passage and potential water quality loss. A site impairment exists and that the interventions or restoration work proposed are appropriate to address the impairment. The proposed design should demonstrate that a positive ecological functional uplift (or change) for the stream and associated riparian system will result. Any wetlands that fall within the boundaries of the floodplain treatment zone and are reported for credit under Protocol 3 should not also be reported using the Non-Tidal Wetlands Expert Panel. Project meets all of the qualifying conditions listed in the original Stream Restoration Protocol Expert Panel report outlined in Appendix B. Project must demonstrate that it either provides, or is tied into existing upstream and downstream grade controls to ensure the project reach can maintain the intended stream access to the floodplain. Project must clearly define the boundary of the effective hyporheic zone. For floodplain restoration and raising the stream bed projects, the EHZ is a maximum of 18 inches deep in the floodplain soil profile, and extends only to those areas that are regularly inundated after the streambed is raised. The actual dimensions must be confirmed by site investigations that define stream flow conditions, root zones, aquifer conditions and the pre-project water table conditions. Project must demonstrate that baseflow conditions are not reduced as a result of the restoration. For example, change from perennial to seasonal intermittent flow. Confirm the presence of legacy sediment deposits. Demonstrate that the design approach restores channel and floodplain connection with the hyporheic aquifer and restores processes within a hyporheic exchange zone. The EHZ is a maximum of 18 inches deep in the floodplain soil profile. When modern site constraints prevent directly connecting the restored channel and floodplain to the hyporheic aquifer, the design should include measures to interrupt flow within the hyporheic aquifer and elevate the hyporheic exchange zone into the restored floodplain. Project has defined EHZ boundaries across channels/floodplain. Legacy sediment removal is the primary floodplain restoration technique.
### Steps to enter data for qualifying conditions **Existing floodplain trapping zone area (acres)** The floodplain trapping zone is where low-energy conditions encourage trapping and filtering of sediments and organic matter in the floodplain during and shortly after storm events. Extends from the floodplain surface to one foot above the baseline floodplain elevation, unless a higher elevation is justified by local H\&H modeling. \ **Proposed floodplain trapping zone area (acres)** The floodplain trapping zone is where low-energy conditions encourage trapping and filtering of sediments and organic matter in the floodplain during and shortly after storm events. Extends from the floodplain surface to one foot above the baseline floodplain elevation, unless a higher elevation is justified by local H\&H modeling. **Pre-restoration treatable flow (%)** **Enter a number between 0 and 1.** Treatable flow is the percentage of flow which accesses the floodplain while remaining below the 1 ft elevation cap (unless a higher elevation is warranted based on H\&H modelling), with baseflow removed. This value is expressed as a percentage and is calculated outside FieldDoc. **Post-restoration treatable flow (%)** **Enter a number between 0 and 1.** Treatable flow is the percentage of flow which accesses the floodplain while remaining below the 1 ft elevation cap (unless a higher elevation is warranted based on H\&H modelling), with baseflow removed. This value is expressed as a percentage and is calculated outside FieldDoc. **Stream length upstream of project (miles)** What is the total length of stream above your restoration project? Measure in miles **Soil nitrogen concentration (lbs/ton) (optional)** This value is optional. In the absence of site-specific monitoring data, this model uses the median soil nitrogen concentration of 4.82 lbs/ton, as recommended by the expert panel report. **Soil phosphorus concentration (lbs/ton) (optional)** This value is optional. In the absence of site-specific monitoring data, this model uses the median soil phosphorus concentration of 1.13 lbs/ton, as recommended by the expert panel report. ## **Protocol 4: Stormwater performance standard**
Protocol 4: Stormwater performance standard Qualifying Conditions Eligible runoff reduction practices are: landscape restoration/reforestation; rooftop disconnection; sheetflow to filter/open space; all ESD practices in MD 2007; dry swale; expanded tree pits; grass channels; green roof; green streets; infiltration; rainwater harvesting; landscape restoration/reforestation. Eligible stormwater treatment practices are: constructed wetlands; filtering practices; proprietary practices; wet ponds and wet swales.
### Steps to enter data for qualifying conditions {% hint style="success" %} Enter a separate set of measurements for each treated load source. {% endhint %}
## **Protocol 5: Outfall and gully stabilization**
Protocol 5: Outfall and gully stabilization Qualifying Conditions The channel or gully slope below the source must exhibit predictive indicators for severe erosion or hill-slope failure and must be observed to be actively enlarging or degrading. The project should utilize a comprehensive approach to stream channel design, addressing longterm stability and resiliency of the channel, banks, and floodplain. Each project must comply with all state and federal permitting requirements, including 404 and 401 permits, which usually contain conditions for pre-and post-project assessment and post construction monitoring. Projects need to meet post-construction stability criteria and successfully establish needed vegetation. Projects should maintain or improve existing native riparian vegetation in the headwater stream corridor to the extent possible. Projects should follow regulatory agency guidance regarding compensation for any losses of forest, wetlands and sensitive habitats within project work areas. Projects should avoid the use of pipe extensions or drop structures unless it can be demonstrated that they are needed to sustain channel stability and they do not introduce new aquatic organism passage issues. The project should provide functional lift within the project reach, typically as indicated by improvements of Levels 2 (Hydraulics) and when possible 3 (Geomorphology) of the stream functions pyramid (Harman et al , 2011). The project directly addresses a headcut, with severe vertical incision (progressive bedlowering). The project MUST NOT introduce barriers or challenges to aquatic organism passage or degrade instream habitat. Projects should always seek to improve passage of aquatic organisms and aquatic habitat where possible. Drop structures, extension of an existing storm drain pipes, stormwater collection features, and scour protection or other hard armoring techniques used in OGSPs are not eligible for credit in perennial or intermittent channels.
{% hint style="warning" %} For full consideration by grant administrators of these Protocol 5 results, you must upload a map of 1) the extent of the Protocol 5 application and 2) a longitudinal profile of the existing conditions, proposed conditions, and equilibrium slope conditions. {% endhint %} ### Steps to enter qualifying conditions **Calculate the existing and equilibrium channel conditions** Calculate the total prevented sediment by inputting the following information into a 3-D surface modeling program such as InRoads or Geopak. * \- Length of proposed project reach (ft) * \- Channel slope (ft/ft) * \- Bank height (ft) * \- Bottom width (ft) * \- Top width (ft) * \- Bulk density (lbs/ft3) * \- Base level control * \- Equilibrium bed slope (ft/ft) * \- Equilibrium bank slope (ft/ft) * \- Future channel width (ft)
# In-Stream Load Reduction Estimates ## Getting started: Inputting data into the stream restoration load models ### Associated \`activity\_types\` The Stream Restoration models load when the `Activity_type` selected is one of the following: `Algal Flow-way Non-Tidal (Custom model)` `Algal Flow-way Non-Tidal Monitored (Custom model)` `Algal Flow-way Tidal (Custom model)` `Algal Flow-way Tidal Monitored (Custom model)` `Diploid Oyster Aquaculture 2.25 Inches (Custom model)` `Diploid Oyster Aquaculture 3.0 Inches (Custom model)` `Diploid Oyster Aquaculture 4.0 Inches (Custom model)` `Diploid Oyster Aquaculture 5.0 Inches (Custom model)` `Diploid Oyster Aquaculture Greater 6.0 Inches (Custom model)` `Site-Specific Monitored Oyster Aquaculture (Custom model)` `Triploid Oyster Aquaculture 2.25 Inches (Custom model)` `Triploid Oyster Aquaculture 3.0 Inches (Custom model)` `Triploid Oyster Aquaculture 4.0 Inches (Custom model)` `Triploid Oyster Aquaculture 5.0 Inches (Custom model)` `Triploid Oyster Aquaculture Greater than 6.0 Inches (Custom model)` ### Activity model view #### Algal Flow custom models
#### Oyster Aquaculture custom models
# Shoreline Restoration Load Reduction Estimates # Stormwater performance standard - Treatment depths other than 1 inch # (not functioning) Drexel/ANS BMP API # Troubleshooting This page is continually updated with commonly asked questions that the FieldDoc team receives. If you can't find your answer here, please [Get in Touch](/support/get-in-touch).\\ ## Creating an Account
The 'Create Account' button is unresponsive During the registration process, some users have reached out because the "create account" button on the registration page is unresponsive. In other words, they fill out the registration form but when they click the Create account button, nothing happens. Here are some tips to try if this happens to you: 1. Clear your browser cache and reload the webpage. 2. Make sure that your browser is up to date with any system updates. 3. Check with your IT department to make sure that FieldDoc.org is added to their safe list.
# Submit an idea {% embed url="" %} # Get in touch The Team behind FieldDoc is ready to dig in to answer your technical questions. We staff a support desk from 9:00 - 5:00 ET Monday through Friday. Reach us at 📧[support@fielddoc.org](mailto:support@fielddoc.org?subject=FieldDoc%20Help%20INSERT%20ACTIVITY%20NAME\&body=!!!For%20timely%20responses,%20make%20sure%20you%20include%20key%20information%20about%20your%20question%20such%20as%20the%20name%20of%20your%20project%20or%20practice,%20or%20better%20yet%20a%20URL%20to%20the%20). Make sure you include key information about your question such as the name of your project or practice, the corresponding grant program (if applicable) or better a yet a URL to the page where you have a question! {% hint style="info" %} We do our best to respond promptly, though occasional high volumes of use may cause delays. The typical response time is within 24 hours! {% endhint %} # Pricing

Basic

For grantees working on active funding opportunities.Plan highlights:
  • Submit your proposals of activity and impact to funders
  • Track implementation progress tied to agreements
  • Meet program reporting requirements
Get started for free

Standard

For practitioners tracking project implementation.Plan highlights:
  • Organize your restoration & conservation work
  • Access all models to estimate or analyze impact
  • Connect Workflows and integrations
Upgrade to Standard

Aggregator

For investors and conveners collecting data.Plan highlights:
  • Manage and analyze multi-participant programs data.
  • Curate standard program metrics and activity types
  • Activate environmental models for your participants
Talk to our team
[Review subscrition description details](/pricing/subscription-descriptions). # Subscription Descriptions ## FieldDoc Subscription Documentation This FieldDoc Subscription Documentation describes the general subscription tiers, billing structures, access limits, renewal terms, cancellation terms, and data retention practices that apply to FieldDoc subscriptions unless a Master Service Agreement, Order Form, Statement of Work, grant agreement, Program agreement, Application-Specific Terms, or other written agreement with The Commons provides otherwise. This document should be read together with the FieldDoc Terms of Service, the FieldDoc Privacy Policy, and any applicable written agreement with The Commons. Capitalized terms not defined in this document have the meanings given to them in the FieldDoc Terms of Service. The Commons may update this Subscription Documentation from time to time as FieldDoc’s subscriptions, features, services, support options, access models, and data retention practices evolve. Unless a signed written agreement with The Commons says otherwise, the updated Subscription Documentation applies to new subscriptions, renewals, upgrades, downgrades, additional usage, add-on services, and continued access after the update takes effect. If there is a conflict between this Subscription Documentation and a signed Order Form, Statement of Work, grant agreement, Program agreement, Master Service Agreement, or other written agreement executed by The Commons, the signed written agreement controls for that Customer relationship to the extent of the conflict. ### 1. Subscription Tiers FieldDoc offers three primary subscription tiers: Basic, Standard, and Aggregator. The Commons may also make Application-specific subscriptions, add-on services, trial access, grant-funded access, pilot access, promotional access, or other access models available from time to time. Subscriptions and access levels are assigned at the Organization level unless The Commons expressly provides otherwise. #### 1.1 Basic Tier The Basic Tier is intended for Organizations using FieldDoc primarily to meet application, participation, or reporting requirements for funding opportunities, Programs, Pact Opportunities, or other workflows that are managed through FieldDoc. Basic access may be appropriate for Organizations that need to create an account, join an Organization, create or submit Pacts, manage limited Activity records, or participate in a Program-specific workflow. Basic access is provided at no cost where permitted by the platform. Basic access does not create a right to indefinite access, indefinite data retention, continued availability of any feature, or access to paid features, Applications, support levels, exports, Models, dashboards, integrations, or workspaces. #### 1.2 Standard Tier The Standard Tier is intended for Organizations, practitioners, and authorized technical service providers using FieldDoc for internal planning, prioritization, modeling, data management, monitoring, reporting, tracking, analysis, and communication related to conservation, restoration, sustainability, environmental, or nature-based work. Standard subscriptions may be purchased through a self-serve process where available. Organizations that need onboarding, configuration, data migration, training, technical assistance, GIS support, reporting support, custom workflows, dashboard development, or other add-on services should contact The Commons to discuss whether a Statement of Work, support plan, or other written arrangement is appropriate. #### 1.3 Aggregator Tier The Aggregator Tier is intended for Organizations, funders, agencies, coalitions, collaborations, and Program Managers that collect, manage, review, analyze, or report conservation and restoration data submitted or shared by external Organizations through FieldDoc. Aggregator subscriptions require coordination with The Commons and may require a Master Service Agreement, Order Form, Statement of Work, grant agreement, Program agreement, or other written arrangement. Aggregator features, Program configuration, Pact Opportunities, Programmatic Metrics, available Models, support commitments, reporting workflows, data retention terms, seat limits, workspace limits, fees, and service commitments will be described in the applicable written agreement or Subscription Documentation. ### 2. Subscription Terms Unless otherwise stated in the applicable Subscription Documentation or written agreement, Basic access remains available while the Organization remains eligible for Basic access, complies with the FieldDoc Terms of Service, and maintains at least one active and contactable Organization Owner. Data associated with Basic access may be subject to retention, archive, or deletion limits described in this document, the FieldDoc Terms of Service, Program requirements, or other applicable written documentation. Standard subscriptions may be offered on a monthly or annual basis. Self-serve Standard subscriptions renew according to the billing interval selected at registration or checkout unless cancelled before the next renewal date. Aggregator subscription terms are set in the applicable Order Form, Statement of Work, grant agreement, Program agreement, invoice, or other written arrangement approved by The Commons. ### 3. Fees and Payment Subscription fees are due at the time a paid subscription begins, unless the applicable Subscription Documentation, invoice, Order Form, Statement of Work, grant agreement, Program agreement, or other written agreement states otherwise. Fees are based on the subscription tier, Applications, features, usage limits, seat limits, workspace limits, support level, service commitments, and add-on services selected by the Customer or otherwise described in the applicable Subscription Documentation. Plans are billed at the Organization level unless The Commons expressly provides otherwise. The Customer is responsible for all fees associated with its subscription, including fees initiated or managed by an Organization Owner, billing contact, administrator, or other authorized representative. Additional fees may apply for increased usage limits, additional seats, additional workspaces, Application-specific access, enhanced support, professional services, custom configuration, data migration, training, reporting assistance, integrations, dashboards, or other add-on services. The Commons may modify subscription fees, tier structures, features, usage limits, support levels, and access models from time to time. Unless otherwise stated in a written agreement, price changes will not apply to a prepaid subscription term already purchased, but may apply to renewals, upgrades, new subscriptions, additional usage, add-on services, or future subscription terms. ### 4. Billing Self-serve Standard subscriptions may include monthly and annual billing options. The billing cycle is selected during registration, checkout, renewal, or other subscription setup process. Monthly subscriptions are billed automatically on a recurring monthly basis unless cancelled before the next renewal date. Annual subscriptions are billed annually unless the applicable Subscription Documentation states otherwise. Annual subscriptions may be offered at a discount compared to monthly billing. Unless otherwise stated in the applicable Subscription Documentation or required by law, prepaid annual subscriptions are non-refundable. Aggregator subscriptions, enterprise arrangements, grant-funded access, sponsored access, and custom subscriptions may be billed annually, semi-annually, according to milestone schedules, or according to another structure described in the applicable Order Form, Statement of Work, grant agreement, Program agreement, invoice, or other written arrangement. The Commons’ default invoicing and payment process is electronic. Invoices and payment records may be managed through The Commons’ billing system, payment portal, or online payment gateway. Customers are responsible for maintaining accurate billing information, retrieving invoices, managing internal payment approvals, and ensuring that payment is made when due. Alternative invoicing structures, purchase order requirements, procurement requirements, or payment processes must be approved by The Commons in advance. A Customer’s internal procurement process, purchase order requirement, invoice approval process, or payment delay does not modify payment deadlines or subscription terms unless The Commons expressly agrees in writing. Unless otherwise stated in an applicable written agreement, Customers are responsible for taxes, duties, assessments, or similar charges associated with paid subscriptions, professional services, support plans, or other paid Services, excluding taxes based on The Commons’ income. ### 5. Failed Payments and Nonpayment If a payment method fails, an invoice is not paid when due, or undisputed fees remain unpaid, The Commons may provide notice and an opportunity to correct the issue where feasible. If the issue is not resolved within 14 days after notice, The Commons may suspend, limit, downgrade, or terminate access to paid features, Applications, workspaces, Program tools, support, professional services, or other subscription-based Services. The Commons may act sooner if required by law, payment processor rules, security concerns, fraud risk, contractual obligations, or platform integrity needs. Suspension, downgrade, or termination for nonpayment does not relieve Customer of responsibility for fees already incurred or payable for the applicable subscription term. ### 6. Free Plan and Free Trials When a new Organization is created in FieldDoc, the Organization may begin at the Basic Tier unless another access level is selected, assigned, sponsored, or approved by The Commons. If a User is the first member of a new Organization, that User may become the Organization Owner and may be responsible for managing Organization membership, permissions, billing settings, subscription selections, and related responsibilities. Basic access is free where permitted by the platform. Basic access may be limited by features, seats, workspaces, support, exports, Application access, data retention, Program access, Models, usage limits, or other restrictions. An eligible Organization Owner may activate a single-use 14-day free trial of the Standard Tier where offered by The Commons. Only one Standard Tier free trial may be activated per Organization unless The Commons expressly allows otherwise. If a free trial requires a payment method and will automatically convert to a paid subscription, The Commons will disclose the applicable price, billing interval, renewal term, payment method, cancellation deadline, and material conversion terms before the paid subscription begins. If the trial is not cancelled before the disclosed cancellation deadline, recurring billing will begin at the end of the trial period and will continue according to the selected billing interval until cancelled. If a free trial does not require a payment method or does not expressly state that it will convert to a paid subscription, the trial will not automatically convert to a paid subscription. ### 7. Seat Limits and Workspace Limits FieldDoc organizes Users by Organizations. Organizations may use workspaces, permissions, collaboration tools, Pacts, Programs, or other platform features to organize Users and records. Seat limits and workspace limits depend on the Organization’s subscription tier, Application access, platform configuration, Program participation, and applicable Subscription Documentation. Unless otherwise stated in the applicable Subscription Documentation or written agreement: Basic Organizations receive up to 3 User seats and 1 workspace. Standard Organizations receive up to 10 User seats and 3 workspaces. Aggregator seat limits, workspace limits, Program configuration, and collaboration structures are customized in the applicable Order Form, Statement of Work, grant agreement, Program agreement, or other written arrangement. The Commons may offer additional seats, workspaces, storage, Program configuration, Application access, or usage capacity for an additional fee. ### 8. Usage Limits Usage limits may apply to seats, workspaces, records, Activities, Pacts, Programs, Pact Opportunities, files, storage, exports, API calls, integrations, Models, dashboards, support requests, or other platform functions. Usage limits are described in the applicable Subscription Documentation, plan chart, Order Form, Statement of Work, support plan, Program agreement, Application-Specific Terms, or other written arrangement. If a Customer exceeds applicable usage limits, The Commons may notify the Customer, require the Customer to reduce usage, require an upgrade, charge additional fees, limit access to certain features, or suspend the affected feature or Service until the issue is resolved. ### 9. Application Access and Available Features FieldDoc may include multiple Applications, modules, tools, workflows, integrations, Models, dashboards, APIs, and services. Not all Applications or features are included in every subscription tier. Application access, available features, Models, exports, dashboards, integrations, Program tools, support levels, and service commitments may vary by subscription tier and may be described in the applicable plan chart, Subscription Documentation, Order Form, Statement of Work, support plan, Program agreement, Application-Specific Terms, or other written arrangement. The Commons may add, modify, rename, replace, suspend, or discontinue features, Applications, integrations, Models, dashboards, APIs, workflows, or services from time to time, subject to any specific commitments in an applicable written agreement. ### 10. Support Level The Commons may provide general support, documentation, webinars, help resources, community guidance, release notes, or other assistance to Users and Organizations. Unless expressly included in Subscription Documentation, an Order Form, Statement of Work, support plan, Master Service Agreement, grant agreement, Program agreement, or other written arrangement, The Commons does not guarantee response times, individualized assistance, data cleanup, configuration support, reporting assistance, training, custom exports, custom dashboards, or other professional services. Support provided by The Commons does not transfer responsibility for data accuracy, Program compliance, legal compliance, record retention, reporting deadlines, or Organization data governance from Users, Organizations, Customers, or Program Managers to The Commons. ### 11. Add-On Services The Commons may provide add-on services, including onboarding, configuration, data migration, training, technical assistance, GIS support, geospatial analysis, reporting, dashboard development, integration support, data cleanup, Program setup, model configuration, workflow design, user support, strategic advising, Digital Services, Data Concierge, Conservation Concierge, or other digital, data, or advisory services. Add-on services are not included in general FieldDoc access unless expressly stated in the applicable Subscription Documentation or written agreement. Deliverables, timelines, assumptions, Customer responsibilities, fees, acceptance criteria, support obligations, and service boundaries for add-on services should be described in the applicable Statement of Work, Order Form, support plan, grant agreement, Program agreement, or other written arrangement. ### 12. Data Retention FieldDoc data retention may depend on subscription tier, Program participation, Pact status, Application access, payment status, account status, Organization status, written agreements, legal obligations, backup practices, audit needs, security requirements, and Program requirements. The Commons may retain, archive, restrict, delete, or make available data following nonpayment, expiration, non-renewal, downgrade, cancellation, suspension, termination, closure of a Pact Opportunity, end of a Program, or end of trial, pilot, evaluation, grant-funded, sponsored, or no-cost access as described in the FieldDoc Terms of Service, this Subscription Documentation, Program requirements, or applicable written agreements. Users and Organizations are responsible for exporting, submitting, archiving, correcting, or otherwise preserving records they wish to retain. #### 12.1 Basic Tier Retention Basic Tier retention is generally tied to the status of the Organization’s Pacts, Program participation, and related FieldDoc workflows. Activity records linked to Pacts that are submitted, awarded, active, pending, completed, retained, or otherwise authorized for continued Program-related access may remain available in FieldDoc for longer periods to support Program administration, reporting, audit, compliance, legal obligations, historical records, Program Manager requirements, or The Commons’ legitimate operational needs. Draft, inactive, non-awarded, non-submitted, de-linked, abandoned, or non-Program-associated records created under Basic access may be archived, restricted, or deleted after 12 months of inactivity or 12 months after the relevant application window, Pact Opportunity, review period, or reporting period closes, unless a Program requirement, written agreement, or The Commons’ operational needs provide otherwise. Basic Organizations should export or otherwise preserve records they wish to retain outside FieldDoc, especially records not linked to an active, submitted, awarded, completed, retained, or otherwise Program-associated Pact. #### 12.2 Standard Tier Retention During an active Standard subscription, the Organization’s records will generally remain available within the limits of the subscription, platform functionality, applicable Terms, and any applicable written agreement. If a Standard subscription expires, is cancelled, is not renewed, is suspended for nonpayment, or is downgraded to Basic, the Organization may lose access to Standard features, Applications, exports, Models, dashboards, additional workspaces, additional seats, or other paid functionality. Unless otherwise stated in a written agreement, The Commons may archive, restrict, or delete data that exceeds Basic Tier limits or is not otherwise eligible for continued access after two months from the effective date of expiration, non-renewal, cancellation, downgrade, or suspension. The Commons recommends that Organizations export records they wish to retain before cancelling, downgrading, or allowing a Standard subscription to expire. #### 12.3 Aggregator Tier Retention Aggregator subscriptions may involve Program-level data, Pact Opportunities, Programmatic Metrics, Models, dashboards, reports, exports, and Activity data shared by participating Organizations. If an Aggregator subscription expires, is cancelled, is not renewed, is suspended, or is terminated, The Commons may limit, downgrade, archive, restrict, or remove access to Aggregator features, Program Manager tools, Program dashboards, Program configuration, exports, reports, Models, Pact Opportunities, support, and related Services. Termination or expiration of an Aggregator subscription does not automatically transfer ownership of underlying Activity records from participating Organizations and does not automatically delete Organization-owned records that participating Organizations are otherwise entitled to retain under their own subscription tier, Program relationship, Pact status, or written agreement. Program-level records, Aggregator-created configuration, dashboards, reports, exports, Program workspaces, and Program-associated data may be archived, restricted, or deleted after two months from the effective date of expiration, non-renewal, cancellation, downgrade, or termination unless a written agreement, legal obligation, Program requirement, or The Commons’ operational needs provide otherwise. Where feasible, The Commons may provide notice to the Aggregator Customer and affected Organization Owners or Program participants before materially reducing access to Program-associated data. Customers, Program Managers, Users, and Organizations remain responsible for exporting or preserving records they wish to retain. ### 13. Renewal Terms Unless otherwise stated in the applicable Subscription Documentation, subscriptions are for the term stated in the Order Form, invoice, online subscription selection, Statement of Work, grant agreement, Program agreement, or other written subscription documentation. Self-serve monthly and annual Standard subscriptions automatically renew according to the billing interval selected by the Customer unless cancelled before the next renewal date. Aggregator subscriptions, custom subscriptions, enterprise arrangements, grant-funded access, sponsored access, and other non-standard arrangements renew only as stated in the applicable Order Form, Statement of Work, grant agreement, Program agreement, invoice, or other written agreement. A subscription may be renewed by online renewal, continued recurring payment, written agreement, execution of a renewal Order Form or Statement of Work, payment of a renewal invoice, or another renewal method approved by The Commons. Renewal terms, fees, Application access, features, seat limits, usage limits, support levels, data retention periods, and service commitments may differ from the prior subscription term and will be described in the applicable renewal documentation. If a subscription expires, is not renewed, is cancelled, or if undisputed renewal fees are not paid when due, The Commons may suspend, limit, downgrade, or terminate access to paid features, Applications, support, professional services, or other subscription-based Services, subject to any notice, cure period, grace period, or different terms stated in the applicable Subscription Documentation or written agreement. ### 14. Cancellation or End of Access Customer may cancel a self-serve subscription through the payment portal where available or by submitting a written request to The Commons. Unless the applicable Subscription Documentation states otherwise, cancellation will take effect at the end of the current subscription term. Customer will continue to have access to the applicable subscription features through the end of the paid term, provided the account remains in good standing and Customer continues to comply with the FieldDoc Terms of Service and any applicable Subscription Documentation or written agreement. Cancellation does not cancel fees already owed for the current subscription term. Unless the applicable Subscription Documentation states otherwise or applicable law requires otherwise, prepaid subscription fees are not refundable and cancellation does not result in a prorated refund. Some FieldDoc access may be provided through a grant, Program, sponsor, pilot, evaluation, trial, beta, demonstration, or other third-party arrangement. Unless otherwise stated in the applicable Subscription Documentation, Program agreement, grant agreement, or other written agreement, such access may end when the grant, Program, sponsorship, pilot, evaluation period, trial period, beta period, demonstration period, or third-party arrangement ends. After a subscription, sponsored access arrangement, trial, pilot, evaluation period, grant-funded access, or no-cost access period ends, The Commons may limit, downgrade, archive, restrict, or remove access to paid features, Applications, support, professional services, Program tools, workspaces, exports, dashboards, Models, integrations, or other Services. Where feasible, The Commons will provide reasonable notice before materially reducing access. Customer, Users, and Organizations are responsible for exporting or preserving records they wish to retain before access ends, subject to FieldDoc’s data retention, Program, Pact, legal, backup, security, and compliance obligations. ### 15. Service-Specific Requirements Certain Applications, Programs, Models, integrations, dashboards, APIs, exports, support plans, professional services, or add-on services may be subject to additional requirements, limits, notices, documentation, or terms. Service-specific requirements may address eligibility, configuration, onboarding, data formats, Activity Types, Programmatic Metrics, Models, reporting deadlines, review processes, privacy expectations, exports, usage limits, support boundaries, data retention, or post-window data management. Service-specific requirements may be described in Application-Specific Terms, Subscription Documentation, a Statement of Work, Order Form, grant agreement, Program agreement, support plan, product description, help documentation, or other written documentation made available by The Commons. Service-specific requirements supplement this Subscription Documentation and the FieldDoc Terms of Service but do not override a signed written agreement executed by The Commons unless that agreement expressly states otherwise. ### 16. Contact Questions about FieldDoc subscriptions, billing, plan limits, renewals, cancellations, or add-on services may be directed to: # Billing Page: Upgrades and Management Organizations that want to upgrade to a Standard plan can either reach out to to get started, or upgrade themselves through the FieldDoc app. Organizations that want to upgrade to Aggregator must reach out to . Plans are managed at the Organization level, so all users within your organization have the same plan. {% @arcade/embed flowId="P4zmdypI9ubfWamHVNXS" url="" %} ## Sign up for Basic When you create your FieldDoc account, you are put on the Basic plan. ## Upgrade to Standard Log in to your existing account. If you are listed as the "Owner" of an organization, you can upgrade your account. In the bottom left hand corner, click the ellipses next to your user name. Then select your organization. Scroll down to the **Billing** section. Decide if you'd like to pay monthly or save 20% and pay annually. Once you have chosen the frequency, click the button "**Upgrade to standard**" You can also write to . We’re happy to create an account or upgrade a plan for you. We can also assist you in choosing add-on services that we can provide. If you are not listed as the owner but you would like to upgrade, please reach out to our team. ## Sign up for Aggregator Please get in touch to sign up for an aggregator account. # Master Services Agreement Last updated: June 13, 2026 This Agreement becomes effective on the earliest date that Customer does any of the following: accepts this Agreement online, signs an Order Form or Statement of Work that references this Agreement, or creates a FieldDoc subscription. That date is the “Effective Date.” This Agreement governs Customer’s access to and use of the FieldDoc Platform and related services, including any Applications, subscriptions, modules, tools, workspaces, support services, professional services, data services, integrations, and other services made available to Customer under this Agreement or applicable Subscription Documentation. “Customer” means the organization, entity, or individual entering into this Agreement, including any individual users, employees, contractors, representatives, collaborators, affiliates, or other persons whom Customer authorizes or permits to access or use the FieldDoc Platform or related services under Customer’s account or subscription (“Authorized Users”). Customer is responsible for all access to and use of the FieldDoc Platform and related services by its Authorized Users and for their compliance with this Agreement. By creating, purchasing, accepting, or using a FieldDoc account or subscription on behalf of Customer, the individual completing the sign-up, order, or acceptance process represents and warrants that they have authority to bind Customer to this Agreement. If the individual does not have such authority, they may not create, accept, or use the account or subscription on behalf of Customer. ### 1. Definitions For purposes of this Agreement: “**Applications**” means the individual applications, modules, products, or service offerings made available through or in connection with the FieldDoc Platform, including FieldDoc Data Manager, Groundwork, and any other FieldDoc applications, modules, or products that The Commons may make available from time to time. “**Authorized Users**” means Customer’s employees, contractors, consultants, agents, collaborators, or other individuals who are authorized by Customer to access the Services under Customer’s account or workspace. “**Customer Data**” means all data, content, records, files, geospatial information, activity information, project information, metrics, reports, attachments, and other materials submitted to, uploaded to, imported into, or generated through the Services by or on behalf of Customer or its Authorized Users. Customer Data does not include FieldDoc’s underlying software, platform technology, system analytics, aggregated or de-identified usage information, or pre-existing FieldDoc intellectual property. “**Documentation**” means FieldDoc’s user guides, help materials, technical documentation, training materials, and service descriptions made available to Customers. “**FieldDoc Platform**” means the FieldDoc technology platform owned and operated by The Commons, including its applications, modules, tools, interfaces, databases, workflows, documentation, APIs, integrations, and related technology. “**Order Form**” means an ordering document, subscription form, invoice, online checkout process, statement of work, or similar document that identifies the Services, fees, subscription package, term, usage limits, support level, or other applicable terms. “**Services**” means the FieldDoc Platform, Applications, software, documentation, support, hosting, subscription services, professional services, data services, integrations, and related services provided by The Commons or FieldDoc under this Agreement or applicable Subscription Documentation. “**Subscription Documentation**” means any Order Form, online subscription selection, checkout page, pricing page, invoice, Statement of Work, support plan, grant agreement, program agreement, or other written documentation that describes Customer’s subscription tier, fees, features, services, usage limits, support level, or other commercial terms. “**Subscription Term**” means the period during which Customer is authorized to access the applicable Services or Applications, as stated in the applicable Subscription Documentation. If no term is stated, the Subscription Term will begin on the Effective Date or the date the applicable Services are made available to Customer and will continue for one year unless terminated earlier in accordance with this Agreement. “**Third-Party Services**” means third-party data sources, software, applications, APIs, models, mapping services, hosting providers, integrations, or other services that interoperate with or are used in connection with the Services. “**Workspace**” means a FieldDoc environment associated with an organization or collaborative relationship through which Customer or its Authorized Users may manage, view, share, or access records. ### 2. Scope of Services The Commons provides the FieldDoc Platform to allow organizations to document, manage, track, analyze, share, and report nature-based, conservation, restoration, water quality, environmental, geospatial, and related programmatic activities. The FieldDoc Platform may include multiple Applications, including FieldDoc Data Manager, Groundwork, and other applications, modules, tools, or services made available by The Commons from time to time. Depending on Customer’s subscription, purchase, workspace configuration, permissions, and applicable Subscription Documentation, the Services may include tools for activity tracking, project and portfolio management, funder reporting, environmental impact estimation, geospatial analysis, mapping, collaboration, dashboards, data imports and exports, data management, workflow support, and related services. Customer’s access to specific Applications, features, usage limits, support levels, data retention periods, professional services, and other service-specific terms will be determined by the applicable Subscription Documentation. ### 3. Access and Use of the Services #### 3.1 Access Rights Subject to this Agreement and applicable Subscription Documentation, FieldDoc grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right to access and use the Services, including the Applications made available to Customer, during the applicable Subscription Term for Customer’s internal programmatic, reporting, collaboration, grant management, environmental analysis, stakeholder communication, data management, and related organizational purposes. #### 3.2 Authorized Users Customer is responsible for identifying, authorizing, and managing its Authorized Users. Customer is responsible for all activity that occurs under Customer-controlled accounts, workspaces, credentials, and user permissions, except to the extent caused by FieldDoc’s breach of this Agreement or failure to maintain reasonable security measures. Customer will ensure that all Authorized Users comply with this Agreement, FieldDoc’s Terms of Service, Privacy Statement, and applicable Documentation. #### 3.3 Account Security Customer is responsible for maintaining the confidentiality of user credentials and for promptly notifying FieldDoc of any known or suspected unauthorized access to Customer’s account, workspace, or Customer Data. #### 3.4 Use Restrictions Customer and its Authorized Users may not: a. Use the Services for any unlawful, fraudulent, harmful, or unauthorized purpose;\ b. Use the Services outside the scope of this Agreement, an applicable Order Form, Documentation, subscription package, workspace permission, or other written authorization from FieldDoc;\ c. Interfere with or disrupt the integrity, performance, or security of the Services;\ d. Attempt to gain unauthorized access to the Services, other users’ accounts, other organizations’ data, or portions of the Services Customer is not authorized to access;\ e. Upload malicious code, malware, or harmful content;\ f. Reverse engineer, decompile, copy, modify, or create derivative works of the Services except as permitted by law;\ g. Circumvent access controls, usage limits, subscription limits, workspace permissions, or security features;\ h. Use the Services to violate the rights of any third party;\ i. Misrepresent FieldDoc outputs, modeled estimates, reports, or analytics as verified outcomes unless independently validated;\ j. Use the Services in a manner that exceeds applicable subscription limits without authorization; or\ k. Permit or enable any third party to access or use the Services except as expressly authorized under this Agreement or an applicable Order Form. ### 4. Subscription Fees, Payment, and Usage Limits #### 4.1 Fees Customer will pay all applicable fees described in the applicable Subscription Documentation. Fees may be based on Applications selected, subscription package, user access levels, workspace access, organization tier, data storage, support level, professional services, integrations, custom configuration, reporting services, data services, modules, add-ons, or other features, services, or usage selected by Customer or authorized for Customer’s account. #### 4.2 Invoicing and Payment Unless otherwise stated in an Order Form, invoices are due within 30 days of the invoice date. Fees are non-refundable except as expressly stated in this Agreement or an applicable Order Form. #### 4.3 Taxes Customer is responsible for all applicable taxes, duties, assessments, or governmental charges associated with Customer’s purchase or use of the Services, excluding taxes based on FieldDoc’s income. #### 4.4 Usage Limits The Services may be subject to usage limits, including limits on number of users, data storage, workspaces, activities, projects, pacts, portfolios, integrations, support hours, or other subscription features. Applicable limits will be described in the Subscription Documentation. If Customer exceeds applicable usage limits, FieldDoc may notify Customer and work in good faith to adjust the subscription package, reduce usage, or apply additional fees. FieldDoc will not apply additional fees without notice unless otherwise stated in Subscription Documentation. #### 4.5 Nonpayment If Customer fails to pay undisputed amounts when due, FieldDoc may provide written notice of nonpayment. If payment remains overdue after 30 days from notice, FieldDoc may suspend or limit access to the Services until payment is received. FieldDoc will not be responsible for any loss, delay, or inability to access the Services resulting from suspension for nonpayment. ### 5. Customer Responsibilities #### 5.1 Compliance with Laws Customer will use the Services in compliance with all applicable laws, regulations, grant requirements, contractual obligations, privacy laws, intellectual property rights, and environmental reporting requirements. #### 5.2 Data Accuracy and Legality Customer is responsible for the accuracy, completeness, integrity, legality, and appropriateness of Customer Data. This includes correct entry and maintenance of restoration activities, geospatial information, environmental metrics, monitoring data, implementation status, modeled inputs, and related records. FieldDoc does not independently verify Customer Data unless expressly agreed in an Order Form or Statement of Work. #### 5.3 Sensitive Data Customer is responsible for determining whether Customer Data includes sensitive, confidential, restricted, proprietary, legally protected, or location-sensitive information. This may include private landowner information, threatened or endangered species locations, cultural resources, tribal information, protected ecological sites, acquisition parcels, monitoring locations, or other information not intended for public release. Customer is responsible for configuring sharing settings and access permissions appropriately. FieldDoc will use reasonable safeguards to protect Customer Data, but Customer should not make sensitive data publicly available through the Services unless authorized. #### 5.4 Customer Instructions Customer is responsible for the decisions it makes using the Services, including how it interprets, shares, reports, publishes, or relies on Customer Data, modeled outputs, maps, reports, dashboards, exports, or analytics. ### 6. FieldDoc Responsibilities #### 6.1 Service Availability FieldDoc will use commercially reasonable efforts to make the Services available on a 24/7 basis, except for planned downtime, emergency maintenance, outages caused by Third-Party Services, force majeure events, Customer misuse, or circumstances beyond FieldDoc’s reasonable control. FieldDoc may perform maintenance from time to time and will use reasonable efforts to provide advance notice of planned downtime when practical. #### 6.2 Support Services FieldDoc will provide standard support as described in the applicable Subscription Documentation. Unless otherwise agreed in writing, support does not include custom consulting, data entry, data cleanup, GIS analysis, custom reporting, model interpretation, training beyond provision of standard materials, grant reporting services, system integration work, or professional services. Additional support, onboarding, configuration, data migration, training, analysis, or professional services may be provided under an Order Form, Statement of Work, grant agreement, or service-level agreement. #### 6.3 Security Measures FieldDoc will maintain reasonable administrative, technical, and organizational safeguards designed to protect the integrity, confidentiality, and availability of Customer Data. Such safeguards may include access controls, administrative controls, secure hosting practices, backup procedures, monitoring, vulnerability management, and other measures appropriate to the nature of the Services. #### 6.4 Security Incidents FieldDoc will notify Customer without undue delay after confirming a security incident that materially affects Customer Data. FieldDoc will provide information reasonably necessary for Customer to assess the incident, subject to legal, security, and confidentiality limitations. FieldDoc is not responsible for security incidents resulting from Customer’s failure to manage user access, credentials, sharing settings, integrations, or Customer-controlled systems, except to the extent caused by FieldDoc’s breach of this Agreement. ### 7. Customer Data and Data Use #### 7.1 Ownership of Customer Data Customer retains all rights, title, and interest in Customer Data. FieldDoc does not claim ownership of Customer Data. #### 7.2 License to Provide the Services Customer grants FieldDoc a limited, non-exclusive, worldwide license to host, copy, process, transmit, store, display, analyze, map, transform, and otherwise use Customer Data as necessary to provide, maintain, secure, support, improve, and operate the Services. This includes use of Customer Data to generate reports, maps, modeled outputs, dashboards, exports, analytics, summaries, and other features requested, configured, or enabled by Customer or its Authorized Users. #### 7.3 Data Sharing Through the Services Customer acknowledges that the Services are designed to support collaboration, reporting, and data sharing among organizations, funders, programs, technical service providers, and other stakeholders. Customer controls whether and how Customer Data is shared through available Service features, including user permissions, workspaces, pacts, portfolios, reports, maps, dashboards, public pages, exports, APIs, integrations, and other sharing tools. FieldDoc is not responsible for disclosures resulting from Customer’s configuration of sharing settings, user permissions, public pages, exports, or authorized integrations. #### 7.4 Sharing with Funders, Programs, and Collaborators If Customer uses the Services in connection with a funder, grant program, collaborative initiative, reporting requirement, or shared workspace, Customer authorizes FieldDoc to make Customer Data available to the relevant funder, program administrator, collaborator, or authorized party as configured in the Services or described in the applicable Order Form, program terms, or Customer instructions. #### 7.5 Aggregated and De-Identified Data FieldDoc may use aggregated or de-identified data derived from use of the Services for product improvement, research, analytics, benchmarking, sector-level reporting, platform performance, and public impact summaries, provided such data does not identify Customer or disclose Customer’s Confidential Information without authorization. #### 7.6 Usage Data FieldDoc may collect and use technical, diagnostic, performance, and usage information relating to Customer’s use of the Services to operate, secure, troubleshoot, improve, and support the Services. #### 7.7 Data Export During the Subscription Term and for 60 days after termination or expiration, Customer may request export of Customer Data in a commercially reasonable format, subject to technical limitations, legal requirements, and any applicable fees for custom export or professional services. #### 7.8 Data Retention, Subscription Lapse, and Deletion Upon termination, expiration, non-renewal, or lapse of Customer’s subscription, FieldDoc may retain Customer Data for a limited period to allow Customer to renew or reactivate its subscription without loss of data. Unless otherwise stated in an Order Form or required by law, contract, funder or program obligation, backup procedure, or Customer instruction, FieldDoc will retain inactive Customer Data for up to 6 months after termination, expiration, non-renewal, or subscription lapse. During this inactive retention period, Customer may not have access to the Services or Customer Data unless Customer renews, reactivates, or otherwise enters into a written arrangement with FieldDoc. FieldDoc may also retain Customer Data as necessary to comply with legal obligations, resolve disputes, maintain backups, support grant or program reporting obligations, preserve historical records shared by Customer with funders, programs, or collaborators, prevent data loss, comply with audit or recordkeeping requirements, or follow FieldDoc’s standard retention practices. Upon Customer’s written request, FieldDoc will delete or anonymize Customer Data in accordance with its standard retention practices, unless retention is required by law, contract, backup procedures, funder or program obligations, shared reporting obligations, audit requirements, or Customer instruction. Deleted Customer Data may continue to exist in backups or archival copies for a limited period, consistent with FieldDoc’s backup and disaster recovery practices. #### 7.9 Backups Customer acknowledges that deleted Customer Data may continue to exist in backups or archival copies, consistent with FieldDoc’s backup and disaster recovery practices. ### 8. Environmental Models, Estimates, and Decision-Support Outputs Customer acknowledges that environmental impact estimates, modeled outcomes, load reductions, greenhouse gas estimates, maps, analytics, metrics, reports, dashboards, and other outputs generated through the Services are based on Customer Data, third-party data, model assumptions, selected methodologies, geospatial inputs, and other variables that may change over time. Such outputs are provided for planning, reporting, prioritization, communication, and decision-support purposes only. FieldDoc does not guarantee that outputs are complete, accurate, suitable for regulatory compliance, sufficient for funding eligibility, or reflective of verified environmental outcomes unless expressly agreed in writing. Customer is responsible for reviewing, validating, and determining the appropriate use of any FieldDoc-generated outputs before relying on them for reporting, compliance, funding, public communications, policy advocacy, or decision-making. ### 9. Third-Party Services, Data, and Integrations The Services may interoperate with or incorporate Third-Party Services, including third-party data sources, GIS layers, mapping tools, models, APIs, hosting providers, software platforms, and integrations. Customer’s use of Third-Party Services may be subject to separate agreements, terms and conditions. FieldDoc is not responsible for Third-Party Services, third-party data, or outputs generated by third-party systems, except to the extent expressly stated in an Order Form. FieldDoc does not warrant the accuracy, availability, completeness, or continued operation of Third-Party Services or third-party data. ### 10. Intellectual Property Rights #### 10.1 FieldDoc Intellectual Property FieldDoc retains all rights, title, and interest in and to the Services, including all underlying technology, software, code, interfaces, workflows, models, templates, designs, Documentation, know-how, improvements, modifications, and related intellectual property. No rights are granted to Customer except as expressly stated in this Agreement. #### 10.2 Customer Data Customer retains all rights to Customer Data, subject to the licenses and permissions granted to FieldDoc under this Agreement. #### 10.3 Feedback If Customer or its Authorized Users provide suggestions, ideas, enhancement requests, recommendations, corrections, or other feedback regarding the Services, FieldDoc may use such feedback without restriction or obligation, provided that FieldDoc does not disclose Customer’s Confidential Information in doing so. #### 10.4 Reports, Outputs, and Attribution Subject to FieldDoc’s rights in the Services and underlying technology, Customer may use reports, maps, exports, dashboards, modeled results, and other outputs generated from Customer Data for Customer’s authorized organizational purposes. Customer may not remove, obscure, or alter any proprietary notices, attribution statements, disclaimers, legends, source notes, third-party data credits, or other required notices included in or generated with the Services, unless expressly authorized by FieldDoc in writing. When Customer publicly shares or publishes maps, dashboards, reports, exports, modeled results, or other outputs generated through the Services, Customer agrees to include reasonable attribution to FieldDoc, The Commons, and applicable third-party data or service providers where attribution is displayed in the Services, required by third-party terms, or reasonably requested by FieldDoc. FieldDoc may provide required or recommended attribution language in the Documentation, applicable Order Form, map interface, export, report template, or other Service materials. Customer is responsible for preserving attribution required by Third-Party Services, including mapping, imagery, basemap, geospatial, model, or data providers. ### 11. Confidentiality #### 11.1 Confidential Information “Confidential Information” means non-public information disclosed by one party to the other that is marked confidential or that reasonably should be understood to be confidential given the nature of the information and circumstances of disclosure. Confidential Information may include business information, technical data, trade secrets, software information, security information, financial information, reports, analyses, documentation, Customer Data, and non-public information generated through the Services. #### 11.2 Exclusions Confidential Information does not include information that: a. Is or becomes publicly available without breach of this Agreement;\ b. Was known to the receiving party before disclosure without confidentiality obligations;\ c. Is independently developed by the receiving party without use of the disclosing party’s Confidential Information; or\ d. Is lawfully obtained from a third party without confidentiality obligations. #### 11.3 Obligations Each party will use the other party’s Confidential Information only to perform or receive Services under this Agreement. Each party will protect the other party’s Confidential Information using at least reasonable care and will not disclose it except to employees, contractors, advisors, service providers, or agents who need access and are bound by confidentiality obligations. #### 11.4 Required Disclosure A receiving party may disclose Confidential Information if required by law, subpoena, court order, public records obligation, or governmental authority, provided that the receiving party gives reasonable notice to the disclosing party when legally permitted. #### 11.5 Public or Shared Data Confidentiality obligations do not restrict use or disclosure of Customer Data that Customer or its Authorized Users intentionally make public or share through the Services with funders, collaborators, public pages, dashboards, reports, exports, or integrations. #### 11.6 Duration Confidentiality obligations survive termination of this Agreement for three years, except that trade secrets remain protected for as long as they qualify as trade secrets under applicable law. ### 12. Privacy FieldDoc’s collection and use of personal information is described in its Privacy Statement, available at \[insert link]. Customer is responsible for ensuring that it has provided all required notices and obtained all required rights, consents, permissions, and authorizations necessary for FieldDoc to process personal information and Customer Data in connection with the Services. If required by applicable law or Customer’s procurement requirements, the parties may enter into a separate Data Processing Addendum. ### 13. Warranties and Disclaimers #### 13.1 Limited Warranty FieldDoc warrants that the Services will materially perform in accordance with applicable Documentation under normal use. Customer’s sole and exclusive remedy for breach of this warranty is for FieldDoc to use commercially reasonable efforts to correct the nonconformity. #### 13.2 Disclaimer Except as expressly provided in this Agreement, the Services are provided “as is” and “as available.” FieldDoc makes no warranties, express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, uninterrupted operation, or error-free performance. FieldDoc does not warrant that the Services will meet Customer’s requirements, that all errors will be corrected, or that the Services will be available without interruption. ### 14. Indemnification #### 14.1 Customer Indemnification Customer will defend, indemnify, and hold harmless FieldDoc, The Commons, and their officers, directors, employees, agents, and representatives from and against any third-party claims, damages, liabilities, costs, and expenses, including reasonable attorneys’ fees, arising from: a. Customer Data;\ b. Customer’s misuse of the Services;\ c. Customer’s violation of applicable law;\ d. Customer’s infringement or misappropriation of third-party rights;\ e. Customer’s unauthorized disclosure or sharing of data through the Services; or\ f. Customer’s reliance on or publication of FieldDoc outputs in a manner inconsistent with this Agreement. #### 14.2 FieldDoc Indemnification FieldDoc will defend Customer against third-party claims alleging that the Services, as provided by FieldDoc and used in accordance with this Agreement, infringe a third party’s intellectual property rights, and will pay damages finally awarded or settlements approved by FieldDoc. FieldDoc will have no obligation for claims arising from: a. Customer Data;\ b. Customer’s misuse of the Services;\ c. Modifications not made by FieldDoc;\ d. Combination of the Services with products, services, or data not provided by FieldDoc;\ e. Third-Party Services; or\ f. Use of the Services after FieldDoc provides notice to stop due to a claim. If the Services become or are likely to become subject to an infringement claim, FieldDoc may, at its option, procure the right for Customer to continue using the Services, modify the Services, replace the Services, or terminate the affected subscription and provide a prorated refund of prepaid unused fees. #### 14.3 Indemnification Process The indemnified party must promptly notify the indemnifying party of the claim, provide reasonable cooperation, and allow the indemnifying party to control the defense and settlement, provided that no settlement may impose liability or obligations on the indemnified party without its consent. ### 15. Limitation of Liability To the maximum extent permitted by law, FieldDoc’s total liability for all claims arising out of or relating to this Agreement will not exceed the fees paid by Customer for the Services during the twelve-month period preceding the event giving rise to the claim. Notwithstanding the foregoing, FieldDoc’s total liability for claims arising from FieldDoc’s breach of its confidentiality obligations, FieldDoc’s data security obligations, or FieldDoc’s indemnification obligations, if any, will not exceed two times the fees paid by Customer for the Services during the twelve-month period preceding the event giving rise to the claim. FieldDoc will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, including lost profits, lost revenue, loss of goodwill, loss of data, business interruption, or costs of substitute services, even if advised of the possibility of such damages. The limitations and exclusions in this Section do not apply to Customer’s payment obligations, either party’s misuse or infringement of the other party’s intellectual property rights, either party’s fraud, gross negligence, or willful misconduct, or any liability that cannot be limited under applicable law. ### 16. Suspension FieldDoc may suspend or limit Customer’s or any Authorized User’s access to the Services if FieldDoc reasonably determines that: a. Customer has failed to pay undisputed amounts when due;\ b. Customer or its Authorized Users pose a security, legal, operational, or reputational risk;\ c. Customer’s or any Authorized User’s use of the Services may disrupt the Services or other users;\ d. Customer or any Authorized User is using the Services unlawfully or in violation of this Agreement, FieldDoc’s Terms of Service, Privacy Statement, applicable Documentation, an Order Form, or any applicable law;\ e. Suspension is required by law, court order, governmental authority, or a Third-Party Service provider;\ f. Customer exceeds usage limits and fails to address the issue after notice; or\ g. Suspension is necessary to prevent unauthorized access, protect Customer Data, protect other users or organizations, or maintain the security or integrity of the Services. Where reasonable under the circumstances, FieldDoc will provide notice and an opportunity to resolve before suspension. FieldDoc may suspend access immediately without prior notice if it reasonably believes immediate action is necessary to prevent harm, unauthorized access, security risk, legal exposure, disruption of the Services, or violation of third-party obligations. Suspension will be limited in scope and duration as reasonably necessary to address the issue. FieldDoc may suspend access for an individual Authorized User, a workspace, specific functionality, or Customer’s account, depending on the nature of the issue. ### 17. Term and Termination #### 17.1 Term This Agreement begins on the Effective Date and continues for the Subscription Term unless terminated earlier in accordance with this Agreement. Termination or expiration of one Subscription Documentation, Application, module, or Service does not necessarily terminate this Agreement or Customer’s right to access other active Services, unless the applicable Subscription Documentation states otherwise or continued access is not technically or commercially feasible. #### 17.2 Renewal Subscriptions renew only as stated in the applicable Subscription Documentation. If the Subscription Documentation does not address renewal, renewal requires mutual written agreement or a new Subscription Documentation. #### 17.3 Termination for Cause Either party may terminate this Agreement or an applicable Order Form for cause upon written notice if the other party materially breaches this Agreement and fails to cure the breach within thirty days after receiving notice. #### 17.4 Termination for Convenience Customer may terminate this Agreement for convenience at any time, subject to payment of all outstanding fees. Unless otherwise stated in Subscription Documentation, prepaid fees are non-refundable. #### 17.5 Termination by FieldDoc FieldDoc may terminate this Agreement or Customer’s access to the Services if Customer materially violates this Agreement, fails to pay undisputed amounts after notice and opportunity to cure, misuses the Services, creates a security or legal risk, or if continued provision of the Services becomes unlawful or commercially impracticable. #### 17.6 Effect of Termination Upon termination or expiration, Customer’s right to access the Services will cease, and Customer must discontinue use of the Services. FieldDoc may disable Customer’s access, subject to any data export rights described in this Agreement. #### 17.7 Survival Sections relating to fees owed, Customer Data, data retention, confidentiality, intellectual property, disclaimers, indemnification, limitation of liability, termination effects, governing law, and any provisions that by their nature should survive will survive termination of this Agreement. ### 18. Professional Services FieldDoc and The Commons may provide professional, technical, advisory, or implementation services in connection with the Services, including services offered as Digital Services, Data Concierge, Conservation Concierge, or other related service offerings. These services may include onboarding, platform configuration, data migration, data cleanup, data structuring, training, technical assistance, GIS support, geospatial analysis, reporting support, dashboard development, workflow design, integration support, data management planning, conservation program support, restoration tracking assistance, impact analysis, funder reporting support, and other advisory or implementation services. Unless expressly included in an applicable Order Form, Statement of Work, grant agreement, or other written arrangement, professional, digital, data concierge, conservation concierge, or advisory services are not included in standard subscription fees. The scope, deliverables, timelines, assumptions, dependencies, Customer responsibilities, fees, review process, and acceptance criteria for such services will be described in the applicable Order Form, Statement of Work, grant agreement, or written arrangement. Customer acknowledges that professional, digital, data concierge, conservation concierge, and advisory services may depend on the completeness, accuracy, timeliness, and availability of Customer Data, third-party data, Customer personnel, Customer systems, funder requirements, and other information provided by or on behalf of Customer. Unless expressly agreed in writing, The Commons does not guarantee that professional services, advisory services, analyses, reports, dashboards, recommendations, modeled outputs, or conservation planning support will result in specific funding decisions, regulatory approvals, verified environmental outcomes, compliance determinations, or programmatic results. Any deliverables provided through professional, digital, data concierge, conservation concierge, or advisory services are stated in the applicable Statement of Work. Unless otherwise stated in a Statement of Work, Customer owns Customer Data and final deliverables created specifically for Customer, while The Commons retains ownership of pre-existing tools, templates, methods, workflows, software, documentation, know-how, code, models, and reusable materials used to provide the services. ### 19. Publicity FieldDoc may use Customer’s name, logo, or trademarks in marketing materials, case studies, press releases, or public customer lists with Customer’s prior written consent. ### 20. Notices Legal notices under this Agreement must be in writing and delivered by personal delivery, recognized overnight courier, certified mail, or email to the addresses identified in the applicable Order Form or otherwise provided by the parties. Notices to FieldDoc should be sent to: The Commons, Inc. 200 Massachusetts Ave Ste 200 Washington DC 20001 Notices are effective upon receipt, except that email notices are effective when sent if no bounce-back or delivery failure is received. ### 21. Order of Precedence If there is a conflict among documents, the following order of precedence applies unless expressly stated otherwise: 1. Applicable Order Form, Statement of Work, or other signed agreement; 2. Data Processing Addendum or Security Exhibit, if any; 3. Application-specific terms or product-specific terms, if any; 4. This Agreement; 5. FieldDoc Terms of Service; 6. FieldDoc Privacy Statement; 7. Documentation, help materials, support materials, or product descriptions. ### 22. General Provisions #### 22.1 Assignment Customer may not assign this Agreement without FieldDoc’s prior written consent, except in connection with a merger, reorganization, or sale of substantially all assets, provided that the assignee agrees to be bound by this Agreement. FieldDoc may assign this Agreement to a successor in interest, affiliate, or entity involved in a merger, reorganization, restructuring, or transfer of the FieldDoc platform or related assets. #### 22.2 Governing Law This Agreement will be governed by the laws of the District of Columbia, without regard to conflict of law principles. #### 22.3 Dispute Resolution and Venue The parties will first attempt to resolve disputes in good faith through informal discussions. If the dispute cannot be resolved, any legal action arising out of this Agreement will be brought in the state or federal courts located in the District of Columbia, and each party consents to the jurisdiction of those courts. #### 22.4 Force Majeure Neither party will be liable for delay or failure to perform due to events beyond its reasonable control, including acts of God, natural disasters, war, terrorism, labor disputes, internet or utility failures, cyberattacks, government actions, public health emergencies, failure of Third-Party Services, or other events beyond reasonable control. #### 22.5 Amendments The Commons may update this Agreement from time to time. Material updates will apply upon renewal, Customer’s acceptance of the updated Agreement, or Customer’s continued access to or use of the Services after reasonable notice of the update, unless earlier changes are required by law, security necessity, changes to Third-Party Services, or changes necessary to protect the security, integrity, or operation of the FieldDoc Platform. The Commons will provide reasonable notice of material changes, which may include notice through the FieldDoc Platform, by email, by posting the updated Agreement on its website, or by another reasonable method. For individually negotiated agreements, amendments to those portions must be in writing and agreed to by both parties unless otherwise stated in an applicable Order Form, Statement of Work, or other signed agreement. #### 22.6 Entire Agreement This Agreement constitutes the entire agreement between the parties regarding the Services and supersedes all prior or contemporaneous agreements, proposals, discussions, or understandings relating to its subject matter. #### 22.7 Severability If any provision of this Agreement is held invalid or unenforceable, the remaining provisions will remain in full force and effect. #### 22.8 Waiver A party’s failure to enforce any provision of this Agreement does not constitute a waiver of that provision or any other provision. #### 22.9 Relationship of the Parties The parties are independent contractors. Nothing in this Agreement creates a partnership, joint venture, agency, fiduciary relationship, or employment relationship between the parties. #### 22.10 No Third-Party Beneficiaries This Agreement does not create any rights or remedies for any third party unless expressly stated.
# Terms of Service Last updated: July 7, 2026 This Agreement becomes effective on the earliest date that Customer does any of the following: accepts this Agreement online, signs an Order Form or Statement of Work that references this Agreement, or creates a FieldDoc subscription. That date is the “Effective Date.” ## FieldDoc Terms of Service The FieldDoc Platform is a software platform operated by The Commons, Inc., a nonprofit organization that builds and maintains digital tools for conservation, restoration, nature-based work, environmental data stewardship, and related programmatic activities. These Terms of Service explain the rules, responsibilities, and conditions that apply when you create an account, use the FieldDoc Platform, access or use any FieldDoc Application, manage data, participate in an Organization, share data with a Program, collaborate through a workspace, use support services, or otherwise interact with FieldDoc Platform services. The FieldDoc Platform may include multiple applications, modules, tools, and services, including FieldDoc Data Manager, Groundwork, and other applications or offerings that The Commons may make available from time to time. By creating an account, using the FieldDoc Platform, accessing any Application, joining an Organization, creating or managing records, sharing data through a Pact or other platform feature, or using any FieldDoc service, you agree to these Terms. These Terms apply to individuals who create FieldDoc accounts and to Organizations whose staff, contractors, volunteers, collaborators, representatives, or other authorized users access or use the FieldDoc Platform. All individuals must create a FieldDoc account and all users must be associated with an Organization. By creating an account, joining an Organization, accessing an Application, or using the FieldDoc Platform, you represent that you are authorized to use the FieldDoc Platform in connection with your Organization and that your use complies with these Terms and any applicable agreements, subscription documentation, program requirements, or platform permissions. ### 1. FieldDoc Mission The Commons believes that better stewardship of restoration data leads to better stewardship of land and water. When activity data is organized, geospatially grounded, model-supported, and connected to the programs and people who rely on it, it becomes an asset: durable evidence for collaboration, transparency, funding, accountability, and better decisions for the natural resources and communities that depend on them. The FieldDoc Platform or any Application exists to support that stewardship by giving restoration and conservation data a place to live beyond scattered spreadsheets, static grant reports, and one-off maps. The FieldDoc Platform or any Application gives practitioners, funders, agencies, and partners a shared system of record for nature-based work: what is being done, where it is happening, who it is connected to, what impact it is expected to have, and provides pathways to move that that information across programs, reporting cycles, and decisions. The FieldDoc Platform or any Application facilitates the creation and retention of digital restoration activity records. It helps users organize implementation data, map locations, estimate environmental outcomes using accepted models, share records through program-specific workflows, and carry that information forward for reporting, planning, accountability, and promotion. The FieldDoc Platform or any Application is built for restoration practitioners, conservation organizations, funders, public agencies, technical assistance providers, and other partners working to track the location, extent, implementation, and impact of conservation, restoration, monitoring, sustainability, water quality, climate, habitat, and related nature-positive work. ### 2. Definitions Throughout these Terms, we use certain FieldDoc-specific words. These definitions explain what those words mean. “**The Commons**,” “we,” “our,” or “us” means The Commons, Inc., the nonprofit organization that owns, manages, maintains, supports, and operates the FieldDoc Platform and associated Applications. “**FieldDoc Platform**” means the FieldDoc technology platform operated by The Commons, including its applications, modules, tools, websites, interfaces, data systems, APIs, integrations, documentation, workflows, and related technology. “**Applications**” means the individual applications, modules, products, tools, or service offerings made available through or in connection with the FieldDoc Platform, including FieldDoc Data Manager, Groundwork, and any other FieldDoc applications, modules, or products that The Commons may make available from time to time. “**Services**” means the FieldDoc Platform, Applications, software, documentation, hosting, support, technical services, professional services, data services, integrations, APIs, and related services provided by The Commons or FieldDoc under these Terms, a Master Service Agreement, Subscription Documentation, or other applicable agreement. A “**User**” is an individual person who creates or uses a FieldDoc account or otherwise accesses the FieldDoc Platform or any Application. Users may include staff, contractors, volunteers, collaborators, grantees, funders, public agency staff, technical assistance providers, consultants, researchers, or other individuals with a legitimate role in using the FieldDoc Platform. An “**Authorized User**” means a User who is authorized by an Organization or Customer to access or use the FieldDoc Platform, an Application, workspace, record, Program, or other Service under that Organization’s account, subscription, permissions, or written agreement. An “**Organization**” is a real-world entity whose Users access or use the FieldDoc Platform. Organizations may include nonprofit organizations, government agencies, funders, universities, businesses, watershed groups, land trusts, technical assistance providers, community-based organizations, and other entities involved in conservation, restoration, monitoring, sustainability, environmental data management, or related work. “**Customer**” means an Organization, entity, or individual that enters into a Master Service Agreement, Order Form, Statement of Work, subscription, paid plan, program agreement, grant agreement, or other written arrangement with The Commons for access to the FieldDoc Platform, Applications, Services, support, or professional services. “**Subscription Documentation**” means any Order Form, online subscription selection, pricing page, invoice, Statement of Work, support plan, grant agreement, program agreement, data retention policy, product description, or other written documentation that describes subscription tier, fees, features, services, usage limits, support level, data retention period, Application access, or other commercial or service-specific terms. “**Application-Specific Terms**” means any additional terms, notices, rules, documentation, requirements, or conditions that apply to a particular Application, module, feature, integration, data service, or product offering. An “**Organization Owner**” is a User who is responsible for managing an Organization’s FieldDoc account, membership, users, records, permissions, subscriptions, and related responsibilities. Each Organization must maintain at least one active and contactable Organization Owner. An “**Organization Member**” is a User assigned to an Organization in the FieldDoc Platform. Organization Members may have different roles or permission levels depending on subscription tier, Application access, workspace configuration, and platform permissions. A “**Program Manager**” is a verified User authorized to manage one or more Programs in the FieldDoc Platform, which may require an Aggregator subscription, Master Service Agreement, Order Form, Statement of Work, grant agreement, Program agreement, or other written arrangement with The Commons. A “**Program**” is an organized initiative in the FieldDoc Platform used to support, track, review, fund, evaluate, manage, or report nature-based, conservation, restoration, monitoring, sustainability, environmental, or related work. A “**Workspace**” is a FieldDoc Platform environment, permission structure, or collaborative space associated with an Organization, Program, Application, or collaborative relationship through which Users may manage, view, share, or access records. A “**Folder**” is an organizational feature within the FieldDoc Platform that may be used to group, organize, or manage related records, including Activities where applicable. An “**Activity**” is a functional record in the FieldDoc Platform that may represent an on-the-ground conservation, restoration, engagement, sustainability, monitoring, or related action. Activity records may include information such as name, description, location, geometry, activity type, implementation status, metrics, model inputs, model outputs, files, photos, notes, reports, and other data. A “**Pact**” is a FieldDoc Platform feature used to share one or more Activities or related data from an Organization with a Program. Creating a Pact may grant the related Program Manager access to the data shared through that Pact for program administration, review, reporting, analysis, compliance, and other Program-related purposes. A “**Pact Opportunity**” is a time-limited or Program-specific channel through which Users or Organizations may share data with a Program through a Pact. For example, a Pact Opportunity may correspond to a grant round, reporting period, application window, or Program-specific submission process. A “**Model**” is a mathematical, scientific, analytical, or decision-support tool used in the FieldDoc Platform to estimate environmental impacts or other outcomes. Model outputs are estimates based on inputs, assumptions, protocols, third-party data, and model versions available at the time of calculation. They are not guarantees, forecasts, verified outcomes, or substitutes for professional judgment. ### 3. Individual User Account Terms #### 3.1 Account creation To use the FieldDoc Platform or any Application, you must create an individual User account. Each User must have their own login. Users may not share account credentials or allow another person to access the FieldDoc Platform or any Application through their account. You must provide accurate account information, including your real name and, unless one does not exist, a valid work email address. You are responsible for keeping your account information, including your email address, current and accurate. Accounts using pseudonyms, aliases, misleading names, shared credentials, invalid or unreachable email addresses, or false Organization affiliations may be suspended or removed from FieldDoc. #### 3.2 Human users only You must be a human to create a FieldDoc account. Accounts registered by bots, automated methods, scripts, or other non-human methods are not permitted unless The Commons gives prior written authorization. #### 3.3 Age requirement You must be at least 18 years old to create a FieldDoc account or use FieldDoc. #### 3.4 Legitimate role requirement You may create a FieldDoc account only if you have a legitimate role in creating, managing, reviewing, collaborating on, submitting, reporting, analyzing, administering, or supporting FieldDoc records, Organizations, Programs, Pacts, or related data. #### 3.5 Organization affiliation All Users must be associated with a verified Organization unless The Commons expressly authorizes a different account structure. A User may join an Organization’s account only if the User is authorized to act as a member, employee, officer, or direct representative of that Organization. Contractors, consultants, collaborators, technical assistance providers, funders, agency partners, volunteers, and other external partners should not join another Organization’s account unless expressly authorized by The Commons or permitted through platform functionality. Where appropriate, external partners may create or be assigned to their own Organization and may be invited to collaborate through workspaces, Pacts, shared records, Application-specific permissions, or other platform features. An Organization Owner or authorized administrator may invite external Users to access or collaborate within an Organization workspace only through available platform permissions and only to the extent the Organization is authorized to provide that access. Users may not misrepresent their identity, role, authority, Organization affiliation, Application access, Program relationship, or permission level to The Commons, FieldDoc staff, Program Managers, other Users, or within the FieldDoc Platform. #### 3.6 One Organization assignment Each User account may be assigned to only one Organization at a time. Users may access multiple organizations through workspace collaboration. If you work with multiple Organizations, you must use the collaboration features made available in FieldDoc. Contact The Commons for guidance. Contractors, consultants, collaborators, and partners may not join another Organization’s account. They may be assigned to their own Organization and invited to collaborate via workspaces, pacts, or on specific records. #### 3.7 Authority to act All FieldDoc Users must be associated with an Organization. You may only join or use FieldDoc in connection with an Organization that you are authorized to represent. By creating an account, joining an Organization, or creating, editing, submitting, sharing, reporting, exporting, deleting, archiving, or otherwise managing data in FieldDoc, you represent that you have the authority to take those actions in connection with that Organization. Organizations are responsible for ensuring that their Users have appropriate authority to access, manage, submit, share, report, export, delete, archive, or otherwise act on Organization data through FieldDoc. #### 3.8 Account security You are responsible for maintaining the security of your account and password. You may not share your login credentials with others. You are responsible for activity that occurs under your account, including activity by anyone who obtains access to your login credentials. The Commons cannot and will not be liable for loss or damage resulting from your failure to maintain account security. #### 3.9 User responsibility for content and conduct You are responsible for your conduct in FieldDoc and for the data, text, files, images, geospatial information, scientific information, reports, metrics, model inputs, and other content that you submit, upload, create, edit, share, export, delete, archive, or manage. By submitting, uploading, creating, editing, sharing, or managing content in FieldDoc, you represent that you have all rights, permissions, consents, and authority necessary to do so. You must not knowingly enter false, misleading, inaccurate, unauthorized, unlawful, or inappropriate information into FieldDoc. You must not misrepresent the status, location, extent, completion, installation, ownership, eligibility, environmental benefit, or reporting status of any Activity or other record. You must not submit content that infringes, misappropriates, or violates the intellectual property, privacy, confidentiality, contractual, proprietary, data-sharing, or other rights of any person or entity. You are responsible for determining whether content includes sensitive, restricted, confidential, proprietary, landowner-related, culturally sensitive, ecological, species-related, or location-based information, and for ensuring that you are authorized to enter, manage, and share that information in FieldDoc. You are responsible for ensuring that your content and use of FieldDoc comply with applicable laws, regulations, grant agreements, Program requirements, landowner agreements, data-sharing agreements, confidentiality obligations, and your Organization’s policies. If you become aware that content you submitted is materially inaccurate, unauthorized, incomplete, or misleading, you are responsible for correcting it or notifying the appropriate Organization Owner, Program Manager, or The Commons. The Commons may rely on the content you submit as accurate, authorized, and complete, but has no obligation to independently verify it. ### 4. Organization Responsibilities #### 4.1 Organization accounts Organizations represent real-world entities whose Authorized Users access or use the FieldDoc Platform, Applications, workspace(s), data, and related Services. New Organizations may be created by Users and may be verified by The Commons or FieldDoc support staff. Organization accounts that do not appear to represent real-world entities, cannot be verified, or are created for misleading, unauthorized, or improper purposes may be suspended, restricted, reassigned, or removed. Organizations may use the FieldDoc Platform at different subscription or access levels, including Basic, Standard, Aggregator, Application-specific subscriptions, trial access, grant-funded access, or other tiers or access models made available by The Commons. Subscription and access levels are assigned at the Organization level unless The Commons expressly provides otherwise. The Applications, features, seats, permissions, usage limits, support levels, data retention periods, and services available to an Organization may depend on its subscription tier, Application access, Program participation, agreement with The Commons, payment status, platform configuration, Subscription Documentation, or other written arrangement. No subscription tier, access level, Application, free access, trial access, or Program participation excuses a User or Organization from complying with these Terms. Detailed pricing, seat limits, feature availability, Application access, payment terms, data retention periods, support commitments, and service commitments may be described separately in Subscription Documentation, an Order Form, Statement of Work, Master Service Agreement, pricing schedule, Program agreement, Application-Specific Terms, or other written arrangement. #### 4.2 Organization Owner requirement Each Organization must identify and maintain at least one active, contactable Organization Owner. Failure to maintain an active Organization Owner may result in account restrictions, deactivation, or administrative intervention by The Commons. #### 4.3 Organization Owner responsibilities Organization Owners are responsible for managing their Organization’s FieldDoc account. This includes responsibility for: * Maintaining accurate Organization membership; * Adding, removing, or updating Users; * Removing Users who no longer work for or represent the Organization; * Assigning appropriate roles and permissions; * Monitoring collaborator access; * Managing Organization records; * Billing * Ensuring Users have authority to act on behalf of the Organization; * Ensuring Organization data is created, shared, retained, archived, exported, or deleted in accordance with the Organization’s own obligations; * Contacting The Commons when Organization membership, ownership, or record ownership needs to be corrected. #### 4.4 Organization-level visibility FieldDoc is designed to support Organization-level transparency. Unless otherwise limited by specific platform permissions, records in an Organization’s portfolio may be visible to all members of that Organization. Users should not enter data into an Organization portfolio unless they are comfortable with authorized Organization Members having access to that data. #### 4.5 User departure or change in role If a User no longer works for, serves, or is authorized to represent an Organization, the Organization Owner is responsible for removing or updating that User’s access. Records created by that User on behalf of the Organization will remain in the Organization’s portfolio unless deleted, reassigned, archived, exported, or otherwise managed in accordance with FieldDoc functionality and these Terms. Deleting or deactivating an individual User account does not delete Organization records associated with that User. #### 4.6 Incorrect Organization membership If a User joins an Organization in error, the Organization Owner should revoke that User’s privileges and contact The Commons at if reassignment or additional support is needed. The Commons may remove Users from FieldDoc or reassign Users to a different Organization at its discretion when necessary to maintain accurate Organization membership. #### 4.7 Collaboration between Organizations FieldDoc may allow Users from different Organizations to collaborate on or share access to records. Cross-Organization access may be provided through collaboration permissions, shared records, Pacts, or other platform features. When a User from one Organization is invited to collaborate on a record, folder, Pact, or other workspace item managed by another Organization, that User may receive access only to the records or areas made available through the invitation. Invited collaborators do not automatically receive access to the managing Organization’s full portfolio unless platform permissions specifically allow it. Unless otherwise agreed in writing or enabled through platform functionality, the managing Organization remains responsible for managing the record. FieldDoc may also allow Organizations to share management access to a single record. In that case, the record may be available within more than one Organization’s workspace, and authorized Users from each Organization may be able to view, edit, organize, share, archive, delete, or otherwise manage the record according to their permissions. Changes made to a shared record may be visible to all Organizations with access to that record. Organizations that share access to or management of a record are responsible for coordinating appropriate data management, permissions, reporting, retention, and deletion decisions. The Commons is not responsible for resolving disputes between Organizations about shared records, unless required by a separate written agreement or necessary to operate, secure, or administer FieldDoc. If record ownership, access, or sharing appears incorrect, Users should coordinate with the relevant Organization Owner(s), authorized collaborators, and, when appropriate, The Commons before deleting or materially changing the record, especially when the record is associated with a Program, Pact, reporting obligation, or other external requirement. The Commons is not responsible for determining the correct real-world ownership, governance, reporting obligations, or data management strategy for records created, shared, or managed by Users or Organizations, unless otherwise agreed in writing through a Statement of Work, grant agreement, Master Service Agreement, or other written arrangement. #### 4.8 Organization responsibility for data stewardship Organizations are responsible for determining how FieldDoc fits within their own data governance, grant reporting, privacy, security, compliance, and record retention practices. Organizations should ensure that their Users understand what data may be entered into FieldDoc, what data may be shared, what data may be sensitive, and who is authorized to act on behalf of the Organization. The Commons provides the FieldDoc platform, related support, and any services expressly agreed to in writing. Unless otherwise agreed in a Statement of Work, grant agreement, Master Service Agreement, Order Form, or other written arrangement, The Commons is not responsible for determining an Organization’s internal data governance practices, reporting obligations, record retention requirements, or real-world authority to create, manage, share, modify, or delete records in FieldDoc. ### 5. Program Manager and Pact Terms Program Manager and Pact terms apply where the relevant Application, Program, subscription tier, or platform configuration makes Program or Pact functionality available. Not all Applications or Services will use Programs, Pacts, Pact Opportunities, Activity records, Models, or the same data-sharing workflows. #### 5.1 Program Manager eligibility Program Manager roles are reserved for verified staff or representatives of Organizations that manage one or more Programs in FieldDoc through an Aggregator subscription. Program Manager access may require a Master Service Agreement, Order Form, Statement of Work, grant agreement, Program agreement, payment arrangement, or other written agreement with The Commons. #### 5.2 Program Manager access Program Managers may access Program-level data and data shared to their Program through Pacts by participating Users and Organizations. Activity records are linked to a Program through a Pact. The Program Manager may view and export the Activity record data linked to that Pact, unless otherwise limited by a separate written agreement or platform configuration. Program Managers may use shared data for Program administration, review, reporting, analysis, compliance, evaluation, communication, and other Program-related purposes. Program Managers are responsible for communicating any Program-specific data use expectations, reporting requirements, or privacy expectations to participating Users and Organizations. Program Managers may not access Activity records, Organization portfolio records, or other data created by an Organization unless those records are linked to the Program through a Pact, shared through another authorized FieldDoc feature, or otherwise made available under a separate written agreement or platform permission. #### 5.3 Program Manager editing rights Program Managers may manage Program-level and Pact-level information according to platform permissions. This may include Pact-level fields such as title, start and end dates, funding amount, status, and other fields made editable to Program Managers through FieldDoc. Program Managers may not edit, delete, or otherwise modify underlying Activity records, metric data, files, geospatial data, or other records owned or managed by another Organization unless expressly authorized through platform permissions, the owning Organization’s authorization, or a separate written agreement. Through an agreement or authorized configuration process with The Commons, Program Managers may configure Programmatic Metrics, Activity Types, Pact Opportunities, and accessible Models for their Programs. Those configurations may be made available to participating Users and Organizations through the applicable Program or Pact Opportunity. #### 5.4 Program requirements Program Managers may establish Program-specific requirements for data entry, reporting, Activity Types, metrics, models, deadlines, review processes, privacy expectations, exports, compliance, and other Program-related obligations. Program-specific requirements may supplement these Terms, but they do not replace or override these Terms unless The Commons has expressly agreed otherwise in a Master Service Agreement, Order Form, Statement of Work, grant agreement, Program agreement, payment arrangement, or other written agreement. Unless otherwise agreed in writing by The Commons, Program-specific requirements are determined, communicated, administered, and enforced by the Program Manager. The Commons is not responsible for creating, interpreting, monitoring, or enforcing Program-specific requirements except as expressly agreed in writing. Users and Organizations participating in a Program are responsible for understanding and complying with both these Terms and any applicable Program-specific requirements. #### 5.5 Pact ownership and creation The Organization receiving or participating in the relevant agreement, award, reporting obligation, or Program relationship will create and maintain the related Pact unless the Program Manager provides different instructions or a separate written agreement states otherwise. Pacts should not be created by unauthorized third parties. If a Pact or Activity is created by the wrong Organization, Users should contact The Commons rather than deleting the record, especially if the record is related to a Program, award, report, or compliance obligation. #### 5.6 Pact sharing and data ownership Creating, accepting, or maintaining a Pact gives the related Program Manager access and use rights to the Activity data shared through that Pact for Program-related purposes. Unless otherwise stated in a separate written agreement, Pact sharing does not transfer ownership of the underlying Activity data from the Organization that owns or manages the Activity. #### 5.7 Program Manager responsibilities after export Program Managers with permission to export data are expected to respect applicable privacy settings, Program requirements, grant requirements, legal obligations, and any separate written agreements governing use of exported data. FieldDoc permission settings may not control data after it has been exported from FieldDoc or transmitted to an external system. ### 6. Data Ownership and License #### 6.1 Ownership of User and Organization data Data entered into FieldDoc is owned or controlled by the User and Organization that creates, manages, or is responsible for that data, subject to any applicable Program requirements, Pact relationships, grant agreements, collaboration arrangements, or other written agreements. FieldDoc assumes that the User and Organization creating a record have the authority to create, manage, and share the associated data. #### 6.2 Organization records Records created by a User on behalf of an Organization are held in a designated FieldDoc Organization workspace unless reassigned, deleted, archived, or otherwise managed through the FieldDoc Platform or any Application functionality or by The Commons. Users should not create, edit, or delete records on behalf of an Organization unless authorized to do so. #### 6.3 Collaboration and sharing Data ownership, access, visibility, and use rights may be affected by collaboration features, Organization membership, Program participation, Pact sharing, exports, APIs, integrations, or separate agreements. Inviting collaborators, sharing data through a Pact, or exporting data may make data available to others. #### 6.4 License to The Commons By entering, uploading, storing, importing, generating, or sharing content through the FieldDoc Platform or any Application, you grant The Commons a non-exclusive, worldwide, royalty-free license to host, store, process, display, reproduce, format, analyze, map, transform, transmit, and otherwise use that content solely as necessary to: Operate, maintain, improve, support, secure, and provide the FieldDoc Platform, Applications, and Services; Provide authorized features, workflows, exports, APIs, dashboards, maps, models, analytics, reports, and integrations; Fulfill authorized Program, Pact, reporting, compliance, administrative, support, and professional services functions; Provide technical assistance, troubleshooting, onboarding, data migration, analysis, configuration, or other services authorized by Users, Organizations, Program Managers, Customers, or applicable agreements; Comply with legal obligations, valid requests, security requirements, or applicable contractual obligations. The Commons will not sell User or Organization content. #### 6.5 License duration The license described above continues for as long as the content remains in FieldDoc or is reasonably needed for authorized platform, Program, reporting, support, backup, legal, compliance, or archival purposes. If content is deleted from the FieldDoc Platform or any Application, the license ends for that content except where retention is necessary for backups, audit logs, legal obligations, Program requirements, dispute resolution, security, or compliance. #### 6.6 Content responsibility The Commons does not pre-screen content entered into FieldDoc. The Commons reserves the right, but does not have the obligation, to refuse, remove, restrict, archive, or disable access to content that violates these Terms, violates law, infringes rights, creates security or privacy risks, includes prohibited information, or is otherwise inappropriate for FieldDoc. ### 7. Data Visibility, Privacy, Sharing, and Exports #### 7.1 The FieldDoc platform is a collaborative platform The FieldDoc Platform and its Applications are collaborative reporting, data management, geospatial, workflow, and decision-support tools. Privacy settings limit certain forms of visibility, editing, mapping, export, public display, or access within the platform, but they do not make data confidential from all parties. Depending on the record and platform configuration, data may be visible to: * The User who created it; * Organization Members; * Organization Owners; * Invited collaborators; * Program Managers; * The Commons staff; * Authorized technical support providers; * Users with appropriate permissions; * Third-party services or integrations authorized through FieldDoc; * Other parties authorized by Program requirements or separate agreements. #### 7.2 No data is fully private No data entered into FieldDoc should be considered fully private or confidential from all other parties. Users and Organizations should not enter sensitive, confidential, restricted, proprietary, culturally sensitive, ecological, landowner-related, location-based, or legally protected data unless they have authority to do so and understand how the data may be viewed, shared, exported, analyzed, displayed, retained, or disclosed. Nothing in this section limits any confidentiality obligations The Commons has under a Master Subscription Agreement, Data Processing Addendum, Statement of Work, grant agreement, or other written agreement. FieldDoc privacy settings govern platform access and visibility; contractual confidentiality obligations may separately govern how The Commons and Customers handle non-public information. #### 7.3 Program Manager visibility Program Managers may view Activity and Pact information shared to their Programs, regardless of whether certain records are marked private within FieldDoc, unless a separate written agreement provides otherwise. Program Managers may export Activity data associated with their Programs according to platform permissions and Program requirements. #### 7.4 The Commons staff access Members of The Commons staff may access User, Organization, Project, Activity, Pact, Program, model, metric, file, geospatial, and other FieldDoc data as needed to provide support, administer the platform, troubleshoot issues, maintain security, fulfill contractual obligations, provide professional services, or operate FieldDoc. #### 7.5 Aggregated and anonymized data The Commons may use data in aggregated or anonymized form for platform analytics, Program summaries, impact summaries, dashboards, reporting, system improvement, research, fundraising, communications, or other mission-aligned purposes. Aggregated or anonymized data should not reasonably identify a specific User, Organization, private record, or sensitive location unless authorized. #### 7.6 Exports Users, Organization Owners, Program Managers, and others with appropriate permissions may export data from FieldDoc. Once data is exported, downloaded, transmitted, or copied outside FieldDoc, FieldDoc permission settings no longer control access to or use of that data. Users, Organizations, and Program Managers are responsible for understanding the consequences of exporting or sharing data and for complying with any applicable laws, agreements, Program requirements, privacy obligations, data-sharing restrictions, or Organization policies that apply to exported data. The Commons is not responsible for how data is used, stored, shared, modified, or disclosed after it has been exported, downloaded, transmitted, or copied from FieldDoc by an authorized User, Organization, Program Manager, integration, or other authorized recipient. #### 7.7 APIs and third-party applications The Commons may provide or authorize APIs, dashboards, integrations, Application-specific connections, data services, or third-party services that connect to or operate with the FieldDoc Platform. APIs, integrations, and connected services will be designed to respect applicable platform permissions and privacy settings where technically feasible, but data shared through exports, APIs, dashboards, integrations, Application-specific workflows, or third-party services may be subject to the receiving party’s systems, policies, agreements, and security practices. Users and Organizations are responsible for understanding when their use of the FieldDoc Platform or an Application causes data to be shared with third-party systems. The Commons may override privacy settings or restrict access when required by law, Program requirements, grant agreements, legal obligations, security needs, or separate written agreements. #### 7.8 Landowner and property information FieldDoc does not intentionally require Users to provide private land ownership details such as landowner names, addresses, tax parcel records, deeds, financial information, or other sensitive property records unless expressly requested by a Program or workflow. Users are encouraged not to enter land ownership data or other sensitive property information unless they have authority to do so and the information is necessary for an authorized FieldDoc purpose. The Commons assumes no liability for unauthorized disclosures of land ownership or property information entered by Users. #### 7.9 Sensitive environmental and location data Users and Organizations are responsible for determining whether data entered into FieldDoc includes sensitive, restricted, confidential, culturally sensitive, proprietary, ecological, species-related, landowner-related, or location-based information. This may include, but is not limited to, data related to rare species, threatened or endangered species, culturally significant sites, tribal resources, private land restoration, regulated infrastructure, vulnerable communities, monitoring locations, or sensitive habitat. Users should not enter or share sensitive data unless they have the authority to do so and understand how that data may be viewed, exported, reported, or disclosed through FieldDoc. ### 8. Data Retention, Deletion, and Account Closure #### 8.1 User deletion of records Data deleted by a User from FieldDoc may be non-recoverable. Users should not delete records, Activities, Projects, Pacts, files, geospatial data, metrics, reports, or other content they wish to retain. The “archive” function, if available, does not delete records but may remove them from certain primary views. #### 8.2 Deleted records The Commons does not guarantee that deleted records can be recovered. Users and Organizations are responsible for exporting or otherwise backing up critical records they wish to preserve outside FieldDoc. #### 8.3 Non-awarded, draft, and inactive records Records created in FieldDoc for planning, application, draft, or non-awarded purposes that are not associated with standard accounts are not guaranteed to be retained indefinitely. Unless otherwise agreed in writing, records that are not linked to an awarded, active, submitted, completed, retained, or otherwise Program-associated Pact or Program may be archived, restricted, or deleted after 6 months of inactivity or 12 months after the relevant application, Pact Opportunity, review, or reporting period closes. This may include records created under a Basic subscription or access level. Where feasible, The Commons will provide notice to the affected User or Organization Owner before deleting inactive records. Users and Organizations are responsible for exporting, submitting, archiving, or otherwise preserving records they wish to retain. #### 8.4 Program-linked records Activities, Pacts, Projects, files, metrics, geospatial data, reports, and other records linked to awarded, submitted, active, completed, retained, or otherwise Program-associated Pacts may be retained for longer periods, including indefinitely, to support Program administration, reporting, audit, compliance, legal obligations, historical records, Program Manager requirements, or The Commons’ legitimate operational needs. #### 8.5 Account deletion At your request, The Commons will delete or deactivate your individual FieldDoc User account and personal information, subject to legal, compliance, security, backup, audit, Program, and contractual retention obligations. To request account deletion, contact . #### 8.6 Account deletion does not delete Organization records Deleting an individual User account does not necessarily delete Organization records, Activities, Pacts, Projects, files, reports, metrics, geospatial data, or other content created or managed by that User on behalf of an Organization. Those records may remain associated with the Organization, Program, or Pact to support collaboration, reporting, audit, compliance, legal obligations, Program Manager requirements, or The Commons’ legitimate operational needs. #### 8.7 Personal information retention The Commons may retain personal information where necessary to comply with legal obligations, respond to valid requests, support Program reporting, investigate misuse, maintain security, resolve disputes, enforce these Terms, or fulfill contractual obligations. The Commons may also use account, usage, and platform information for internal analysis, product planning, user research, sector research, outreach planning, and service improvement, subject to the FieldDoc Privacy Policy. Where practical, The Commons will use aggregated or de-identified information for these purposes. #### 8.8 Backups and infrastructure FieldDoc relies on third-party infrastructure providers, including cloud storage, hosting, processing, and delivery services, to store and process account and portfolio data. The Commons keeps periodic backups of FieldDoc data. However, The Commons cannot guarantee recovery from all data loss events, including catastrophic failures, third-party outages, human error, cyber incidents, or events beyond our control. Users and Organizations are encouraged to use available export features to back up critical data. Customers with a Master Subscription Agreement, Order Form, or other written agreement may have additional data export rights, including post-termination export rights, as described in that agreement. ### 9. Data Accuracy, Verification, and Model Outputs #### 9.1 User responsibility for accuracy Users and Organizations are responsible for accurately documenting the location, extent, Activity type, implementation status, completion status, metrics, model inputs, files, and other information entered into FieldDoc. Users must not knowingly misrepresent Activity installation status, implementation progress, eligibility, location, extent, ownership, completion, or reporting status. #### 9.2 The Commons does not verify all data The Commons does not independently verify the correctness, completeness, ownership, legality, applicability, accuracy, or authenticity of all data entered into FieldDoc. The Commons cannot verify all Activity type selections, geospatial data, model inputs, uploaded files, reports, implementation claims, monitoring data, or other information entered by Users. #### 9.3 Program Manager review Program Managers may review, approve, reject, request changes to, or otherwise evaluate data submitted to their Programs. Program Managers are responsible for communicating Program-specific requirements, review criteria, reporting expectations, and deadlines to participating Users and Organizations. #### 9.4 Model inputs and outputs FieldDoc Models depend on the accuracy, precision, completeness, assumptions, and applicability of the data entered into them. If a User provides inaccurate, incomplete, provisional, generalized, or estimated inputs, Model outputs may be affected. Model outputs are estimates based on the inputs, assumptions, protocols, and model versions available at the time of calculation. They should not be treated as independently verified environmental outcomes unless separately reviewed, approved, or validated by the relevant Program Manager, regulator, technical expert, or other authority. #### 9.5 No guarantee of model accuracy The Commons makes no guarantee that Model outputs are accurate, complete, current, appropriate for a particular purpose, comparable to outputs from other systems, or within expected ranges. Due to differences in model methods, versions, assumptions, protocols, data inputs, and third-party systems, FieldDoc Model outputs may differ from estimates produced elsewhere. #### 9.6 Third-party models The Commons may integrate third-party, public, peer-reviewed, Program-specific, or partner-provided models. The Commons is not responsible for the completeness, correctness, availability, assumptions, scientific validity, or continued operation of third-party models, model APIs, model documentation, or model protocols. #### 9.7 Duplicate reporting The Commons is not responsible for detecting or preventing duplicate reporting of Activity installations, environmental benefits, modeled outcomes, metrics, or other data entered into FieldDoc. Users, Organizations, and Program Managers are responsible for identifying and resolving duplicate reporting risks in accordance with applicable Program requirements or agreements. #### 9.8 Geospatial data The Commons bears no responsibility for the source, validity, accuracy, precision, ownership, legality, or appropriateness of geospatial data submitted by Users. Users and Organizations are responsible for ensuring that they have the right to enter, upload, share, and report geospatial data in FieldDoc. ### 10. Third-Party Services, APIs, and Integrations #### 10.1 Third-party services FieldDoc may depend on or integrate with third-party services, including cloud hosting providers, storage providers, analytics tools, model APIs, mapping tools, data import tools, export tools, authentication services, email services, dashboard tools, and other software or infrastructure providers. #### 10.2 Third-party terms Some third-party software or services may be subject to additional notices, licenses, or terms and conditions. By using FieldDoc features that depend on third-party services, you may be subject to those additional terms. #### 10.3 No guarantee of third-party availability The Commons does not guarantee that third-party services, APIs, integrations, models, or external systems will remain available, compatible, error-free, secure, or unchanged. FieldDoc features may be modified, interrupted, degraded, or discontinued if third-party services change, fail, become unavailable, impose new restrictions, or become incompatible with FieldDoc. #### 10.4 Data shared with third-party services Data transmitted to authorized third-party services may be processed, stored, analyzed, displayed, or returned according to the purpose of the integration. Users and Organizations are responsible for understanding when their use of FieldDoc causes data to be shared with third-party systems. ### 11. Professional Services #### 11.1 Professional services by The Commons The Commons may provide professional, technical, advisory, implementation, data, or support services related to the FieldDoc Platform, Applications, or related conservation and environmental data systems, including but not limited to onboarding, configuration, data migration, training, technical assistance, GIS support, geospatial analysis, reporting, dashboard development, integration support, data cleanup, Program setup, model configuration, workflow design, user support, strategic advising, Digital Services, Data Concierge, Conservation Concierge, and other digital, data, or advisory services. #### 11.2 Separate agreements Professional services may be provided under a separate Master Service Agreement, Order Form, Statement of Work, grant agreement, Program agreement, or other written arrangement. Unless expressly included in such an agreement, professional services are not included in general FieldDoc access. #### 11.3 Deliverables and timelines Deliverables, timelines, assumptions, responsibilities, fees, acceptance criteria, and support obligations for professional services should be described in the applicable written agreement. #### 11.4 Access to data for services When The Commons provides professional services, The Commons staff may access User, Organization, Program, Pact, Activity, geospatial, model, metric, file, export, or other data as needed to perform those services. #### 11.5 Third-Party Service Providers Unless expressly authorized in writing by The Commons, no third party is authorized, certified, endorsed, or approved by The Commons to provide official FieldDoc implementation, configuration, technical assistance, training, data migration, reporting, model configuration, integration support, or other FieldDoc-related professional services. Users and Organizations may choose to work with their own consultants, contractors, or technical assistance providers, but those third parties act on behalf of the User or Organization, not on behalf of The Commons, unless The Commons has expressly agreed otherwise in writing. The Commons is not responsible for the acts, omissions, advice, work product, data handling, security practices, representations, or fees of any third-party consultant, contractor, or service provider that has not been expressly authorized by The Commons in writing. ### 12. Acceptable Use and Code of Conduct #### 12.1 Lawful use You may not use FieldDoc for any illegal purpose or in violation of any applicable law, regulation, policy, agreement, or third-party right. You are responsible for complying with laws that apply to your use of FieldDoc, including but not limited to copyright, privacy, data protection, public records, grant compliance, environmental reporting, and data-sharing laws. #### 12.2 Mission-aligned use You may not use FieldDoc for purposes that do not align with the mission of the platform. FieldDoc is intended to support conservation, restoration, nature-based work, sustainability, monitoring, reporting, data stewardship, environmental analysis, Program administration, and related activities. #### 12.3 Prohibited technical conduct You must not: * Modify, adapt, hack, interfere with, or disrupt FieldDoc; * Attempt to gain unauthorized access to FieldDoc systems or data; * Transmit worms, viruses, malware, destructive code, or harmful content; * Scrape, harvest, or extract data without authorization; * Circumvent permissions, privacy settings, access controls, or security features; * Use FieldDoc in a way that disrupts other Users, Programs, Organizations, or services; * Falsely imply that another website, system, organization, product, or service is associated with FieldDoc or The Commons. #### 12.4 Reverse engineering You may not disassemble, decompile, reverse engineer, or attempt to derive the source code, structure, underlying ideas, algorithms, or technical architecture of FieldDoc, except to the extent such activity is expressly permitted by law or authorized in writing by The Commons. This includes, without limitation: * Converting machine-readable code to human-readable code; * Disassembling or decompiling object code; * Examining platform behavior to recreate source code or proprietary logic; * Permitting others to do any of these activities. To the extent any such activity is permitted by written agreement, the results will be treated as confidential information unless otherwise stated. #### 12.5 Brand use No person or entity may misrepresent themselves as the owner, operator, sponsor, or official representative of FieldDoc. You may not use the FieldDoc name, logo, brand marks, or other identifying materials without authorization from The Commons. #### 12.6 User conduct You must not abuse, harass, threaten, intimidate, defame, impersonate, mislead, invade the privacy of, or otherwise harm other FieldDoc Users, Program Managers, collaborators, Organizations, or The Commons staff. This applies to conduct through the FieldDoc platform, support channels, email, meetings, webinars, trainings, community forums, and other FieldDoc-related communications. #### 12.7 Unauthorized data access or use Without written consent from The Commons or authorization through FieldDoc permissions, you may not attempt to access, extract, copy, scrape, export, use, or analyze data belonging to other Users, Organizations, Programs, or Program Managers. This includes attempts to pull Organization names, contact information, private records, geospatial data, model outputs, analytical results, or other data for unauthorized third-party purposes. #### 12.8 Prohibited content You may not enter, upload, transmit, or share content that: * Is unlawful, fraudulent, false, misleading, or unauthorized; * Violates intellectual property rights; * Violates privacy or data protection rights; * Contains malware or harmful code; * Is abusive, threatening, defamatory, obscene, or harassing; * Includes sensitive personal information that should not be entered into FieldDoc; * Includes government-issued identification numbers, financial account numbers, social security numbers, passport numbers, driver’s license numbers, credit card numbers, or similar information unless expressly authorized and necessary; * Violates these Terms, Program requirements, or applicable agreements. ### 13. Suspension, Removal, and Enforcement #### 13.1 Suspension or restriction The Commons may suspend, restrict, deactivate, remove, or limit access to FieldDoc for any User, Organization, Program, Pact, record, or content if The Commons reasonably determines that: * These Terms have been violated; * A User misrepresented their identity, authority, or Organization affiliation; * A User or Organization poses a security, privacy, operational, legal, or reputational risk; * Use of FieldDoc may disrupt the platform or other Users; * Use of FieldDoc is unlawful or unauthorized; * A User entered false, misleading, harmful, sensitive, or prohibited content; * A User or Organization failed to maintain required Organization ownership or contact information; * A Program or Organization failed to pay undisputed amounts when due under a separate agreement; * Suspension is required by law, court order, legal request, third-party provider, Program requirement, or separate written agreement. #### 13.2 Removal of data or content The Commons may remove, restrict, archive, or disable access to any content or record that The Commons determines violates these Terms, violates law, creates risk, is inaccurate or misleading, infringes rights, exposes sensitive information, or is otherwise inappropriate for FieldDoc. #### 13.3 Reassignment of records The Commons may reassign Users, Organizations, records, Pacts, Activities, Projects, or other content when reasonably necessary to correct mistaken ownership, Organization affiliation, Program association, or platform configuration. #### 13.4 No obligation to monitor The Commons does not have an obligation to monitor all content, data, records, or User activity in FieldDoc. Failure to enforce a provision of these Terms in one instance does not waive The Commons’ right to enforce it later. ### 14. Payment, Program-Specific Terms, and Order of Precedence #### 14.1 General access Users may create accounts, join verified Organizations, and use certain FieldDoc features at no cost where permitted by the platform. There is no general cost to create an Organization, add staff members, or submit Pacts to Programs unless otherwise stated in a separate agreement or Program requirement. #### **14.2 Subscription Terms** Organizations may access the FieldDoc Platform or specific Applications through free access, trial access, grant-funded access, paid subscriptions, Application-specific subscriptions, Program-specific access, or other access models made available by The Commons. Unless The Commons expressly provides otherwise, subscriptions and access levels are assigned at the Organization level. The subscription tier, subscription term, fees, payment terms, seat limits, usage limits, Application access, available features, support level, data retention period, renewal terms, cancellation terms, and any service-specific commitments are described in the applicable Subscription Documentation. By creating, selecting, purchasing, renewing, or continuing to use a subscription or access level, the Customer agrees to the applicable Subscription Documentation and these Terms. The Commons may limit, suspend, downgrade, or terminate access to paid features, Applications, support, professional services, or other subscription-based services if a subscription expires, is not renewed, is cancelled, exceeds applicable usage limits, or if undisputed amounts are not paid when due, subject to any notice, cure period, or different terms stated in the applicable Subscription Documentation or written agreement. Free, trial, evaluation, grant-funded, or Program-sponsored access may be limited in duration, features, seats, support, data retention, Application access, or usage. Unless otherwise agreed in writing, The Commons may modify, limit, or discontinue free, trial, evaluation, grant-funded, or Program-sponsored access at any time. #### 14.3 Program features and paid services Some of the features provided on this platform are provided on the basis of payment. The fees, duration and conditions applicable to the purchase of such Products are described dedicated sections. To purchase Products, the User must register or log into the platform or speak with a representative of The Commons. Organizations that subscribe to or purchase Subscriptions, manage Programs, access advanced features, receive professional services, use paid support, exceed usage limits, or enter into specific arrangements with The Commons may be subject to fees, payment terms, and additional obligations. Payment terms may be set out in a Subscription Documentation, Order Form, pricing page, invoice, Statement of Work, support plan, grant agreement, Program agreement, Application-Specific Terms, or other written arrangement. #### 14.4 Additional Program terms Individual Programs may establish additional requirements or terms for participating Users and Organizations. These may include requirements related to eligibility, deadlines, Activity types, metrics, models, data entry, reporting, review, export, privacy, compliance, or retention. #### 14.5 Order of precedence These Terms apply generally to all Users, Organizations, and use of the FieldDoc Platform and Applications. Customers with a Master Service Agreement, Order Form, Statement of Work, Data Processing Addendum, Security Exhibit, grant agreement, Program agreement, Application-Specific Terms, or other written agreement with The Commons may have additional or different rights and obligations. If there is a conflict among applicable documents, the following order of precedence applies unless a written agreement executed by The Commons expressly states otherwise: 1. Applicable Order Form, Statement of Work, grant agreement, Program agreement, or other signed written agreement; 2. Data Processing Addendum, Security Exhibit, or similar data protection terms, if any; 3. Application-Specific Terms, if any; 4. Master Service Agreement, if any; 5. These Terms; 6. FieldDoc Privacy Policy; 7. Documentation, help materials, support materials, product descriptions, or platform guidance. If there is a conflict between these Terms and Program requirements established by a Program Manager, the Program requirements may apply to that Program relationship, but they do not change The Commons’ general Terms or obligations unless The Commons has agreed in writing. These Terms continue to apply to individual User accounts, account conduct, acceptable use, platform access, and general platform use unless expressly modified by a written agreement executed by The Commons. ### 15. FieldDoc Features, Bugs, Availability, and Longevity #### 15.1 Platform features The Commons designs FieldDoc with care, based on its own experience and feedback from Users, Organizations, Program Managers, and partners. However, The Commons does not guarantee that FieldDoc will meet every User’s, Organization’s, Program’s, or Program Manager’s specific requirements or expectations. #### 15.2 Bugs and errors The Commons tests FieldDoc features and works to address reported bugs, especially bugs related to security, privacy, data integrity, or core platform functions. Not all reported bugs will be fixed. The Commons does not guarantee that FieldDoc will be error-free, uninterrupted, or free of defects. #### 15.3 Feature changes The Commons may add, modify, suspend, discontinue, rename, replace, or remove FieldDoc Platform features, Applications, modules, tools, integrations, workflows, or services from time to time. The Commons will work to maintain existing features where practical, but features, Applications, and services may change or become unavailable due to technical limits, funding limits, user needs, third-party service changes, browser changes, security concerns, infrastructure changes, product evolution, Application-specific changes, or other reasons. For Customers with a Master Service Agreement, Order Form, support plan, or other written agreement, any specific commitments regarding Applications, service availability, support, or feature access are governed by that agreement. #### 15.4 FieldDoc longevity The Commons is dedicated to supporting FieldDoc for as long as it has the funding, resources, technical capacity, and operational ability to do so. The Commons may modify, pause, transition, or shut down FieldDoc if continued operation becomes impractical, unfunded, legally restricted, technically impossible, or otherwise unsustainable. Where feasible, The Commons will provide notice of major service changes or shutdowns. #### 15.5 No guarantee of continuous access The Commons does not guarantee continuous access to FieldDoc. FieldDoc may be unavailable due to maintenance, outages, bugs, security incidents, third-party failures, infrastructure failures, legal requirements, funding changes, or events beyond The Commons’ control. For Customers with a Master Service Agreement, Order Form, support plan, or other written agreement, any specific service availability commitments are governed by that agreement. ### 16. Disclaimers and Limitation of Liability #### 16.1 Use at your own risk You use FieldDoc at your own risk. FieldDoc is provided on an “as is” and “as available” basis. The Commons disclaims warranties to the fullest extent permitted by law, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, availability, reliability, and error-free operation. #### 16.2 No professional advice The FieldDoc Platform or any Application may help Users organize, analyze, model, report, or communicate data. The FieldDoc Platform or any Application does not provide legal, engineering, scientific, regulatory, financial, tax, accounting, grant compliance, or professional advice. Users, Organizations, and Program Managers are responsible for obtaining appropriate professional guidance when needed. #### 16.3 Limitation of liability To the fullest extent permitted by law, and except to the extent a Master Service Agreement, Order Form, Data Processing Addendum, Security Exhibit, or other written agreement executed by The Commons provides otherwise, The Commons will not be liable, in law or equity, to any User, Organization, Program Manager, or third party for any direct, indirect, incidental, special, consequential, punitive, exemplary, or similar damages, including damages for loss of profits, goodwill, use, data, funding, opportunity, reputation, or other intangible losses, even if The Commons has been advised of the possibility of such damages. This includes damages resulting from: 1. Use of the FieldDoc Platform or any Application; 2. Inability to use the FieldDoc Platform or any Application; 3. Errors, bugs, outages, or service interruptions; 4. Loss, corruption, deletion, or alteration of data; 5. Unauthorized access to or alteration of data; 6. User error; 7. Misconfigured permissions; 8. Program Manager decisions, requirements, statements, actions, or funding decisions; 9. Third-party integrations, APIs, models, services, or infrastructure; 10. External deadlines, including failure to allow sufficient time to create an account, receive an Organization assignment, complete data entry, submit a Pact, or complete Program reporting; 11. Reliance on Model outputs, metrics, reports, exports, maps, dashboards, or other FieldDoc Platform or any Application outputs; 12. Duplicate, inaccurate, incomplete, unauthorized, or misleading data entered by Users; 13. Any other matter relating to the FieldDoc Platform or any Application or these Terms. #### 16.4 Third-party conduct The Commons is not responsible for statements, conduct, decisions, requirements, or actions of third parties, including Users, Organizations, Program Managers, funders, agencies, contractors, collaborators, consultants, or third-party service providers. ### 17. Privacy Policy and Communications #### 17.1 Privacy Policy Information you provide to the FieldDoc Platform or any Application is subject to the FieldDoc Privacy Policy. The Privacy Policy governs The Commons’ collection and use of personal information. By using the FieldDoc Platform or any Application, you consent to the collection and use of information as described in the Privacy Policy. #### 17.2 System communications The Commons may contact Users by email or through the platform to provide system-wide updates, account notices, support messages, release notes, security notices, Program-related notices, community updates, or other FieldDoc-related communications. Some communications are necessary for account, security, Program, or platform administration. ### 18. Changes to These Terms The Commons may update these Terms from time to time. These Terms will continue to apply to individual User accounts, acceptable use, platform conduct, and general use of the FieldDoc Platform or any ApplicationPlatform unless expressly modified by the applicable written agreement. If The Commons makes a material change to these Terms, The Commons will provide reasonable notice through the email address associated with a User’s account, through the FieldDoc Platform, by posting the updated Terms on the FieldDoc website, or by another reasonable method. The Commons will determine whether a change is material in good faith, using reasonable judgment. Unless otherwise stated in the notice, updated Terms will become effective when posted or otherwise made available. Your continued access to or use of the FieldDoc Platform, any Application, or any Services after the updated Terms become effective means that you accept the updated Terms. If you do not agree to the updated Terms, you must stop using the FieldDoc Platform and may request account deletion by contacting . For Customers with individually negotiated agreements, changes to those agreements will be governed by the amendment provisions in the applicable written agreement. These Terms will continue to apply to individual User accounts, acceptable use, platform conduct, and general use of the FieldDoc Platform unless expressly modified by the applicable written agreement. ### 19. Contact If you have questions about these Terms, the FieldDoc Platform or any Application, The Commons’ practices, your account, your Organization, or your rights, please contact us. **Email:** **Mailing address:** The Commons, Inc.\ 200 Massachusetts Ave NW\ Washington, DC 20001
# Privacy Policy Last updated: June 15, 2026 ## FieldDoc Platform Privacy Policy The Commons, Inc. ("The Commons") operates the FieldDoc Platform, including FieldDoc Data Manager, Groundwork, and other FieldDoc applications, modules, tools, websites, interfaces, integrations, support services, professional services, and related services that we make available from time to time. This Privacy Policy explains how we collect, use, disclose, retain, and protect personal information when individuals create accounts, use the FieldDoc Platform or any Application, participate in an Organization, access a workspace, share data with a Program, request support, use professional services, interact with integrations, or otherwise communicate with The Commons. This Privacy Policy applies to individual Users, Authorized Users, Organization Owners, Organization Members, Program Managers, Customers, and other individuals who interact with the FieldDoc Platform or The Commons. This Privacy Policy should be read together with the FieldDoc Platform [Terms of Service](/service-agreements/terms-of-service), [Master Service Agreement](/service-agreements/master-services-agreement), and any Order Form, Statement of Work, Subscription Documentation, Data Processing Addendum, Program requirements, or Application-Specific Terms. If a written agreement between The Commons and a Customer provides additional or different privacy, security, data processing, or retention terms, that written agreement will govern that Customer relationship to the extent of the conflict. ### 1. Definitions For purposes of this Privacy Policy: **"The Commons"** means The Commons, Inc., the nonprofit organization that owns, manages, maintains, supports, and operates the FieldDoc Platform. **"FieldDoc Platform"** means the FieldDoc technology platform operated by The Commons, including its applications, modules, tools, websites, interfaces, data systems, APIs, integrations, documentation, workflows, and related technology. **"Applications"** means the individual applications, modules, products, tools, or service offerings made available through or in connection with the FieldDoc Platform, including FieldDoc Data Manager, Groundwork, and any other FieldDoc applications, modules, or products that The Commons may make available from time to time. “**Services**” means the FieldDoc Platform, Applications, software, documentation, hosting, support, technical services, professional services, data services, integrations, APIs, and related services provided by The Commons or FieldDoc under these Terms, a Master Service Agreement, Subscription Documentation, or other applicable agreement. **"User"** means an individual person who creates or uses a FieldDoc account or otherwise accesses the FieldDoc Platform or any Application. **"Authorized User"** means a User who is authorized by an Organization or Customer to access or use the FieldDoc Platform, an Application, workspace, record, Program, or other Service under that Organization's account, subscription, permissions, or written agreement. **"Organization"** means a real-world entity whose Users access or use the FieldDoc Platform. **"Customer"** means an Organization, entity, or individual that enters into a Master Service Agreement, Order Form, Statement of Work, subscription, paid plan, program agreement, grant agreement, or other written arrangement with The Commons for access to the FieldDoc Platform, Applications, Services, support, or professional services. **"Customer Data"** means data, records, files, geospatial information, activity information, project information, metrics, reports, attachments, and other materials submitted to, uploaded to, imported into, or generated through the Services by or on behalf of a Customer, Organization, User, or Authorized User. **"Personal Information"** means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked to an identifiable individual. **"Subscription Documentation"** means any Order Form, online subscription selection, pricing page, invoice, Statement of Work, support plan, grant agreement, program agreement, data retention policy, product description, or other written documentation that describes subscription tier, fees, features, services, usage limits, support level, data retention period, Application access, or other commercial or service-specific terms. Capitalized terms not defined in this Privacy Policy may have the meanings given to them in the FieldDoc Platform Terms of Service, applicable Master Service Agreement, or applicable Subscription Documentation. ### 2. Information We Collect We collect information in several ways, depending on how you interact with the FieldDoc Platform, The Commons, your Organization, and any applicable Programs or Services. #### 2.1 Information You Provide We may collect information that you or your Organization provide directly, including: * Name; * Work email address; * Organization name and affiliation; * Job title, role, or relationship to an Organization or Program; * Account credentials or authentication information; * Profile information; * Communication preferences; * Support requests, help desk communications, training communications, or other correspondence; * Billing, subscription, procurement, or administrative contact information; * Information submitted through forms, workflows, Applications, workspaces, Programs, Pacts, support channels, or professional services. #### 2.2 Account, Organization, and Platform Information We may collect information related to your account and your use of the FieldDoc Platform, including: * Account status; * Organization membership; * role and permission settings; * workspace access; * Application access; * Program participation; * support history; * subscription-related information; * feature usage; * login activity; * audit logs; * administrative records; * records of invitations, approvals, access changes, exports, submissions, or other platform activity. #### 2.3 Customer Data, Organization Data, and Project Data Users and Organizations may submit data, files, geospatial information, activity records, project records, metrics, reports, model inputs, model outputs, notes, attachments, images, exports, and other content through the FieldDoc Platform. Some Customer Data may include Personal Information or sensitive information if entered by Users, Organizations, Customers, Program Managers, or other authorized parties. The Commons processes Customer Data to provide, operate, secure, support, improve, and administer the FieldDoc Platform and related Services, and as otherwise described in the Terms of Service, applicable Subscription Documentation, or written agreements. #### 2.4 Automatically Collected Information When you access the FieldDoc Platform, we may automatically collect technical and usage information, including: * IP address; * device information; * browser type and version; * operating system; * pages, records, or features accessed; * dates and times of access; * referring pages; * session activity; * error logs; * diagnostic information; * cookie information; * similar technical, usage, performance, or security data. We use this information to provide the FieldDoc Platform, maintain security, troubleshoot issues, monitor performance, improve functionality, prevent misuse, support audit and administrative needs, and enforce our Terms of Service and applicable agreements. #### 2.5 Information from Organizations, Customers, Programs, and Third Parties We may receive information about Users from Organizations, Customers, Program Managers, collaborators, funders, technical assistance providers, service providers, or other third parties. For example, an Organization Owner may invite a User to join an Organization, a Program Manager may identify a reporting contact, or a Customer may provide contact information for subscription, support, onboarding, billing, or professional services purposes. If you provide Personal Information about another person or user to The Commons, you represent that you have the authority to do so and that the disclosure complies with applicable law, agreements, and Organization policies. ### 3. Information We Do Not Intentionally Collect The FieldDoc Platform is designed for conservation, restoration, nature-based work, environmental data stewardship, Program administration, reporting, and related activities. It is not intended to collect highly sensitive personal information unless The Commons expressly authorizes such collection for a specific purpose. Users should not enter, upload, or share the following information through the FieldDoc Platform unless expressly authorized and necessary for an approved FieldDoc purpose: * Social Security numbers, passport numbers, driver's license numbers, government identification numbers, or similar identifiers; * credit card numbers, financial account numbers, or payment card information, except through approved payment or invoicing systems; * protected health information; * biometric data; * precise personal location information unrelated to an authorized FieldDoc purpose; * information about children; * other sensitive personal information that is not necessary for use of the FieldDoc Platform. The Commons does not intentionally collect characteristics of protected classifications, such as race, ethnicity, religion, sexual orientation, gender identity, disability status, or similar information, unless that information is voluntarily provided by a User or is included in Customer Data submitted by a User, Organization, Customer, or Program. The Commons does not intentionally require Users to provide private land ownership details, such as landowner names, addresses, tax parcel records, deeds, financial information, or other sensitive property records, unless expressly requested by a Program, workflow, Application, or written agreement. Users and Organizations are responsible for ensuring that they have authority to enter, manage, or share any landowner, property, cultural, ecological, species-related, or location-sensitive information. ### 4. How We Use Information We may use Personal Information, Customer Data, and related information to: * Provide, operate, maintain, secure, and improve the FieldDoc Platform, Applications, and Services; * Create and manage User accounts, Organization accounts, workspaces, roles, permissions, Programs, Pacts, subscriptions, and support relationships; * Verify User identity, Organization affiliation, authority, Program participation, account eligibility, and platform permissions; * Provide customer support, training, onboarding, troubleshooting, technical assistance, professional services, data services, and administrative support; * Enable collaboration, sharing, reporting, exports, dashboards, maps, models, analytics, integrations, Program workflows, and other platform features; * Communicate with Users, Organization Owners, Program Managers, Customers, and other contacts about accounts, security, support, subscriptions, Programs, platform updates, service notices, policy changes, and related matters; * Analyze usage, improve services, develop new features, conduct product planning, perform user research, and support mission-aligned reporting; * Create aggregated or de-identified information for platform analytics, Program summaries, impact summaries, dashboards, reporting, system improvement, research, fundraising, communications, or other mission-aligned purposes; * Protect the FieldDoc Platform, The Commons, Users, Organizations, Programs, Customers, and third parties from security risks, misuse, fraud, unauthorized access, unlawful activity, or violations of our Terms; * Comply with legal obligations, contractual obligations, grant or Program requirements, audit obligations, valid legal requests, dispute resolution, and enforcement of our agreements. The Commons does not sell Personal Information or User, Organization, or Customer content. If The Commons makes AI-assisted features available through the FieldDoc Platform or an Application, those features may be subject to additional notices, Application-Specific Terms, Subscription Documentation, or written agreements. The Commons will not use Customer Data to train public or third-party AI foundation models unless authorized by the applicable Customer, agreement, or law. ### 5. How We Share Information We may share Personal Information, Customer Data, and related information with the following categories of recipients. #### 5.1 The Commons Personnel and Authorized Support Providers We may share information with The Commons staff, contractors, advisors, and authorized service providers who need access to provide, secure, support, administer, or improve the FieldDoc Platform or related Services. #### 5.2 Organizations, Users, Program Managers, and Collaborators The FieldDoc Platform is a collaborative platform. Depending on platform permissions, workspace settings, Program participation, Pact relationships, Application functionality, and Customer instructions, information may be visible or available to: * the User who created it; * Organization Owners; * Organization Members; * Authorized Users; * invited collaborators; * Program Managers; * funders; * technical assistance providers; * Customers; * Users with appropriate permissions; * other parties authorized by Program requirements, platform features, or separate agreements. Users and Organizations are responsible for understanding how permissions, workspaces, Pacts, public pages, dashboards, exports, integrations, and other FieldDoc features may affect visibility and sharing. #### 5.3 Vendors and Service Providers We may share information with vendors and service providers that support hosting, cloud infrastructure, security, analytics, communications, email, customer support, ticketing, mapping, geospatial services, authentication, storage, processing, backups, professional services, and other operational needs. These vendors and service providers are authorized to use information only as necessary to provide services to The Commons or as otherwise permitted by applicable law or agreement. The Commons may update its vendors and service providers from time to time. #### 5.4 Third-Party Services, APIs, and Integrations The FieldDoc Platform may interoperate with third-party services, APIs, dashboards, integrations, mapping tools, model APIs, data import tools, export tools, or other external systems. Data transmitted to authorized third-party services may be processed, stored, analyzed, displayed, or returned according to the purpose of the integration and the terms, policies, and security practices of the receiving service. Users, Organizations, Customers, and Program Managers are responsible for understanding when their use of the FieldDoc Platform or an Application causes data to be shared with third-party systems. #### 5.5 Legal, Compliance, and Safety Purposes We may disclose information to courts, regulators, law enforcement, government authorities, public agencies, or other parties when required by law, legal process, public records obligation, subpoena, court order, governmental request, or to establish, exercise, or defend legal rights. We may also disclose information where reasonably necessary to investigate, prevent, or address security incidents, fraud, misuse, unlawful activity, violations of our Terms, threats to safety, or risks to the FieldDoc Platform, The Commons, Users, Organizations, Customers, Programs, or third parties. #### 5.6 Organizational or Platform Transitions We may disclose or transfer information in connection with a merger, restructuring, reorganization, transition, transfer, assignment, or other change involving the FieldDoc Platform, related assets, or The Commons's operations, subject to appropriate protections and applicable law. ### 6. Collaborative Features, Visibility, and Exports FieldDoc privacy settings and permissions control certain access within the platform, but they may not control information after it has been exported, downloaded, transmitted, shared through an integration, disclosed under a Program requirement, or otherwise transferred outside the FieldDoc Platform by an authorized User or recipient. No data entered into the FieldDoc Platform should be considered fully private or confidential from all other parties. Users and Organizations should not enter sensitive, confidential, restricted, proprietary, culturally sensitive, ecological, landowner-related, location-based, or legally protected data unless they have authority to do so and understand how the data may be viewed, shared, exported, analyzed, displayed, retained, or disclosed. Nothing in this Privacy Policy limits any confidentiality obligations The Commons has under a Master Service Agreement, Data Processing Addendum, Statement of Work, grant agreement, or other written agreement. ### 7. Aggregated and De-Identified Information The Commons may use aggregated or de-identified information derived from use of the FieldDoc Platform for product improvement, research, analytics, benchmarking, sector-level reporting, platform performance, public impact summaries, fundraising, communications, and other mission-aligned purposes. Aggregated or de-identified information should not reasonably identify a specific User, Organization, Customer, private record, or sensitive location unless authorized. The Commons will use reasonable measures designed to prevent de-identified information from being used to identify individuals where applicable law requires such measures. ### 8. Cookies and Similar Technologies We use cookies and similar technologies to operate the FieldDoc Platform, maintain sessions, remember preferences, support authentication, improve performance, understand feature usage, troubleshoot issues, and protect security. Some cookies are necessary for the FieldDoc Platform to function. If you disable cookies, some features may not work properly. We may also use analytics or support technologies to understand platform usage and improve Services. Where required by law, we will provide any required choices or consent mechanisms for non-essential cookies or similar technologies. The FieldDoc Platform does not currently respond to "Do Not Track" browser signals. Where required by applicable law, The Commons will honor legally required opt-out preference signals or other required mechanisms. ### 9. Communications The Commons may contact Users by email, through the FieldDoc Platform, or through other reasonable methods to provide: * account notices; * security notices; * support messages; * release notes; * service updates; * Program-related notices; * subscription or administrative notices; * policy updates; * training, onboarding, or professional services communications; * community updates or mission-related communications. Some communications are necessary for account, security, Program, legal, or platform administration and may not be optional. You may unsubscribe from optional marketing or community communications where an unsubscribe option is provided. Even if you unsubscribe from optional communications, we may still send transactional, security, account, support, Program, legal, or administrative communications that are necessary to operate the FieldDoc Platform or manage your account. ### 10. Data Retention We retain Personal Information, Customer Data, and related information for as long as reasonably necessary to provide the FieldDoc Platform and Services, maintain accounts, support Organizations and Programs, comply with legal or contractual obligations, resolve disputes, maintain security, support audits, preserve backups, enforce agreements, and fulfill authorized Program, reporting, grant, or professional services obligations. Retention periods may vary depending on the type of information, the applicable Application, subscription tier, Program participation, Organization status, Customer instructions, Subscription Documentation, legal requirements, backup procedures, or written agreement. Deleting an individual User account does not necessarily delete Organization records, Program records, Pacts, Activities, project data, files, reports, metrics, geospatial information, model outputs, audit logs, or other records created or managed by that User on behalf of an Organization or Customer. Those records may remain available to the Organization, Program, Customer, or other authorized parties as described in the Terms of Service, applicable Subscription Documentation, or written agreements. Upon request, The Commons will delete or deactivate an individual User account and associated Personal Information, subject to legal, compliance, security, backup, audit, Program, contractual, and operational retention obligations. Deleted information may continue to exist in backups, archives, logs, or disaster recovery systems for a limited period consistent with our backup, security, legal, and operational practices. Users, Organizations, Customers, and Program Managers are encouraged to use available export features to preserve critical data outside the FieldDoc Platform when appropriate. ### 11. Security The Commons uses reasonable administrative, technical, and organizational safeguards designed to protect Personal Information and Customer Data against unauthorized access, loss, misuse, alteration, or disclosure. These safeguards may include access controls, authentication controls, role-based permissions, secure hosting practices, encryption in transit, backup procedures, logging, monitoring, vulnerability management, administrative controls, and vendor security practices appropriate to the nature of the FieldDoc Platform and the information we process. No method of transmission or storage is completely secure. The Commons cannot guarantee absolute security. Users are responsible for maintaining the confidentiality of their credentials, using appropriate account security practices, and promptly notifying The Commons of any known or suspected unauthorized access to their account, Organization, workspace, or data. If The Commons confirms a security incident involving Personal Information or Customer Data, The Commons will provide notice as required by applicable law and any applicable written agreement. ### 12. Your Choices and Privacy Rights Depending on where you live and how you interact with the FieldDoc Platform, you may have rights to request access to, correction of, deletion of, or information about certain Personal Information we maintain about you. You may also have rights to object to, restrict, or opt out of certain uses of Personal Information where applicable law provides those rights. To make a privacy request, contact us at ****. We may need to verify your identity and authority before responding. Your account's association with an Organization, Customer, Program, or written agreement may require additional coordinate with the relevant Organization Owner, Customer, or Program Manager as appropriate. Some requests may be limited by legal obligations, security requirements, backup procedures, Program or grant obligations, contractual obligations, audit requirements, or the rights and responsibilities of an Organization, Customer, or other authorized party. We will not discriminate against you for exercising privacy rights provided by applicable law. If you believe that information we maintain about you is inaccurate, outdated, incomplete, irrelevant, or misleading, you may contact us to request correction. We will take reasonable steps to correct information where required by applicable law and where correction is technically and operationally feasible. If you believe that we have violated applicable privacy law, you may contact us using the information below. We will review your complaint and respond within a reasonable timeframe. You may also have the right to contact a regulatory authority or data protection authority. ### 13. Children and Age Restrictions The FieldDoc Platform is not intended for individuals under 18 years old. Users must be at least 18 years old to create a FieldDoc account or use the FieldDoc Platform. If you learn that anyone under 18 has provided Personal Information to The Commons through the FieldDoc Platform without authorization, please contact us at ****, and we will take appropriate steps to address the information. ### 14. International Use and Data Transfers The Commons operates the FieldDoc Platform from the United States, and information submitted to the FieldDoc Platform may be processed and stored in the United States. If you access or use the FieldDoc Platform from outside the United States, you understand that your information may be transferred to, stored in, and processed in the United States or other locations where The Commons or its service providers operate. Additional terms may apply under an applicable Data Processing Addendum, Subscription Documentation, or written agreement. ### 15. Third-Party Sites and Services The FieldDoc Platform may link to or interoperate with external sites, applications, APIs, integrations, dashboards, maps, data sources, or other services that are not operated by The Commons. The Commons is not responsible for the privacy, security, content, policies, or practices of third-party sites or services. Users, Organizations, Customers, and Program Managers should review the privacy policies and terms of those third-party services before using them or transmitting data to them. ### 16. Changes to This Privacy Policy The Commons may update this Privacy Policy from time to time to reflect changes in our practices, Services, Applications, technology, legal requirements, or operational needs. If we make material changes, we will provide reasonable notice, which may include posting the updated Privacy Policy on the FieldDoc website, providing notice through the FieldDoc Platform, sending notice to the email address associated with your account, or using another reasonable method. Unless otherwise stated, updates will become effective when posted or otherwise made available. Your continued use of the FieldDoc Platform, any Application, or any Services after the updated Privacy Policy becomes effective means that you acknowledge the updated Privacy Policy. If required by law, we will obtain consent or provide an opportunity to opt in or opt out of certain new uses of Personal Information. ### 17. Contact Us If you have questions about this Privacy Policy, The Commons's privacy practices, your account, your Organization, or your privacy rights, please contact us. **Email:** **Mailing address:** The Commons, Inc.\ 200 Massachusetts Ave NW\ Washington, DC 20001
# FieldDoc Guides ### Program Guides Funding Program Guides provide details on data entry and management for specific funding opportunities. If you have programmatic questions, we recommend that you reach out to your funding program manager.
Cover image
Chesapeake & Atlantic Coastal Bays Trust FundMaryland Department of Natural Resources/pages/RT99lMhwLU2f1upS2ttz/files/sFcpuSox7zro6EhYGFqk
Chesapeake Bay Stewardship FundNational Fish and Wildlife Foundation/pages/LJvOZxLAdAXBMZ4kruKH/files/qpt3dz6aM1Z3HgyjdEGj
Delaware River ProgramNational Fish and Wildlife Foundation/pages/2lpmknqDRwI9Ziw6VwOp/files/r3bhaT4umIEZZp1iJP54
## User Guides
Technical Service Providers/pages/XefQ0sdAj1dD0zyphI90
# Chesapeake Bay Stewardship Fund Funding Organization Lead: National Fish and Wildlife Foundation ## CBSF Available RFPs For detailed instructions on submitting your application, please visit the RFP documentation. Be sure to adhere to all guidelines and deadlines stated in the RFP.
Innovative Nutrient and Sediment ReductionFull Proposal by Invite OnlyUse the Guide/pages/kjQVJrJ3FAhkiZE7fBmS
Small Watershed GrantsPact Code: 78JCSWG Guide
Chesapeake WILDPact Code: 9GM6WILD Guide
# 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. {% hint style="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. {% endhint %} ## 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. {% @arcade/embed flowId="NRyipVR9TyyoW1Kbga19" url="" %} ## Commonly asked questions ### Account management and collaboration
Who should use FieldDoc? 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. {% @arcade/embed flowId="hhJFFWQ3pgSlLtR6rP48" url="" %}
How do I add someone from outside of my organization? 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. {% @arcade/embed flowId="hhJFFWQ3pgSlLtR6rP48" url="" %}
I can't log in to my account. Reach out to . 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
What is a pact? 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.
Where did my projects go? 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.
What should my activity records represent? 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
What "counts" as a pact geometry? 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.
What do I model? 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.
Why can't I use a large polygon for my model run? 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.
Can I add multiple BMPs to one model run? 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.
What do I enter for my application versus reporting during my period of performance? 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.
Do I need to add non-modeled, programmatic metrics? 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.
# CBSF Grant Reporting Guide Follow these steps for guidance on how to complete a final report for a NFWF CBSF grant You've reached the end of your grant’s period of performance! Now it’s time to submit your final report. We’re here to help you prepare your FieldDoc pact to meet your reporting requirements. This guide will walk you through how to prepare your FieldDoc pact so it meet's NFWF’s final reporting requirements. By the end of this guide, your pact will have digital representations of *what* work was implemented, *where* the restoration work occurred, *how much* impact it had on meeting target goals. NFWF Program staff will be reviewing your FieldDoc pact, which contains all of the activities records that you implemented, to make sure that it aligns with the information reported in Easygrants. Your final updates in FieldDoc will involve a combination of the following steps: remove demonstration entries, create new activities, adjust activity extent, adding metrics, reporting implementation progress, or re-running models of sediment and nutrient loads. Whatever your final report requires, this guide is designed to walk you through it—clearly and completely—so you can feel confident that your FieldDoc data meets the expectations for final submission. {% hint style="warning" %} This guide assumes that you have a basic understanding of how data is managed and shared in FieldDoc. If you are new to the system, we recommend looking at the documentation to orient yourself to how the system works. {% endhint %} ## **Final Report Optional Tasks List** These are optional tasks you may need to perform to complete your final report: * [ ] Remove demonstration or placeholder activities. [→](#remove-demonstration-activities-from-your-pact) * [ ] Create new activities that were not included in earlier reporting. [→](#create-new-activity-records-with-verifiable-implementation-data) * [ ] Edit existing activities, such as changing the extent or geometry, if needed. [→](#edit-existing-activity-records) * [ ] Review and update metric implementation progress to reflect actual outcomes. [→](#step-2.-update-your-programmatic-metrics-implementation) * [ ] Add the installation completion date. [→](#step-3.-add-completed_on-dates-to-all-activities) * [ ] Ensure all required fields and documentation are complete [→](#step-4.-review-your-data) * [ ] Confirm that your Pact is ready for submission to NFWF [→](#step-4.-review-your-data) ## Get Started. Find your Pact Every grant award should have a single pact in FieldDoc. This pact will have all of the work that you proposed in your original application. When you open the Pact, you will arrive on the Pact Overview Page. Activity records can be added or removed from this pact. {% @arcade/embed flowId="un0j2rZnjFzV68w6rBb1" url="" %}
What is a Pact? Pacts were introduced in FieldDoc in November 2024 as a new way to organize and share data with funders. A Pact is the mechanism through which an organization shares a group of activity records from your organization's portfolio funders like NFWF. This change marked a major update to how FieldDoc structures and tracks implementation data. If your FieldDoc records were created before November 2024, you used a **Project** to organize and share your work. It was automatically shared with NFWF. Projects still exist as folders that contain your activity records, but they are no longer visible to NFWF. Funders now view data exclusively through **Pacts**. To support your final reporting, The Commons created a Pact for your grant and linked all associated activity records from the original Project. This ensures that the information you update will be correctly shared with NFWF as part of your final report. {% hint style="warning" %} Any new activity records that you create in a Project are not visible to NFWF until you add them to the Pact. {% endhint %}
Tips on finding your Pact. * The Pact name matches the name of your project in your grant award and includes the easygrant ID. * If you cannot find your pact in your workspace, there is a good chance someone outside of your organization created it, such as a consultant; and when they created it they did so in their organization instead of yours. You want to be the owner of all of your records and have access to everything. Please reach out to so that you can re-gain access to your Pact and associated activity records.
## Step 1. Update your records to represent your own-the-ground implementation activities A pact collects activity records from your organization's portfolio and shares them with a funder. The records that are linked to a pact remain in your organization's portfolio. {% hint style="info" %} Activity records from one organization's workspace portfolio can be shared to multiple pacts. Activity records can only belong to a single organization workspace - you cannot add records from different organizations to the same Pact. {% endhint %} You can create or edit activity records within the existing pact. The goal is for the activity records in your pact to represent the on-the-ground activities accomplished as a result of this award. Spend some time cleaning up your records until they meet this requirement. ### Remove demonstration activities from your pact When you submit your final report, all activity records should be verifiable sites. If you used demonstration data in your application, you'll want to de-link these activity records from the pact. {% @arcade/embed flowId="dtzYIMrqcy9cvSnaHHJE" url="" %} {% hint style="danger" %} If you *delete* an activity record in your pact, it will be deleted from your portfolio. If you *de-link* the activity record, it will be removed from the pact but will remain in your workspace portfolio. {% endhint %} ### Create new activity records with verifiable implementation data Need to add new activity records to your pact? You can either create new records in your pact or link existing records from your portfolio. Each activity record may include the following information: * [ ] **Activity Name.** give the record a unique, searchable name * [ ] **Activity Type.** designate a standard practice and, if relevant, connects the activity to the associated model * [ ] **Geometry.** indicate implementation location * [ ] **Model.** estimate sediment and nutrient reductions * [ ] **Programmatic metrics** set a target for non-modeled outcomes. {% @arcade/embed flowId="ja352H6CRZnBW2gGTX3s" url="" %} ### Edit existing activity records All activity records should represent verifiable work that was implemented. You may want to review the activity record information for all activities in your pact. Each activity record may include the following information: * [ ] **Activity Name** Revise the common name - make sure it's unique! * [ ] **Activity Type** re-assign a standard practice - this will force you to re-run the model * [ ] **Geometry** change an implementation footprint * [ ] **Model** estimates sediment and nutrient reductions * [ ] **Programmatic metrics** set a target for non-modeled outcomes. {% @arcade/embed flowId="44PlDnwN70JFa8C50vFS" url="" %} ## Step 2. Update your Programmatic Metrics Implementation {% hint style="info" %} This step applies to **programmatic metrics**, which are manually tracked and updated in FieldDoc. It does not apply to estimated sediment, nutrient, or load reductions generated by FieldDoc models. FieldDoc **model** results are based on the activity inputs provided when the model is run. The model outputs provide calculations for what the reduction will be when the activity is implemented. Therefore, the calculation you created during your record creation is still the calculation that is included in your summary when your record is complete. No action changes the model result other than changing the input value. For example, marking an activity as complete does not automatically change the model results, and you do not need to rerun a model unless the underlying input values have changed. {% endhint %} Metrics are tracked within individual activity records. When you created your records in FieldDoc, you selected metrics from NFWF's programmatic metric list and set `planned_values` for each metric. Now that you've arrived at the end of your period of performance, it's time to enter in your `implemented_values`. From the Pact Metrics Tab, you can quickly enter in the `implemented_value`. {% @arcade/embed flowId="J0RH2qBOse9WRv2YcY3k" url="" %} ## Step 3. Add `Completed_on` dates to all activities Within each activity record there is a field where you can enter the `completed_on` date. This date should represent when the activity was installed to specification. This date is important because it is used by NFWF to complete NEIEN reporting requirements relevant to this implementation work. {% @arcade/embed flowId="5QgpBryRfcVtamsZWsQX" url="" %} ## Step 4. Review your data Let's take a look at your Pact overview page and make sure that everything meets the requirements for NFWF. 1. **Recipient organization** is the same as the grant award recipient. 2. All "demonstration" data has been removed and replaced with verifiable representations of on the ground, implemented activities. 3. **Models** have been run with the latest extent data. 4. All **Programmatic Metrics** listed on the Pact match what is listed in your Easygrants account. 5. All programmatic metrics have both `planned_values` and `implemented_values` and they match. 6. Each activity record has a `completed_on` date. {% @arcade/embed flowId="jgKuI4aKAf9Rsk0XEb4N" url="" %} ## Step 5. Upload a screenshot of your overview page to your Easygrant report NFWF asks that you upload a file with the FieldDoc pact overview page to your final report. We recommend take a screenshot of the overview page and uploading that. Alternatively, you can print this page to pdf and import that view. # SWG and WILD RFP ## Submit a CBSF Application ### Training tutorial: Create a pact {% @arcade/embed flowId="g2pqWOcjKcwpIaan2HO0" url="" %} ### Walk through creating a pact and adding activities {% embed url="" %} ### Apply for funding The following walks through the key steps to completing the FieldDoc portion of your application. {% stepper %} {% step %} ### Create FieldDoc Account To use FieldDoc, you must create an account within your organization of employment. All lead application organizations must have a FieldDoc account. :seedling: Learn More: [Create Account](/manage-your-organization/user-account) {% endstep %} {% step %} ### Navigate to the workspace of the lead applicant Collaborators and technical service providers should create accounts within their own organizations, then be invited into the applicant organization’s workspace to help configure the Pact. {% endstep %} {% step %} ### Create a Pact A pact is like an envelope through which these records are shared. * From the Home Page, click "Apply for Funding". * **Pact ID**. Find the funding opportunity's unique Pact Code [here](#cbsf-rfps). * **Pact Name**. Your pact name must ***include your application's Easygrant ID*** and the ***Project Title*** as it appears in your application. Once a pact is created, you can create records and add programmatic metrics. * **Pact Description.** This is an optional field where you can add information relevant to your proposal or notes for your team. It is visible to everyone who can see this pact. {% endstep %} {% step %} ### Link Activity Records to the Pact Activity Records capture the on-the-ground work that will be completed through the proposed funding. You can create new activity records in the pact or link existing records from your portfolio. Activity records should include: * A unique activity name * Assign the `Activity Type` * A footprint of the implementation location * Run the Adapted CAST model to estimate sediment and nutrient load reductions {% endstep %} {% step %} ### Calculate sediment and nutrient load reductions Models must be manually run for each activity, they are not automatically calculated. * Open the edit activity modal for a record. * Navigate to the **Models** tab. * Review the required inputs. Enter the input as instructed. * Click Run. {% endstep %} {% step %} ### Switch status to Submitted. For Program Managers to review your FieldDoc data, you must submit the Pact by changing the status to "Submitted". Follow any additional guidance provided in the RFP to complete your application. {% endstep %} {% endstepper %} ### Review your submission * [ ] I have **created a Pact** within the correct funding opportunity RFP to which I am applying. * [ ] The **Recipient** matches the lead applicant organization in the application. * [ ] The **Pact Name** includes the grant application ID. * [ ] All ame matches my project proposal title and of proposed activities are linked to the Pact. * [ ] I have calculated the sediment and nutrient load reductions for each record. #### Final submission steps * [ ] Do you need to upload a pdf of FieldDoc to your application? FieldDoc does not have an in-app PDF converter. To create an uploadable file, please use your browser's print option or capture a screenshot of your Pact overview page to upload to your application. *** ## FAQs - Creating a proposal
Do I have to use FieldDoc for my Proposal? **2026 Small Watershed Grants**: NFWF requires all applicants proposing to implement water quality improvement actions to utilize FieldDoc to calculate estimated load reductions. Those load reductions will be uploaded to the Easygrant application. *** **2026 Chesapeake WILD:** Are you proposing implementation of activities that will improve water quality? If yes, then you should use FieldDoc to calculate the sediment and nutrient load reductions. No other applicants need to use FieldDoc during the application stage. *** **2026 Innovative Sediment & Nutrient Reduction**: Please ask your Program Manager for specific guidance.
Which BMP should I select as my Activity Type? The FieldDoc team cannot provide guidance on specific BMPs. If you are unsure which BMP to select, we recommend reaching out the the NFWF Field Liaisons, NFWF Program Managers, or reviewing [CAST BMP Documentation](https://cast.chesapeakebay.net/Documentation/BMPs).
What should the geometry represent? Each Activity record must have corresponding geospatial component to represent the implementation footprint. You can use a point, line, or polygon to delineate your activity area. * ***I know my implementation location***. If the implementation area is known, please delineate the actual footprint to the best of your ability. * ***I do not know my implementation location.*** If the implementation site has not yet been determined, use a point or polygon to indicate a general location. Make sure to indicate in your activity record name and description fields that this is a demonstration site. When running the model, input the estimated total extent value to calculate load reductions. FieldDoc has options for how to delineate geometries to activity records. 1. If you have a .csv, shapefile, or GeoJSON file, use [**import**](/essentials/import#import)**.** You can import a *single* geometry or batch import *multiple* geometries. Each row will create a new activity record. 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.
I don't think FieldDoc is providing an accurate model output for TN, TP, or TSS? It is accurate. FieldDoc is using an Adaptive CAST efficiency table provided to us by the CAST modelers. If you do not agree with the outputs, you are welcome to clear the model inputs and enter in your own custom `TN`, `TP`, and `TSS` outputs within the **Programmatic Metrics** list!
How do I turn on the models? Models do not run automatically. Open the **Edit Activity** modal and switch to the **Run Model** tab. Follow the prompts to input values into the required fields. Click run.
I don't know where I'm working yet. Do I need to put in geometry types? At the application stage, you can use representative locations for your application if you have not yet chosen the implementation locations. Representative locations should look like a verifiable installation site. **Do not use a large geometry that covers a large area to indicate where you are working.** Make sure to indicate in the activity name field that this is a representative site. If awarded funding, by the end of the period of performance your FieldDoc records must delineate actual installation sites for restoration work.
I want to use an alternative sediment and nutrient load reduction estimate. How do I associate those with my activity records? You do not need to run the adapted CAST model for any of your activity records if you have alternative outputs that you would like to use. Once your activity record has been associated with the Pact, find the following programmatic metrics in the available list: `Total Nitrogen (custom)` `Total Phosphorus (custom)` `Total Suspended Solids (custom)` Enter in the values that you have calculated in the `planned_value` field. NFWF may ask that you provide the calculations to defend your alternative values. You can upload your calculation documentation to the **Documents** tab within the **Activity record** or **Pact**.
I have a technical service provider creating my proposal. How should we proceed? FieldDoc is optimized for collaboration. **The Pact must be owned by the organization that is submitting the proposal**, which means that the organization submitting the proposal must have a FieldDoc account. Once the organization is in FieldDoc, the organization user can invite collaborators from outside of their organization to their [workspace](/manage-your-organization/workspaces) or to their [Pact](/essentials/pacts). We recommend that you invite your technical service provider to your workspace. Once in the organization's workspace, any member of the workspace can create, edit, or delete records on behalf of that organization. The pact created within a workspace will be owned by that workspace. **Technical service providers should not make pacts for their clients in the TSP's account.**
Is my proposal ready to submit? Here's a checklist to use to make sure you've followed the requirements. * [ ] I have created a [Pact](/essentials/pacts#create-a-pact) within RFP to which I am applying. * [ ] The **organization name** listed as the recipient on the Pact matches the lead applicant organization in Easygrants. * [ ] The **Pact name** matches my *Project Proposal Title* and includes the *Easygrants ID*. * [ ] [Activity](/essentials/activities) records have been linked to the Pact that represent the proposed activities that will be completed, if funded. Each activity record includes: * [ ] The [programmatic metric](/essentials/activities/activity-metrics#programmatic-metrics) `planned_values` in FieldDoc match those in Easygrants. * [ ] [Geometries](/essentials/activities/geometry) have been added for each activity record that delineate the implementation location or a representative site. * [ ] I have run the nutrient and sediment load reduction model. * [ ] Hit **submit**.
## FAQs - Sharing data to NFWF's Easygrant System
How do I create a PDF of my Pact? FieldDoc does not have a 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.
How do I convert geospatial exports from FieldDoc to import into Easygrants? At the time that these FAQs were written, Easygrants only accepts 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. FieldDoc offers three geospatial files in the export package. The .csv, .GeoJSON, and Geopackage formats which allow for more analytical flexibility of extended use. 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. If you require assistance in using the easygrants geospatial tools, please reach out to .
## FAQs - Tracking Implementation
How do I replace representative records with my actual work? 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.
Do I need an activity record for every location where we conducted work? 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.
Do I need to create records for my Match? The activity records in your Pact and the programmatic metrics should align with the work that is documented in your Easygrant report.
How do I update the TN, TP, and TSS measurements? The FieldDoc models that estimate the TN, TP, and TSS assume installation of the activity (BMP). Therefore, there is no way to track implementation progress on these modeled outcomes. Once you run the model, you are finished.
When do I need to use FieldDoc for implementation tracking? **SWG Tracking Implementation** – Upon grant award, NFWF will require all projects submitted under this solicitation to utilize FieldDoc for tracking and reporting of on-the-ground conservation and restoration activities resulting from their grant project.
## FAQs - System Updates and the impact on my project FieldDoc 2.0 builds on the legacy FieldDoc platform that was in operation until November 2024. All of the data that was entered into the legacy system is preserved and accessible in FieldDoc 2.0. The following answer some common questions about the migration and platform update.
What is a Pact? Legacy FieldDoc had limited functionality, automatically sharing all project data immediately with funders. This approach significantly restricted usability for our most important audience—on-the-ground restoration professionals. In FieldDoc 2.0, we've redesigned the structure so organizations can build comprehensive portfolios of their nature-based activities and selectively share these records with funders. Organizations can now share the same records with multiple funders. If your organization primarily uses FieldDoc to fulfill reporting requirements and you're familiar with the legacy system, you can continue using FieldDoc 2.0 similarly: create a Pact, then add activity records to that Pact. The key point to remember is that **only records attached to a Pact are visible to the Funding Program manager.**
Why do I have a Project and a Pact with the same name? When The Commons released **FieldDoc 2.0**, we ensured that all existing data was migrated into the new system and made available within the new data model structure. Because all activity records (formerly called practices) were initially created through Projects, and all Projects were associated with funding programs, we automatically created a Pact for each Project during migration. If you have activity records that did not receive funding or were never intended for a funding application, you may now delete the associated Pact. The activity records and their project classifications will remain intact.
I created a new practice (now called activity record) in my Project. Why can't I add programmatic metrics? Projects are no longer automatically shared with funding program managers. Projects no longer automatically include access to programmatic metrics. Therefore, in order to add programmatic metrics to an activity record, make sure to link the activity record to the correct Pact first. Once the activity record is linked, you can access the programmatic metrics and assign the correct ones to your activity.
How do I turn on the models? In Legacy FieldDoc, models were automatically turned on for every practice. We have removed the automation to give users more autonomy over the data associated with their portfolio. To turn on models, in an activity record: 1. Open the **Edit Activity** modal 2. Assign an `activity type`, 3. Select the **Models** tab, enter the `Unit Value` 4. Click **Save**. You can also turn off models by selecting the Clear button or Reset button.
I can't find a project that I used to be able to see. Where did it go? If you cannot find a project that you used to have access you, then you need to reach out to your collaborators and ask for them to add you as a Workspace Collaborator.
## Get updates ## NFWF Chesapeake Bay Stewardship Fund Visit the NFWF website to learn more about this program and its important work. ### Program Contacts Jake Reilly, Program Director Oleksandr Faryga, Program Manager Ragan Smith, Regional Program Coordinator Victoria Moreno, Regional Program Coordinator # Delaware Watershed Conservation Fund Funding Organization Lead: National Fish and Wildlife Foundation ### Program Contacts Erin Lewis, NFWF Delaware River Program Director - Ragan Smith, NFWF Coordinator, Northeastern Regional Programs - [ragan.smith@nfwf.org](http://ragan.smith@nfwf.org/) ## DWCF Awards: Tracking Implementation DWCF applicants and grantees are no longer required to track implementation of their activities for NFWF funded work in FieldDoc. Access your pact and activities linked to the pact will be frozen after November 30, 2026. 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. ## FAQs - Creating an proposal
Do I have to use FieldDoc for my Proposal? **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.
Which BMP should I select as my Activity Type? Choose the activity type that best aligns with the work that you are doing. Use the `description` field to provide more detail.
What should the geometry represent? 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.** 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.
I don't think FieldDoc is providing an accurate model output for TN, TP, or TSS? 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.
How do I turn on the models? Standard users can access models through the **Tools/Models** tab.
I don't know where I'm working yet. Do I need to put in geometry types? 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.
I have a technical service provider creating my records. How should we proceed? 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. 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.
## FAQs - Sharing data to NFWF
How do I create a PDF of my Pact? 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.
How do I get my FieldDoc geospatial data into NFWF's Easygrants system? 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 for assistance.
## FAQs - Tracking Implementation
How do I replace representative records with my actual work? 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.
Do I need an activity record for every location where we conducted work? 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.
How do I update the TN, TP, and TSS measurements? Re-run the model that is associated with an activity record.
# DWCF 2026 Application Guide # DWCF FieldDoc Set Up Guide Hello! Congratulations on your National Fish and Wildlife Foundation Delaware River Program Award! As part of your grant compliance, you are asked to use FieldDoc to track the implementation location and impact of your activities. This guide walks you through how to create and maintain this data. #### Step 1: Open the Correct Pact Navigate to the pact associated with your grant or program. All activity records must be created within the correct pact. #### Step 2: Create an Activity Record For **each completed activity**, create one activity record. Each activity record must include: * **Location**\ Add spatial data showing where the activity took place. * **Activity Type**\ Select the activity that was implemented from the provided activity list. * **Outcomes and Impacts**\ Enter modeled sediment and nutrient load reductions and all required programmatic metrics. #### Step 3: Review for Completeness Confirm that all required fields are filled out and that the information accurately reflects the completed work. #### Step 4: Submit the Pact Once all required activity records are complete, click the **“Finished”** button in the pact. Submitting the pact confirms that your data entry is complete and ready for program review. *** # MDNR Chesapeake & Atlantic Coastal Bays Trust Fund Maryland Department of Natural Resources Get updates All applicants are required to use FieldDoc to estimate nitrogen, phosphorus and sediment reductions. Any proposal that does not include calculations from FieldDoc will not be considered. ### Program Contact If you have programmatic or custom model questions, please reach out to Ari Engelberg: ## Pact Code & RFP
Chesapeake & Atlantic Coastal Bays Trust Fund RFPRFP Detailshttps://dnr.maryland.gov/ccs/Pages/funding/grantsgateway.aspx
FieldDoc Pact Code3WP9
FieldDoc training webinar Register HereNovember 9, 2026
{% hint style="danger" %} **Important: Required for MDNR Grant Review** ***Failure to follow these requirements may delay or prevent MDNR review of your application.*** 1. You will be required to share a **FieldDoc Pact** as part of your Grants Gateway application. **Program Managers can only view activity records that are correctly linked to this Pact and created in the correct workspace.** Projects and activity records within a project are not visible to program managers. 2. **For Technical Service Providers.** Ensure that you are working within the **lead applicant’s workspace**. Records created in the wrong workspace **cannot be linked between workspaces** for review. {% endhint %} ## Learning Objectives Please take advantage of this documentation as a first step when utilizing FieldDoc. The [DNR](mailto:ari.engelberg@maryland.gov) and[ FieldDoc staff](mailto:support@fielddoc.org) are available to answer your questions to support your application. After reviewing this guide, you’ll have the knowledge needed to: * **Build a Pact**. Your pact must include a record for each implementation sites proposed in your grant application. These are activity records. Within each activity record you will delineate a footprint and run a model to estimate sediment and nutrient load reductions. That's it! * **Grab the shareable FieldDoc Pact URL.** You will put this URL into your application in Grants Gateway. If you put in the wrong URL, the reviewers cannot access the FieldDoc portion of your application. FieldDoc routinely releases system updates. **Users must follow the instructions in this guide to make sure your application is received by the Chesapeake and Atlantic Coastal Bays Trust Fund Program Managers.**
Important reminders before starting your application. 1. MDNR Trust Fund Reviewers can *only* see records within a submitted pact. **Do not share Activity Record or Folder URLs.** 2. The Pact will be "owned" by the organization of the [workspace](/manage-your-organization/workspaces) in which the pact was created. The Pact must be created within the official applicant's workspace. Before getting started, add your technical service providers and contractors to the main applicant's workspace. Once added, these users can create Pacts on the client's behalf. 3. **Do not re-use old activity records that have already been created.** Create new activity records for your FY28 application.
## Getting Oriented Your FieldDoc task is to build your pact and activity records to share with the the Trust Fund Review Team. The majority of your time in the system will be spent preparing your activity records. ### Opening your workspace * A **Workspace** is an organization’s working area in FieldDoc. It contains a distinct Portfolio of Activities, folders, Pacts, Metrics, and other records that users with access can create, organize, review, and update. Users may access a Workspace through their Organization or be added as a collaborator when they need to work with another organization’s records. * Create the application's [pact](/essentials/pacts) within the workspace of the official grant applicant. If this application is a collaboration, the lead applicant organization can invite other FieldDoc users to their workspace in order to properly create the Pact and associated record data. ### What's a Pact? * A **Pact** is the digital container for a single application. It shares access to the activity records and modeling outputs associated with one grant submission. {% hint style="info" %} **Each Grants Gateway application will have a single Pact.** Do not create a separate Pact for every proposed implementation project within your application. Data can be created directly within the Pact, or it can be linked from a workspace portfolio. {% endhint %} ### What's an Activity Record? **Activity records are the representation of one discrete restoration action** (e.g., a riparian buffer, a stream restoration) with spatial location, type, and associated model outputs. * Within each activity record you will input: * **Activity Name** - A unique name that references the proposed project activity * **Activity Type** - Chosen from a standard list, will ‘turn on’ access to any applicable models * **Geometry** - use a point, line, or polygon to indicate the implementation area. The geometry collects critical information for many models. * Model sediment and nutrient load reductions - input a unit and click run to generate sediment and nutrient load reductions with the model associated with the activity type that was selected. The information inputted within each activity record will appear in summary on the Pact overview page and via the Pact Atlas. {% hint style="success" %} All data will become visible to the Trust Fund Managers **after the Pact is Submitted.** {% endhint %} ## Step-by-Step Guide Now that you've been familiarized with key FieldDoc terms, it's time to set up your FieldDoc pact. Follow along as we on-board a new user and their technical service provider so as they create their Trust Fund Application. > `Calvert Conservation` is a new group working to reduce runoff in Maryland by partnering with ag producers, nonprofits, and engineers. They’re applying to the Trust Fund to restore three streams and install riparian buffers at seven high-impact sites. > > To support their FieldDoc application, `Margaret`—the Director of Conservation—creates a new user account and sets up the Calvert Conservation workspace. They plan to bring in staff from `Eco-Saber`, their technical service provider, who helped plan the projects and has shapefiles ready. Margaret invites `Alex` from `Eco-Saber` to the `Calvert Conservation` workspace so that Alex can create the FieldDoc portion of the application on the behalf of `Calvert Conservation`. ### Step 1: Create your FieldDoc account Take the following steps: 1. Open fielddoc.com/register 2. Create an account by entering in your real `First Name`, `Last Name`, `work email`, and `password`. 3. Open the email with the verification code. You have 10 minutes to enter this code into FieldDoc. 4. Once confirmed, based on your email domain, FieldDoc will either invite you to create a new organization or join an existing one. 5. Once your account is linked to an organization, you can start using the system. {% hint style="info" %} **Common Troubleshooting Solutions** If you have **issues creating an account**, check with your IT department or Network manager to make sure that FieldDoc is listed on the "safe list" of websites. If you **cannot create or join an organization** based on your registered email domain, reach out to and our team can complete the configuration for you. {% endhint %} ### Step 2: Invite collaborators to your workspace Margaret is going to invite her technical service provider, Alex, to the workspace. Once Alex has access, they will be completing the proposal on behalf of the `Calvert Conservation` organization. 1. Log in to your account. Open up your **settings** panel in the left hand corner. 2. Open the **workspace** settings. 3. Within the **Members** tab, enter the `email address` of the individual that you would like to invite. 4. Set their **permission level** to "read only" or "admin". If the user will be creating, editing, or deleting data they must have admin access. 5. Click **invite**. If you want to remove access or re-send the invite, you can do that at any time. 6. The invited collaborator will receive an **email** from with a button asking them to accept the invitation. 7. Upon acceptance, the user will be prompted to complete setting up their user account if they do not already have a FieldDoc account. 8. Once logged in, the collaborator will need to **switch workspace**s in the upper left hand corner in order to create records within their collaborator's account. ### Step 3: Create the pact using the provided pact code From within the `Calvert Conservation` workspace, create a pact in the open funding opportunity. 1. On the Home Page, choose Apply for funding 2. Create a Pact. Type or paste a 4-character opportunity code (required for pact setup). Enter enter in the unique pact code for this funding opportunity: **3WP9**. 3. Add a `Name`. Match it to the Application Title you are using in Grants Gateway. You have the option of adding a `Description` as well. 4. Click Create pact to generate the pact. 5. Now you have a pact shell within which you can add activity records. ### Step 4. Add Activity Records. There are multiple ways to add activity records to your pact. This section provides three basic options for creating activity records and making them visible within the pact. {% hint style="warning" %} We are sharing the basic ways to create activity records and add the required attribute data. Some applicants may want to create a more tailored FieldDoc experience with more data management support. For example, you may want to use the workspace's portfolio folder structure to set up a project folder with sub-folder sections to segment and organize your activity records before sharing them to your Pact. That level of detail is not included in this guide. {% endhint %} ### Option 1. Create activity records in FieldDoc 1. From the Activity tab in your pact, click the + New activity button. 2. Give your activity a unique **activity name**. 3. Click save. 4. Open the **activity overview** icon on the tile. Now you can configure your record. 1. **Activity type**. Open the universal list of activity types and associate one with this record. Make sure to choose the activity type that has an available Adapted Chesapeake Model. 2. **Geometry**. You can import a single file or use the draw tools (point, line, or polygon) to indicate the location and extent of the installation location. *Tip: If you do not yet have a confirmed location, use a demonstration location rather than drawing a massive polygon, which could interrupt model accuracy.* 3. **Model**. Follow the prompts on the model page to enter in the required fields and run the model. 5. Have more activity records? Repeat this process! ### Option 2. Create activity records via import {% hint style="info" %} You can import a single geometry file within the activity record. Use file import if you have a file that will create multiple records. {% endhint %} 1. From the Activity tab in your pact, click the "[file import](/essentials/activities#file-import)" button. 1. Import your file. 2. Use the mapping tool to map your source field names to the FieldDoc schema. 3. Click **save**. 4. A record will be created for each row in your file. 2. **Add activity type**. Open the record or toggle to the table view to add the activity type to each record. 3. **Activate the model**. Open the Edit Activity modal. Navigate to the model tab, enter in the required fields to run the model. ### Option 3. Link existing activity records Already have existing activities in your workspace portfolio that you want to make a part of this application? You can use the '**Link activity**' button to connect existing activities to this new pact. {% hint style="danger" %} **Don’t re-use outdated activity records.**\ FieldDoc regularly updates its models and platform tools. If your activity records were created **before November 2024**, they may contain outdated calculations or incomplete data fields. We strongly recommend that you **create a new activity record** from scratch rather than linking an old one to a new Pact. You can look in the bottom left hand corner of the model table to see the "last run date". If you choose to reuse a record, you must at **minimum**: * Open the record * Refresh the model using the "**Refresh**" button. * Re-run the model outputs. This ensures that the data you're submitting reflects the most current standards and avoids errors in your application. {% endhint %} ### Important note on models The Trust Fund Managers place an emphasis on using the FieldDoc system to estimate sediment and nutrient reductions for your proposed work. FieldDoc has configured the following models for your use. :heavy\_plus\_sign: Adapted Chesapeake Nutrient and Sediment Load Reduction Model :heavy\_plus\_sign: In-stream load reduction estimates :heavy\_plus\_sign: Shoreline restoration load reduction estimates :heavy\_plus\_sign: Stormwater performance standard - treatment depths other than one-inch :heavy\_plus\_sign: Stream restoration load reduction estimates (Protocols 1 - 5) To support use of these models and supplement external training opportunities to understand how the models function, we recommend checking out the [Model Documentation](/resources/models) provided in the documentation section. Here, you will find provide links to expert panel documentation and math that supports these models. ### Step 5. Submit your pact to your Grants Gateway application The pact must be submitted in FieldDoc and shared to the Grants Gateway in order for the full application to be considered complete. 1. On the pact overview page, click the **Submit** button. 2. Take the URL from the top of your Pacts overview page and copy it using your keyboard shortcuts (for example, CONTROL+C). 1. Open your Grants Gateway application. In the common application, navigate to the field that asks for the **FieldDoc URL**. Paste in the url from your FieldDoc pact. 2. :white\_check\_mark: 3. :x: [https://app.fielddoc.com/projects/fb41615f-778f-400f-866a-7c61cb6e8c25](https://app.fielddoc.com/projects/fb41615f-778f-400f-866a-7c61cb6e8c25/) {% @arcade/embed flowId="AxdWpGVuKOcWkvI0VDL9" url="" %} ## FAQs - Creating an proposal
How do I associate my activities to the Pact? The system has expanded options for organizing and sharing activity records. This has resulted in multiple pathways through which you can create activity records and share them as part of funding applications. If you didn't create the activities within the Pact, use the **Link Activities** button to add activities from your portfolio to your application.
Why aren't my Activities appearing in my Pact? This is a loaded question and there is no single answer. However, keep in mind the following truths to help troubleshoot: 1. All Activities must be linked to a Pact. If you create an Activity through a Pact, the Activity will appear and automatically be a part of that Pact. So, if you create an Activity through your workspace's Portfolio page or within a Project, you need to take the additional step of manually linking the Activity to a Pact. 2. Pacts are workspace-specific. Did the activities get created in the correct workspace? If you are a collaborator and you're not seeing the activities in the **Link Activities** list, there is a good chance you accidentally created it in the wrong workspace.
Why can't my funder see my application? 1. Did you [Create a Pact](https://help.fielddoc.org/docs/create-a-pact) and assign the related Activity(ies) to the Pact? 2. Did you click "Submit to Funder"? The Trust Fund Program managers can only see activity records that are included in a Pact created through their Pact Opportunity. Please reach out to to get a code to create your Pact. Once Activity records are created or added to the Pact, you must click "submit to funder" for the records to be shared with Trust Fund program managers. {% hint style="danger" %} * Do not try to share a Project. You will know you are sharing a project if the URL says Project in it. * Do not try to share a pact that you created for a different funder. The Trust Fund staff cannot see that pact. {% endhint %}
Where did Sites go? Sites have been re-named with a more generalized organizational folder called [Sections](/essentials/portfolio/sections). If you typically create multiple sites within your application, you can assign sections to them instead. The recommended workflow if you want to use this sub-folder is: 1. Create a Project folder in your portfolio. 2. Within the Project, create your sections. 3. Add activity records within the sections following the common guidance and workflow. 4. Create or open your Pact. Navigate to the Activities tab. 5. Click the "Link Activities" button. Select the activities that you created to link them to your pact. With this workflow, the sections will remain intact within your workspace's portfolio and the funding program managers will be able to view all of the records from within the Pact. {% hint style="info" %} Remember that naming conventions are important! Do your future self and colleagues a favor and do not give two activity records the same name, even if they are in different folders in your portfolio. {% endhint %}
What URL do I share in my Trust Fund application? Please share the Pact URL as part of your Trust Fund application.
How do I turn on the Sediment & Nutrient Load Reduction Models? In FieldDoc 2.0, models are not automatically generated. Users must complete the data input as a final step and ask the system to generate the outputs. :seedling: Learn more: [Model outputs](/essentials/model-outputs)
Should I add a pact for every project site? No. If you are submitting a single application to the Trust Fund, you should submit a single pact. All implementation locations should be included in the application as activity records.
# Chesapeake Bay Program IIJA Funding Guide #### Introduction & Purpose The following document outlines the information provided by state and jurisdictional leads for their ability to share information on the location of IIJA-funded BMPs with the Chesapeake Bay Program through the FieldDoc Platform. Details that inform this guide has been collected through a series of meetings and emails with jurisdiction leads.
FieldDoc allows practitioners to create digital records of on-the-ground implementation that indicate where implementation will happen/has happened, what will be/was implemented, and how much it improved water quality. Tracking this information allows the Chesapeake Bay Program to analyze how much their investments within each jurisdiction helped meet environmental and community-based Bay-wide goals. This guide exists to ensure that your agency has the information needed to complete FieldDoc reporting and remain within compliance of your federal grant reporting requirements. Any questions or changes to the processes outlined here should be sent to and The Bay Program Office. #### Grant Requirements & Reporting Context #### Reporting Requirements for Infrastructure-Funded Grants Infrastructure funded grants include additional post-award reporting requirements that help maintain accountability to taxpayers and advance equity. All Infrastructure-related grant and cooperative agreement programs must track and report post-award information on the status of award-specific goals and objectives, including 1) project-level location data and 2) the phase of project implementation.
CBPO has contracted with The Commons to utilize FieldDoc as the collection system for this information. Within FieldDoc, a “pact” is a unit for organizing an organization’s collection of practices. Within the pact, recipients should report geometry data for each practice implemented utilizing Infrastructure funds. The Commons and EPA CBPO have worked with each recipient to develop workflows for importing data to minimize reporting burden.
Recipients are required to submit this information in FieldDoc on a semi-annual basis, to coincide with progress report submission dates. Data for all activities completed since the start of their Infrastructure grant should be represented in the FieldDoc account. CBPO will use data collected through this process to assess compliance with the Justice40 requirements.
What must be reported in FieldDoc * A record for each implemented activity (BMP) should be created in FieldDoc and linked to the IIJA Pact once the activity has been installed to completion. * The record should include selecting an activity type from the provided list, a geometry that indicates the implementation location and extent (polygon preferred), and implementation date. ## ## Points of Contact | Associated with | Point of Contact | Email | | --------------- | ---------------- | --------------------------- | | Bay Program | Matt Robinson | | | FieldDoc | John Dawes | | | FieldDoc | Erin Hofmann | | ## FieldDoc Reporting Process Overview ### Access & Accounts #### How to request a FieldDoc account If the jurisdiction lead does not have a FieldDoc account or if new staff need to be added, please email for assistance. #### Your jurisdiction’s IIJA workspace When you log-in to FieldDoc, you will switch to the IIJA workspace. This workspace is separate from the general FieldDoc workspace and will exclusively contain records reported to IIJA. ( 💁 [How to find your workspace](https://app.arcade.software/share/SZ5n1NWevB0ahgH83Huk)) ### Preparing Your Data * Data will be exported from your management system to be imported into FieldDoc. You should import into FieldDoc all implemented BMPs funded with IIJA funds that have been installed to completion and have not yet been reported to CBPO via FieldDoc. * The easiest way to prepare the data from the export is to create a .csv file with the following fields that capture the following (tip: if you have shapefiles or geojson files that contain polygon footprints for each implementation location, those files types are preferred): * Activity name or code to enter into the FieldDoc Activity Name Field * Activity description or BMP type to enter in the FieldDoc description field * Implementation location: minimum standard latitude and longitude in decimal degrees * BMP footprint/extent * Extent unit * Completion date * Check your source file for completeness. Do all required fields have values? Are the coordinates accurate? Make any edits that you’d like to capture in the import. For example, is there a value for every acreage? ### Importing Your Data * Once your file is prepared, it is time to import into FieldDoc. The required fields as they appear in FieldDoc are listed below. Note that the import field name is dependent on how you structured your source file. **You do not need to map the geospatial data**, **even latitude and longitude!** |


| FieldDoc Field name | Instructions | | ----------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |


| practice:name | Give each record a unique identifier that you can use as a reference and differentiator. | |


| practice:description | Use this field to capture the BMP before selecting from the standard list or provide other details about the implementation | |


| practice:extent | Typically, the implementation footprint | |


| practice:extent\_unit | Unit must map to the [standardized vocabulary of acceptable unit names](https://docs.google.com/spreadsheets/d/1ZY0B3NrxkDHM6EEMdRmzlBBV2q5lZDYQeG0dkwJExNE/edit?usp=sharing) | |


| practice:completed\_on | The estimated data that the BMP was installed to completion | | latitude | Do not map | Imports automatically | | longitude | Do not map | Imports automatically | {% hint style="info" %} **Import File Preparation Tips** * FieldDoc can import .CSVs, shapefiles, or geoJSON files. The step-by-step guide assumes that you will be importing a spreadsheet converted to a .csv file. The locations will be indicated using latitude and longitude coordinates. If possible, shapefiles should be imported within each record after upload. * You do not need to map the geometry fields during the import, FieldDoc recgonizes those as points and will create the geospatial data from them. * Activity types fields cannot be directly imported into FieldDoc, that’s why we suggest mapping them to the practice description field for easy reference. You will assign the activity type field within the FieldDoc system. * Extent units must match [the standard vocabulary in FieldDoc](https://docs.google.com/spreadsheets/d/1ZY0B3NrxkDHM6EEMdRmzlBBV2q5lZDYQeG0dkwJExNE/edit?usp=sharing). Please update your unit of measure field before importing. If they do not import you can simply select the appropriate unit within FieldDoc. {% endhint %} ### Find your Pact A Pact has been created for you so that the records can be shared with the IIJA program managers. The pact is named IIJA Practice Implementation. The pact is accessible via the Pact view within the IIJA workspace portfolio. All activity records will be imported by you into this pact. Only activity records that are in this pact are visible to the IIJA program managers. The same pact will be used and updated through the period of performance. ### Entering Activities & Practices Once you have opened your pact, you will navigate to the pact Activities tab. Here, select the button to “Import file”. Select your source file. Then, using the mapping feature, map the source file fields to the FieldDoc schema. Click save. FieldDoc will create an activity record for each row in the source file. Once the activity records have been created, you will need to associate an activity type with each record. This is easily done using the table view and keyboard shortcuts to copy and paste activity types for each record. The locations have been captured by the source file coordinate fields. ### Completing submission * Email once your bi-annual report is completed in FieldDoc. * You will receive a confirmation of receipt from both The Commons and EPA-CBP. ### Ongoing Reporting * Repeat the data entry process bi-annually, as part of your existing reporting schedule. * Only newly implemented BMPs, or those that have not yet been reported need to be reported in FieldDoc, should be imported in each reporting period. # National RKM Conservation Program ## Objective After completing this guide, you’ll have the knowledge needed to: * **Complete your Pact**. At the end of your period of your performance, you will use FieldDoc to report what work was completed, where it took place, and what impact it had. All of this information will be shared to RKM via a unique pact. ## Key Terms ### Pact * A **pact** is a digital envelope for each grant award letter. At the end of your period of performance, it will contain all the activity records and metrics associated with each award letter. * A pact will be created on your behalf for each award that you receive from The Foundation, you do not need to create one. You will find all pacts associated with your organization in your workspace, including a Pact for each award letter that you receive from The Foundation. The FieldDoc team will pre-load the award details (title, number, program, etc.) into each Pact, so users aren’t duplicating data entry. If you see any inaccuracies or have questions, email for assistance. * Activity records are the core element in each pact. If desired, a pact can also include documents, photos, links to outside resources, and reporting attachments that are important to share as part of the award’s record. * Only users with access to the organization’s workspace will see the Pact. Foundation Program Managers will be able to see all information that has been shared through the pact. * The data and metrics tracked in a Pact will be the authoritative record the Foundation will use regarding where your work took place and what was done. This data may be used in analytics, funding reports, and for other mission-driven goals as determined by The Foundation. {% hint style="info" %} Data can be created directly within the Pact, or it can be linked from a workspace portfolio. {% endhint %} ### Activity Record In FieldDoc, the activity record is the fundamental unit of work. You'll create a record for each of your implementation actions, like stream restoration, forest conservation, or trail maintenance. These records serve as the digital representation of real-world restoration and conservation practices happening on the ground. Think of it this way: you're translating the “dirt you’re moving on the landscape” into structured data. This data becomes essential for tracking your progress toward environmental outcomes and sharing results with funders, regulators, and partners. **Activity records are the representation of one discrete restoration action** (e.g., a riparian buffer, a stream restoration) with spatial location, type, and associated programmatic metrics. * Within each activity record you will input: * [Activity Name](/essentials/activities#general-settings) - A unique name that references the proposed project activity * [Activity Type](/essentials/activities/general-settings/activity-type#set-your-activity-type) - Choose from a standard list curated by The Foundation. * [Geometry](/essentials/activities/geometry#how-to-input-geospatial-data-into-activity-records) - use a point, line, or polygon to indicate the implementation area. The geometry collects critical information for many models. A polygon is the preferred geometry type! * [Programmatic metrics](/essentials/metrics/metrics-programmatic) - attach any of the available programmatic metrics and assign a planned target and the implemented value. * There are multiple ways to create activity data in FieldDoc. FieldDoc offers two main ways to enter activity data: * [Batch file import](/essentials/import) * [Single Activity Record creation](/essentials/activities#create-activity-records) The information inputted within each activity type will appear in summary on the Pact overview page and via the Pact Atlas. ## Step-by-step guide For every award that you have received from The Foundation, you have a corresponding FieldDoc pact. The Pact has been created on your behalf and can be found in your organization's workspace (Step 2) after you create your account (Step 1). If you have received multiple awards from the Foundation, you will see a pact for each one. Please report your activities within the correct pact. ### Step 1. Create your account 1. Navigate to . 2. Create an account using your real name and business email address. 3. Confirm the registration in your inbox. 4. FieldDoc will match your account to the correct organization. If FieldDoc cannot find a match, we ask that you reach out to our team to complete the set up: . 5. Once you have completed your registration, you will have access to all data in the organization account. Welcome! {% @arcade/embed flowId="GUwNAj7jEI27rtiF4m8J" url="" %} ### Step 2. Find your pact A Pact has been created for every award you have received from the Foundation. At the end of your period of performance, you will populate your Pact with activity records to show where your work took place and what you accomplished. Each Pact is named after the project title listed in your grant award, and the grant award ID is included for reference. {% @arcade/embed flowId="8rw08yOdGhwJSWTbW7QM" url="" %} If you have trouble locating the correct Pact, please reach out to your program officer and copy **** so we can direct you to the right place. ### Step 3. Create activity records For each implementation item that you are reporting on in your narrative. The records should include: 1. Activity name 2. Activity type 3. Location 4. Extent 5. Programmatic metrics There are two ways to add activity records to your pact: create or import. #### Create records {% @arcade/embed flowId="hYs8LQoZf9YGqmeOxNjh" url="" %} ### Step 4. Click to confirm that it's complete. ## FAQs 1. When should I complete my FieldDoc report? 2. What activities should I be reporting? 3. How should I represent the installation locations? 4. I don’t see an applicable activity type. 5. I already have geometries for my activity records, what should I do? # Technical Service Providers - Grant Application Guide Your guide to assisting a partner organization with an upcoming grant application in FieldDoc. Updated 04/2025 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 email to help you learn the new workflow, avoid common issues, and make sure data is correctly shared and reported. {% hint style="danger" %} **What's changed?** * **Projects** are not automatically shared with funder. * **Modeled metrics** no longer automatically turn on. * **Import geospatial data** to create new activity records, not halfway through the set up process. * Use **Pact Codes** to share your records with funders and assign **programmatic metrics.** And more! {% endhint %} If you're collaborating across organizations, this guide is for you. *** ## Understanding the FieldDoc Data Model We recommend familiarizing yourself with the FieldDoc data model to best understand how the different components fit together. ### Each Organization has a workspace. * Within an organization workspace, you can view your portfolio. The portfolio provides structure for your folders, much like Google Docs or your file manager does. * [Project folders](/essentials/portfolio/project-folders) are the top-level organizing structure and should be used for organization programs. We do not recommend giving a project folder the same name as a grant application. * [Sections](/essentials/portfolio/sections) (formerly known as Sites) provide a sub-folder management. These can be used to organize groups of activities within a project. * [Activity](/essentials/portfolio/activities-records) 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. * Activity records can be nested Project Folders > Sections > Activities. Use of the Project and Sections is not required and is available to support better organization. * Workspaces are only visible to the users who have access to that workspace. Collaborators can be invited to a workspace so that they can create records within that workspace. ### Sharing Activity Data * 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. * Activity records are the only portion of your workspace portfolio that can be shared via Pacts. * A single activity record can be shared to multiple pacts. #### Data model
*** ## 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 ](/manage-your-organization/user-account) {% 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. From there, you can create a Pact and activity records on their behalf. [Workspaces](/manage-your-organization/workspaces) {% endstep %} {% step %} #### **Configure the Pact details correctly.** * Make sure you use the **Pact opportunity code** for the correct funding opportunity. * 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 that are created within the same workspace as the Pact can be linked to it. Make sure you are creating all project records, activities, and metrics from within the lead applicant’s workspace. [Pact Overview](/essentials/pacts) {% endstep %} {% endstepper %} *** ## Completing the FieldDoc portion of a funding application ### Introducing Pacts Pacts are the new way to share your activity record data for a specific funding opportunity in FieldDoc. [Learn about Pacts](https://help.fielddoc.org/essentials/pacts)
If you're applying for funding, follow these tips to get started: 1. **When you are applying for funding, Do not create a project, create a Pact.** Projects are now just an organizational folder within each organization’s portfolio. You must create a Pact. 2. **Finding your pact code**. Each finding opportunity has a unique Pact code for this funding cycle. Check in the Help Doc [Program Guidance](/guides-1/program-guides/chesapeake-bay-stewardship-fund) for your code. 3. **Naming your Pact**. The Pact name should match the name of the title used in your grant application. If you use any alternative, the program managers will 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. {% hint style="warning" %} Do not share any Project views, those are not visible to your funding program manager! {% endhint %} *** ### 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. We recommend learning about the new [Portfolios](/essentials/portfolio) setup, this will help you understand the changes to sharing with funders. {% 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. {% endhint %} [Learn about activity records ](https://help.fielddoc.org/essentials/activities) There are two ways to create activity records in FieldDoc: manually (one by one) or by importing a file. {% hint style="success" %} To save time and ensure your records are correctly linked, we recommend creating your[ Pact](/essentials/pacts#create-a-pact) first, then [adding your activity records](/essentials/pacts#link-activity-records-to-a-pact) from the Pacts > Activities tab. {% endhint %} #### Create individual activity records. 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**](/essentials/activities/general-settings/activity-type)**.** Select what you are implementing via the standard list. 2. [**Geometry**](/essentials/activities/geometry). Draw your activity footprint to indicate the location and extent of the installation using a point, line, or polygon. 3. [**Models**](/essentials/activities/models). 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**](/essentials/activities/activity-metrics). 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. Use the Import File button if you have geospatial files on hand, whether you are importing them individually or in batch format. FieldDoc can import [.csv](/essentials/import#file-type-csv), [.GeoJSON](/essentials/import#file-type-geojson), or [Shapefiles](/essentials/import#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. :seedling: Learn more: [Import](/essentials/import) ## Frequently Asked Questions
Where do I find the Pact Code? 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).
Can I move activity records between workspaces? No. Activity records are not movable between workspaces.
Can I add activity records from multiple workspaces to one pact? No. Workspaces are siloed. Activity records are 'stuck' within their workspace.
Where do I go for more help? For more details, check out our expanded help center. For technical support, send an email . Remember that the support desk is open 9:00-5:00 Monday through Friday. Expect a 24 hour response time for your ticket.
# FieldDoc Academy ## Upcoming Webinars Register [here](https://airtable.com/appH9IkpNkq1ru4Ub/pagD9iIe86LdeaAfz/form) for notice of upcoming webinars. ## Funding Program Webinars Hosted in collaboration with funding program managers, these webinars provide guidance for grantees associated with a funding program that uses FieldDoc.
Chesapeake & Atlantic Coastal Bays Trust FundMaryland Department of Natural ResourcesSeptember 11, 2025https://youtu.be/nD0_OsHQWlw?si=R3WAMmrPAVy8OEOq/files/U1EKqOYQXD6olf8BwFG5
Chesapeake Bay Stewardship FundNational Fish and Wildlife FoundationHosted February 2026https://nfwf.sharefile.com/public/share/web-sece8f38f198c4dee88fa021ee0137b0c/files/pxy5X28uFgqyUN4pKbq9
Delaware River ProgramNational Fish and Wildlife Foundation2025 recording TBD/pages/crtKUU73pn524cVsyImQ/files/Ae11ZeGtudhwUBh98mvL
## FieldDoc Courses Find and watch an on-demand webinar.
Introducing FieldDoc 2.0/pages/LJvOZxLAdAXBMZ4kruKH
Portfolio 101/pages/BM6bLRbF2fibkByD8SC0
Collaboration 101/pages/bQFdlqYZdfVEDSTm7wyV
Sharing to Funder/pages/BM6bLRbF2fibkByD8SC0
Data Management/pages/KwOixS0YX8WuCdaWZlRV
Modeling/pages/Jvex2f0asDMPUWhdJ0MZ
Mapping/pages/EZ2g4d5e1KZo6aQfB0Q0
Reporting/pages/fI2VwEi4g95zTincAssf
Advanced Features/pages/v60aMwxPl4qAh76mgD2b
## Guides to get stuff done
Cover image
From entry to impact: a practical guide to stewarding conservation and restoration data/files/Fv0YCWKktskYcKn6HL6D/pages/KZpqYlqPEbCSskUqjRGD
## Reports and Papers
Mapping Impact: The state of geospatial tool capacity among restoration practitioners/files/lKB93US4ml8ub5NDbirE/pages/TlWfWPBpLKzbECfsQf4G
# Build a Data Management Plan

Download the article (PDF)

Learn how to build a simple, repeatable data management plan that keeps conservation and restoration data accurate, reusable, and ready for reporting—inside FieldDoc and beyond. This guide walks through how to design a data management lifecycle—from defining standards and workflows to reviewing and maintaining records over time. It is designed for nonprofit and practitioner-led organizations managing conservation and restoration data who need approaches that fit real-world constraints. Rather than prescribing a single system or tool, the guide focuses on practical habits and shared conventions that help data remain usable, trustworthy, and adaptable as programs, staff, and reporting needs evolve. # FieldDoc 2.0 Introducing FieldDoc 2.0. Learn about the latest features of the FieldDoc platform. {% embed url="" %} # Portfolio 101 {% embed url="" %} In this training, we dive deep into the new data model and how the relaxed data restrictions open up opportunities to expand FieldDoc’s use within your organization and across your grants. This session is a great starting point—once you understand the system’s core capabilities, the rest of the series will inspire fresh ideas about how to leverage your nature-based data, not just for funder reporting but for broader impact and insights. ## Recap & Keep Learning! ### Data Model One of the biggest updates in FieldDoc 2.0 is the new data model, and it’s a game-changer. In the past, you had to create a project within a program before you could enter any data. That meant all your records were automatically visible to the program managers, and your attribute data was limited to what they had curated for their programs. We restructured the data model to make FieldDoc a true amplifier for your restoration and conservation efforts, helping you get more value and impact out of your data. Now, everything starts in your organization account. You’ll build out your portfolio there, complete with all the relevant attribute data. When the time comes, you can choose which records to share with a funding program—no more creating duplicates or being locked into someone else’s structure. This shift makes your data more reusable, scalable, and interoperable. For example, if you’re working with multiple funders in FieldDoc, you can easily share the same records without re-entering anything. It’s also a huge boost for smoother data entry and management, which I’ll show you in just a moment. ### Portfolio Portfolios serve as the hub for your organization’s metrics, projects, and activities. They also include Pacts, a powerful feature that lets you share specific parts of your Portfolio with third-party program managers—like funders or investors. ### Metrics In the legacy version of FieldDoc, the power of metrics flew under the radar, playing a secondary role to other features. But in FieldDoc 2.0, they’ve stepped into the spotlight. In fact, building out your metrics first is now a smart strategy—it sets a solid foundation before you start creating activity records. The new metrics feature in FieldDoc lets you create and track organization-specific metrics directly at the activity level. This means you can easily track whatever matters most to your organization—like the number of trees planted or miles of fence installed—right in FieldDoc. For the first time ever, you can include your own organization-specific metrics directly in the system. You can assign target values at both the organization level and within individual activity records. As you start assigning values, you’ll be able to track your progress in overview summaries and atlas views—making it easier than ever to see the big picture of your work’s impact. And don’t worry—programmatic metrics aren’t going anywhere! You’ll still be able to assign and track those after creating a Pact. The best part? Your programmatic metrics will remain separate from your organizational ones, giving you clarity and control. ### Projects In FieldDoc 2.0, Projects have taken on a completely new role. They’re no longer tied directly to grant agreements. Instead, they’re now an optional organizational tool—a way to group and manage a batch of activity records within your organization. Projects are no longer constrained by funding opportunities, so you can structure them however suits your needs. When does it make sense to use Projects? * If your organization runs multiple initiatives—like a tree planting program and a fence installation program—you might want to track metrics specific to each initiative or you want to be able to filter your activity lists by program when applying for grants. Using Projects can help with that. * If your team operates in distinct regions, you might want to organize activities into projects that align staff with those regional responsibilities. ### Activities In your activity records, you’ll define activity types, which unlock access to relevant environmental models. It’s also where you’ll enter your metric targets, as we discussed earlier, and add geospatial footprints indicating the location of your efforts on the landscape. ### Pacts You’ll be maintaining a single source of truth of your own portfolio and then sharing portions with funders. Funders have the benefit of standard and simplified reporting. # Collaboration 101 {% embed url="" %} This webinar starts with how to create a FieldDoc account. You’ll want to keep this info handy for onboarding colleagues or consultants. It’s the kind of thing that saves you time later when someone asks, “How do I get started?” We dive into the expanded **organization account components**. This is where things start to get interesting because we’ll explore how these updates give you more flexibility and functionality in managing your organization. We end on **Workspaces and Collaboration**. We’ll spend most of our time here because these are the powerhouse features of the system. Workspaces and collaboration tools are the secret sauce for improving data sharing, co-management, and teamwork.\ We’ll cover: * The different permission levels and how to assign them. * Best practices for navigating between workspaces. * How these tools make collaboration seamless and efficient. By the end of this session, you’ll not only have a better understanding of FieldDoc 2.0, but you’ll also be ready to wow your team with how much smoother data sharing and project management can be. ## Recap & Keep Learning! ### Creating a FieldDoc Account While many users may already have their FieldDoc accounts set up, understanding the process is essential for onboarding colleagues or consultants. Having this information readily available can save time and reduce confusion when helping others get started. 🌱 Learn more: [Create your account](/manage-your-organization/user-account) #### Key Steps: * Sign up with your current work email to ensure communication and updates are properly routed. * Link the account to your organization for seamless data management. * Share this guidance with new team members or consultants to streamline the onboarding process. ### Expanded Organization Account Components The recent updates to organization account management in FieldDoc provide more flexibility and functionality, making it easier to oversee projects, users, and data. 🌱 Learn More: [Organization Account Management](/manage-your-organization/organization) #### Key Features: Improved organization-level tools for managing projects and activities.\ Direct association of data and users with the correct organization, ensuring accuracy and compliance in reporting.\ The ability to manage permissions and invite new users to join the organization efficiently. ### Workspaces and Collaboration Workspaces and collaboration tools are the standout features of FieldDoc, enabling powerful teamwork and streamlined data sharing. #### Key Features **Permission Levels:** * Admins have full control over user management and content editing. * Read-only users can view content but cannot make changes. **Navigating Between Workspaces:** Users can seamlessly switch between workspaces when managing data across multiple organizations.\ This feature ensures that projects and records remain organized and tied to the appropriate entity. #### Improving Collaboration: Workspaces serve as central hubs for project management, allowing multiple users to collaborate effectively.\ These tools simplify co-management by maintaining clear data ownership and structured workflows. # Sharing to Funder {% embed url="" %} This webinar begins by introducing how the new data model changes the way grantees create applications and generate implementation reports to meet funding requirements. Watching this webinar will help you familiarize yourself with the updated reporting processes. We’ll cover how to create an application, but it’s also essential to stay informed by attending webinars hosted by Funders using FieldDoc to understand the specific requirements of each funding opportunity. The majority of this webinar focuses on implementation. We’ll dedicate most of our time here because, although FieldDoc 2.0 significantly simplifies implementation reporting, it introduces a completely new workflow that all users need to learn. Key highlights include: * Tracking progress towards metric goals. * Incorporating additional activity records outside of a Pact that need to be included. * Adding programmatic metrics to activity records. By the end of this session, you’ll have a solid understanding of FieldDoc 2.0 and will be equipped to impress your team with how much smoother it is to create applications and share reports with Funders. ## Recap & Keep Learning! ### Data migration from legacy FieldDoc to FieldDoc 2.0 No data was lost in the migration from the legacy system! When you log in to FieldDoc, you’ll notice a new record type - Pacts. You'll notice that the names of Pacts match those of Projects. They are identical! This is because we transitioned all of your existing Project data into corresponding Pacts with the same names. Pacts are linked to the same activity records, which are still organized within Project folders. Rest assured, activity records were not duplicated during this process. Your Projects have been reconfigured to serve as "folders" rather than the primary source of grant compliance data. For every Project that existed in FieldDoc prior to November 11, 2024, we created a corresponding Pact. Each Pact includes links to the practice records within the Project folder—now referred to as Activities—that were previously only associated with the Project. If your account included any test Projects or Activities, we created Pacts for those as well. To keep your workspace organized, we recommend performing some housekeeping: review your account and delete any test Pacts, Projects, or Activities you no longer need. It’s important to note that any Projects or Activities added after November 11, 2024, were not automatically included in the new Pacts. These records are managed under the new system and workflow. If you’ve added new data since this date, you’ll need to manually incorporate it into the appropriate Pact or create a new Pact as needed. By understanding these changes, you can better navigate the updated system and ensure your data is organized and accessible for compliance and reporting purposes. Let us know if you need any assistance! ### Create an Application FieldDoc has de-coupled Organization Portfolios, the records of conservation and restoration work practitioners are implementing across the landscapes, from Funding Opportunities. This change provides better ownership and data-sharing practices for all data users in the system. Applications are now created through Pacts. 🌱 Learn more: [Pacts](/essentials/pacts) ### Submit A Report: Implementation Track progress toward implementation and share that progress with your funder! You can batch add your implementation progress via Pacts, or update individual records. {% hint style="warning" %} How to add activities to a Pact after the Pact has been created Pacts have a hand "Link Record" feature that allows you to link any activity record from your portfolio to a Pact. So if you're creating new records throughout the project period, remember to add the activities the pact and programmatic metrics to each record as you go along. {% endhint %} ### FieldDoc features impacted by these workflows #### Modeled Metrics Models must be 'turned on' within each activity records (in Legacy FieldDoc most models were automatically activated). 🌱 Learn more: [Modeled Metrics](/resources/models) #### Programmatic Metrics FieldDoc now hosts two type of metrics: **Organization Metrics** and **Programmatic Metrics**. All metrics continue to be tracked within activity records. However, users can now also track implementation directly within Pacts as well! 🌱 Check out: Programmatic Metrics for steps on how to add programmatic metrics to your activity records (Big hint - first you need to create a Pact!) # Data Management {% embed url="" %} Mastering FieldDoc is all about starting strong with effective data management. This live walkthrough will arm you with essential tips and tricks to maximize your success. From leveraging Projects as organizational folders and adopting smart naming strategies to exploring import best practices and utilizing table features, you'll gain practical insights to optimize your experience in the platform. ## Recap and Keep Learning ### Projects Projects in FieldDoc serve as an optional and flexible organizing structure, similar to "folders," designed to help you group and manage records effectively within your organization. Projects are tied to your organization, offering a way to organize data by initiatives, geographic areas, or staff responsibilities, and they allow for collaboration through shared access. While they can hold some direct data, most metrics are added and aggregated from associated activity records. Unlike Pacts, Projects have distinct purposes, and caution is advised against using Projects to represent specific grant agreements to avoid disorganization and confusion during reporting. Ultimately, whether to use Projects depends on your organizational needs, and FieldDoc will ensure data from 'Legacy FieldDoc' is preserved, with updates and cleanup tips forthcoming to optimize data management. 🌱 Keep Learning: [Project](/getting-started/quickstart/build-your-portfolio) ### Sites *(becoming* Sections*)* FieldDoc has evolved its approach to sub-folders, originally a mandatory feature that users found cumbersome and of limited value. Initially serving as a rollup for practice records, sub-folders did not align well with user needs. Now, FieldDoc offers greater flexibility, making sub-folders an optional organizational tool that users can employ as needed to enhance their workflow. Looking ahead, a new and improved Site-like sub-folder feature is set to launch in Q1, offering a more intuitive and effective way to organize and track site-specific data, addressing past limitations and aligning with user needs. 🌱 Keep learning: [Sections](/essentials/portfolio/sections) ### Activities Activities are the backbone of FieldDoc, serving as the primary data entry point for tracking work and outcomes. Properly setting up and managing activities is essential for accurate reporting and effective data organization. Thoughtful naming conventions, such as including location, activity type, and installation year, make activities easier to find and reference. The description field provides flexibility to add specific details or context to each activity, enhancing its utility. Activities have a one-to-one relationship with projects, but they can be reorganized without deletion, ensuring flexibility. Key dates like completion or annual installation can also be tracked within activity records to support ongoing efforts. For advanced reporting and compliance, especially with grants or state agencies, NEIEN fields are available to align activities with the required schema, streamlining reporting processes. 🌱 Keep learning: [Activities](/essentials/portfolio/activities-records) ### Imports FieldDoc’s new import feature simplifies the process of uploading data, allowing users to import Activities, Metrics, NEIEN, and Projects directly from the home page. Activities and Metrics are particularly useful, and the tool supports geospatial files for batch-importing multiple records. During the import, users can map source file fields to FieldDoc fields for precise data alignment. However, some limitations exist: Activity Type and Modeled Metrics must be set manually after import, and matching record keys will overwrite existing data, so ensuring unique keys is critical. Before finalizing the import, users can review their data in a non-responsive viewer to catch any errors. Looking ahead, upcoming webinars will introduce Workflows, a feature that allows users to update existing records with external files or systems, offering even greater flexibility. After importing, users should complete key steps such as adding activity types, activating models, and refining metrics. From here, the transition to exploring Table functionality is seamless. ### Tables & Grid Views Table views in FieldDoc 2.0 address long-standing user requests for a more streamlined way to manage large volumes of data. Previously, navigating individual activity records and metrics was time-consuming, making table views a game-changer for efficiency. With features like filtering, editing, sorting, and copy-paste functionality, table views simplify data organization and allow users to identify trends, fill gaps, and prioritize tasks effectively. They are particularly useful for activities, enabling users to add activity types or switch project assignments directly in the table. For Pacts, users can add Metrics or implemented values within the table view, streamlining data entry. Metrics linked to activities offer insights into contributions at both the organizational and funder levels, with the flexibility to report the same data without duplication. Additionally, planned values must be entered before implementing metrics, ensuring clarity in reporting. When combined with the Import feature, table views create a seamless workflow, allowing bulk data imports followed by efficient refinement and assignment of details. ### Clean Up To keep your FieldDoc setup clean and efficient, follow these key steps: * **Remove Test Records**: Delete any "test" records created during setup or experimentation to avoid clutter and confusion. * **Turn Off Unnecessary Models**: If you're using custom metrics for Total Nitrogen (TN), Total Phosphorus (TP), or Total Suspended Solids (TSS) instead of FieldDoc's automated models, disable unused models to streamline your workflow. :seedling: Learn more: [Models](/essentials/activities/models) * **Check Project Ownership**: Ensure you have the correct ownership permissions for your projects to avoid unexpected restrictions on managing your data. * **Eliminate Duplicate Records**: Identify and remove duplicate activity records or metrics to maintain data accuracy and organization. * **Switch Records in a Pact**: Adjust options for any duplicate or incorrect records tied to a Pact to ensure accurate representation of your metrics and activities. * These steps will help maintain a clean, functional, and well-organized FieldDoc workspace. # Modeling {% embed url="" %} The FieldDoc Models Webinar provides an in-depth overview of how environmental practitioners can leverage FieldDoc's modeling tools to estimate and communicate the environmental benefits of their restoration and conservation activities. The session highlights the role of standardized models, such as the Adapted CAST Model, Stream Restoration Protocols, and Stormwater Performance Standards, in providing science-based, transparent, and consistent calculations for nutrient and sediment reductions. Participants are guided through the process of activating models within FieldDoc, including preparing activity records, understanding data inputs, and utilizing results for reporting and strategic planning. The webinar emphasizes the flexibility of FieldDoc 2.0, enabling users to independently activate and troubleshoot models, while also underscoring the importance of aligning modeled outputs with funding requirements and broader environmental goals. Future developments and enhanced API integrations promise to expand accessibility and support for users across diverse geographies and activity types. ## Recap & Keep Learning! A model is a simplified representation of a real-world system or scenario used to understand, predict, or analyze outcomes. In the context of environmental modeling—like the Chesapeake Assessment Scenario Tool (CAST)—models simulate how various factors (e.g., land use, weather, human activities) and interventions on the landscape interact to impact environmental conditions, such as nutrient and sediment levels in water bodies. While models are valuable tools, they inherently lack precision. Models are meant to guide users to answer complex environmental questions but are not an authoritative source of truth. ### Benefits of models Models in environmental restoration and conservation provide science-based, standardized estimates to help practitioners understand and communicate the anticipated environmental benefits of their activities. They offer consistency across projects, organizations, and funding programs, enabling clear comparisons and data-driven decision-making. By using robust, peer-reviewed calculations, models estimate reductions in key pollutants like nitrogen, phosphorus, and sediment, supporting more effective resource allocation and demonstrating measurable progress toward environmental goals. FieldDoc streamlines the modeling process with user-friendly tools that make complex calculations accessible to users of all skill levels. Results are delivered in clear, actionable formats, empowering users to track their progress, meet reporting requirements, and share impactful stories with funders and stakeholders. While models are not perfect predictors, they serve as essential tools for guiding decisions, aligning efforts across scales, and driving meaningful environmental outcomes. 🌱 Learn more: [What are Models?](/resources/models) ### How to activate models Activating models in FieldDoc begins with preparing your activity records. Users must define the **activity type**, **location**, and **extent** (e.g., implementation footprint, drainage area, or animal units) to ensure accurate calculations. Once these details are in place, users can activate models manually— a significant shift from earlier versions where models were automatically enabled. This update provides users with greater **autonomy** and **transparency**, allowing them to troubleshoot issues directly if a model cannot calculate results. The activation process also includes selecting the appropriate model, such as the **Adapted CAST Model** or **Stream Restoration Protocols**, and entering the necessary data inputs based on clear, step-by-step guidance provided within the system. This structured approach ensures users can effectively generate accurate, meaningful environmental benefit estimates while maintaining flexibility for internal planning and strategic goal-setting. 🌱 Learn more : [Modeled Metrics](/getting-started/quickstart/model-environmental-benefits) ### Tips to using models #### Missing land-river segment? For models with a geographic component, it's essential to attach a geometry to the activity record for the model calculations to work properly. However, even with a geometry in place, you might encounter an error or receive a null value if the geometry is located outside a valid land-river segment or HUC12 associated with the selected Activity Type. [![](https://camo.githubusercontent.com/a042cc3e1b8007e1f52f5039e59c7d8edeffb14e113edb6d9f120cfc78a1cf73/68747470733a2f2f66696c65732e726561646d652e696f2f313433306165343963353138356131383737376262343865653733646134663334386531386130623235313237343131646264656436306162326137306566352d53637265656e73686f745f323032352d30312d30315f61745f31312e31382e35395f504d2e706e67)](https://camo.githubusercontent.com/a042cc3e1b8007e1f52f5039e59c7d8edeffb14e113edb6d9f120cfc78a1cf73/68747470733a2f2f66696c65732e726561646d652e696f2f313433306165343963353138356131383737376262343865653733646134663334386531386130623235313237343131646264656436306162326137306566352d53637265656e73686f745f323032352d30312d30315f61745f31312e31382e35395f504d2e706e67) #### Check the associated model When selecting the Activity Type to associate with your Activity record, pause and check the attached model. #### Read activity type description and unit type for more guidance Each activity type has a description that may provide details on how to delineate the activity footprint or provide other guidance in regards to when to select the option or how to configure inputs to activate the model. Also check the Unit Type to confirm that you are entering the correct value. #### Do not re-use ‘old’ records Records can become 'stale' over time. When updates are made to models, attempting to re-run outdated records may result in errors. The best practice is to delete old records that are not associated with an existing compliance requirement such as a grant agreement—especially those that are several years out of date—and start fresh to ensure accurate results and avoid calculation issues. #### Reporting load reductions The estimated sediment and load reduction data generated in FieldDoc are not reported to the Chesapeake Bay Watershed Jurisdictions via NEIEN. FieldDoc has a NEIEN reporting module that is used to configure your activity records to report to states for compilation and reporting to the NEIEN warehouse using the authoritative CAST models. 🌱 Learn more: [NEIEN](/essentials/activities/general-settings/neien) ### Adapted CAST Model Isolation Scenario Tables One of the major models supported in FieldDoc is the Chesapeake Assessment Scenario Tool (CAST) Isolation Tables. These are specialized datasets used to isolate and quantify the pollutant reduction impacts of individual Best Management Practices (BMPs) within the Chesapeake Bay watershed. These tables are part of the Chesapeake Bay Program’s CAST tool, and designed to estimate the impact of various conservation and restoration practices on nutrient (nitrogen and phosphorus) and sediment pollution levels in the Chesapeake Bay. The Commons relies on and works closely with the Chesapeake Bay Programs CAST Team to\ ensure all BMP Isolation Scenario tables are aligned and congruent with the latest public release\ provided by Bay Program Modeling partners. The expert panels behind these isolation tables are constantly revising and refining their work. So we work with the CAST modeling team to update tables and maintain consistency with BMP types. > 🚧 FieldDoc is not a credit calculator > > These are practice specific estimates and are not meant to concretely align with CAST. The Bay Program and CAST are the primary leads for assigning crediting to practices for the Chesapeake Bay TMDL. FieldDoc provides a helpful analytic but the nutrient and sediment load reductions we calculate are only a guiding analytic and not a credit. 🌱 Learn more: [Adapted Chesapeake Nutrient and Sediment Load Reduction Model](/resources/models/adapted-chesapeake-nutrient-and-sediment-load-reduction-model) ### Stream Restoration The Maryland Department of Natural Resources (DNR) plays a key role in implementing and overseeing the stream restoration protocol calculators. The calculators for all five protocols are closely aligned with the [Chesapeake Stormwater Network (CSN) Stream Restoration Protocols](https://chesapeakestormwater.net/resource/a-unified-guide-to-crediting-stream-and-floodplain-restoration-practices-in-the-chesapeake-bay-watershed/), which provide standardized guidelines for calculating the environmental benefits of stream restoration activities, such as nutrient (nitrogen and phosphorus) and sediment reductions. FieldDoc currently supports five protocols. The protocols, input fields, and calculations are based off of CSN's published research and shift year to year as the science evolves. Supported Protocols are: * Protocol 1. Prevented Sediment * Protocol 2. Denitrification in the hyporheic zone * Protocol 3. Floodplain reconnection * Protocol 4. Stormwater performance standard * Protocol 5. Outfall and gully stabilization # Mapping {% embed url="" %} This webinar explores the geospatial components of FieldDoc. FieldDoc offers geospatial data management unlike any other platform out there. Not only does the geospatial data link directly to your on-the-ground representations of restoration and conservation activities, but it also provides critical data to power the environmental benefit models in the system. This live walkthrough will arm you with essential tips and tricks to get geospatial data into your account and maximize your success. ## Recap and Keep Learning! ## Atlas Atlas visualizes your metrics and activity footprints. It is designed as a simple analytic tool. Data within a specific context is visible within the respective Atlas view. ## Map Editor ### Import You can import shapefiles, GeoJSON files, and even .csv files into FieldDoc. We encourage use of the Importer if you are batch creating records and have your geospatial data on hand, as it will save you lots of time. ### Create New Records From the Map Editor, you can create new activity records. Note: This functionality is not intended to be your entry point for multiple record creations. #### Activity Records Using the draw tools, you can add new activity records to your portfolio via Map Edit. Once delineated, you can add some attribute data such as the `Activity name` and `Activity description`. Additional attribute data will need to be added within the record. ### Edit Records Within the Map Editor, you can edit the geometry within each Activity record feature. # Reporting {% embed url="" %} Ready to share your activity records with a funder? Or report progress towards implementation? Watch this webinar! Reporting follows this workflow: 1. Find your Pact, 2. Link or create Activities 3. Associating Programmatic Metrics 4. Tracking implementation progress. ## Recap and Keep Learning! {% hint style="danger" %} Pacts have replaced Projects If you use FieldDoc to meet grant reporting compliance requirements, you must now use Pacts to share your progress. Pacts streamline reporting and protect your organization portfolio's integrit {% endhint %} # Advanced Features {% embed url="" %} Once you have mastered the foundational components of FieldDoc and built your authoritative portfolio of nature-based records, you can work with Advanced Features to enhance data management and analytical capabilities. ## Recap and Keep Learning! ### Linked Pages Linked pages allow you to place directly into your Project folders and Activitiesrecords external links that can be opened in a pop-out in FieldDoc. These linked pages display as a tile and invite users to bring back into FieldDoc any additional documentation relevant to your work. If the URL that hosts your Linked Page is not supported, please reach out to our team so we can explore configuring it. ### Integrations (Beta) Integrations allow you to connect and sync your FieldDoc portfolio with a third party application. At this time, we support Airtable and ArcGIS Online. If you are interested in using these integrations, please get in touch with our team. The integrations are in Beta mode and are not intended to be used without support and guidance. ### Workflows Use the provided templates or configure your own workflows to push and pull record from one of the supported FieldDoc integrations! --- [Next Page](/llms-full.txt/1)