> Source: https://mywaypoint.ai/docs/examples/weekly-escalation-write-up
> Documentation index: https://mywaypoint.ai/llms.txt


# A weekly escalation write-up

**You ask Chip to write the Monday escalation summary; it asks for last week's, mirrors its four sections & files a fresh document every week before the call.**


## For

- [For Engineering](https://mywaypoint.ai/for-engineering)
- [Trend analysis](https://mywaypoint.ai/use-cases/trend-analysis)
- [For Support](https://mywaypoint.ai/for-support)
- [For Product](https://mywaypoint.ai/for-product)

## In

- [Jira Cloud](https://mywaypoint.ai/docs/integrations#jira-cloud)
- [Slack](https://mywaypoint.ai/docs/integrations#slack)
- [Email](https://mywaypoint.ai/docs/integrations#email)

## Use case

```prompt-request
Every Monday I have to write up what happened with escalations last week for the leadership call. Can you do that instead of me?
```

## What Chip builds

No new table, since escalations already exist: one scheduled automation plus a filing convention.

- **The automation.** Every Monday at 06:00 it collects the previous week's escalations, writes the digest & files it as a document.
- **The document.** One per week, filed under the week it covers, so a re-run updates that week's document.
- **The sections.** The numbers, notable escalations, still open & trend, mirroring the pasted write-up.

![A document page headed Support Runbook Reviews intent, with Doc type, Path, Status & Description above the body](https://mywaypoint.ai/static/assets/chip-build/document-page-intent.png "Figure: a document Chip wrote, with its type, path & status shown above the body. Captured on a different build.")

Chip runs it against a real past week, then activates it & hands over that week's digest as a sample to mark up.

**How it runs now.** Every Monday before the call, the week's write-up is filed in the format the room already knows. Want it in Slack as well? That is one more sentence to Chip.