Weekly Engineering Update Template
A five-minute read that keeps stakeholders (leadership, other teams, sometimes the whole company) honestly informed without needing a meeting. The value is in consistency and honesty.
A weekly update that only ever says "everything's great" stops being trusted.
How to use this document
- Write it the same day every week (e.g. Friday afternoon or Monday morning) so it becomes a habit, not a scramble.
- Be honest about what's blocked or slipped, that's the whole point of a status update. Good news travels itself; the update's job is surfacing the bad news early.
- Keep it skimmable: bullets over paragraphs, bold the one-line takeaway per section.
Week of [date]
Team: [team name]
Author: [name]
TL;DR
One or two sentences. If someone reads only this, what should they know?
[Summary]
Shipped this week
What actually went live, merged to main, or reached users. Not "started" and not "in progress."
- [Item], [one-line impact, e.g. "reduces p95 latency on X by 40%"]
- [Item]
In progress
What's being worked on now, with a real status, not just a project name.
| Item | Status | Expected | Notes |
|---|---|---|---|
| [Project] | [On track / At risk / Blocked] | [date] | [brief context] |
| [Project] | [status] | [date] |
Blocked / at risk
Say it plainly. Don't bury a blocker inside "in progress."
That's how surprises happen two weeks later.
- [Item], blocked on [what/who] since [date]. [What's needed to unblock.]
Metrics
Whatever your team actually tracks: reliability, velocity, whatever matters. Pull real numbers.
Don't estimate.
| Metric | This week | Last week | Trend |
|---|---|---|---|
| [e.g. Uptime] | [99.95%] | [99.98%] | [↓ see incident note] |
| [e.g. Deploys shipped] | [12] | [9] | [↑] |
| [e.g. Open P0/P1 bugs] | [3] | [5] | [↓] |
Incidents / notable issues this week
[If any, link postmortems. If none, say "None" rather than omitting the section.]
Coming up next week
- [Planned item 1]
- [Planned item 2]
Asks / need from others
Explicit requests. A decision needed, a review needed, a dependency from another team.
- [e.g. Need design review on X by Wednesday to stay on schedule]
Example: filled TL;DR + Shipped
TL;DR: Shipped CSV export and the search performance improvement. Billing migration is now at risk because of an upstream API rate-limit change we found mid-week.
Shipped this week
CSV export from table view. First requested feature to ship from the Q1 backlog, closes 14 open support tickets.
Search index rework. p95 search latency down from 1.8s to 210ms for large workspaces.
Blocked / at risk
Billing migration, blocked since Wednesday on a rate-limit change from [payment provider]. Need their support team to raise our quota. Ticket filed, ETA unknown.
이 템플릿을 팀 워크스페이스로 복제하려면 → rootr.io