# Templates

Reusable blueprints that prefill event create flows.

Source: https://statusdashboard.com/docs/events/templates

> This is a plan-gated feature. If it isn't available in your account, visit the [Billing](/docs/org-mgmt/billing) page or contact support to review your options.

Event templates store reusable playbook copy and defaults your team applies when creating new incidents, maintenance windows, or informational notices. Pick a template from [Templates](/app/templates) to prefill title, description, and other standard fields, then complete instance-specific details before publishing.

***

## Overview
Event templates store **playbook fields only** — the language and defaults your team reuses across events. They do not include instance-specific inputs such as affected components, workflow status, the first timeline message, publish state, or maintenance window times.

## What templates store
| Field                  | Incident | Maintenance | Informational |
| ---------------------- | -------- | ----------- | ------------- |
| Template name          | required | required    | required      |
| Title                  | required | required    | required      |
| Description            | required | required    | required      |
| Impact analysis        | optional | optional    | —             |
| Coordinator            | optional | optional    | optional      |
| Notifications          | optional | optional    | optional      |
| Segment targeting      | optional | optional    | optional      |
| Custom attributes      | optional | optional    | optional      |
| Maintenance automation | —        | optional    | —             |

## Using a template
1. Open [Templates](/app/templates).
2. Create or edit a template with your team's standard copy and defaults.
3. From **Events**, choose **From template**.
4. Playbook fields are prefilled; complete components, status, timeline message, times (maintenance), and publish.