--- title: "Engineering status report template · DeliverySheet" description: "The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape." canonical_url: "https://www.deliverysheet.com/blog/engineering-status-report" last_updated: 2026-08-21 meta: author: "Tan Gravam" "og:description": "The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape." "og:image": "https://www.deliverysheet.com/_og/s/o_3da885d6af78684f.png" "og:image:alt": "The status report that answers questions — DeliverySheet essay card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "The status report that answers questions — DeliverySheet" "twitter:description": "The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape." "twitter:image": "https://www.deliverysheet.com/_og/s/o_3da885d6af78684f.png" "twitter:image:alt": "The status report that answers questions — DeliverySheet essay card" "twitter:title": "The status report that answers questions — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) # **The status report that answers questions** 21 August 2026 · 3 min read · by [Tan Gravam](https://www.deliverysheet.com/about) ## **What should an engineering status report include?** **The short answer ** The status report worth sending has four sections and fits on a page: what is committed — owner, size, target; what closed since last time, honestly — delivered, delivered with named differences, or not delivered; what is at risk, each with the reason the accountable person gave and the decision or help needed; and what was committed early on a recorded exception. That is the whole template. What it deliberately omits is activity — lists of things worked on answer no question leadership has, and every line of activity crowds out the line that needed a decision. A status report is not proof of motion. It is the promises, compared with reality, on a schedule. Most status reports are written to prove the team is busy, and leadership does not have that question. The questions leadership has are four, they are always the same four, and a report shaped around them fits on a page. Here is the shape, copyable; then why each part earns its place. ## The template | Section | Per line | | --- | --- | | 1. Committed | Demand · owner · size · target | | 2. Closed since last time | Delivered / delivered with named differences / not delivered — the difference in words | | 3. At risk | What changed, in the accountable person's words · the decision or help needed | | 4. Committed early | The exception: why early · what is missing · who accepted | That is the whole report. Weekly or fortnightly, whichever cadence your commitments actually change at. Nothing else goes in. ## Why these four **Committed** answers "what are we on the hook for?" — the baseline every other line is read against. It changes rarely, which is itself information: a committed list that churns weekly is a planning problem announcing itself. **Closed honestly** is the section most reports fake with "done". Three closes, not one — and [the difference recorded whenever the result was not clean](https://www.deliverysheet.com/blog/delivered-is-not-an-outcome) — because the delta between promise and result is the only line leadership can calibrate on. A report whose every close is a clean "delivered" is not a good quarter; it is a report that has stopped carrying information. **At risk** is a judgement, not a computation — [a colour is only worth reading with the reasoning attached](https://www.deliverysheet.com/blog/rag-status-is-a-judgement). Two sentences per item: what changed, and what decision or help is needed. The second sentence is the report's entire return on investment — it converts reading into unblocking. **Committed early** is the section nobody else includes and the one that builds the most trust: the promises made before readiness, with [their recorded exceptions](https://www.deliverysheet.com/glossary/commitment-exception). Reporting your own gambles, with names attached, is what makes the rest of the report believable — and [counting them at quarter end](https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions) is where estimation debates go to be settled. ## What is deliberately missing Activity. No "worked on", no ticket counts, no velocity, no per-person anything. Activity lists answer no question leadership has, and every line of activity crowds out a line that needed a decision — the reader's attention is the report's budget, and busy-proof spends it on nothing. The deeper argument is [its own essay](https://www.deliverysheet.com/blog/reporting-delivery-to-leadership): report promises against outcomes, never motion. Also missing: narrative. If a section needs three paragraphs of context, the problem is upstream — the commitment was never specific enough to report on in a line, which is a [readiness problem](https://www.deliverysheet.com/glossary/decision-ready-demand) wearing a writing problem's clothes. The report is what makes the meeting short. With it written beforehand, [the status meeting has a thirty-minute agenda](https://www.deliverysheet.com/blog/project-status-meeting-agenda) and spends it on decisions. ## Where the report comes from The template works in any tool, including none. The failure mode is not the format — it is that assembling it honestly takes an hour of chasing, so it decays into copy-paste. In DeliverySheet the four sections are the reports hub read off the live record: the commitment ledger, the closes with their differences, the risk register with each risk's mitigation and its demand's owner, and the early-commitment list. The reason behind an at-risk status and the help needed are on each demand's check-ins. The report stops being a document someone writes and becomes a view someone opens — which is the only cadence that survives a busy quarter. I'm Tan Gravam. I build **DeliverySheet** — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date. $189/month per workspace, unlimited members. 7-day free trial — card required, cancel before it ends and you're not charged. I answer the support email myself. [**Start 7-day trial **](https://www.deliverysheet.com/login?next=/app) [**See pricing **](https://www.deliverysheet.com/pricing) Not ready for that? Play [eight rounds of Request or topic?](https://www.deliverysheet.com/spot-the-request) It takes two minutes and needs no sign-up. ## **More on after the commitment** [Read the overview: After the commitment: tracking, closing and learning →](https://www.deliverysheet.com/topics/deliver) - [How to tell stakeholders a project is late](https://www.deliverysheet.com/blog/telling-stakeholders-a-project-is-late) When to tell stakeholders a project is delayed, the four parts of the message, and five project delay emails to copy, from a new date to a stop. - [A retrospective that isn't theatre](https://www.deliverysheet.com/blog/a-retrospective-that-isnt-theatre) Most retrospectives produce agreement and no memory. The one-question format: require one written lesson, attached to the work it came from. - [Green is a judgement, not a colour](https://www.deliverysheet.com/blog/rag-status-is-a-judgement) Status reporting decays into a colour nobody believes. What makes it useful again is requiring the reason, not the rating. ```json {"@context":"https://schema.org","@graph":[{"@id":"https://www.deliverysheet.com/#website","@type":"WebSite","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date. AI-assisted shaping, planning and commitment governance for engineering leaders.","name":"DeliverySheet","url":"https://www.deliverysheet.com/","publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#webpage","dateModified":"2026-08-21","datePublished":"2026-08-21","description":"The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape.","name":"Engineering status report template","url":"https://www.deliverysheet.com/blog/engineering-status-report","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/engineering-status-report"]}],"primaryImageOfPage":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/#identity","@type":"Organization","alternateName":"Delivery Sheet","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date.","name":"DeliverySheet","url":"https://www.deliverysheet.com","founder":{"@type":"Person","@id":"https://www.deliverysheet.com/about#person","name":"Tan Gravam"},"logo":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.deliverysheet.com","position":1},{"@type":"ListItem","name":"Writing","item":"https://www.deliverysheet.com/blog","position":2},{"@type":"ListItem","name":"The status report that answers questions","item":"https://www.deliverysheet.com/blog/engineering-status-report","position":3}]},{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#article","@type":"Article","dateModified":"2026-08-21","datePublished":"2026-08-21","description":"The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape.","headline":"The status report that answers questions","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_3da885d6af78684f.png","author":{"@id":"https://www.deliverysheet.com/about#person"},"image":{"@id":"https://www.deliverysheet.com/#/schema/image/1"},"isPartOf":{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#webpage"},"keywords":["reporting","engineering management","templates"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/engineering-status-report#/schema/question/1","@type":"Question","inLanguage":"en","name":"What should an engineering status report include?","acceptedAnswer":{"@type":"Answer","text":"The status report worth sending has four sections and fits on a page: what is committed — owner, size, target; what closed since last time, honestly — delivered, delivered with named differences, or not delivered; what is at risk, each with the reason the accountable person gave and the decision or help needed; and what was committed early on a recorded exception. That is the whole template. What it deliberately omits is activity — lists of things worked on answer no question leadership has, and every line of activity crowds out the line that needed a decision. A status report is not proof of motion. It is the promises, compared with reality, on a schedule."}},{"@id":"https://www.deliverysheet.com/about#person","@type":"Person","jobTitle":"Founder","name":"Tan Gravam","url":"https://www.deliverysheet.com/about","sameAs":["https://gravam.com","https://twitter.com/TanGravam","https://github.com/TanGravam"]},{"@id":"https://www.deliverysheet.com/#logo","@type":"ImageObject","caption":"DeliverySheet","contentUrl":"https://www.deliverysheet.com/logo.png","inLanguage":"en","url":"https://www.deliverysheet.com/logo.png"},{"@id":"https://www.deliverysheet.com/#/schema/image/1","@type":"ImageObject","contentUrl":"https://www.deliverysheet.com/_og/s/o_3da885d6af78684f.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_3da885d6af78684f.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.