> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/goals.md).
# Goals
Goals track one Userlane metric against a target and a due date, so an organization can show progress toward an outcome it is accountable for.
A goal is a time-bound commitment measured with Userlane data. You choose the outcome you are working toward, pick a metric that shows progress on it, and set a target to reach by a due date. Userlane updates the metric every day, so the goal always reflects where things stand without anyone assembling a report by hand.
Goals do not change HEART[^1]. Where a metric relates to a HEART dimension, the metric shows it, which gives you somewhere to look when progress stalls.
## What Goals do
Goals turn an outcome that an application owner is accountable for, such as faster onboarding or fewer data entry errors, into a number with a deadline. The same record can back a program review, a steering committee update, or a benefits realization report, and nobody has to export data into a spreadsheet to build it.
A goal tracks one metric against a target and a due date.
## Outcomes and metrics
Creating a goal starts with an outcome, which describes the result you expect, such as faster time to productivity, lower training cost, fewer mistakes, or lower support cost. You then choose a metric, which is how progress toward that result is measured. The outcome narrows the metric list to the ones that fit it.
Metrics draw on what Userlane already measures in the application, such as guide completion, task completion, validator results, and survey responses. A metric can only report a value once the matching content exists, so a task-based metric needs tasks defined for the application.
The outcome you choose narrows the list of metrics.
## How a goal measures progress
Every goal has a start date, which is today unless you change it. The start value is the metric's reading on that date, and progress is measured from there. You can set the start date in the past, which helps when a goal is created after the moment you wanted to measure from: a go-live that has already happened, for example, or a goal you had to recreate after a mistake.
The calculation method decides which period the current value covers. A **Rolling window** always shows performance over the last 30 days. An **Expanding window** shows performance from the start date to the current date.
By default a goal measures **Everyone**. To track a subset of users, such as one department, choose an audience[^2] when you set the metric details.
Set the calculation method, audience, and dates for a goal.
A goal stays **In progress** until its due date, even if the metric reaches the target earlier. On the due date, it becomes **Completed** if the metric meets or exceeds the target, and **Overdue** if it does not. Goals that are no longer active are listed on the **Archived** tab.
## Create a goal
Goals are created from the **Goals** page, in the **Intelligence** section of the portal sidebar.
{% stepper %}
{% step %}
#### Choose the expected outcome and the metric
Select **Create a Goal**, then select the outcome that best describes the result you are working toward. Then select the metric you want to track. The list only shows metrics that fit the outcome you chose.
{% endstep %}
{% step %}
#### Set the metric details
Select the content the metric is based on, for example the guides users should complete. Then choose the audience to measure, or keep **Everyone**, and select **Next**.
{% endstep %}
{% step %}
#### Set the goal details
Choose the **Calculation Method**, enter the **Target Value**, and give the goal a name your team will recognize. Check the **Start Date**, choose a **Due Date**, and select **Create a Goal**.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**Measuring from go-live.** To show progress from launch, set the start date to the go-live date, even if you create the goal afterwards.
{% endhint %}
## Relevant articles
{% content-ref url="/pages/TBF4QYHDMWQghy26u8xI" %}
[HEART](/intelligence/heart.md)
{% endcontent-ref %}
{% content-ref url="/pages/nJSkeXwSmCTopscQ7Fmx" %}
[Tasks](/intelligence/tasks.md)
{% endcontent-ref %}
{% content-ref url="/pages/TKBRGmMaapWk0xuF3XwG" %}
[Audiences](/administration/audiences.md)
{% endcontent-ref %}
{% content-ref url="/pages/i1K1cNUetLC3hx3jInea" %}
[Go-live: how to prepare for launch](/best-practices/go-live-how-to-prepare-for-launch.md)
{% endcontent-ref %}
## FAQ
Do goals change HEART?
No. Goal progress and goal status have no effect on HEART.
How often does goal progress update?
Once a day. Goal progress reflects the previous day's data and is not real-time.
When does a goal count as completed?
On its due date, if the metric meets or exceeds the target. A goal that reaches its target early stays in progress until the due date, and a goal that misses its target becomes overdue.
Can the start date of a goal be in the past?
Yes. Setting an earlier start date keeps the right starting point for a goal created after a go-live or recreated after a mistake.
What happens if the audience used by a goal is deleted?
Userlane shows a warning before the audience is deleted. If the deletion goes ahead, the goal measures everyone from the next daily update.
Does a goal need tasks or other content to work?
It depends on the metric. A metric based on tasks, guides, validators, or surveys needs that content in place before it can report a value.
[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it: Happiness, Efficiency, Adoption, Risk, and Task Success.
[^2]: An audience is a reusable group of users defined by attribute rules, used for targeting content and filtering analytics.
---
# 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://docs.userlane.com/intelligence/goals.md?ask=&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.
