TemplateDocs
Weekly team report
A weekly team report template built to be scanned in under a minute: wins, metrics against target, risks with an ask, and next week's focus.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your document
# Weekly report: Growth Engineering
**Week of:** Sep 1-5, 2026 · **Author:** Kabir
## Wins
- Shipped the referral-link redesign; click-through is up 18% in the first three days.
- Closed the flaky checkout test that had been blocking CI for two weeks.
## Metrics vs. target
Signups: 1,240 vs. 1,400 target (89%). Activation rate: 42% vs. 40% target (105%). CI pass rate: 91% vs. 95% target (96%).
## Risks (with asks)
CI pass rate is still below target - root cause is a shared test database that gets corrupted under parallel runs. Ask: two days from Platform to give CI its own ephemeral database.
## Next week's focus
Ship the onboarding checklist A/B test, pair with Platform on the CI database fix, and start discovery on the referral cap.
How to use it well
- →Lead with the metric, not the activity - "shipped the redesign" is a fact about your calendar, "click-through up 18%" is a fact about whether it worked.
- →A risk without an ask is just a complaint the reader can't act on. Naming exactly what you need, and from whom, is what turns a status report into something a manager can actually unblock.
- →Four sections, one screen. The moment a weekly report needs scrolling, people start skimming the wins and skipping the risks - which is the one section that most needs reading.