Eng Status Rollup

Demo

Click to play with sound.

---
name: Eng Status Rollup
description: Rolls up team engineering status into an exec-ready update covering progress, risks, and asks. Use weekly or before leadership syncs to replace noise with a clear signal.
---

# Eng Status Rollup

Execs do not need a feature list. They need to know: are we on track, what might go wrong, and what do you need from them? Everything else is noise that buries the signal.

## The Three-Section Format

Every rollup uses exactly three sections. Progress: what shipped or advanced materially since the last update. Risk and blockers: what is threatening the plan, and what is the current mitigation. Asks: what decision or resource is needed from leadership, with a deadline.

## Progress Section Rules

Lead with outcomes, not activities. 'Auth service is live for 20% of users' beats 'We finished the auth service work.' If nothing shipped, say so and explain why in one sentence. Avoid velocity metrics that require context to interpret; use milestone language instead. Cap this section at 4 bullet points.

## Risk and Blockers Section Rules

Each risk gets: a one-line description, the likelihood (high / medium / low), the impact if it materializes, and the current mitigation. Do not soft-pedal risks to look in control — the rollup's credibility depends on raising real issues before they blow up. A status report with no risks is almost always missing something.

## Asks Section Rules

An ask is a specific decision or resource with a clear owner and a date by which a response is needed. 'We need more headcount' is not an ask. 'We need approval to hire 1 senior backend engineer in Q3 to hit the platform migration date; decision needed by July 1' is an ask. No more than 2 asks per update — more than that suggests prioritization has not happened yet.
… install to load the full skill