> 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/help-center/metrics/adding-and-editing-metrics/where-do-i-add-metrics-on-an-activity-record-a-pact-or-both.md).

# Where do I add metrics: on an activity record, a pact, or both?

Metrics are specific to activity records. The metrics added to individual activity records are rolled up and display on the parent overview page. Overview pages exist for pacts and nested folders.

For basic users who are using FieldDoc to apply to a funding opportunity, you will add your metrics once the activity record has been added to a pact. Only once an activity record has been linked to a pact can you access and select metrics from the list provided by the Program. We call these programmatic metrics. 

Standard users can manage their own curated list of organizational metrics. Organizational metrics can be added to activity records from within the organization's portfolio. 

## How to add a metric

To add a metric to an activity record: 

* open up the edit activity modal. 
* Navigate to the metric tab. 
* If there are metrics available to be selected, a button will appear that you can click. 
* This will open up the list of available metrics. 
* Add in the `planned_value`. If the activity is complete, add the `implemented_value` too.

{% hint style="info" %}
All metrics should have a `planned` value.
{% endhint %}


---

# 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/help-center/metrics/adding-and-editing-metrics/where-do-i-add-metrics-on-an-activity-record-a-pact-or-both.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.