Weekly status report template for software teams, filled from GitHub and Slack in 15 minutes

A weekly status report has one job: tell people who weren't in the room what changed, what's at risk and what you need from them. Most reports fail at it for the same reason. They're written from memory on Friday afternoon, so they list activity ("worked on checkout") instead of outcomes, and the one risk that matters is buried in paragraph four.

This guide gives you a template that fits on one screen, a filled-in example, and the searches that pull each section straight from GitHub, Jira and Slack, so writing the report takes fifteen minutes instead of an hour of chasing people.

The template

Copy this into Notion, Confluence, a Google Doc or a Slack post:

# [Project name] status: week of [date]

Status: On track / At risk / Off track
One line on why: [the single most important thing a reader should know]

## Shipped this week
- [Outcome, not activity] ([link to PR or release])

## In progress, and when it lands
- [Item]: [expected date], [owner]

## Risks and blockers
- [Risk]: [impact if it happens], [what we're doing], [owner]

## Decisions and changes since last week
- [What changed]: [why], [link to the discussion]

## Asks
- [What you need, from whom, by when]

Five sections, in that order, because that's the order readers care about: did we deliver, what's next, what could go wrong, what changed, and what do you need from me.

A filled-in example

# Checkout redesign status: week of October 26, 2026

Status: At risk
One line on why: the payment provider's new API is two weeks late,
which pushes the beta from November 16 to November 30.

## Shipped this week
- Saved cards now work for returning customers (PR #412)
- Checkout error rate back under 0.5% after the retry fix (PR #418)

## In progress, and when it lands
- Address autocomplete: November 6, Priya
- Apple Pay: blocked on the provider API, see risks

## Risks and blockers
- Provider API delay: beta moves two weeks; we're building against
  their sandbox now so we lose days, not weeks. Owner: Sam

## Decisions and changes since last week
- Dropped PayPal from the beta scope: under 2% of test orders used it.
  Discussion: #proj-checkout thread, October 28

## Asks
- Marketing: confirm the November 30 beta date works for the launch email
  by November 4