> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/working-in-the-smartmodel-tm/add-key-drivers-and-results.md).

# Add Key Drivers and Results

## How do I add Key Drivers + Results?

{% embed url="<https://youtu.be/IGOWm4xadNo>" %}

### Step by Step process

1. Right click anywhere in the row or highlight multiple rows *(multi-select works!)*
2. Hover over "Drivepoint"
3. Select: "Enable Key Driver/Result"
4. Wait a few minutes and view your results in Quick Edit & the Agent *(should be 2min or less!)*

## **✨ New Key Drivers and Results tab**

A new standardized tab called "Key Drivers + Results" is being added to all customer SmartModels™. This tab consolidates all key drivers (like DTC AOV, conversion rates, marketing spend) and key results (P\&L outputs, metrics) in one central, locked tab.

Previously, key drivers were hardcoded in the app; now they're stored directly in the model, giving customers the ability to self-serve and curate which drivers appear in Quick Edit and the Agent.

#### Format Requirements

For the Key Drivers + Results tab to be valid and processed correctly by Drivepoint, the following format rules must be met:

**Header rows (Row 2 and Row 3)**

* Cell **C2** must contain the value: `End of Period`
* Cell **C3** must contain the value: `Period Type`

**Date columns (starting at column K)**

* **K2 and all subsequent date columns in Row 2** must contain a valid date that falls on either the **last day of the month** (e.g., `1/31/2025`) or the **1st of the month** (e.g., `1/1/2025`)
* **K3 and all subsequent date columns in Row 3** must contain either `Forecast` or `Actual`

> ⚠️ If any of these requirements are not met, the tab will fail validation and Drivepoint will not be able to process it. Double-check these cells before saving your model.


---

# 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://docs.drivepoint.io/working-in-the-smartmodel-tm/add-key-drivers-and-results.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.