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

# Templates

> Save an evaluation configuration so you can re-launch or schedule it.

A **template** saves a full evaluation configuration — agents, personas, test sets, metrics, and run settings — so you can launch the same evaluation again without rebuilding it, or put it on a recurring [schedule](/concepts/runs/overview#scheduled-runs).

## What a template stores

| Saved            | Notes                                                                                   |
| ---------------- | --------------------------------------------------------------------------------------- |
| **Agents**       | One or more. Required.                                                                  |
| **Personas**     | One or more. Required.                                                                  |
| **Test sets**    | One or more, optionally narrowed to specific test cases. Required.                      |
| **Metrics**      | The metrics to evaluate against.                                                        |
| **Mutations**    | Any [agent mutations](/concepts/agents/mutations) to test alongside the base agent.     |
| **Iterations**   | How many times each test case runs.                                                     |
| **Concurrency**  | How many simulations run in parallel.                                                   |
| **Sub-sampling** | If enabled, the sample size and a fixed seed, so each launch evaluates the same subset. |

A template needs at least one agent, one persona, and one test set.

## Creating a template

Templates are built from the **Launch** page, not a separate form — you set up a run as usual, then save it.

1. Go to the **Launch** page (on the **Templates** page, **Create Template** takes you here).
2. Select your agents, personas, and test sets, and choose iterations, concurrency, metrics, and any mutations.
3. Click **Launch ▾ → Save as Template**, give it a name, and save.

<img src="https://mintcdn.com/coval-2e18a559/PsZjYYktmurY_8PN/images/templates/save-as-template-light.png?fit=max&auto=format&n=PsZjYYktmurY_8PN&q=85&s=59ebcd30fc6bcbbc8786e872d033878c" alt="The Launch page with the Launch button's dropdown open, showing the Save as Template option" className="rounded-lg block dark:hidden" noZoom width="2656" height="1522" data-path="images/templates/save-as-template-light.png" />

<img src="https://mintcdn.com/coval-2e18a559/PsZjYYktmurY_8PN/images/templates/save-as-template-dark.png?fit=max&auto=format&n=PsZjYYktmurY_8PN&q=85&s=16842e8edffc2c4dcda3a99456b00a4b" alt="The Launch page with the Launch button's dropdown open, showing the Save as Template option" className="rounded-lg hidden dark:block" noZoom width="2658" height="1522" data-path="images/templates/save-as-template-dark.png" />

The new template opens on its own detail page, where you can edit it later.

## Launching from a template

On the **Launch** page, open the **Template** dropdown and pick a saved template. Its agents, personas, test sets, metrics, and run settings populate the form. Adjust anything you want for this run, then click **Launch**.

<Note>
  Changes you make on the Launch page apply to that run only — they are **not** saved back to the template. To change the template itself, edit it on its detail page.
</Note>

## Editing and deleting

Open a template from the **Templates** list to edit it. You can rename it, change the description, and update any part of the configuration — agents, personas, test sets, metrics, mutations, iterations, concurrency, or sub-sampling — then **Save Changes**.

To delete a template, click **Delete** and confirm by typing its name. A template can't be deleted while an active scheduled run still points to it — disable that schedule first.

## Scheduling recurring runs

Any template can drive a recurring evaluation. From the **Launch** page, set up the run and choose **Launch ▾ → Schedule** to run it on an interval (e.g. every 6 hours) or at a set time of day. The schedule always points to a template, so updating the template changes what the schedule runs.

See [Scheduled Runs](/concepts/runs/overview#scheduled-runs) for the full scheduling options and how to manage them.
