The Structure of a Request: How to Write an Email That Gets an Immediate Answer

To get the same result from a colleague you may need three one-hour meetings – or a single email. That is the difference in communication efficiency. Inefficient communication frustrates both sides, and if you communicate like that with someone often, their willingness to work with you slowly drops.

I measure communication efficiency simply: by the total time and number of interactions needed to reach the result. And the biggest difference is made by how the very first request is phrased.

Three parts of every request

Before every request, stop, think and phrase it like this:

What you need – information, brainstorming, a decision, inputs…

Why you need it – you give the other side context so they can come up with a better solution than you would, and so they know what happens if you don’t get it in time.

How you need to receive it – when and in what form (phone call, email, meeting, structure of the output).

Example 1: asking for information

Hi Peter,

I need all planned outage dates of the TAPO system and their duration, from today until the end of the year. If you don’t plan that far ahead, I need to know at least one week before each outage when TAPO will be down.

We have deployed a payroll module that works with TAPO, and when TAPO is down, payroll calculations go wrong. The vendor will only fix this at the beginning of next year, so until then I need to pause payroll processing during those times or find another solution.

Let me know which option works better for you. I always need the information by email, the first batch by the beginning of the month, when we switch to the new system. If I don’t have it, I will have to postpone our go-live until I do.

Thank you,

Notice: Peter immediately knows what to deliver, why it matters, by when and in what form. He even has two options to choose from. He doesn’t need to ask follow-up questions.

Example 2: asking your manager for a decision

How do you get your boss to answer your email right away? By making every request as ergonomic as possible so it takes her minimal effort. You do the work for her – she only decides.

Hi Marta,

I need your approval to buy new bug-tracking software.

I recommend Fizzy by 37signals at 200 € per month, a cloud solution with no limits on users or projects. I validated it with Jana, who leads testing, and it is her favourite too.

If this works for you, just reply “OK” and I’ll buy it with the company card today. If you have questions, send me a time and I’ll call you.

Alternatives considered:

• Atlassian Jira, cloud, 4,000 € per month (25 € × 160 licences). No guest access, so we can’t build a client portal.
• GitHub, cloud, 2,400 € per month (15 € × 160). Too technical for our product team.

Thanks in advance for your time and decision, Stanislav

One word is enough to answer. The recommendation, price, validation, next step and alternatives are all in one place.

The warning signal

You are writing an explanatory sentence at the end of the email.

When that happens, go back to the beginning, clarify what you actually want to say and rewrite the message using the structure above. An explanatory sentence at the end is almost always a sign that the request was not clear from the start.

Why it works

• It forces you to think through what you actually need. What does the expected result look like? Where does your responsibility start and end?
• You respect other people’s time. Every request draws on the most valuable thing people have – their time and attention.
• You reduce spam. Fewer words that don’t serve the result, fewer follow-up questions.
• You quickly learn whom you can rely on. Answers to clearly structured requests are a litmus test: who delivers what you ask for, who fairly declines when they can’t make it, and who avoids.

Invitation to reflect

• Go through your last three sent emails. Did they contain all three parts – what, why and how?
• How often do you get exactly what you need in the first reply? How many times do you have to clarify and add to your request?
• Pick one area of your work where you will use the request structure for a whole month. Then compare what changed.

This article is based on my upcoming book Management Essentials. The next step is how to assign work so it actually gets done.

Ready to take the first step?

The intro call takes 20 minutes, it’s free and there is no obligation.

Book a free intro call →