# Internal updates people open, read and act on.

Publish the weekly update, the launch brief or the incident review as a page only your team can open. People filter it to what concerns them, and you can see who has read it.

## Why updates get skipped

The weekly update is usually a long message in a busy channel, or an email nobody scrolls through. People read the first two lines and miss the risk in paragraph six. On Thursday you find out nobody saw the decision you needed.

A page can be read in pieces. Tessel’s product and engineering update above lets the mobile team filter to its own items, or hide everything that hasn’t changed since last week.

## A weekly rhythm

1. **Let the agent draft it** Give it the week’s closed tickets, metrics and standup notes. Ask for the same layout as last week, so people know where to look.
2. **Publish it to the team** In a team workspace, **Private** means everyone in the workspace can open it, and nobody else.
3. **Post the link where people talk** A private link pasted into Slack shows a plain card with no title, so nothing leaks into a channel with guests.
4. **Check who read it** **Views** lists each teammate who opened it and when. Then you can nudge the two people whose decision is due instead of the whole channel.

## Updates that work as pages

| Update | What the page adds |
| --- | --- |
| Weekly or monthly update | Filters by team, changes since last time, metric charts |
| Launch brief | Timeline, owners, a checklist with progress |
| Incident review | A timeline you can step through, with the fix and follow-ups |
| All-hands notes | The slides, the numbers and the Q&A in one place |
| Onboarding guide | A path through the first week, with links to every document |

## Every week in one place

Publish each week as its own artifact in an Updates project, and you can find any of them by what’s inside. Search for “when did we ship live ETAs?” and you get the week it happened. Or keep one living link that always shows this week, with past weeks in its version history.

> **Guests.** People in your team workspace can always open every link in it, whatever its mode. To share one update with a contractor, invite them by email for that artifact only.

## Limits

- There are no comments or reactions on the page. Discussion stays in your chat tool, with the link at the top of the thread.
- Views counts people who opened the link, not how far they read.

## Make your own

Have these ready:

- This week’s shipped work
- Metrics with last week’s values
- Risks with owners
- Decisions needed, with due dates

Then ask your agent:

```
Write this week’s team update as one self-contained HTML page, in the same
layout as last week’s (attached). Lead with a three-line summary. Then:
shipped, metrics with sparklines and week-over-week change, risks with status
and owner (expandable), decisions needed with owner and due date, and people
news. Add a team filter and a toggle that shows only what changed since last
week. Keep it calm and scannable.

Publish it privately to artifact.guru in the Updates project and give me the
link.
```

## Questions

### Can people outside the workspace see it?

Not while it’s Private. To include someone outside, share that one update with their email address.

### Can I see who hasn’t read it?

Views lists who opened a Private link. On an Email link it also lists the invited people who haven’t opened it yet.

Source: https://artifact.guru/use-cases/team-updates