The one idea
Email is not one template. It is a set of types, and each type has a fixed job. Once you can name the type, the structure is already decided and you are only filling in facts.
A request and a status update look superficially similar and behave completely differently. A request needs a deadline and one owner. A status update needs no reply at all — and if you write it as though it does, you have created work for someone.
Ask yourself "what am I trying to make happen?" before you ask "how do I word this?"
Identify the type — request, update, escalation, decline — and use that type's structure. The wording is the last five percent.
Each type has a different expected response and a different cost of being misread. Matching structure to type is what makes a message legible to a reader scanning forty others.
The universal structure
Every type below is a variation on the same five parts.
| Part | What it does |
|---|---|
| Subject | States the ask and the deadline. Read even when the body is not |
| Context | One or two lines. Only what the reader needs to decide |
| The ask | One sentence. A verb aimed at one named person |
| The deadline | A day and a time, not "ASAP" |
| Close | Thanks, and what you will do next |
Two rules that apply everywhere. One email, one ask — a second ask halves the chance the first gets done. And the subject line is the message for anyone reading on a phone between meetings.
Fourteen types
1. The request
Purpose: get a specific person to do a specific thing. Tone: plain, warm, unapologetic.
Subject: Need your sign-off by Wed 5pm — Q3 vendor list
Hi Deepak,
Can you sign off the attached vendor list by Wednesday 5pm? Three names changed since your last review; they are highlighted.
Procurement closes the window on Thursday morning, so anything after that waits until the next cycle.
Thanks — Sana
2. The follow-up (they are not late yet)
Purpose: keep something visible without implying failure. Reply to your own thread so the history travels with it.
Hi Deepak — checking in on the vendor list. Still fine for Wednesday 5pm, or would Thursday morning be easier? Happy either way, I just need to tell procurement which.
3. Chasing a late reply
Purpose: get an answer. Tone: neutral, never sarcastic, never wounded. Assume they did not see it, because usually they did not.
Subject: Still need sign-off — Q3 vendor list (was due Wed)
Hi Deepak,
Following up on this — I haven't heard back and the procurement window closed this morning.
Two options: I can request a one-week exception, or we push the three new vendors to the next cycle. Which would you prefer? If I don't hear by 3pm today I'll request the exception, as that keeps the most options open.
Thanks — Sana
Notice what is missing: "as per my previous email", "gentle reminder", "I have followed up multiple times". Those signal irritation and put the reader on the defensive, which slows the reply down. Notice what is present: two options and a default.
4. The status update
Purpose: stop people asking. Requires no reply. Same shape every week so it can be scanned in ten seconds.
Subject: Migration — week 3 status (no action needed)
On track for 14 Oct.
- Done: user table migrated, 1.2M rows, verified
- In progress: order history — about 60%, finishes Thursday
- Blocked: nothing
- Risk: the reporting team hasn't confirmed their cut-over window. Chasing; will flag if not resolved by Friday.
The header line — "on track", "at risk", "slipping" — matters most. A reader who only reads three words should still get the correct impression.
5. The escalation
Purpose: bring in someone with authority to unblock. Facts only, no blame, no adjectives.
Subject: Decision needed — payments testing blocked 6 days
Hi Rekha,
Bringing this to you because it needs a decision above my level.
Payments testing has been blocked since 2 September waiting for sandbox credentials from the vendor. I have followed up on 2, 4 and 8 September (thread below). No response.
Impact: we lose the 14 October release if this is not resolved this week.
Options: (a) you or Sanjay raise it with their account manager, (b) we test against the old sandbox, which leaves the new refund flow untested, or (c) we move the release to 28 October.
My recommendation is (a). Can you decide by Thursday?
6. The apology, or correcting your own mistake
Purpose: contain the damage and restore trust. The instinct is to explain first. Resist it — explanation before acknowledgement reads as excuse.
Order: what happened, what the impact is, what you have already done, what you need. Apologise once, briefly, and do not grovel.
Subject: Correction — yesterday's revenue figure was wrong
Hi all,
The revenue figure in yesterday's deck was wrong. I reported ₹4.2 crore for August; the correct figure is ₹3.7 crore. I pulled the number before the credit notes were posted.
Corrected deck attached. The August figures were used in the board pack, so Nitin — you'll want the updated slide 6 before Friday.
Sorry about this. I've added a check that the finance close is complete before I pull the report, so it does not happen again.
Meera
7. Declining
Purpose: say no clearly, without damaging the relationship. Be brief. A long no reads as negotiable.
Hi Arun — I can't take the audit on. I'm on the migration until 14 October and adding this would put that at risk.
If it can wait until the 15th, I can start then. Otherwise Kavya has done two of these before and would be a good fit.
Three moves: a clear no, one honest reason, one alternative. No apology spiral, no invented excuse. And no "unfortunately at this moment in time due to bandwidth constraints", which is four words of hedging around a decision you have already made.
8. Asking for clarification
Purpose: get what you need without sounding as though you did not read the brief. State your interpretation and ask them to confirm — far easier to answer than "can you clarify?"
Hi Sir — before I start on the competitor analysis, can I check I've understood?
I'm assuming you want the top five competitors by revenue, one page each, focused on pricing, and that you need it for the 12th board meeting.
If that's right I'll get started. If not, tell me which part is off.
This is the single highest-return email a new employee can learn. It costs five minutes and saves three days of work in the wrong direction.
9. The meeting request
Purpose: get time booked. Include the purpose, the length, and the decision required — otherwise it becomes a meeting about deciding what the meeting is for.
Subject: 30 min this week — decide the reporting cut-over date
Hi Rekha, Sanjay,
Can we take 30 minutes this week to fix the reporting cut-over date? We need a decision before Friday so the vendor can schedule.
Thursday 11:00 or Friday 09:30 both work for me — invite to follow once you pick. One-page background attached; five minutes of reading.
10. The meeting summary
Purpose: make the meeting real. Sent within a day, or it is worthless. Decisions and owners, not a transcript.
Subject: Notes — reporting cut-over (28 Oct decided)
Decision: cut-over on 28 October, 22:00–02:00.
Actions
- Sanjay: confirm the window with the vendor — by Fri 12 Sep
- Sana: update the release plan — by Mon 15 Sep
- Rekha: tell the regional leads — by Wed 17 Sep
Open: whether the old reports stay available for 30 days. Rekha to check with compliance.
Corrections welcome — otherwise I'll take this as agreed.
That last line does real work. It makes silence into agreement and gives anyone who misremembers a chance to say so now rather than in December.
11. Replying to a recruiter
Purpose: stay in the running and give them what they need to move you forward. Reply within 24 hours. Answer their actual questions — availability, notice period, expectations — because a recruiter cannot progress you without them.
Subject: Re: Backend Engineer role — Priya Nair
Hi Aditi,
Thanks for reaching out — yes, I'm interested.
- Current role: backend developer at Zentro, 2 years, mostly Python and PostgreSQL
- Notice period: 60 days, possibly negotiable to 45
- Expectation: ₹18–22 LPA fixed, flexible for the right role
- Available for a call: any weekday after 6pm, or Friday afternoon
CV attached. Happy to answer anything else.
Priya
Bullets, not paragraphs — a recruiter is copying these into a form. On salary: if you genuinely do not have a number yet, "I'd rather understand the role first — what range is budgeted?" is a normal, professional answer.
12. Thank-you after an interview
Purpose: be remembered accurately. Send within 24 hours. Short. One specific detail from the conversation proves you were present.
Subject: Thank you — backend engineer interview, Tuesday
Hi Aditi,
Thanks for your time on Tuesday. I enjoyed the discussion, particularly the problem you described with the reconciliation job running past the batch window — I've hit a version of that before and it's a genuinely interesting constraint.
It confirmed my interest in the role. Do let me know if you need anything further from me.
Priya
Do not restate your CV, and do not ask when you will hear back if they already told you.
13. The leave request
Purpose: get approval and reassure your manager that nothing breaks. Say who covers what — that is what the approval actually turns on.
Subject: Leave request — 14–18 Oct (5 days)
Hi Meera,
I'd like to take leave from Monday 14 to Friday 18 October, back on Monday 21st.
The migration finishes on the 11th, so nothing critical falls in that week. Kavya has agreed to cover the daily checks, and I'll hand over on the 10th.
Applied in the HR system as well. Let me know if the dates are a problem.
14. Asking for a deadline extension
Purpose: get more time while keeping your credibility. Ask early — an extension requested a week ahead is planning, the same request on the deadline is a failure report. Never ask for "some more time". Name the new date.
Subject: Request — move the compliance report to 22 Sep
Hi Rekha,
Can we move the compliance report from 15 to 22 September?
The audit data arrived four days late and two of the branch returns are still missing. I can hit the 15th, but the branch figures would be estimates, which defeats the purpose of the report.
If the 15th is fixed, I can deliver everything except section 4 on time and send section 4 on the 22nd. Which do you prefer?
Sana
A note on Indian workplace convention
Opinion Some habits common in Indian offices actively hurt you when you write to
anyone outside your immediate circle — including recruiters at multinationals,
overseas clients, and increasingly your own leadership.
- "Respected Sir/Madam", "Dear Sir" to someone whose name you know. Use the name. "Hi Rekha" is normal and respectful nearly everywhere now. Where your office genuinely runs on "Sir" in person, match it — but never to an external recruiter or client.
- "Please do the needful." Ubiquitous, and it means nothing. The reader has to work out what the needful is. Replace with the actual verb.
- "Kindly revert." In standard English "revert" means to go back to a previous state. Say "reply".
- Excessive CC. Copying five seniors on a routine request is read as pressure, not diligence. CC people who need the information. Use BCC only to protect addresses on a bulk send — quietly BCC'ing someone into a live conversation is how trust dies.
- Ornate closings. "Thanking you in anticipation", "Yours obediently". "Thanks" and your name.
None of this is about sounding Western. It is about being read quickly and correctly by someone who does not share your office's conventions.
Writing any of these in four minutes
1 of 6Name the type. Request, update, escalation, decline, clarification? Say it out loud. The structure follows from the name.
Try this
You promised a client a report by Friday. On Wednesday you discover the data you need will not arrive until Monday. Write the email.
Decide the type before you write.
Your challenge
Level 3 · IndependentBuild your own playbook. Pick the five types from this lesson you will actually send in the next month, and write a real draft of each — real names, real dates, real situations from your work or your job search.
You have succeeded when each draft passes all four tests:
- The subject line names the action and the date.
- There is exactly one ask, aimed at one named person.
- There is a stated deadline or a stated default.
- Someone with no context could tell you who does what by when.
Save them somewhere you can find in twenty seconds. The point of a playbook is that you never write these from scratch again.
What people usually get wrong
- Subject lines that are labels. "Update", "Query", "Regarding the report". They tell the reader nothing and get buried.
- Two asks in one email. You will get one answer. Send two emails.
- Chasing with "as per my previous email". It reads as an accusation and slows the reply.
- Replying to a recruiter in prose. They need notice period, expectations and availability as data. Give them bullets.
- Asking for an extension on the deadline itself. Ask a week early and it is planning. Ask on the day and it is a failure.
- Apologising for four paragraphs. Long apologies are about your discomfort, not the reader's problem. One line, then the fix.
- Reply-all by reflex. Check who is actually on the thread before you say anything you would not say to all of them.
- Sending a summary three days after the meeting. By then everyone has a different memory and yours no longer wins.
How someone experienced does it
Experienced people keep a personal file of emails that worked — not templates downloaded from somewhere, but their own messages that got a fast yes. When a situation repeats, they open the old one and change the facts. Ninety seconds instead of twenty minutes, and the quality is higher because that version has already been tested on a real reader.
They also write the difficult ones and do not send them immediately. Anything involving anger, blame, or a large sum gets drafted, left for an hour, and re-read. The delay changes the message roughly half the time, and it has never once made it worse. Put the recipient's address in last so you cannot send it by accident.
The subtlest skill is knowing when the email is a bad instrument. Bad news to a person you like, a disagreement with your manager, anything where the reader may feel accused — these go badly in writing because the reader supplies a tone you did not intend, and then the written record makes it permanent. The move is a short conversation, then a short email confirming what you agreed. That email is easy to write, because the hard part already happened out loud.
When not to use this
Do not use email when:
- A five-minute conversation would settle it. Four rounds of clarification over two days is a conversation you refused to have.
- The matter is legally or emotionally serious for you personally — resignation disputes, harassment, anything with a lawyer in its future. Get advice on what to put in writing before you write it, because email is evidence and cannot be recalled.
- You are angry. Not never — just not now.
What actually happens to your email in someone's inbox
A busy reader processes their inbox in passes. First pass: sender and subject only, deciding what to open at all. Second pass: first two lines of the ones that survived. Only the third pass is reading.
Two practical consequences. Your subject line and first sentence are doing almost all the work, so they carry the ask. And an email that requires the third pass to be understood will be deferred — not rejected, deferred, which feels the same to you but means the reader has classified it as effort.
Most mail clients also show a preview of the first line or so next to the subject. If your first line is "I hope this email finds you well", you have spent your entire preview on nothing.
Prove it
Your five drafts, saved. Then send at least one of them for real this week.
Add one line to each after it is sent: what came back and how fast. Over a few months that file becomes a record of what genuinely works on the people you actually write to, which no generic guide can give you.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned choosing the right structure for a specific work email. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood choosing the right structure for a specific work email. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at writing the common types of work email — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.