# Track progress with check-ins

## What is a check-in?

Check-ins are the way that you and your team will keep your key results up to date in Tability. By answering three simple questions, you'll be able to track progress, uncover issues, ask for assistance, and celebrate victories. Each week (or more, depending on the plan settings), you'll be asked for:

* The updated metric for your key result
* How confident you are on achieving the key result
* Details about why you're confident or not confident.

Tability will track your check-ins over time, creating a graph that displays how the metric has changed, how confidence has changed, and highlighting any discussions had in the platfom.

## Why check-ins?

Setting good goals at the beginning of the quarter is only half the work. Without a good strategy to track progress, you'll see focus drifting away from what matters the most.

Tability has a built-in reminders system that will take care of nudging outcomes/key results owners when updates are due.

Regular check-ins will:

* Improve accountability
* Increase transparency
* Drive alignment between teams
* Accelerate execution

## Finding your pending check-ins

All of the key results that are assigned to you will appear in your **My focus** page. The key results that need to be updated with a check-in will have a red dot appearing on them:

<figure><img src="/files/bquG8Or4jsHW1RL5qvei" alt=""><figcaption></figcaption></figure>

## How to create a check-in

<figure><img src="/files/tUD4iLH3Q9I1nnGEoMIX" alt=""><figcaption></figcaption></figure>

1. Click on an outcome/key result
2. In the detail panel, click on the *Create check-in* button
3. Fill in the form and click *Create* to save your check-in

## Best practices

### Use trends to express your confidence

Tability will display a progress chart to show you how your progress is going. Use this chart to estimate your future progress and adjust your confidence accordingly.

### Write meaningful updates

Don't just write your progress number. Your check-ins should help your team answer these 5 questions:

* **Progress:** where are we today?
* **Expectation:** is this where we're supposed to be?
* **Trends:** are we getting better or worse?
* **Root cause:** what do we think happened?
* **Action:** should we do things differently?

Some answers will be covered by the progress chart, but it's still important to provide context – this is the easiest way to get help.

### Not more than 2 yellow statuses in a row

<figure><img src="/files/LpHCDQ1ZTHhcD1zxICpJ" alt=""><figcaption></figcaption></figure>

Your check-ins will have confidence status attached to them:

* Green = on track
* Yellow = at risk
* Red = off track

Make it a rule that you can't have more than 2 yellows in a row. The 3rd check-in needs to be either green or red.

Adopting this rule will help everyone confront risks earlier instead of hedging their opinions for too long.

## Learn more:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td></td><td><strong>Automate check-ins</strong></td><td>Pull metrics automatically from your other tools to simplify check-ins</td><td><a href="/pages/klk6IPoEpahhrKt0t7iV">/pages/klk6IPoEpahhrKt0t7iV</a></td><td><a href="/files/Dr66hid41LgBJpR7IH4q">/files/Dr66hid41LgBJpR7IH4q</a></td></tr><tr><td></td><td><strong>Check-ins best practices</strong></td><td>How to get the most value from writing (and reading) check-ins</td><td><a href="/pages/GxkDULmzgW7xhEvifStI">/pages/GxkDULmzgW7xhEvifStI</a></td><td><a href="/files/pPWNaqpPe9vP0gvSpV8z">/files/pPWNaqpPe9vP0gvSpV8z</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://guides.tability.io/docs/tutorials/track-progress-with-check-ins.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
