# How to Request a Meeting With Your Boss: Sample Emails for 8 Situations Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/how-to-request-a-meeting-with-your-boss-sample-emails/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/how-to-request-a-meeting-with-your-boss-sample-emails.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Not sure how to ask your boss for a meeting? Eight sample emails for one-on-ones, feedback, workload and pay, plus what to put in the subject line. ## Key facts - Title: How to Request a Meeting With Your Boss: Sample Emails for 8 Situations - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Building Confidence - Primary keyword: how to request a meeting with your boss sample emails - Source page: https://headwayskills.com/knowledge/working-with-your-manager/how-to-request-a-meeting-with-your-boss-sample-emails/ ## What this page covers - Not sure how to ask your boss for a meeting? Eight sample emails for one-on-ones, feedback, workload and pay, plus what to put in the subject line. - Practical guidance for how to request a meeting with your boss sample emails - How this topic connects to Working with Your Manager ## Detailed explanation You have something to raise with your manager and you are stuck on the part that should be easiest: asking for the time. Working out how to request a meeting with your boss feels delicate, but the request itself is ordinary, and managers expect it. Send [a short email](/knowledge/communication/business-email-writing/) that names the topic in the subject line, states the purpose in the first sentence, proposes two or three specific times, and says roughly how long you need. Three or four sentences is enough — anything longer tends to delay a yes rather than earn one. Below is the anatomy of that email, then sample emails for eight common situations, including the one almost nobody covers: what to do when nothing comes back. ## What makes a meeting request easy to say yes to Nearly every problem with these emails is structural, not a matter of wording. Four things do most of the work. **Name the topic in the subject line.** ManageBetter's guidance is to keep it to roughly 30–50 characters and name the actual subject. "One-on-One: Q2 Goals" tells your manager more than "One-on-One Meeting," lets them arrive prepared, and stays findable in their inbox months later. **Put the purpose in the first sentence.** Indeed's guide says to be direct from the opening line and skip the introduction. If the meeting covers more than one thing, set the points out as bullets rather than a paragraph. **Do not make it mysterious.** A bare "Can we talk?" is named by NerdyJoe as the mistake to avoid, because an unexplained request creates unnecessary anxiety. Your manager will spend the gap wondering whether you are resigning. Withholding the topic feels polite from your side and reads as a warning from theirs. **Offer times and a length.** Two or three specific slots, plus how long you need. If you can see your manager's calendar, propose openings that are already free; if not, ask which part of the week suits them. Indeed's convention is mid-morning or mid-afternoon, Tuesday through Thursday. One thing worth unlearning: formality is not respect. Bubbles' guide singles out "It would be greatly appreciated if you could find the time to meet" as the anti-pattern, and offers "Could we set aside some time to discuss this?" instead. Stiff phrasing reads as distance. If you have read this far and the email is still unwritten, the gap is probably not wording. Judging when to ask, how much to say up front, and how to [raise something awkward](/knowledge/communication/difficult-conversations-at-work/) with the person who reviews your work is a set of habits rather than a talent — and habits are learnable, so it is worth knowing [where your habits stand](https://assessment.headwayskills.com/) before the next one comes up. ## Eight sample emails for the situations that actually come up Use these as structures, not scripts. Change the names, keep the shape. ### 1. Requesting a regular one-on-one With no [standing meeting](/knowledge/working-with-your-manager/effective-one-on-one-meetings/), ask for the pattern rather than a single conversation. The Keka and Qandle templates lead with cadence and duration, because a short fixed length is what makes the request easy to approve. > **Subject:** 15-minute check-in every other week? > > Hi Sam — could we set aside 15 minutes every other Wednesday to run through what I'm working on and anything I need a decision on? I'd bring a short list so it stays quick. Wednesday at 10:00 or Thursday at 14:00 both work this week. Fifteen minutes is the version your manager can approve today, and these meetings tend to grow once they exist. ### 2. Asking for feedback on your performance Tie it to work in progress. The examples collected by status.net connect the feedback request to ongoing projects, which stops it reading as a request for reassurance. > **Subject:** Feedback on the Q3 handover > > Hi Sam — could I get your read on how the Q3 handover went, and on anything you'd want done differently next time? Half an hour would cover it. Tuesday afternoon or Thursday morning? Naming what you want feedback *on* is what makes this answerable. "How am I doing?" gives your manager nowhere to start. ### 3. Raising a workload problem Maestro Labs' template guidance is to raise awareness of the problem and propose a solution in the same message. That pairing is the difference between flagging and complaining. > **Subject:** Priorities for the next two weeks > > Hi Sam — the migration and the client reporting land in the same fortnight and I don't think I can do both well. I have a suggestion for which to push, but I'd rather agree it with you than decide it myself. Do you have 20 minutes before Thursday? Note the last sentence: you are not asking your manager to [fix your workload](/knowledge/working-with-your-manager/how-to-push-back-on-your-boss/), but to confirm a call that is theirs to make. ### 4. Getting a decision on a stalled project When something is blocked, the meeting exists to unblock one decision. Indeed's own sample does exactly this — it names the project and the issues encountered, then proposes a loose window ("this week or next"). > **Subject:** Decision needed: vendor for the retention project > > Hi Sam — we're stuck between two vendors on the retention project and it needs your call to move. I can lay out both options in 15 minutes. I'm free most of Wednesday and Friday morning. Naming the decision in the subject line moves this up the queue; a manager who can see the request is a blocker treats it differently from one that looks like a chat. ### 5. Opening a career-growth conversation This one is not urgent, so it competes with everything that is. Routine's guidance is to name the areas you want to develop and reference what you have contributed, then offer flexibility on timing rather than pressing for a slot. > **Subject:** Time to talk about where I go next > > Hi Sam — now the reporting project has shipped, I'd like to talk about where to point myself next. I've been drawn to the analysis side and would value your view on whether that's realistic here. No rush — any 30 minutes in the next fortnight works. The flexibility is deliberate: making a development conversation easy to schedule is what keeps it from being postponed indefinitely. ### 6. Raising pay or promotion Signal the topic; do not negotiate in the email. Template collections keep this subject line explicit rather than coy, on the same logic as everything else — an unnamed serious topic is worse than a named one. > **Subject:** Compensation review — could we find some time? > > Hi Sam — I'd like to talk about my compensation. I've put together where I think my responsibilities have moved over the past year and would rather walk you through it in person. Would 30 minutes next week be possible? Everything else belongs in the meeting, where you can read the room and respond. ### 7. Proposing a change to how you work Hours, remote days, scope. These carry more detail up front than the other types, because your manager usually has to check a policy before answering anything. > **Subject:** Proposal: moving to Tuesdays and Thursdays in the office > > Hi Sam — I'd like to discuss shifting my office days to Tuesday and Thursday so they line up with the design reviews. I've checked it doesn't clash with the team's core days. Could we take 20 minutes, and is there anything you'd need from HR first? That last clause does quiet work: it shows you know the decision may not be entirely theirs, which makes you easier to say yes to. ### 8. Following up when nothing comes back An unanswered request rarely means no; it usually means your email arrived during a bad hour. None of the top guides on this keyword cover the follow-up, which is odd, because it is the most likely thing to happen. > **Subject:** Re: 15-minute check-in every other week? > > Hi Sam — bumping this in case it got buried. Happy to work around your calendar; if it's easier, I can put 15 minutes in a free slot and you can move it. Wait about a week, reply on the original thread so the context is attached, and offer to do the scheduling yourself. Making the reply cheap works better than making the request urgent. ## The habits that make asking easier Once you have sent three or four of these, the email stops being the hard part. What separates people who find this easy from people who put it off for a fortnight is a handful of ordinary working habits. **Working with Your Manager** changes the frame more than any template will. A regular one-on-one — weekly or every other week — is not a favor your manager grants you; it is the ordinary machinery of a working partnership, and asking for it is you doing your half. The behaviors that make these requests land are the ones that make the whole relationship work: preparing before you show up, being specific about what you need, and bringing a proposed answer alongside the problem rather than the problem alone. **Communication** covers the mechanics above — leading with the main message, keeping the subject line short and specific, copying only the people who need it. It also covers a question that comes before the email: whether writing is the right medium at all. Writing suits one-way messages and things worth a record. Anything sensitive, complicated, or likely to need negotiating is better as the conversation you are trying to arrange. **Building Confidence** closes the gap between having the draft and sending it. The move is unglamorous: decide in advance exactly when you will send it, then get past the first step only. The discomfort does not vanish so much as shrink, and it shrinks through repetition — the third request costs a fraction of the first. None of the three is a personality type; all are behaviors you can build, and they sit inside a set of **twelve work skills** that recur across almost any job. The free Job Skills Test is the quickest way to see which of the twelve is doing the least work for you right now — you can [measure them instead of guessing](https://assessment.headwayskills.com/). Some of this may already sound like how you operate — you may be the person who names the topic in the subject line without thinking about it, and who hesitates only on the harder conversations. That is worth noticing, because it tells you which specific habit is holding the email up. Requests like these do not get rarer as your career goes on. They get bigger: more consequential topics, busier calendars, people further from you in the organization. The habits behind them scale with the stakes, which is why it is worth knowing now which are solid and which need work — both of which you can change, at whatever pace suits you, without becoming a different person at work. You have also already done the part most people skip, which is thinking about how to ask rather than quietly deciding not to. ## See where your work skills stand The only thing left is to find out which of these habits is weakest for you right now, so you know where to put the effort. The Job Skills Test is a **free** self-assessment of your work skills. You answer a short set of questions and get a picture of where you stand across all twelve — which ones already work for you, and which one or two would make the biggest difference over the next year. There is nothing to prepare and no right answers to work out in advance. Take it whenever you have a quiet moment; it will still be there later. **[Take the test](https://assessment.headwayskills.com/)** *Free, takes 7 minutes, and your results appear the moment you finish.* ## 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? Not sure how to ask your boss for a meeting? Eight sample emails for one-on-ones, feedback, workload and pay, plus what to put in the subject line. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Communication, 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/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.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/working-with-your-manager/how-to-request-a-meeting-with-your-boss-sample-emails/ Preferred summary: "Not sure how to ask your boss for a meeting? Eight sample emails for one-on-ones, feedback, workload and pay, plus what to put in the subject line." ## Change log - 2026-07-07: Content collection version published.