# How to Write an Email to Senior Management: Sample and Steps Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-email-to-senior-management-sample/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-email-to-senior-management-sample.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 An email to senior management needs the ask in the first two sentences and under 125 words. A worked sample, plus the seven steps behind it. ## Key facts - Title: How to Write an Email to Senior Management: Sample and Steps - Category: Working with Your Manager - Primary skill: Communication - Related skills: Working with Your Manager, Influence - Primary keyword: how to write email to senior management sample - Source page: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-email-to-senior-management-sample/ ## What this page covers - An email to senior management needs the ask in the first two sentences and under 125 words. A worked sample, plus the seven steps behind it. - Practical guidance for how to write email to senior management sample - How this topic connects to Communication ## Detailed explanation Writing to someone two or three levels above you is a different job from writing to your own team, and most people feel it the moment they open a blank message. The short version: an email to senior management states the decision you need in the first two sentences, keeps the body to roughly 125 words, gives only the context that decision requires, and closes with one clear next step. A sample helps, but it is a shape rather than a script — subject line, ask, context, next step. What makes it land is a decision you make before you write a word. ## How to write an email to senior management, step by step The order below matters more than the wording. Two of the seven steps happen before you start typing, and they are the ones the template collections tend to skip. ### 1. Check the reporting line before you write Ask who owns this topic. If it sits inside your own manager's remit, they should either know the message is going or send it themselves. That is not deference — it is the practical rule that keeps a helpful email from reading as a bypass. Three situations make it straightforward: the senior person asked you directly, the email is routine visibility going to a group, or your manager has already agreed you should be the one to write. If you are going upward *because* of your manager, that is a different email with different stakes, and it deserves a conversation first. This step comes first because it changes the mechanics of everything after it — who is on the To line, who is copied, and how much backstory the reader needs. ### 2. Decide whether this should be an email at all Executive advice is unusually consistent here. As the Jack Henry FinTalk guidance puts it, if the message needs more than three or four short paragraphs, you should probably be setting up a conversation instead. The reason is not politeness. Email is good for one-way information, for documentation, and for giving someone time to think. It is poor at anything requiring negotiation, nuance, or a shared reconstruction of a messy situation — and a long email asking a senior reader to do that reconstruction usually produces silence rather than a decision. A workable test: if you cannot state the ask and the context in the space of a phone screen, [book fifteen minutes](/knowledge/working-with-your-manager/how-to-request-a-meeting-with-your-boss-sample-emails/) and send a two-line email requesting it. ### 3. Name the single thing you want to happen Write it out in one sentence before you open the email. Most messages upward are one of four things: a decision, an approval, a request to unblock something, or pure visibility with no action attached. If you cannot name which one yours is, the email is not ready — and stacking two asks into one message reliably gets you an answer to neither. Keep one email to one subject. This is the point at which most drafts go wrong, because the writer knows the whole situation and quietly assumes the reader wants it too. ### 4. Write a subject line that states the action Executive-email guides converge on the same formula: action type, then topic, then timeframe, in about five to eight words. "Approval needed: reporting tool renewal, by Oct 10" tells the reader what is wanted, about what, and when. "Quick question" tells them nothing and gets triaged accordingly. The mechanism is inbox triage. A senior inbox is sorted in a fast scroll, and the subject line is where your message is filed as open now, open later, or never. Writing it after step 3 rather than before is deliberate — you can only name the action once you know what it is. ### 5. Put the ask first, the context second This is the part every source agrees on and most drafts get backward. Executive emails use the inverted pyramid: conclusion first, supporting detail after, with the ask inside the first two sentences. Practitioner guidance puts the body under roughly 125 words and suggests one line of context, on the reasoning that extra background dilutes rather than strengthens the point. If you are [escalating something](/knowledge/working-with-your-manager/sample-email-to-your-boss-about-a-problem/), add one thing the template collections consistently recommend and writers consistently omit: quantify the exposure. Name the days at risk, the milestone affected, or the budget implication. Even a directional estimate is more useful than describing a situation as concerning, and it converts a complaint into a decision. Where you have already tried to resolve something, a two-line timeline of what you did and when carries the justification for escalating without you having to argue for it. ### 6. Make the reply a single easy decision Senior readers want to answer, not to compose. So give them something to answer. Offer a recommendation they can approve or decline rather than an open question. If you need time with them, suggest two specific windows instead of asking when they are free. If there is a genuine choice, lay out the options as a short bulleted list — the white space does real work on a small screen. Tone matters most when the news is bad. The guidance on this is to stay with facts and to find fault with actions rather than people; complaints and frustration are the one thing that reads worse in writing than it does in the room, because the reader supplies a tone you did not intend. ### 7. Run a pre-send check, then follow up once The checklist that circulates in executive-communication guides is short enough to actually use: is the ask in the first two sentences, is the body [under about 150 words](/knowledge/communication/to-write-a-concise-email-message/), is the subject line actionable, are only the necessary people copied, and have you proofread it twice. [Copying half the department](/knowledge/communication/examples-of-email-etiquette/) is the most common unforced error — it turns a decision into an audience. Then leave it alone. One follow-up after three to five business days reads as professional; several read as pressure and, as one guide notes, reduce your effectiveness rather than increase it. ## A sample email to senior management Here is what those steps look like assembled. The scenario is an approval request going one level above the writer's own manager. > **Subject:** Approval needed: reporting tool renewal, by Oct 10 > > Hi Mark, > > I'd like your approval to move our reporting tool to Vendor B before the October 10 renewal. Maria has reviewed the comparison and supports it. > > Where things stand: > > - The current contract auto-renews on October 10 for another twelve months. > - Vendor B covers the two reports we currently build by hand, which takes about six hours a week across the team. > - Migration takes two weeks, so a decision by October 3 keeps us on the date. > > If you're comfortable, I'll start Monday and confirm here when it's done. If you'd rather talk it through, I have fifteen minutes free Thursday or Friday morning. > > Thanks, > Anna Notice what is doing the work. The ask is in sentence one. Sentence two settles the reporting line, so the reader never has to wonder whether this went around anyone. The context is three lines with one real number in each. The close gives a yes, a no, and a calendar slot, and the whole body runs under 130 words. What a sample cannot tell you is which of those moves you already make and which one you drop under pressure — and that is worth [knowing before you send](https://assessment.headwayskills.com/), since the fix is a habit rather than a better template. ## What actually makes these emails easy to write Read the sample again and most of what makes it work happened before the writing: knowing who owned the topic, knowing exactly what was wanted, and knowing how the reader would spend their thirty seconds. Those are three separate habits, and they recur in every message that goes up a level. **Communication** covers the mechanics on the page. Lead with the main message, keep the subject line concise, copy only the people who need it, and reply in reasonable time. It also covers the choice you made in step two — conversation when a topic is sensitive, complex, or needs negotiating; writing when the other person needs time or the point is one-way. Being brief and stating the main point first are not stylistic preferences here; they are what makes a busy reader able to act. **Working with Your Manager** is the part the sample handles in a single clause. The relationship works as a partnership, which in practice means aligning with your manager before you align with anyone else, bringing something closer to a solution than a problem, and being honest about status even when the status is uncomfortable. It also tells you when going up a level is legitimate rather than risky — a question no template can answer for you. **Influence** is what turns a well-formed email into a decision. Most of it happens in preparation: understanding what the reader actually cares about, and knowing how the decision really gets made and by when. The rest shows up as keeping it simple, naming the drawback instead of hiding it, taking a smaller yes when the full one is unlikely, and following through afterward on what you said you would do. Knowing which of the three to work on is the more useful question, and a quick read on [which habits you already have](https://assessment.headwayskills.com/) settles it faster than guessing — it covers twelve work skills in all, of which these are three. None of them is a disposition you either have or don't; each is a set of moves you can practice on the next email you send. ## The part of this you can build Some of this may already match how you work. Plenty of people reread a message twice before sending it, or check with a colleague before pressing send on something sensitive, without ever having called that a skill. Looking up how to write this before writing it is the same instinct — thinking about the reader before thinking about yourself. Whatever is not there yet is not a fixed point. Writing upward is a set of moves, and moves get better with repetition; you don't have to become a more assertive person or a different kind of writer to make them. It also gets less optional. The further into a career you go, the more of your work is judged by people who only see the written version of it, which is a good argument for building the habit now, while the emails are still low-stakes and a clumsy one costs you nothing. You know what a good one looks like now. The open question is which part of it you would have to work at. ## See where your own work skills stand The last piece is knowing which part that is. The **free** Job Skills Test is a short self-assessment of your own work skills. It shows where you stand across all twelve of the skills this article draws on — including writing clearly under pressure, working well with the person you report to, and getting a decision out of someone busier than you — and which one or two would make the biggest difference to you right now. There is nothing to prepare, and you can do it quietly on your own before the next message goes up the chain. ## 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? An email to senior management needs the ask in the first two sentences and under 125 words. A worked sample, plus the seven steps behind it. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Working with Your Manager, Influence. ### 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/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-email-to-senior-management-sample/ Preferred summary: "An email to senior management needs the ask in the first two sentences and under 125 words. A worked sample, plus the seven steps behind it." ## Change log - 2026-07-07: Content collection version published.