How to Ask Questions in Email
How to write the email itself: how long to make it, how formal to be, whether to number your questions, how to ask a second time without friction, and when the question does not belong in an inbox at all.
The questions
Open any question for the note
Am I asking a question or making a request?
Why ask it
Worth settling before you write, because the two need different endings. A question ends when you have the information; a request ends when someone has done something. Emails that blur the two produce answers with no action, or action with no answer.
How long should a question email be?
Why ask it
Short enough that the whole thing is visible without scrolling on a phone, which is roughly five or six lines. Longer emails are not rude, but they get deferred to a quieter moment that may not come this week.
Should I phrase it as a question or as a statement of what I need?
Why ask it
Use a question mark when you want information and a flat statement when you want a decision. "Could you possibly let me know if the date works?" invites a yes with no date attached; "I have pencilled in the 12th, tell me if that is wrong" produces either silence, which is agreement, or a correction.
How do I lay out several questions so all of them get answered?
Why ask it
Numbered lines, one question per line, no sub-clauses. The reader can then reply inline with 1, 2, 3, and you can see at a glance what is missing. Questions embedded in prose get answered in aggregate, which usually means partially.
Bullets or numbers?
Why ask it
Numbers, if you want to be able to refer back to a specific item later in the thread. Bullets read as a list of considerations rather than a list of things needing answers, which is fine for context and poor for questions.
How do I signal how much detail I want back?
Why ask it
Say it outright: "a one-line answer is plenty" or "as much detail as you can spare." Without a signal, most people guess low, which is why carefully worded questions come back with a single word and no explanation.
How formal should the tone be?
Why ask it
Match the last email you received from that person rather than picking a register in the abstract. If you have never heard from them, err slightly formal for the greeting and plain for the question itself, since flowery wording around a request tends to obscure what is being asked.
Should I apologise for asking?
Why ask it
Once at most, and only if you are genuinely imposing on someone with no obligation to help. Repeated apology reads as either fishing for reassurance or expecting a refusal, and it makes a short answer feel unkind, which slows the reply down.
Is it worth saying why I am asking this particular person?
Why ask it
Yes, in one clause, especially for anyone who receives a lot of requests. "You built the original importer, so you are the only person who would know" both explains the choice and quietly rules out being redirected to someone else.
When is a question better asked in chat than in email?
Why ask it
When the answer is a fact one person holds and will take them ten seconds to give. Email suits questions that need a written record, need thinking time, or cross an organisation. Sending a one-word question by email is not wrong, but it will typically wait longer for a slower answer.
When should I not put a question in writing at all?
Why ask it
When any honest answer would be damaging in a forwarded thread, or when you are asking about someone rather than about work. Written questions get archived, screenshotted and read by people you did not choose, and no amount of careful phrasing undoes that.
Does it matter what time I send it?
Why ask it
Mostly it matters that it arrives during the recipient's working hours, so it lands near the top of an inbox someone is actually reading. A question sent late at night also sets an expectation about your own hours that is hard to walk back.
How do I write a question for someone who works in another language or time zone?
Why ask it
Short sentences, no idioms, dates written with the month spelled out, and any deadline given with a time zone attached. Idiomatic softeners such as "if you could possibly see your way to" are the first thing to go, because they are also the first thing to be misread.
How do I ask a new question in a reply without looking like I ignored theirs?
Why ask it
Answer their point first, in one line, then start a new paragraph for your question. Replies that open with a fresh question read as a subject change, and the person who wrote the original email usually notices that theirs went unanswered.
Should I quote the earlier thread or trim it?
Why ask it
Keep the part your question depends on and cut the rest. A question sitting above forty lines of quoted history makes the reader hunt for what changed; a question with two quoted lines above it can be answered without leaving the message.
How do I ask something I have already asked once?
Why ask it
Restate the whole question rather than pointing back at it, and add nothing about the delay. "Reposting this so it is easy to find" is enough. Any reference to how long you have waited turns an answerable question into a small negotiation about fault.
How do I ask when I might be wrong about the premise?
Why ask it
Put the assumption in its own sentence and invite correction: "I have understood that the API only returns active users. If that is right, how do we handle..." This gives the reader a cheap way to fix your framing instead of answering a question that does not apply.
Should I just ask for a call instead?
Why ask it
Ask for a call when the answer depends on the answer to something else, or when the last two emails have each raised a new question. Do not lead with it for a question that fits in a sentence, because a fifteen-minute meeting request costs the other person more than a written reply.
How do I keep a question from reading as passive-aggressive?
Why ask it
Cut "as I mentioned," "per my last email," "just checking," and any question beginning with "why didn't you." What remains, a plain question and a date, reads as neutral even when you are annoyed, and it keeps the thread usable if it is forwarded.
How do I make sure I never have to ask this again?
Why ask it
Put the answer where the next person will look: a document, a ticket, a shared page, with a line back to the email. Answers that live only in your inbox get re-asked within months, usually by you, and the second ask is harder because the person remembers answering it.
Writing the email
Practical guidance for the conversation itself
Four habits that do most of the work
Lead with the question
First or second sentence, on its own line. Context can follow underneath for anyone who needs it.
Be specific about the unit of the answer
Ask for a date, a number, a name or a yes. Vague questions are answered vaguely and then need a second email to pin down.
Make it scannable
Numbered questions, short paragraphs, no walls of text. Most business email is read while doing something else.
Give an out
Saying that a short answer is fine, or that a redirect is welcome, removes the main reason people leave an email unanswered: they do not have time to answer it properly.
Shapes you can reuse
One question
- 1Subject: [Object]: one question about [specific thing]
- 2Hi [Name],
- 3[The question, one sentence.]
- 4Context if you need it: [two lines].
- 5Thanks, [Your name]
Three questions
- 1Subject: Three questions on [project]
- 2Hi [Name], three short ones, in order of how much they block me:
- 31. [Question]?
- 42. [Question]?
- 53. [Question]?
- 6Answering inline is fine, and 3 can wait if you are short of time.
Asking again
- 1Subject: Re: [original subject]
- 2Hi [Name], reposting this so it is easy to find rather than buried in the thread.
- 3[Full question, restated.]
- 4If it belongs with someone else, say the word and I will take it there.
What goes wrong
The question that arrives in paragraph four
Everything above your question is competing with it. Move the question up and cut half the context.
Softening until nothing is asked
"I was just wondering whether it might be possible to maybe get an idea of the timeline" contains no answerable question. One polite clause, then ask.
Questions you could answer yourself
Search the thread, the shared drive and the documentation first. People notice which of your questions were free to answer, and it affects how fast they answer the next one.
Reply-all by reflex
If only one person can answer, reply to that person and summarise back to the group if the answer matters to them.
Chasing the next morning
Two or three working days is normal for a question with no stated deadline. Chasing sooner without one teaches people to ignore your deadlines when you do set them.