Free template

Weekly engineering report template.

A weekly engineering report is a one-page summary of what a development team shipped, what is in review, what is blocked and what comes next. This free template gives you the four sections and the wording; copy it or download it as Markdown.

What goes in a weekly engineering report?

Four sections, in this order, one page. Write it on Friday afternoon or Monday morning, in plain words, so that someone outside engineering can read it in two minutes. Numbers go in the first line of each section; names go next to what they shipped, never next to a grade.

  1. 1Shipped this weekMerged and deployed. One line per item, in plain words, with the person who carried it.
  2. 2In reviewOpen pull requests waiting on someone. Say who, and since when.
  3. 3BlockedWhat cannot move and why. One line each, with the ask.
  4. 4Next weekThree to five items the team intends to ship. No more.
Weekly engineering report · Team · Week NMon D → Fri D
1Shipped this week• PDF export of invoices · Marie• Webhook consumer moved to a queue · Kofi• 3 bug fixes on billing screen · Tomás
2In review• Rate limiter per customer · waiting on Kofi · 3 days• Feature flags for GHES · waiting on Inès · 1 day
3Blocked• Payment webhooks migration · blocked 14 days · needs product decision on retries
4Next week• Finish rate limiter• Start audit log• On-call: Léa
Or skip the writing

Generate it from GitHub automatically.

Squadlog fills these four sections from your team’s commits, pull requests and reviews: what shipped in plain words, what is in review, what is blocked and for how long. Every Monday at 08:00, as a web page and a PDF, for every manager of the team.

Questions

About weekly reports

All answers →
  • One page. Four sections, a number in the first line of each, one line per item. If it takes more than two minutes to read, cut.
Stop writing it by hand on Friday evening.7-day free trial, then 6 € per developer per month. Managers who only look are free.