--- title: "Declining a request: email templates · DeliverySheet" description: "Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer." canonical_url: "https://www.deliverysheet.com/blog/declining-a-request-email-templates" last_updated: 2026-10-11 meta: author: "Tan Gravam" "og:description": "Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer." "og:image": "https://www.deliverysheet.com/_og/s/o_d577467c494ba57e.png" "og:image:alt": "Declining a request by email: seven scripts to copy — DeliverySheet essay card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "Declining a request by email: seven scripts to copy — DeliverySheet" "twitter:description": "Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer." "twitter:image": "https://www.deliverysheet.com/_og/s/o_d577467c494ba57e.png" "twitter:image:alt": "Declining a request by email: seven scripts to copy — DeliverySheet essay card" "twitter:title": "Declining a request by email: seven scripts to copy — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) # **Declining a request by email: seven scripts to copy** 25 September 2026 · 9 min read · by [Tan Gravam](https://www.deliverysheet.com/about) ## **How do you write an email declining a request?** **The short answer ** A good email declining a request has four parts and fits in a few lines: one sentence restating what was asked, as the problem rather than the proposed solution, so the requester knows it was understood; the decision in plain words — no, not now, not yet, a smaller yes, or the wrong team; one honest reason tied to capacity or priority rather than to the idea's worth; and what happens next — the condition that would change the answer, the date you will look again, or the person who now owns it. Choose the script after making the decision, not instead of it. The email to avoid is the polite non-answer — "we'll look into it" — which the requester eventually receives as a no nobody sent. This page is the wording, not the argument. Why a no should be [recorded as a decision](https://www.deliverysheet.com/blog/saying-no-is-a-recorded-decision) and what a good one contains when you [say it to a stakeholder](https://www.deliverysheet.com/blog/how-to-say-no-to-a-stakeholder) are separate essays. What follows is seven short emails you can copy, edit and send: one for each honest answer a request can get inside the company, and one for when the person asking is a customer. Each has a note on when it is the right one. For work that is already committed and running late, the matching page is [how to tell stakeholders a project is late](https://www.deliverysheet.com/blog/telling-stakeholders-a-project-is-late). Pick the script after you have made the decision, not instead of making it. An email cannot turn an undecided request into a decided one; it can only report the decision clearly. Replace everything in square brackets, and keep the result about as short as it is here: a long refusal reads as a negotiation. ## What every script has in common - **The request, restated** in one sentence, as the problem rather than the proposed solution. If you cannot write that sentence, send script 3 instead. - **The decision, in plain words.** No, not now, not yet, a smaller yes, or wrong team. Never two of them at once. - **One honest reason**, tied to capacity or priority rather than to whether the idea is any good. - **What happens next**: the condition that would change the answer, the date you will look again, or the person who now has it. ## 1. The decline **When to use it:** you have understood the request and you are not going to do it, at any priority you can foresee. > Subject: \[Request name]: decision > > Hi \[name], > > Thanks for sending this. As I understand it, you need \[the problem, in one sentence]. > > We have decided not to take this on. The reason: \[one sentence, e.g. "it is worth doing, and it lost to X and Y, which we are already committed to"]. > > What would change that: \[the condition]. If I can't see one, I'd rather say so: please don't plan around this happening. > > I've recorded the decision and the reason in \[where], so it is there if this comes up again. > > \[You] If there is genuinely no condition, the last honest line is the "please don't plan around this" one. A decline that hints at a future it does not mean is a slow maybe with better manners. ## 2. Not now: parked until a review date **When to use it:** the request is a real candidate, but something specific stands in the way: a migration, a contract, a commitment that has to finish first. > Subject: \[Request name]: parked until \[date] > > Hi \[name], > > Thanks for this. As I understand it, you need \[the problem, in one sentence]. > > We are not starting it now. It is parked, not declined: it is waiting on \[the specific thing], and starting before that would mean \[the cost]. > > I will look at it again on \[review date] and write to you either way. If \[the condition] changes before then, tell me and I'll bring it forward. > > Until then, please don't plan around it landing this quarter. > > \[You] The review date is the part that makes this a park rather than a hiding place, and "write to you either way" is the part that makes the date mean something. If you honestly cannot name a date, say so: "parked with no review date; if this becomes pressing, bring it back with what changed." That is still an answer. A "maybe next quarter" with no date is not. ## 3. Not enough to decide yet **When to use it:** the request names a subject ("SSO", "reporting", "the mobile app") rather than [something that should change](https://www.deliverysheet.com/blog/a-topic-is-not-a-request), or it says what is wanted but not who it matters to or why now. > Subject: \[Request name]: two questions before we decide > > Hi \[name], > > Thanks for raising this. Before I can give you a real answer I need two things, a sentence or two each: > > 1\. What should be different once this is done? Not the feature: what changes, and for whom. > > 2\. Who is affected if nothing changes, and why does it matter now rather than next quarter? > > Once I have those I'll come back with a decision by \[date]. > > \[You] Send it the same day the request arrives, while the requester still has the context in their head. Two questions is the limit: a third starts to read as a form. And put the follow-up date in your own calendar, because a question nobody chases is [a wait with no end](https://www.deliverysheet.com/blog/waiting-on-information-is-a-state). If you want to see which of the two a request is missing before you write, paste it into the free [request check](https://www.deliverysheet.com/request-check): it shows whether the need, the impact and the why-now are there, and drafts the questions to send back for whatever is not. ## 4. Yes, but smaller **When to use it:** part of the request fits and the rest does not, and the part that fits would still solve something real for the requester. > Subject: \[Request name]: what we can take on > > Hi \[name], > > We can do part of this. As I understand it, the core need is \[the problem, in one sentence]. > > What we can take on: \[the smaller scope], which the team has sized at \[their figure]. > > What we are not doing: \[the named exclusions], because \[one reason]. > > If the smaller version does not actually solve \[their problem], please tell me now rather than at the demo. I'd rather change the scope this week than deliver the wrong half. > > \[You] The exclusions are the working part of this email. [An out-of-scope list](https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing) is what holds in week six, when the missing half is asked for again as a small favour. And only quote a size the delivering team gave you; a figure you guessed in the reply will be quoted back as a promise. ## 5. Wrong door: redirect to the right owner **When to use it:** the request is reasonable, and another team or person owns the system or decision it touches. > Subject: \[Request name]: \[owner's name] owns this > > Hi \[name], \[owner's name], > > \[Name], this sits with \[owner's team] rather than mine: they own \[the system or decision]. I've copied \[owner's name] with what you sent me, so you don't have to explain it twice. > > \[Owner's name], the short version: \[the problem, in one sentence]. Could you confirm to \[name] that you have it? > > My team isn't taking this on, so please don't count on us for it. If it turns out to need work from us as well, I'm happy to talk about that part. > > \[You] Redirect to a person, not to a channel or a queue, and copy the requester, so that the handover is something both sides can see. "Not our team, try the platform channel" is a decline that makes the requester do the routing. ## 6. When sales has already promised a date **When to use it:** a customer has been given a date before engineering has seen the work. This one is not a refusal, because the promise already exists. It is a reply that [books the promise as what it is](https://www.deliverysheet.com/blog/the-date-sales-already-promised). > Subject: \[Customer]: \[date] commitment > > Hi \[sales lead], > > Thanks for the heads-up on \[customer] and the \[date] date. We'll treat it as a commitment: the customer has it, so there's no point pretending otherwise. > > It was made before we sized the work, so I'm recording it as an early commitment, with four things on the record: why it was made early (\[the deal]); what we don't know yet (\[the open questions]); who accepts the risk if the date turns out to be wrong, which I'd suggest is \[sales leader], by name; and what would change the date. > > The team will size it by \[date]. If it doesn't fit, I'll come back with what it displaces or what we'd cut, before the customer hears anything different. Can we agree now who tells the customer if the date moves? > > \[You] The "who accepts the risk" line meets the most resistance and does the most work. It turns an argument about blame into a [commitment exception](https://www.deliverysheet.com/glossary/commitment-exception) with a name on it, which is the only record from which a pre-promised date can later be counted. ## 7. Declining a customer's request **When to use it:** a customer has asked for a feature, a change or a date, the answer is no, and the reply leaves the company. The four parts are the same. Two things change. The reason is about what you have chosen to build, never about how busy the team is, because a customer hears "we are busy" as "ask again next month". And nothing in it may read as a promise. > Subject: Your request: \[what they asked for] > > Hi \[name], > > Thank you for asking, and for explaining what is behind it. As I understand it, you need \[the problem, in one sentence]. > > We are not going to build this. \[One sentence of reason, e.g. "It would solve a real problem for you, and it would pull the product away from what most of our customers use it for."] > > What you can do today: \[the closest thing that exists, a workaround, or another product, by name]. > > I have recorded your request and the reason for this answer. If our answer changes, you will hear it from me. Please don't plan around that. > > \[You] Three lines to keep out of it. "It's on our roadmap", unless it is a commitment with an owner and a date: the customer will repeat it to their own management as one. "Not at this time", with no date behind it: either it is a decline, so say that, or it is a park, so send script 2 and give the date you will look again. And an apology for the decision. Be sorry it is not the answer they hoped for; do not be sorry for having priorities. A date written to a customer is a [commitment](https://www.deliverysheet.com/glossary/delivery-commitment) from the moment it is sent, whoever sent it. ## "Due to prior commitments": the phrase, and what to write instead The commonest line in a decline is "due to prior commitments, we are unable to take this on." It is honest, and it tells the reader nothing they can use: which commitments, until when, and whether to ask again. Left as it is, it reads as a polite way of not answering. The phrase works once three things are added: the commitment by name, the date it ends, and what happens to this request then. > We can't start this now. The team is committed to \[X] until \[date], and taking this on would move that date. I'll look at this again on \[review date] and tell you then whether it goes into the next plan, and if the answer is still no, I'll say so plainly. If there is no date on which you would look again, the request is being declined and not parked, so use the first script and say that. A prior commitment is a reason for "not now"; it is rarely a reason for "never". Naming the commitment also invites the one useful reply this email can get: "this matters more than X." That is a decision for whoever owns both, and it is better made in the open than argued through [a side channel](https://www.deliverysheet.com/blog/the-side-channel). ## The emails not to send "We'll look into it." "Let's add it to the backlog." "Maybe next quarter." Each of these is polite in the moment and gets received months later as a no that nobody sent. That is the [slow maybe](https://www.deliverysheet.com/glossary/slow-maybe), and it costs more goodwill than any of the scripts above. If you are tempted to send one, it usually means the decision has not been made yet. Make it, then pick the script that matches. ## If you use DeliverySheet The emails stay yours to write and send; the product records the decision each one reports. At the Decide stage a shaped demand gets one of four outcomes: plan it, run a time-boxed discovery, park it, or decline it. Parking and declining both require a written reason, and a park requires either a review date or an explicit choice to park it indefinitely, so the reason line in scripts 1 and 2 already exists before you open your email. Capture holds the bar that script 3 asks for: a request does not enter the lifecycle without a stated need plus either an impact or a trigger. 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 turning a request into a decision** [Read the overview: Turning a request into something you can decide on →](https://www.deliverysheet.com/topics/intake) - [How to say no to a stakeholder](https://www.deliverysheet.com/blog/how-to-say-no-to-a-stakeholder) The slow maybe costs more relationship than a fast no. What a good refusal contains, and how to deliver one to someone senior without burning anything. - [Waiting on information is a state, not silence](https://www.deliverysheet.com/blog/waiting-on-information-is-a-state) Most requests that die never got refused. They got asked a question and then quietly stopped existing. Waiting has to be a state with an owner and a date. - [AI project requests: what to ask first](https://www.deliverysheet.com/blog/ai-project-requests) How to evaluate an AI use case before committing a team: the ordinary request bar, plus four questions about the task, the data, quality and failure. ```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/declining-a-request-email-templates#webpage","dateModified":"2026-10-11","datePublished":"2026-09-25","description":"Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer.","name":"Declining a request: email templates","url":"https://www.deliverysheet.com/blog/declining-a-request-email-templates","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/declining-a-request-email-templates#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/declining-a-request-email-templates#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/declining-a-request-email-templates"]}],"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/declining-a-request-email-templates#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":"Declining a request by email: seven scripts to copy","item":"https://www.deliverysheet.com/blog/declining-a-request-email-templates","position":3}]},{"@id":"https://www.deliverysheet.com/blog/declining-a-request-email-templates#article","@type":"Article","dateModified":"2026-10-11","datePublished":"2026-09-25","description":"Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer.","headline":"Declining a request by email: seven scripts to copy","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_d577467c494ba57e.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/declining-a-request-email-templates#webpage"},"keywords":["stakeholder management","templates","decisions"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/declining-a-request-email-templates#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/declining-a-request-email-templates#/schema/question/1","@type":"Question","inLanguage":"en","name":"How do you write an email declining a request?","acceptedAnswer":{"@type":"Answer","text":"A good email declining a request has four parts and fits in a few lines: one sentence restating what was asked, as the problem rather than the proposed solution, so the requester knows it was understood; the decision in plain words — no, not now, not yet, a smaller yes, or the wrong team; one honest reason tied to capacity or priority rather than to the idea's worth; and what happens next — the condition that would change the answer, the date you will look again, or the person who now owns it. Choose the script after making the decision, not instead of it. The email to avoid is the polite non-answer — \"we'll look into it\" — which the requester eventually receives as a no nobody sent."}},{"@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_d577467c494ba57e.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_d577467c494ba57e.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.