# How to Write an Email Requesting Something: 7 Examples Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-email-for-requesting-something-example/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-email-for-requesting-something-example.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 an email requesting something, with 7 real examples - approval, information, time off, a meeting, feedback - plus wording that gets replies. ## Key facts - Title: How to Write an Email Requesting Something: 7 Examples - Category: Communication - Primary skill: Communication - Related skills: Influence, Time Management - Primary keyword: how to write email for requesting something example - Source page: https://headwayskills.com/knowledge/communication/how-to-write-email-for-requesting-something-example/ ## What this page covers - How to write an email requesting something, with 7 real examples - approval, information, time off, a meeting, feedback - plus wording that gets replies. - Practical guidance for how to write email for requesting something example - How this topic connects to Communication ## Detailed explanation Here is how to write an email requesting something: name the request in the subject line, greet the person, and say exactly what you want in the first sentence. Add one or two lines of context, give a specific deadline, and leave [an easy way to say no](/knowledge/time-management/how-to-say-no-without-hurting-someone-feelings/). Then stop. Most people do the opposite — three lines of throat-clearing before the ask — which is why so many request emails sit unanswered. The wording that actually works is duller than you would expect, and it changes surprisingly little from one situation to the next. ## What every email requesting something needs Whatever you are asking for, a request email has the same six moving parts. **A subject line that names the request.** The common failure is a vague one: "Quick question," or simply "Request." Request-email guides such as Fyxer's single these out because they give the reader no reason to open now rather than later. "Approval needed: Q3 training budget" carries the topic, the action, and the urgency before the message is even open. **The ask in the first sentence.** Not the third paragraph. "I'd like to request approval for…" or "Could you send me…" Indeed's guide to writing an email requesting something puts this first for a reason: the reader decides whether to keep going in about a line and a half. **One or two lines of context.** Why you need it, or what prompted it. Resist the urge to justify at length. A long justification reads as an apology, and an apology invites a no. **A specific deadline.** Even a soft one. "By Thursday" and "sometime next week" both work. "As soon as possible" does not, because it means something different to every reader. **A graceful exit.** A line like "if that's not workable, no problem — just let me know" protects the relationship if the answer is no. It also tends to raise the reply rate, because it removes the cost of declining. **Brevity.** Email guides converge on roughly 50 to 125 words as the range where replies peak. Past that, your message starts to feel like work. Those six take up less room than most people expect. What no template can tell you is [how direct you are allowed to be](/knowledge/communication/assertive-communication-skills/) with this particular person — a peer, a manager you've met twice, someone senior you've never met. That judgment is a read on your own communication habits rather than on the format, and it's worth [checking where yours stand](https://assessment.headwayskills.com/) rather than building a habit on a guess. ## 7 examples of emails requesting something Each example below uses the same six parts. Read them for the pattern, not the wording — the phrasing you copy from a stranger rarely sounds like you. ### 1. Requesting information from a colleague **Subject:** Need the Q2 supplier figures by Friday > Hi Marek, > > Could you send me the Q2 supplier spend figures? I'm putting the cost review together for Anna and yours is the last piece. > > Friday would be ideal, but Monday morning still works if this week is full. > > Thanks, > Sofia Notice how little explanation it carries. The ask is one sentence, the reason is one sentence, and the deadline has give in it. Naming who the work is for ("for Anna") also tells Marek where the request sits among his other tasks. ### 2. Requesting approval from your manager **Subject:** Approval needed: €400 for the SQL course > Hi Daniel, > > I'd like to ask for approval to take the intermediate SQL course in March. It costs €400 and runs two evenings a week, so it wouldn't overlap with the reporting cycle. > > It would let me build the monthly dashboards myself instead of queueing them with the data team. > > Happy to send the syllabus if useful. Could you let me know by the 20th, when enrolment closes? > > Thanks, > Priya Approval requests are the one case where "[what's in it for them](/knowledge/influence/how-to-be-more-persuasive/)" belongs explicitly in the email. The line about the data team is not padding — it converts a personal wish into a reduced bottleneck for the manager. ### 3. Requesting a meeting **Subject:** 30 minutes on the onboarding handover? > Hi Lena, > > Could we take 30 minutes to walk through the onboarding handover before you go on leave? > > I'm free Tuesday 10–12 or Thursday afternoon. If neither suits, send me two slots that do. > > Best, > Tom Meeting requests fail most often on the closing line. Offering specific slots rather than asking "when works for you?" removes a whole round of email — a point the meeting-template collections at close.com and Fyxer both make. Naming the duration matters too: "30 minutes" is a smaller decision than "a meeting." ### 4. Requesting a deadline extension **Subject:** Requesting two extra days on the compliance draft > Hi Ahmed, > > I'd like to ask for two extra days on the compliance draft — Thursday instead of Tuesday. > > The legal review came back with more comments than expected, and I'd rather submit something you can sign off than something you have to send back. > > Sections 1–3 are finished if you'd like to see them Tuesday as planned. > > Thanks, > Julia Ask early, name the new date, and offer partial delivery. What sinks an extension request is vagueness — "a bit more time" leaves your reader to invent a date and then feel let down by it. ### 5. Requesting time off **Subject:** Holiday request: 12–16 May > Hi Claire, > > I'd like to request holiday from 12 to 16 May. > > The sprint closes on the 9th and nothing is scheduled that week, so the timing should be clean. Rasmus has agreed to cover the Wednesday standup. > > Let me know if that works and I'll put it in the system. > > Thanks, > Ben Time-off requests are procedural, so the whole job is showing you've thought about the gap you leave. Naming the person covering for you does most of that work in a single clause. ### 6. Requesting feedback on your work **Subject:** Quick feedback on Thursday's client deck? > Hi Marta, > > Would you have 10 minutes to give me feedback on the client deck I presented Thursday? > > I'm mainly interested in whether the pricing section landed — I rushed it and couldn't read the room. > > No rush at all if this week is busy. > > Thanks, > Oscar The narrow question is what makes this work. "Any feedback?" is a request for unpaid labor; "did the pricing section land?" is a question someone can answer in two lines while waiting for a lift. ### 7. Requesting a reference or recommendation **Subject:** Would you be willing to be a reference? > Dear Ms. Okafor, > > I'm applying for an analyst role at Nordvest and would like to ask whether you'd be willing to act as a reference. > > We worked together on the customer-retention project in 2024, and I've attached the job description in case it's helpful for context. > > They would likely contact you in the next two weeks. If you'd rather not, I completely understand — just say the word. > > Best regards, > Amina This is the request that most needs a genuine exit line. A reference given reluctantly is worse than no reference, so making the no easy is in your interest as much as theirs. Attaching the job description also spares them the work of remembering what you did. ## What to do when nobody replies Send one follow-up, not three. Reply in the same thread after three to five working days, keep it to two lines, and repeat the ask rather than asking whether they saw the first email — "Following up on the Q2 figures; still hoping for these by Monday" gives them somewhere to land without making them scroll. If the second message goes unanswered too, [the medium](/knowledge/communication/most-effective-ways-of-communication/) is probably wrong. Email is the right choice for requests that are simple, documentable, or need the other person's time to consider. Anything sensitive, negotiable, or complicated will move faster in a two-minute conversation, and the email you send afterwards can just confirm what you agreed. ## The skills behind a request that gets answered Read the seven examples again and you'll notice the format is doing very little of the work. What separates the ones that get answered is a set of judgments made before any wording was chosen: how much to explain, how much to ask for, and how much of someone else's time you are quietly spending. **Communication** is the visible layer — leading with the main message, keeping the subject line concrete, sending only to the people who need it, and proofreading before you press send. The harder half is the choice underneath: some requests should never be emails at all. Anything you expect resistance to, or that needs back-and-forth to land, belongs in a conversation, with the email as the record afterwards. **Influence** is what turns a clear request into a persuasive one. Most of it is preparation — working out what's in it for the other person before you write, so the ask connects to something they already care about, as the SQL-course email does. The rest is being willing to ask at all, presenting the drawbacks honestly, and following up once without apology when the answer matters. **Time Management** explains why some requests get answered first. When a task arrives, the receiver has to establish four things before they can start: who's asking, what exactly is wanted, when it's due, and what "done" looks like. A request email that answers all four in advance is simply cheaper to act on than one that requires a clarifying reply. None of these are email tricks — they're habits that show up wherever you work with other people, and they're learnable in the ordinary way, by finding the weakest one and practicing it. The free Job Skills Test covers twelve such work skills and will show you [where your communication sits](https://assessment.headwayskills.com/) among them. ## You may already do more of this than you think If you read the seven examples looking for the one closest to your own situation rather than one to copy wholesale, that instinct is the useful half of this skill already. Adapting a pattern to a specific person is the part templates can't do for you. The rest is buildable from where you are now — you don't have to become a different kind of communicator, or a naturally assertive one, to write a request people answer. You just need to know which of the underlying habits is currently costing you replies. And the asks get bigger as you go: a budget, a promotion, a role change, a person's professional reputation attached to your name. The wording stays much the same. The judgment behind it is what has to grow. So it's worth knowing where that judgment currently sits. The Job Skills Test is a **free** self-assessment of your work skills — twelve of them, including communication — that takes about seven minutes. You answer a set of questions about how you actually work, and it shows you where you stand on each skill and which ones would repay attention first. No preparation, and nothing to read beforehand. **Take the skills test** Free, seven minutes, results on screen right 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 an email requesting something, with 7 real examples - approval, information, time off, a meeting, feedback - plus wording that gets replies. ### 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/how-to-write-email-for-requesting-something-example/ Preferred summary: "How to write an email requesting something, with 7 real examples - approval, information, time off, a meeting, feedback - plus wording that gets replies." ## Change log - 2026-07-07: Content collection version published.