# Weekly update format

Use for a concise status page that lets readers scan shipped work, metrics, next work, and risks.

## Great instance

- Leads with what changed since the last update.
- Uses a small metrics table with deltas and interpretation.
- Makes next commitments concrete.
- Flags risks early enough for help.

## Cut

- Activity logs, gratitude sections, and vague momentum claims.
- Metrics without baseline or meaning.
- Long paragraphs that bury the ask.

## Skeleton

```markdown
# Weekly update: <team or project>, <date>

## Shipped
- <user-visible change and proof>

## Metrics
| Metric | This week | Previous | Meaning |
| --- | --- | --- | --- |

## Next
- <commitment, owner, expected proof>

## Risks
- <risk, needed decision or help>
```

## Section prompts

- Keep paragraphs under four lines.
- Put numbers in the table, interpretation in the meaning column.
- Make each risk a decision target.
- Prefer shipped outcomes over effort.

## Renderer moves

Catalog: ../building-artifacts.md#what-each-file-type-becomes - md doc reader sections; table cell anchors.