> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hire-balt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routines

> The tasks Balt does on his own, on a schedule or after an event.

A routine is a task Balt takes on without being chased: an update every Monday, a recap after each meeting, a follow-up when a quote goes unanswered. Find them under **Routines**, in the console.

![Your routines](https://mintcdn.com/balt/2sSdIKl16CvfyLFT/images/screens/en/routines-list.png?fit=max\&auto=format\&n=2sSdIKl16CvfyLFT\&q=85\&s=e3fa30d20d05940762a9b29bd9b58caf)

| Tab | What you find there |
| - | - |
| **Personal** | The routines you asked Balt for |
| **Organization** | The Balt team's routines, and the ones an administrator switched on for you |
| **Discovery** | Use cases Balt suggests, and routines your colleagues shared |

## For you or for the whole organization

A well-tuned routine rarely serves one person. A salesperson's Monday update serves the whole sales team, a project lead's meeting recap serves every project lead. Instead of everyone reinventing the same process, one person gets it right once and the whole organization benefits.

There are two ways to do it.

| | Share in Discovery | Deploy to organization |
| - | - | - |
| Who can | Any member, with one of their routines | An administrator, with one of their routines |
| What others get | A card in the **Discovery** tab, which they use if they want | The routine, switched on for them with nothing to do |
| Who adjusts it | Everyone adapts their routine as they like | The administrator decides whether people may change it |
| Follow-up | None, each routine lives its own life | The administrator sees who has it, who's waiting and who switched it off |

Sharing suits a good practice you suggest. Deploying suits a process the whole team should follow the same way. See [Share a routine](https://docs.hire-balt.com/en/routines/share.md) and [Deploy to organization](https://docs.hire-balt.com/en/routines/deploy.md).

## A colleague's routines

An administrator can see a colleague's routines: in **Routines**, pick the person in the **You** selector, next to the search. If they pause or delete one, the person gets an email.

## Everything about routines

> [card] [Create a routine](https://docs.hire-balt.com/en/routines/create.md)
>
> Ask Balt for it, what sets it off, its mode

> [card] [A routine's page](https://docs.hire-balt.com/en/routines/routine-page.md)
>
> Where it answers, what it does without asking, its states

> [card] [Runs and versions](https://docs.hire-balt.com/en/routines/runs-and-versions.md)
>
> Each run's result, and going back

> [card] [The Balt team's routines](https://docs.hire-balt.com/en/routines/balt-team.md)
>
> The ones on from day one

> [card] [Share a routine](https://docs.hire-balt.com/en/routines/share.md)
>
> Offer it to your colleagues in Discovery

> [card] [Deploy to organization](https://docs.hire-balt.com/en/routines/deploy.md)
>
> Switch it on for everyone, for administrators only

> [card] [Follow a deployed routine](https://docs.hire-balt.com/en/routines/follow.md)
>
> Who has it, who's waiting, and improving it

> [card] [Collect answers from the team](https://docs.hire-balt.com/en/routines/collect.md)
>
> Ask each colleague and get the summary


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.