--- title: "Quarter end: count the exceptions · DeliverySheet" description: "Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line." canonical_url: "https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions" last_updated: 2026-08-07 meta: author: "Tan Gravam" "og:description": "Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line." "og:image": "https://www.deliverysheet.com/_og/s/o_711c6915c8cb532c.png" "og:image:alt": "Close the quarter by counting the exceptions — DeliverySheet essay card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "Close the quarter by counting the exceptions — DeliverySheet" "twitter:description": "Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line." "twitter:image": "https://www.deliverysheet.com/_og/s/o_711c6915c8cb532c.png" "twitter:image:alt": "Close the quarter by counting the exceptions — DeliverySheet essay card" "twitter:title": "Close the quarter by counting the exceptions — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) # **Close the quarter by counting the exceptions** 7 August 2026 · 5 min read · by [Tan Gravam](https://www.deliverysheet.com/about) ## **What should you review at the end of a quarter?** **The short answer ** A quarter closes on three counts, not a demo and a mood. Count the honest closes: commitments that reached a recorded outcome — delivered, delivered with a named difference, or not delivered — each with a verdict and a lesson. Count the slips: of the non-clean closes, what actually differed, because differences cluster and the cluster names the stage that is lying to you. And count the early-commitment exceptions: how many promises crossed the line unready, on the record. Each count changes next quarter differently — the first sets how much to commit, the second says what to fix before committing, and the third tells you whether your misses come from estimation or from the door. Most quarters end with a demo and a feeling. The demo shows what shipped; the feeling — pretty good, rough one, we'll catch up — becomes the organisation's memory of the quarter. Neither is data. A quarter actually closes on three counts, and each one changes something specific about the next quarter's plan. ## Count one: honest closes Of the commitments made, how many reached a recorded outcome — delivered clean, delivered with a named difference, or not delivered — each closed with a verdict and a written lesson. A commitment that just stopped is not closed; it is abandoned, and it counts against this number, not toward it. This is the count a completed-and-learned view exists to answer at a glance, and it is the numerator of your organisation's trust: the ratio of promises to honest closes is the only delivery metric leadership can verify for itself. What it changes: the size of next quarter's line. A group that closed eight of thirteen honestly does not need better estimates; it needs to commit less until the ratio recovers. Committing eleven and closing eleven builds more credibility in two quarters than any dashboard ever has. ## Count two: slips, with the differences named Of the non-clean closes, what actually differed from the promise — not the fact of slipping, which count one already holds, but the substance: what shipped instead, what was cut, what moved and why. This count only exists if closes record the difference, which is why a close should never be a checkbox. The value is in the clustering, because differences are rarely random. Three slips that all trace to an unconfirmed dependency point at the planning stage. Differences that trace to capacity optimism point at the estimates and their confidence levels. Scope that grew mid-quarter points at the door. The cluster names the stage that is lying to you — which is the one thing a "we missed some dates" retrospective can never do. ## Count three: early-commitment exceptions How many of the quarter's commitments crossed the readiness bar on a recorded exception — committed early, with why-now, what's-missing, who-accepts and the changing condition written down at the time. This count is the reason the exception exists at all: an early-commitments report is only possible because every early commitment paid its four fields on the way in. It is also the most diagnostic of the three. Line count three up against the misses. If most of your misses were early commitments, your estimation is fine and your door is broken — dates are being promised before evidence, and the fix is upstream of every retro action item you were about to write. And if the exception count itself rises quarter on quarter, escalation has become cheaper than the front door, and the price needs rebalancing. ## A worked example Nadia runs delivery for a sixty-engineer product group. Her Q3 close: thirteen commitments. Eight closed clean. Three closed with named differences — one scope exclusion dropped late, one three-week slip, one delivered without its migration. Two not delivered. All thirteen carry a verdict and a lesson, so count one reads: thirteen of thirteen closed honestly, eight clean. The differences cluster hard: both non-deliveries and the slip trace to one platform team whose "confirmed" dates were never actually confirmed. Count three: four commitments were early exceptions — and three of the five non-clean closes were among those four. The counts write next quarter's changes almost by themselves. The line drops from thirteen to eleven. Nothing that depends on the platform team gets committed without a date that team recorded itself. And the escalation path that produced three of the four early commitments now runs through the planning room, out loud, at the same four-field price. None of this came from the demo, and none of it would have survived as "the feeling". These counts are the honest form of the number leadership usually asks for: [the say/do ratio, counted from the record](https://www.deliverysheet.com/blog/say-do-ratio-delivery-predictability). ## The counts are the report Conveniently, the three counts are also the leadership report — they are exactly the shape of [promises against outcomes](https://www.deliverysheet.com/blog/reporting-delivery-to-leadership), compressed to one screen. A leadership team that hears the same three counts every quarter learns to trust the line behind them, and a leadership team that trusts the line stops asking for the activity lists. What happens between the commitment and the close — status that carries reasons, outcomes that are comparisons — is the subject of [the delivery overview](https://www.deliverysheet.com/topics/deliver). 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) - [The say/do ratio: measuring delivery predictability without scoring people](https://www.deliverysheet.com/blog/say-do-ratio-delivery-predictability) The say/do ratio is commitments kept over commitments made. Three ways the number lies, how to count it from a record, and why it never sits next to a name. - [Your first 90 days: aim for one honest close](https://www.deliverysheet.com/blog/first-90-days-one-honest-close) New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised. - [When to stop a project you already committed to](https://www.deliverysheet.com/blog/when-to-stop-a-committed-project) Sunk cost, the three signals that justify cancelling, kill criteria set at commitment time, and how to close a stopped project honestly. ```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/quarter-end-count-the-exceptions#webpage","dateModified":"2026-08-07","datePublished":"2026-08-07","description":"Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line.","name":"Quarter end: count the exceptions","url":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions"]}],"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/quarter-end-count-the-exceptions#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":"Close the quarter by counting the exceptions","item":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions","position":3}]},{"@id":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions#article","@type":"Article","dateModified":"2026-08-07","datePublished":"2026-08-07","description":"Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line.","headline":"Close the quarter by counting the exceptions","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_711c6915c8cb532c.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/quarter-end-count-the-exceptions#webpage"},"keywords":["delivery","reporting","governance"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions#/schema/question/1","@type":"Question","inLanguage":"en","name":"What should you review at the end of a quarter?","acceptedAnswer":{"@type":"Answer","text":"A quarter closes on three counts, not a demo and a mood. Count the honest closes: commitments that reached a recorded outcome — delivered, delivered with a named difference, or not delivered — each with a verdict and a lesson. Count the slips: of the non-clean closes, what actually differed, because differences cluster and the cluster names the stage that is lying to you. And count the early-commitment exceptions: how many promises crossed the line unready, on the record. Each count changes next quarter differently — the first sets how much to commit, the second says what to fix before committing, and the third tells you whether your misses come from estimation or from the door."}},{"@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_711c6915c8cb532c.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_711c6915c8cb532c.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.