# Incident write-up published email template

> Explore this incident write-up published email template for technology and software. Preview its status, three key details, and next action.

Source: https://design.moosewave.com/templates/incident-write-up-published-email-template/

---

Transactional Alerts & status

# Incident write-up published email template

A post-incident report shared publicly including the uncomfortable parts.
Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.
**Best for**
: A post-incident report shared publicly including the uncomfortable parts
**Structure**
: State or event context · Plain-language explanation · Three labelled facts
**Style**
: timetable · quiet sans
**Industry fit**
: Technology & software
Responsive design preview

## See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.
Want to change the copy and style?

## Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.
Message anatomy

## A useful starting point, with the important parts named.

The outage was nineteen minutes. The detection failure was forty-one, and that is the part worth reading and the part we have changed.

### What you can change

- Brand name
- Subject line
- Preheader
- Eyebrow
- Headline
- Supporting copy
- Primary action label
- Primary action URL

### What to keep clear

- State or event context
- Plain-language explanation
- Three labelled facts
- Primary and secondary action
- Support or privacy footer
Complete starting copy

## Read it as text, not only as a picture.

**From**
: Wheatfield Alerts
**Subject**
: What went wrong last Tuesday, in full
**Preheader**
: Including the 41 minutes before anybody noticed.
Incident report

### Including the part where we did not notice for forty-one minutes

The outage was nineteen minutes. The detection failure was forty-one, and that is the part worth reading and the part we have changed.

#### Outage

19 minutes

#### Time to detect

41 minutes

#### Changes made

3
Moosewave MCP

## Give an agent the structure, the job, and a stopping point.

The brief asks for a new draft and stops before send.

**Read the complete brief**
Connected work

## Take the design beyond the canvas.

Keep exploring

## Related transactional templates

[001 Transactional Open preview ↗ Alerts & status DNS change scheduled A name server change with the propagation reality explained Technology & software](/templates/dns-change-scheduled-email-template/)
[002 Transactional Open preview ↗ Alerts & status Mobile mast works A local network upgrade with the honest short-term downside Technology & software](/templates/mobile-mast-works-email-template/)
[003 Transactional Open preview ↗ Alerts & status Outage resolved An outage ending, with what was lost stated honestly Technology & software](/templates/outage-resolved-email-template/)
[004 Transactional Open preview ↗ Alerts & status Planned service work Neighborhood internet maintenance notice with expected outage and support options Technology & software · Community & public service](/templates/planned-service-work-email-template/)