Skip to main content
Back to module
Professional Communication & Teamwork · Clear Workplace Writing

Emails that get answers

Reading31mLesson 1 of 3 in this module

Write a concise request email that puts the ask and the deadline first.

Why it matters

In almost every STEM job, a lot of the work happens over email. You ask a lab manager for instrument time. You ask a senior developer to review your code. You tell a client a part will arrive late. A clear email gets a fast answer. A vague one gets ignored, or it starts a long thread of back-and-forth questions.

The good news is that a useful work email follows a pattern you can learn in an afternoon. You do not need fancy vocabulary. You need to make the reader's job easy.

The core idea: lead with the ask

Busy people read the subject line and the first two sentences, then decide whether to deal with the message now, later or never. So put the most important thing first.

A request email has five parts:

  1. A specific subject line. Say what you need and by when, if there is a deadline.
  2. A short greeting. Use the person's name. "Hi Priya," is fine in most workplaces.
  3. The ask, in one or two sentences. What do you need, from whom, and by when?
  4. The context the reader needs to act. Only the facts that help them say yes or no. Use bullet points for more than two items.
  5. A clear close. Thank them, and make the next step obvious.

Think of it as "bottom line up front". The reader should know what you want even if they stop reading after the first paragraph.

Worked example

Here is a first draft from a new lab technician:

Subject: Question

Hi,

I hope you are doing well. I wanted to reach out because I have been
working on the stability samples and I noticed that the HPLC schedule
looks pretty full this week and I was wondering if there was any
possibility of maybe getting some time on it at some point, because
the samples need to be run soon. Let me know what you think.

Thanks

The reader has to work out what is being asked, how much time is needed and how urgent it is. Here is the rewrite:

Subject: Request: 2 hours on HPLC-2 before Thursday noon

Hi Priya,

Could I book 2 hours on HPLC-2 before Thursday at noon? The schedule
shows it is full, so I wanted to ask you directly.

Context:
- 12 stability samples (batch 4417) reach their 30-day pull on Thursday.
- They must be injected within 24 hours of the pull.
- Any slot Wednesday afternoon or Thursday morning works for me.

If HPLC-2 is not possible, is HPLC-1 free? I can adjust the method.

Thanks,
Sam

The second version is not much longer, but it is far easier to answer. Priya can reply with a single line: "Wednesday 2–4 pm is yours."

The same pattern works in software. Compare "Can you look at my PR?" with:

Subject: Review needed by Friday: PR #212 (password reset fix)

Hi Marco,

Could you review PR #212 by end of day Friday? It fixes the bug where
reset links expired after 5 minutes instead of 24 hours.

- 3 files changed, about 60 lines.
- Tests added for the expiry check.
- The part I am least sure about is the timezone handling in expiry.js.

Thanks!
Jordan

Pointing to the part you are unsure about saves the reviewer time and gets you better feedback.

Tone and courtesy

Be polite and direct at the same time. "Could you..." and "Would you be able to..." are polite without being vague. Avoid stacking softeners ("I was just wondering if maybe possibly..."), which hide the ask. Avoid all caps and lots of exclamation marks, which read as shouting.

When you write to someone senior or outside your team, keep it a little more formal. When you reply to a teammate in a quick thread, a shorter style is fine. If you are unsure, mirror the tone of the person you are writing to.

Before you hit send

Run this quick checklist:

  • Subject line: could someone find this email by searching for it in a month?
  • First two sentences: do they state the ask and the deadline?
  • Recipients: is the person who must act in "To"? Are people who only need to know in "Cc"? Did you remove anyone who does not need it?
  • Attachments and links: did you actually attach the file you mention? Do the links open for someone outside your account?
  • Proofread: read it once out loud, or at least slowly. Check names, dates, numbers and units.
  • Sensitive content: never put passwords, patient data or other confidential information in email unless your organization's policy says how.

Common mistakes

  • Burying the ask at the bottom of a long story.
  • Several unrelated requests in one email. The reader answers one and forgets the rest. Send separate emails, or number the requests.
  • No deadline. "Soon" means different things to different people. Give a date and time.
  • Reply-all by habit. Only reply to everyone when everyone needs the reply.
  • Writing while angry. Save it as a draft and reread it later, or talk in person.

Following up

If you get no reply, follow up politely after a reasonable wait (often two working days, sooner if the deadline is close). Reply in the same thread so the context is there: "Hi Priya, following up on this. Thursday's deadline still stands. Is Wednesday afternoon possible?"

Quick recap

  • Put the ask and the deadline in the subject line and the first two sentences.
  • Give only the context the reader needs, in bullets.
  • Be polite and direct; make the next step obvious.
  • Check recipients, attachments and facts before sending.

Try it

Open the Do tab. You will rewrite a real request of your own into a clear email using the five-part pattern.

Also in this lesson: