> ## Documentation Index
> Fetch the complete documentation index at: https://test-8ad8522e-feat-ai-sre.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Event templates

> Learn how to use complete status update and status description templates to quickly publish status page events

Manually filling in event details is time-consuming and prone to missing key information. Flashduty Status Pages provide **event templates** that let you quickly publish events using pre-set content, reducing repetitive work.

Status pages support two template types: **complete status updates** (pre-defined templates) and **status descriptions** (message templates).

***

## Complete status updates (pre-defined templates)

Complete status update templates are used to quickly create events with complete initial information. Each complete status update template contains the following fields:

| Field           | Description                         |
| --------------- | ----------------------------------- |
| **Title**       | Event title                         |
| **Type**        | Event type: Incident or Maintenance |
| **Status**      | Initial event status                |
| **Description** | Detailed event description          |

### Use cases

Complete status update templates are ideal for foreseeable, recurring event scenarios. For example:

* **Routine maintenance**: Create a template titled "Scheduled System Maintenance" with status pre-set to Scheduled and standard maintenance notification wording in the description
* **Known issues**: Create templates for common service degradation scenarios with pre-set titles and descriptions

### Manage complete status update templates

<Steps>
  <Step title="Create a template">
    In the status page settings under the **Event Templates** tab, select **Complete status update** and click **Create Template**. Fill in the title, type, status, and description.
  </Step>

  <Step title="Use a template">
    When publishing an event, select a complete status update template. The system auto-fills the template fields, which you can then adjust as needed.
  </Step>

  <Step title="Edit or delete">
    You can modify a template's title, description, and status at any time, or delete templates that are no longer needed.
  </Step>
</Steps>

***

## Status descriptions (message templates)

Status description templates are used to pre-set update messages for different event status stages. Unlike complete status update templates which focus on event initialization, status description templates focus on the notification wording used as events progress.

Each status description template contains the following fields:

| Field        | Description                               |
| ------------ | ----------------------------------------- |
| **Title**    | Template name                             |
| **Type**     | Event type: Incident or Maintenance       |
| **Messages** | Pre-set update text for each event status |

### Message mapping

Status description templates provide pre-set text for each status in the event lifecycle:

<Tabs>
  <Tab title="Incident">
    | Status            | Example pre-set message                                                    |
    | ----------------- | -------------------------------------------------------------------------- |
    | **Investigating** | "We are investigating an issue affecting \[service name]."                 |
    | **Identified**    | "The issue has been identified and the team is actively working on a fix." |
    | **Monitoring**    | "A fix has been implemented and we are continuing to monitor."             |
    | **Resolved**      | "The issue has been resolved and service is operating normally."           |
  </Tab>

  <Tab title="Maintenance">
    | Status        | Example pre-set message                                      |
    | ------------- | ------------------------------------------------------------ |
    | **Scheduled** | "Planned maintenance will begin at \[time]."                 |
    | **Ongoing**   | "Maintenance is in progress. Some services may be affected." |
    | **Completed** | "Maintenance is complete. All services are back to normal."  |
  </Tab>
</Tabs>

### Use cases

Status description templates are ideal for standardizing event update wording, ensuring that different team members use consistent language when progressing events.

### Manage status description templates

<Steps>
  <Step title="Create a template">
    In the status page settings under the **Event Templates** tab, select **Status description** and click **Create Template**. Fill in the title, type, and message content for each status.
  </Step>

  <Step title="Use a template">
    When adding a timeline update to an event, select a status description template. The system auto-fills the message text based on the current event status.
  </Step>

  <Step title="Edit or delete">
    You can update a template's title, type, and message content at any time, or delete templates that are no longer needed.
  </Step>
</Steps>

***

## Template preference

You can choose a **default template type** (**Status description** or **Complete status update**) at the top of the **Event Templates** tab in the status page settings. When publishing events, the corresponding template list will be shown by default. This preference does not prevent you from switching to other template types.