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

# Routines

> Create repeated workflows that run on a schedule or on demand.

Routines help with repeated work. User-created routines can run on a schedule or run manually. Some workspaces may also have Tendor-managed monitoring for connected inboxes, such as tender email summaries after Gmail or Microsoft 365 is connected.

<CardGroup cols={2}>
  <Card title="Watch integrations and routines" icon="circle-play" href="/guides/videos/integrations-and-routines">
    See how connected accounts and routines support repeated tender work.
  </Card>
</CardGroup>

## What routines are for

Use routines for work that happens repeatedly:

* Summarising tender opportunity emails through a connected inbox workflow
* Preparing a daily pipeline summary
* Keeping project memory and follow-up context current
* Checking for missing documents or next actions
* Running a recurring prompt for a personal or team workflow

Built-in or Tendor-managed examples may include tender inbox monitoring, weekly opportunity scans, nightly project memory updates, and daily pipeline summaries.

## Personal and team routines

| Routine type | Who can use it                                                    |
| ------------ | ----------------------------------------------------------------- |
| **Personal** | Created for your own work and connected accounts                  |
| **Team**     | Available to the organisation; admins and owners can create these |

The Routines page lets you filter by **All**, **Personal**, and **Team**.

## Create a routine

Open **Routines** and choose **New routine**. You can:

* **Create via chat** - Ask AI helps gather the missing details, then prepares the routine name, timing, review settings, and instructions.
* **Create manually** - Choose what the routine should check, when it should run, who owns it, and whether it should ask before taking action.

For scheduled routines, choose how often it repeats and what time it should run. For manual routines, run it when you need it.

## Write a good routine prompt

A routine should have one clear job. Include:

* What to check
* Which project, inbox, search, or connected account to use
* What output you want
* Who should review the result
* Whether the routine should only suggest actions or prepare changes for approval

Avoid combining unrelated jobs into one routine. Create separate routines for separate workflows.

## Routine examples

Use these examples as starting points, then adjust the inbox, project, owner, schedule, and review settings for your team.

| Routine                       | Trigger                                                           | Connected account                         | Review setting                          | Expected result                                                                          |
| ----------------------------- | ----------------------------------------------------------------- | ----------------------------------------- | --------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Tender inbox summary**      | Every weekday morning, or through Tendor-managed inbox monitoring | Shared tender inbox                       | Review before taking action             | A short summary of new opportunities, deadlines, attachments, and suggested follow-up    |
| **Weekly opportunity review** | Every Monday morning                                              | Opportunity searches and saved filters    | Suggest only                            | A ranked list of opportunities to assess, with reasons to review or skip each one        |
| **Missing evidence check**    | Before a project review meeting, or on demand                     | Project files and Library                 | Review before changing files            | A checklist of missing certificates, case studies, insurance documents, or company proof |
| **Project follow-up summary** | End of each week                                                  | Project workspace and connected task tool | Review before posting or creating tasks | A summary of open actions, owners, due dates, and suggested next steps                   |

## Review settings

Routines can either suggest work for review or prepare changes that need approval. Start with review turned on for anything that touches connected accounts, project files, or customer-facing work.

## Review runs and proposals

Each routine has a detail page where you can see previous runs, inspect failures, run it now, pause it, edit it, or delete it. Some routines may prepare proposals or suggested actions that need review before they are applied.

Review failed runs before editing the routine. A failure may mean the connected account expired, a file moved, a prompt was too broad, or the routine needs a narrower scope.

Routine outputs can also appear in **Results** when there is something durable to review. Approval requests and proposed actions appear in **Needs action** when they are waiting for you.

<CardGroup cols={2}>
  <Card title="Results and actions" icon="inbox" href="/guides/results-and-actions">
    Learn where routine outputs and approval requests appear.
  </Card>
</CardGroup>

## Connected-account routines

Some routines need a connected account, such as Gmail or Microsoft 365. If the account is disconnected or expired, reconnect it from **Integrations** or **Settings -> Security -> Connected Accounts**.

User-created routines currently run manually or on a schedule. If your team needs inbox monitoring that reacts to tender-related email activity, connect the relevant email account and work with Tendor to enable the matching monitored workflow.

<Warning>
  Start with narrow prompts. A routine should have one clear job, clear review expectations, and access only to the accounts or files it needs.
</Warning>