> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/become-a-tability-power-user/features/check-ins.md).

# Check-ins

Keep outcome progress, confidence, and context current with regular check-ins

Check-ins are recurring progress updates for outcomes or key results. Each check-in records the current metric value, your confidence in reaching the target, and the context your team needs to understand what changed.

Regular check-ins help teams:

* see progress and confidence trends over time
* identify risks before the end of a goal cycle
* discuss blockers and offers of help in context
* keep dashboards, presentations, and reports current

## Complete a check-in

Start with [How to create check-ins](/docs/become-a-tability-power-user/features/check-ins/how-to-create-check-ins.md) for the step-by-step workflow. You can find updates that need your attention in **My focus**, then open an outcome to post its latest value, confidence, and analysis.

For guidance on writing a useful update, see [Track progress with check-ins](/docs/tutorials/track-progress-with-check-ins.md) and [Check-ins best practices](/docs/tutorials/track-progress-with-check-ins/check-ins-best-practices.md).

## Automate progress data

If your metric already lives in another system, you can reduce manual entry with a data source, Zapier, or the Check-ins API:

* [How to automate check-ins](/docs/become-a-tability-power-user/features/check-ins/automate-check-ins.md)
* [Using the Check-ins API](/docs/become-a-tability-power-user/features/check-ins/using-the-check-ins-api.md)
* [Connect an outcome to a data source](/docs/become-a-tability-power-user/features/outcomes-key-results/data-sources.md)