> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/metrics/metrics-programmatic.md).

# 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.md). 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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.fielddoc.org/essentials/metrics/metrics-programmatic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.