Templates · Newsletters
Weekly team digest template
A short weekly roundup of decisions, links and shout-outs
Start with this template →Sign in
Opens on reph with the template ready to start. No account needed; sign in to keep your document.
Filled example
The template filled in for a made-up company, so you can see what good looks like.
Platform team digest, week of September 28
Week of September 28, 2026
This week in numbers
Decisions made
- Postgres 17 upgrade moves to November 4: the replica lag tests need another week of production-shaped traffic. Ask Hannah.
- Feature flags stay in our own service, not a vendor: the cost comparison came out at $41,000 a year for a vendor against roughly two engineer days a quarter to maintain ours. Ask Tariq.
- Code freeze for the EU residency beta starts October 20: only fixes for the beta branch after that date. Ask Luis.
Worth reading
Shout-outs
- Rosa: rebuilt the deploy dashboard in her first week, and on-call now sees failed canaries before Slack does.
- Aiden: stayed on the September 22 incident until the fallback planner was in, then wrote the timeline the next morning.
- Femi from Sales: brought us the exact SSO error a prospect hit, which turned a vague ticket into a one-line fix.
Next week
- Finish the replica lag test run and publish the results.
- Ship rate-limit dashboards for the public API.
- Pair with Integrations on the PagerDuty webhook retries.
- Rotate digest author: Tariq writes next week.
The template
Show the blank template
Weekly team digest
Week of [date]
This week in numbers
Two or three numbers the team watches. Keep the set stable so week over week means something.
Decisions made
Each with the reason and who to ask, so nobody relitigates it in a thread.
- [Decision]: why, and who to ask.
Worth reading
Shout-outs
Name the person and the specific thing they did.
Next week
Questions
- When should it go out?
- Same day and time every week, Friday afternoon works for most teams
- How long should it be?
- Short enough to read on a phone in two minutes
- Who writes it?
- Rotate the author weekly so it does not become one manager's chore
- How does the team get it each week?
- Publish it, then use Set up sending on the doc to email a workspace list; teammates join with the list's signup link from the workspace's Audiences panel
- Can I check it first?
- Send me a test in the send dialog emails only you; the subject starts as this week's dated title
Fill it with your agent
Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.
Find my reph doc "Weekly team digest" with search_docs, then read it with read_doc. Draft this week's digest from the decision log, sprint board, merged pull requests and team channel highlights since last Friday. Find last week's digest with search_docs and call get_reader_signals to see which links were clicked. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (decisions with no owner, estimated numbers) with add_comment quoting that section's heading line, then call request_review with a one-line summary.
Related templates
Start with this template →Sign in