# How to Write a Formal Email for a Request Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-email-for-a-request/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-email-for-a-request.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 How to write a formal email for a request: the subject line, where to put the ask, how much detail to give, and what changes depending on what you are asking for. ## Key facts - Title: How to Write a Formal Email for a Request - Category: Communication - Primary skill: Communication - Related skills: Influence, Building Confidence - Primary keyword: how to write a formal email for a request - Source page: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-email-for-a-request/ ## What this page covers - How to write a formal email for a request: the subject line, where to put the ask, how much detail to give, and what changes depending on what you are asking for. - Practical guidance for how to write a formal email for a request - How this topic connects to Communication ## Detailed explanation The hard part of a request email is rarely the wording. It is that you are asking someone with more authority than you for something, and you do not want to sound like you are demanding it. The format itself is settled: put the request in the first two sentences, give the email a subject line under ten words that names what you want, greet the person formally, include only the details they need in order to act, say when you need it, and close politely. What the format does not tell you is which details count. A request for a document and a request for a recommendation letter look nearly identical on the page, and they fail for completely different reasons. ## Before you write: does this belong in an email? Almost every guide on this topic starts at the subject line. The decision before it matters more. Writing suits requests where the other person needs time to think, where a record is worth keeping, or where the message is one-way. A conversation suits anything sensitive, complicated, or negotiable, and a request can easily be all three. The practical test is what a refusal would cost you. If a no is fine and the details are simple, write. If you need them to weigh something, or you expect to negotiate the shape of the request, five minutes of conversation beats three careful drafts. Send the email afterward to confirm what you agreed. ## The parts of a formal email for a request Every formal request email carries the same six components. None of them is optional, and each one fails in a predictable way. **The subject line.** Under about ten words, naming the action rather than the topic. Career and writing sites converge on the pattern "Request for [specific thing]" — Request for Access to Shared Drive Folder, Request for Flexible Work Arrangement — and warn against "Quick question" or a bare "Request." A vague subject line shifts the work of classifying your email onto the recipient, who responds by deferring it. **The greeting.** For a first approach, or anyone senior to you, [use title and last name](/knowledge/communication/starting-a-formal-email/): Dear Professor Chen, Dear Ms. Okafor. "Hi" is fine once you correspond regularly, but formality is the safe default on a first message and it relaxes from there. **The request itself, in the first two sentences.** The most repeated rule across the top results, and the one most people get wrong. Readers triage by scanning openings, so a request buried under three paragraphs of context is functionally invisible however carefully those paragraphs are written. The instinct to build up to the ask is what stops it being read. **Only the details needed to act.** Add the facts that let the person say yes without writing back to ask you something. If you need more than one thing, put the items in a numbered list. That is a mechanism, not a preference: a paragraph containing three questions typically comes back with one answer, while a numbered list comes back with three. The British Council's C1 writing guidance builds request emails this way for the same reason. **A stated deadline.** "When you get a chance" is not a deadline; it is a request to be deprioritized. Give a date, and where it helps, say what it depends on. **A close, a sign-off, and a proofread.** Thank them for their time, then sign off with Sincerely or Best regards and your full name. The Commonwealth of Pennsylvania's email etiquette guide, used in its own staff training, lists what actually damages professional messages: an unclear subject line, no greeting before a bare instruction, [excessive length](/knowledge/communication/concise-communication/), spelling errors, and no clear call to action. All mechanical, all avoidable, and all of them outrank vocabulary. Widely repeated guidance puts the whole email under about 150 words. Past that, you are usually including context that belongs in an attachment or a meeting. ## Five kinds of request, and what each one has to carry Most advice here presents one template at a time, which makes fifteen samples look like fifteen separate problems. They are not. Request emails fall into a small number of types, and the type determines what the message must contain. The guides that organize the territory rather than sampling it, such as Hiration's breakdown of request letters, cluster around the same set. ### An information request You want facts, a document, a status, or an answer the recipient already holds. Nothing has to be decided, and the only cost to them is retrieval time, so the email lives or dies on specificity. "Could you send me the onboarding policy?" invites a link to an intranet page. "Could you send me the current parental leave policy, as a PDF if you have one?" gets you the document. ### An approval or permission request You are asking someone with authority to say yes: a purchase, a schedule change, leave, a course exception, a proposed approach. This is the only type where the person carries consequence for agreeing, which changes what the email must include. It needs the decision inputs, not just the ask — what it costs, what it affects, what happens if they decline — in a form they could forward to their own manager without rewriting it. ### A meeting or time request You are asking for a slice of somebody's calendar: an introductory conversation, a supervision slot, a debrief. That is their scarcest resource, so the email is judged on how little of it you make them spend arranging things. Propose two or three specific windows, state how long you need, and say what the conversation is for. That turns an open-ended negotiation into a yes or a no. ### An assistance or action request You want someone to do work: review a draft, cover a shift, unblock a process. You are spending their effort here, not just their attention, which makes the scope boundary essential. The failure mode is an ask that could plausibly mean twenty minutes or two days; faced with that ambiguity, people defer rather than commit. Say what you need done, roughly how big it is, and by when. ### An endorsement or introduction request You are asking someone to lend you their credibility: a reference, a recommendation letter, an introduction. Their reputation is at stake rather than their time, so this type needs two things the others do not. Attach the supporting material — your CV, the role, the deadline, a reminder of the work you did together — so saying yes is not also a research project. And give them a clean exit, an explicit line that a no is fine, which is what makes a yes worth having. ## Asking without sounding like you are demanding The tone risk here is not rudeness. Almost nobody writing to a professor or a manager is rude. The two real failures run in opposite directions. The first is [implied accusation](/knowledge/professional-behaviors/passive-aggressive-examples/), usually in a follow-up rather than the first message. Mindtools, in its list of common email mistakes, flags the standard offenders: "Per my last email" tells the recipient they failed to read something, "As previously discussed" questions whether they were paying attention, and "Going forward" implies a mistake has been made. Each is technically neutral and lands as a reprimand, which is a strange thing to send someone you need a favor from. The second is [over-apology](/knowledge/confidence/lack-of-confidence/). Three sentences about how sorry you are to bother them reads as anxiety, pushes the request down the page, and quietly asks the recipient to reassure you before they can help. One line of acknowledgment is enough: you know they are busy, here is what you need. If you recognize yourself in the second more than the first, the wording was never the real issue. The hesitation before sending is a habit, and it will show up in every ask you make for the next decade, which makes it worth knowing [where your communication habits stand](https://assessment.headwayskills.com/) rather than rewriting one email at a time. ## What to do when nobody replies Silence is the outcome most template articles never address, because they end at the sign-off. The working convention across the career-advice sites is to wait five to seven days before a polite follow-up. Less reads as pressure; much more and the thread has gone cold. Keep it short, reply inside the original thread so the context travels with it, and restate the request in one sentence rather than asking whether they saw your email. If there is still nothing after a second attempt, read it as information rather than rejection. A non-answer usually means the request landed at a bad moment or reached the wrong person, and both are fixable by asking someone else or asking again later. ## The skills that make asking easier Very little of what separates a request email that works from one that sits unanswered is vocabulary. It is knowing what the reader needs in order to act, being willing to make the ask plainly, and following up without treating silence as a verdict. Those are habits, and habits can be learned. **Communication** covers the mechanics directly: leading with the main message, writing a subject line that earns its space, choosing only the recipients who need to be there, and proofreading before you send. It also covers the judgment before all of that, which is whether the request belongs in writing or in a conversation. Clear, direct, brief, and stated positively is what turns a sent request into a completed one. **Influence** supplies the preparation the templates leave out. Understanding what is in it for the other person changes what you write — the ask stops being a favor and becomes something they can act on. It also covers the two ends most people drop: being willing to ask at all, since the worst available answer is no, and persisting afterward, which makes the follow-up momentum rather than nagging. **Building Confidence** is why a request gets padded with apology, or drafted four times and never sent. The useful move is not to feel ready first. It is to accept the discomfort of asking and send anyway, and to decide in advance when the email gets written so it does not slide another week. Each request you send makes the next one cost less. None of the three is a fixed trait, which is why it is worth knowing which one is actually costing you. A free 7-minute assessment gives you that read, and it covers the full set of twelve work skills rather than only the three here, so you can see [where your weak link is](https://assessment.headwayskills.com/) instead of guessing. ## Where this shows up later Some of this may already describe how you work. If you have ever cut a paragraph because the reader did not need it, or picked up the phone instead of writing a fourth message, you have already made the judgment these habits rest on. Asking also gets more consequential rather than less. The further you go, the more of your work depends on people agreeing to something you cannot require of them: resources, time, a decision, a name attached to yours. That is squarely within what you can change without becoming a different person. You have already done the part most people skip, which is treating a request as something with a method rather than assuming your instincts will cover it. The next step is finding out where the rest of your work skills sit. ## See where your skills actually sit The only thing left is to get a read on it. The Work Skills Test is a **free** self-assessment that shows you where you stand across all twelve work skills, including the communication and influence habits behind everything above, and which of them would make the biggest difference to you right now. It takes about 7 minutes, and you finish with a clear picture of your strengths and your gaps rather than a general impression. **Take the skills test** No sign-up needed, and you get your results straight away. ## 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? How to write a formal email for a request: the subject line, where to put the ask, how much detail to give, and what changes depending on what you are asking for. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Influence, Building Confidence. ### 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/confidence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-email-for-a-request/ Preferred summary: "How to write a formal email for a request: the subject line, where to put the ask, how much detail to give, and what changes depending on what you are asking for." ## Change log - 2026-07-07: Content collection version published.