# How to Write a Formal Email Requesting Something Canonical URL: https://headwayskills.com/knowledge/communication/formal-how-to-write-email-for-requesting-something/ Markdown URL: https://headwayskills.com/knowledge/communication/formal-how-to-write-email-for-requesting-something.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Asking someone at work for something by email? Nine rules for writing a formal request that is clear, easy to say yes to, and hard to leave unanswered. ## Key facts - Title: How to Write a Formal Email Requesting Something - Category: Communication - Primary skill: Communication - Related skills: Influence, Time Management - Primary keyword: formal how to write email for requesting something - Source page: https://headwayskills.com/knowledge/communication/formal-how-to-write-email-for-requesting-something/ ## What this page covers - Asking someone at work for something by email? Nine rules for writing a formal request that is clear, easy to say yes to, and hard to leave unanswered. - Practical guidance for formal how to write email for requesting something - How this topic connects to Communication ## Detailed explanation The draft has been open for twenty minutes. What you need is not unreasonable, the person can almost certainly provide it, and every version still comes out sounding either [demanding or apologetic](/knowledge/communication/assertive-communication-skills/). To write a formal email requesting something, put the request in the subject line, state it within the first two sentences, ask for one thing only, name a real date, say briefly why you are asking this person, and include everything they need in order to act. That is the format, and the format is the settled part. What decides whether you get a yes is something the templates do not cover. ## Nine rules for a formal email requesting something Guides on this topic disagree about almost nothing structural. Indeed, LeaveBoard, RequestLetters and Instantly all describe the same sequence — subject line, greeting, a line stating the purpose, the supporting detail, the request itself, a closing with thanks — and that agreement is worth trusting. The rules below assume the skeleton and work on the harder question underneath it: what the person reading has to have in front of them before they are able to say yes. Most request emails that fail are polite, correctly formatted and unanswered. ### 1. Put the ask in the subject line The subject line is not a topic label. It is the thing that decides whether the message is opened now, opened later, or never opened at all, and the guidance across sources is to keep it under about ten words and name the action rather than the subject area. "Request for Copies of Employment Documents" and "Approval Needed for Updated Budget" both tell the reader what they are being asked to do before they open anything. According to the Booher Research Institute, some people skim only subject lines when deciding what to work on, which means an action left out of the subject may never be seen. "Quick question" hides the request instead of introducing it. ### 2. Make the request in the first two sentences The instinct is to warm up: explain the background, acknowledge how busy they are, apologize a little, and arrive at the ask somewhere in the third paragraph. Tomba's analysis of request emails describes exactly what happens next — the recipient scans, finds no clear action, and files the message under "later," which is the same folder as "never." Say what you want first and put the context after it. This feels rude to write and does not read that way, because the reader is scanning a queue rather than listening to you. Every guide in the top results gives the same instruction: state the purpose in the opening sentence, without build-up. ### 3. Ask for one thing Two requests in one email means the reader has to make two decisions, and as Tomba puts it, most people faced with two decisions make zero. If you need a document and an introduction, that is two messages. If the second thing is genuinely minor, subordinate it clearly so there is no ambiguity about which one you are actually waiting on. A message with two asks reliably gets one answer, and rarely the one that mattered more. ### 4. Name a date, not "ASAP" An unstated deadline does not read as flexibility. It reads as no urgency, and the thread loses to every piece of work that has a real clock attached to it. A vague deadline sits alongside the buried ask in Tomba's list of the things that silently kill request emails. Give a specific date and, where it helps, the reason behind it — the meeting it feeds into, the thing that unblocks. This is the part that feels most like pressure and is in fact the opposite: a date lets the reader schedule you instead of carrying you around as an open loop. Do not invent urgency you do not have. A deadline you made up to force a reply is the one thing here that genuinely is pushy, and people notice. ### 5. Say why you are asking this person A request that could have been sent to anyone reads like it was. Name what makes them the right recipient — they own the system, they have the file, they were in the meeting. Where the request goes to a manager, the advice collected by status.net and Fyxer is consistent: connect the ask to something beyond your own convenience, whether that is a team goal, a deadline other people depend on, or a result the request makes possible. This is the point at which a request email stops being a writing task, which is why no amount of rephrasing fixes an ask that has no answer to "[why does this matter to me](/knowledge/influence/influence-without-authority/)?" ### 6. Hand over everything needed to say yes Fyxer's guidance is blunt about it: if the request is not specific, it is hard for anyone to agree to it. Attach the file rather than offering to send it. Include the link, the form, the reference number. Say what "done" looks like, and say honestly how much work you think you are asking for. Every detail you leave out becomes a clarifying question, and a clarifying question turns a two-minute yes into a thread that both of you eventually abandon. ### 7. Match the formality to the relationship Formality is set by who the recipient is, not by how nervous you feel about asking. The standard division across sources is straightforward: "Dear Ms. Lopez" for executives, external contacts, HR, legal, and anything involving budget; "Hi Sam" for a colleague you speak to daily. Formal does not mean archaic, and a request written in the language of a nineteenth-century solicitor reads as distance rather than respect. When you cannot tell which level applies, open one notch more formal than feels natural and take your cue from how they reply. ### 8. Leave a graceful way to decline The most consistently recommended politeness device is grammatical: ask as a question. "Could you…", "Would it be possible to…", "I would appreciate it if you could…" — TextRanch and Linguaholic both note that a question positions you as seeking help rather than issuing an instruction, and that giving the reason for the request improves cooperation. Where a full yes is unlikely, name a smaller version you would also accept. [Making refusal cheap](/knowledge/time-management/how-to-say-no-at-work/) is what makes agreement cheap, and a "no" you receive quickly is worth more than the silence you get from a request that left no room for one. ### 9. Decide the follow-up before you need it Silence is almost never refusal. It is inbox volume, and the norms for handling it are well defined. Serif's follow-up guidance puts one concise chase at around three days for time-sensitive requests and three to seven business days for ordinary ones, with [two follow-ups](/knowledge/influence/follow-up-after-a-meeting/) as the professional norm and a third reserved for high-stakes situations — beyond that, messages get ignored rather than acted on. Knowing the ceiling in advance takes the decision out of the moment, which is where it usually goes wrong in one direction or the other. Read the nine back and notice how few of them are about words. Three concern the writing; the other six are decisions made before the message is opened — what exactly you want, when, why this person, what happens if nothing comes back. This is also not a one-off situation. You will send hundreds of these, for larger things each time, so it is worth [checking the habit behind them](https://assessment.headwayskills.com/) rather than solving it one draft at a time. ## What makes some people easy to say yes to None of the nine rules asked for better vocabulary. They asked you to decide what you want, judge what the other person needs in order to act, and be willing to make the ask at all. Those are different abilities from writing, and they turn up in a great many places besides an inbox. **Communication** covers the mechanics without ceremony: lead with the main message, keep the subject line concise, send it only to the people who need it, be brief, be direct, proofread, and reply in reasonable time. It also covers the decision that comes before the draft, which the template posts skip entirely — whether this belongs in an email at all. Writing is right when the other person needs time to think, when there should be a record, or when information moves one way. A conversation is right when the matter is sensitive, complicated, or a negotiation. Some of the requests that take twenty minutes to word are requests that should have been a two-minute conversation and a one-line email confirming it. **Influence** — getting it and applying it — is the part the guides leave out. The recipient owes you nothing, so the wording is not what produces the yes. What produces it is working out in advance what the request is worth to them, keeping the ask simple, being straight about the drawbacks instead of overselling, taking a partial yes when a full one is unlikely, and following up until the thing is actually done. It also starts before the email: a reputation for delivering what you said you would is what makes later asks cheap to make. This is not persuasion technique or manufactured urgency — the distinction between influence and manipulation is exactly the distinction between rules four and eight above and the pressure tactics they warn against. **Time Management** describes the other side of the same transaction, and you already know it from experience. Before anyone can take on a task, they need four things: who is asking, what precisely is wanted, when it is due as a real date rather than "as soon as possible," and what counts as finished. You have been on the receiving end of requests missing two of the four, and you know what you did with them. Writing your own request from that seat is the shortest route to one that gets acted on. Not one of the three is a temperament, and each can be worked on deliberately. If you cannot tell which of them is actually costing you — and most people cannot, from the inside — the free Job Skills Test scores you across these and the nine others in the same framework, and will name [which gap to close first](https://assessment.headwayskills.com/) instead of leaving you to guess. Some of the nine rules are probably already how you write, and the ones you have right tend to be the ones a bad experience taught you. The rest are conventions rather than character, learned the ordinary way, and learning them asks nothing about who you are. You are also reading this instead of sending version four, which is what most people skip when a message is making them uncomfortable. The requests will not stay this small, either. What you need from other people grows with your responsibilities — budget, someone's time, a decision that is not yours to make — and the habits you build on a request for a document are the ones you will be using for those. What is missing at this point is a read on where you are starting from. ## Before the next thing you have to ask for The Job Skills Test is a **free** self-assessment of the skills you use at work. You answer questions about how you actually operate day to day, and it scores you across all twelve — communication, influence and time management among them — then shows which ones would repay attention first. It takes about seven minutes, you do it on your own, and nothing about it is urgent. Take it before the next request you have to make, and you will know whether to spend your effort on the writing or on the asking. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, about seven minutes, and you can do it in one sitting.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Asking someone at work for something by email? Nine rules for writing a formal request that is clear, easy to say yes to, and hard to leave unanswered. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Influence, Time Management. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/knowledge/time-management.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/formal-how-to-write-email-for-requesting-something/ Preferred summary: "Asking someone at work for something by email? Nine rules for writing a formal request that is clear, easy to say yes to, and hard to leave unanswered." ## Change log - 2026-07-07: Content collection version published.