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

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.