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

# 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 ](https://help.fielddoc.org/essentials/model-outputs.md)outcomes. Manual metrics can be attached to activity records from curated lists. The most common lists are associated with a [pact](https://help.fielddoc.org/essentials/pacts.md). 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.&#x20;

{% hint style="info" %}
**Looking to calculate modeled metrics?** To look closer at how modeled metrics are managed, start [here](https://help.fielddoc.org/essentials/activities/models.md).&#x20;
{% 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

<table><thead><tr><th width="175.625">Field</th><th>Description</th><th>Details</th></tr></thead><tbody><tr><td>'planned_value' </td><td>The proposed outcome, or target goal, that will be achieved at the end of the performance period.</td><td>This is a number field. This field is typically set when a record is created and remains the same. </td></tr><tr><td>'implemented_value`</td><td>The amount implemented to date.</td><td>This is a number field. This field is typically updated during reporting periods, with the final implementation report displaying the final implemented value.</td></tr></tbody></table>

## 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. Navigate to the **Metrics** tab.
2. Select the **Pact** within which you want to add **Metrics**.
3. Click **+ Add Metrics**. A list of all metrics associated with the Pact appears.
4. 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.
5. All selected metrics will appear in the metrics view with their `planned_value`.&#x20;

{% @arcade/embed flowId="NjIq7KHEp97fhnizRl4m" url="<https://app.arcade.software/share/NjIq7KHEp97fhnizRl4m>" %}
{% endtab %}
{% endtabs %}

## Enter implementation progress for metric values for reporting

{% tabs %}
{% tab title="Enter within activity record" %}

### Step-by-step instructions

1. Navigate to the **Metrics** tab.
2. Under **Programmatic Metrics**, select the **Pact** within which you want to add **Metrics**.
3. Click  the ellipses next to the metric that you want to update. A pop up with `planned_value` and `implemented_value` fields appears.
4. Enter in the `implemented_value`. Click Save.
5. 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.

&#x20;
{% endtab %}
{% endtabs %}


---

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