> 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/how-do-i-add-a-metric-to-an-activity-record.md). # How do I add a metric to an activity record? Each activity record can contain both programmatic and organizational metrics. Remember, a metric is a value that someone enters or reports directly for a record (or pact)—it’s *declared*, not calculated. That also means that it has to be manually entered or imported to each record. There are two pathways to manually enter metrics in FieldDoc: within an activity record's Edit Activity modal or within the activity record metric table view. ## Enter via Edit Activity modal If you only have a handful of records, I recommend using the edit activity modal to enter your metric data. * Navigate to the Edit Activity modal. * Open the Metrics tab. * Click the **+ Add Metrics** button. * A list of all metrics available to select appears. Scroll through the list and select all metrics that you want to add to the record. * For the metric to be added to the activity, you must enter a value into the `planned_value` field. * The metrics added via the modal will display on the Activity Overview tab. ## Enter via table view Table views for metrics are available within folders, records, and pacts. The table view is a great way to add metrics and targets (`planned_values`), and then track progress toward implementation for each metric. From the table view, there is less clicking around and more data entry that can occur per minute. Watch out, the table views are not exactly like an excel spreadsheet. Here are some tips to consider: * If you are entering data quickly, it might not save everything. Make sure that the table indicates the work has saved before you complete your next entry. This is especially important if you do not have a strong internet connection. * If you want to use keyboard shortcuts to copy and paste, make sure to include the name *and* key columns. --- # 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/help-center/metrics/adding-and-editing-metrics/how-do-i-add-a-metric-to-an-activity-record.md?ask=&goal= ``` `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.