--- title: "When sales promises a date · DeliverySheet" description: "The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision." canonical_url: "https://www.deliverysheet.com/blog/the-date-sales-already-promised" last_updated: 2026-08-21 meta: author: "Tan Gravam" "og:description": "The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision." "og:image": "https://www.deliverysheet.com/_og/s/o_409d73bf90142fb8.png" "og:image:alt": "The date sales already promised — DeliverySheet essay card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "The date sales already promised — DeliverySheet" "twitter:description": "The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision." "twitter:image": "https://www.deliverysheet.com/_og/s/o_409d73bf90142fb8.png" "twitter:image:alt": "The date sales already promised — DeliverySheet essay card" "twitter:title": "The date sales already promised — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) # **The date sales already promised** 21 August 2026 · 5 min read · by [Tan Gravam](https://www.deliverysheet.com/about) ## **What should engineering do when sales has already promised a date?** **The short answer ** When sales has already promised a customer a date, the commitment exists whether engineering accepts it or not — refusing to acknowledge it just moves the promise off every record while keeping it in the contract. The honest move is to book it as what it is: an early commitment made before readiness, with the exception recorded — why it was made, what is still unknown, who accepted the risk (which is sales leadership, by name, not "the business"), and what would change it. Do that consistently and two things happen: this quarter's plan absorbs the truth instead of hiding it, and by the third quarter you can show exactly what pre-promised dates cost — which is the only argument that has ever changed a sales process. The email arrives on a Tuesday. A deal closed, congratulations all round, and in paragraph three: the customer has been told the integration ships by end of March. Engineering is learning about the commitment and its date in the same sentence. What happens in the next hour determines whether this becomes a delivery problem or stays what it currently is — a recording problem. ## The commitment already exists Start from the fact everyone in the room wants to argue with: the promise is made. It is in a contract, or in a customer's planning, or in the relationship — and engineering's acceptance was never a precondition for its existence. Refusing to "accept" it does not un-promise it; it just moves the promise off every internal record while keeping it fully alive in the external one. Now the organisation carries a real commitment that no plan accounts for, no capacity was reserved for, and no one is accountable for — the maximum-risk configuration, achieved in the name of process purity. The angry meeting has the same defect. It renegotiates blame, not the date, and it teaches sales one lesson only: involve engineering even later next time. ## Book it as what it is A pre-promised date is an early commitment — a promise made before readiness — and the honest handling already exists: [record the exception](https://www.deliverysheet.com/blog/early-commitment-exception). Four fields, filled in the open: - **Why it was made early:** the deal, named. This is a legitimate reason — real revenue on a real signature outranks process comfort, and pretending otherwise is its own theatre. - **What is still unknown:** whatever shaping has not happened — scope, dependencies, the capacity figure the delivering team never gave. - **Who accepts the risk:** sales leadership, by name. Not "the business", not the account executive's manager's manager — a person who can later be asked whether they would accept it again. This field does the most work and meets the most resistance, in that order. - **What would change the decision:** the condition — "if discovery finds the vendor API cannot batch, the date moves and the customer hears it by the 15th." Then run the demand through the same machinery as everything else — shaped, sized by the team, dependencies confirmed — knowing the date arrived before the evidence. The exception does not bless the gamble. It makes the gamble *countable*. The reply to the sales lead that puts those four fields on the record is [written out as an email you can copy](https://www.deliverysheet.com/blog/declining-a-request-email-templates). ## Displacement, out loud Capacity did not grow when the deal closed. [The pre-promised demand is an edit to the quarter, not an addition](https://www.deliverysheet.com/blog/the-mid-quarter-ask) — something above the line moves down, visibly, and its stakeholder is told by name. Skip this step and the displacement still happens; it just happens silently, to a victim discovered at quarter end, which converts one honest hard conversation now into two dishonest ones later. If the date has not reached the customer yet, there is still room for [three offers instead of one no](https://www.deliverysheet.com/blog/pushing-back-on-an-unrealistic-deadline). ## The only argument that changes a sales process Here is what recording buys, three quarters in: a list. Every pre-promised date, its exception, its owner, and [its close](https://www.deliverysheet.com/glossary/honest-close) — kept, kept with differences, missed. When [the exceptions are counted](https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions), the conversation with sales leadership stops being "please involve us earlier", which is a plea, and becomes "pre-promised dates missed at three times the rate and cost us these two renewals", which is a business case. Nobody has ever changed a sales process with a plea. The record is not revenge — it is the only shared set of facts from which the process can improve. And notice the quiet symmetry: the same record protects sales. When engineering's own estimate slips on a demand that *was* ready, the ledger says so too. A commitment system nobody can game in either direction is the thing that finally makes the Tuesday email arrive as a question instead of a verdict. 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 deciding what to commit to** [Read the overview: How to decide what to commit to →](https://www.deliverysheet.com/topics/commit) - [You will commit before you are ready. Make it cost four fields.](https://www.deliverysheet.com/blog/early-commitment-exception) Banning early commitments does not stop them, it hides them. Recording them takes a minute and converts an invisible gamble into a named decision. - [The mid-quarter ask is an edit, not an addition](https://www.deliverysheet.com/blog/the-mid-quarter-ask) Capacity did not grow when the urgent ask arrived. A mid-quarter request is an edit to a named commitment — the honest record names what it displaces. - [OKRs point. Commitments deliver.](https://www.deliverysheet.com/blog/okrs-and-commitments) An OKR names a direction; it doesn't promise anyone anything specific. Why teams that run on OKRs alone still miss dates — and what fills the gap. ```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/the-date-sales-already-promised#webpage","dateModified":"2026-08-21","datePublished":"2026-08-21","description":"The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision.","name":"When sales promises a date","url":"https://www.deliverysheet.com/blog/the-date-sales-already-promised","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/the-date-sales-already-promised#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/the-date-sales-already-promised#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/the-date-sales-already-promised"]}],"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/the-date-sales-already-promised#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 date sales already promised","item":"https://www.deliverysheet.com/blog/the-date-sales-already-promised","position":3}]},{"@id":"https://www.deliverysheet.com/blog/the-date-sales-already-promised#article","@type":"Article","dateModified":"2026-08-21","datePublished":"2026-08-21","description":"The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision.","headline":"The date sales already promised","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_409d73bf90142fb8.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/the-date-sales-already-promised#webpage"},"keywords":["commitment","stakeholder management","sales"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/the-date-sales-already-promised#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/the-date-sales-already-promised#/schema/question/1","@type":"Question","inLanguage":"en","name":"What should engineering do when sales has already promised a date?","acceptedAnswer":{"@type":"Answer","text":"When sales has already promised a customer a date, the commitment exists whether engineering accepts it or not — refusing to acknowledge it just moves the promise off every record while keeping it in the contract. The honest move is to book it as what it is: an early commitment made before readiness, with the exception recorded — why it was made, what is still unknown, who accepted the risk (which is sales leadership, by name, not \"the business\"), and what would change it. Do that consistently and two things happen: this quarter's plan absorbs the truth instead of hiding it, and by the third quarter you can show exactly what pre-promised dates cost — which is the only argument that has ever changed a sales process."}},{"@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_409d73bf90142fb8.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_409d73bf90142fb8.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.