How to Write a Professional Email: 7 Rules + 5 Templates

A professional email has 5 parts: a subject line that previews the ask, a salutation that fits the relationship, a body that opens with the ask and ends with one action item, a sign-off that matches the tone, and a signature that identifies you. Get those right and the rest is style.

Here is a useful way to think about it. Writing a professional email is like packaging a delivery. The recipient should know what is inside before they open it (subject), who it is from (salutation), what action is needed (body), and how to respond (sign-off). Skip a step and the package looks suspicious — they leave it on the table for later, or worse, they bin it.

After 24 years of training working professionals in Singapore, I can tell you most emails fail not because the writer’s grammar is weak. They fail because the writer buries the ask, mismatches the register, or picks the wrong channel altogether. This article walks through seven rules and gives you five copy-paste templates for the situations you will actually face — emailing your boss, your client, a professor, a stranger, and the thank-you you owe after a meeting.

---

1. The 5 parts of every professional email

Every well-written professional email contains the same five components, in the same order:

1. Subject line — previews the ask in under 50 characters.
2. Salutation — addresses the recipient at the right register.
3. Body — opens with context (one sentence), states the ask (one to two sentences), and lists action items.
4. Sign-off — closes at a register that matches the opening.
5. Signature — identifies you with name, role, organisation, and contact.

If a recipient opens your email and cannot tell within five seconds what you want and what they need to do about it, the email has failed at its job. The five-part structure is the simplest scaffold for not failing. Memorise it. Every email you write should pass the five-part check before you hit send.

2. Subject lines that get opened (and the ones that get ignored)

Most inboxes are triaged in under three seconds per email. Your boss has 200 unread messages this morning and is deciding which 30 are worth opening. The subject line is the entire pitch.

Six paired examples — bad subject on the left, better one on the right:

Bad	Better
Quick question	Approval needed: Q3 budget reallocation by Friday
Hi	Vendor onboarding — next step on your side
Update	Project Atlas: status, two blockers, decision needed
Re: Re: Re: Re: meeting	Tomorrow’s 10am meeting — moved to 11am
Following up	Following up on the quotation request from 28 April
Complaint	Service complaint — invoice INV-2891, missing items

Three rules will cover most situations. Keep it under 50 characters so it doesn’t truncate on mobile. Front-load the keyword the recipient will search on later — three months from now, when they need to find this email, “Q3 budget reallocation” is searchable, “Quick question” is not. Avoid “Hi”, “Update”, and “Quick question” entirely. They tell the recipient that you didn’t bother to think about them, which is a poor first move when you are about to ask them to do something. HBR’s military-precision subject-line writeup has a tighter version of this same rule, if you want the longer reasoning. For the broader Outlook-and-inbox angle (folders, rules, scheduled send), our companion piece on how to write an effective email covers the tooling side.

3. How to start: salutations by relationship

The salutation is where most professional emails stumble. Either the writer over-formalises with someone they have worked with for a year, or under-formalises with a senior they have never met. Both are equally bad signals.

Match the salutation to the relationship and the context:

Relationship	First contact	Ongoing	Casual register
Boss / senior	Dear Mr Tan / Dear Ms Lim	Hi James / Hi Sarah	Hi James (after explicit invitation)
Client	Dear Mr Tan	Hi James / Dear James	Use sparingly — defaults to formal
Professor / academic	Dear Professor Chen / Dear Dr Chen	Dear Professor Chen	Avoid casual entirely
Stranger (cold outreach)	Dear Mr Tan	n/a	n/a
Group / team	Dear team / Hi all	Hi team	Morning, all

A note on Singapore corporate context. When in doubt, default formal. Within ministries, stat boards, banks, professional services firms, and most large local companies, “Dear Mr Tan” reads as respectful and standard. “Hi Bob” to someone you have never met, especially someone two grades above you, can read as presumptuous. The cost of being too formal once is roughly zero. The cost of being too casual once can be the entire deal. Singapore working culture leans deferential on first contact — work with that, not against it.

4. The body: opening line, ask, action items, sign-off

The body has four jobs and they should happen in this order.

Opening line — one sentence of context. Why are you writing? “I’m following up on our conversation last Tuesday about the vendor onboarding timeline.”

The ask — one or two sentences. What do you need, and by when? “I need your approval on the revised timeline by end-of-day Friday so we can confirm the kickoff date with the vendor.”

Action items — bulleted if there are more than one. What does the recipient need to actually do?

• Review the attached revised timeline.
• Confirm or comment by Friday EOD.
• Loop in your finance lead if budget clearance is needed.

Closing line — one sentence, then sign-off. “Happy to jump on a quick call if anything is unclear. Best, Sarah.”

The single most common email failure I have seen across many years of corporate training is the buried ask. The writer opens with three paragraphs of context, then asks the question in the fourth paragraph, by which point the reader has already decided to deal with it later. Later turns into never. The email gets archived, the deadline slips, and the writer wonders why the boss is annoyed.

The fix is extremely easy. Read your draft. Find the sentence that contains the actual request. Move it to within the first 30 words of the body. Then re-read. The email is now doing its job. If you want the structured version of this discipline across all your work writing, Effective Business Writing at softskills.sg is the in-depth course we run on it.

5. Five templates you can copy today

Five templates for the situations you will actually face. Subject line, salutation, body, sign-off — copy, paste, swap the bracketed placeholders.

5.1 — Formal complaint

Subject: Service complaint — Invoice [INV-2891], missing items

Dear [Mr Tan / Customer Service Manager],

I am writing regarding invoice [INV-2891] dated [28 April 2026]. The shipment received on [30 April] was missing two items: [Item A] and [Item B], both listed on the invoice.

Could you please:

• Confirm receipt of this complaint by [end of week].
• Arrange for the missing items to be dispatched, or issue a credit note for [SGD amount].
• Let me know the expected resolution timeline.

I have attached photos of the delivery and the original packing list for your reference.

Sincerely, [Your full name] [Role, Organisation]

When to use: any formal complaint to a vendor, supplier, or service provider. What to swap: the invoice number, dates, items, and the specific resolution you want — do not write “please look into this”, write what you want them to do.

5.2 — Thank-you after a meeting

Subject: Thanks — [meeting topic], [date]

Hi [James],

Thanks for taking the time to meet earlier today. I appreciated your perspective on [the timeline question / the procurement constraints / the team structure].

A quick recap of what we agreed:

• I’ll send over the revised proposal by [Tuesday].
• You’ll loop in [name / department] for input on [topic].
• We’ll reconvene [next Friday] to confirm next steps.

Let me know if I’ve missed anything.

Best, [Your name]

When to use: within 24 hours of any professional meeting where decisions or next steps were discussed. What to swap: the recap bullets — these are the actual value of the email. The thank-you is the opening; the recap is the substance.

5.3 — Requesting a quotation

Subject: Quotation request — [service or product], [your company]

Dear [Mr Tan / Sales Team],

I am writing to request a quotation for [specific service or product] for [your company name].

Specifications:

• Quantity / scope: [details]
• Required delivery date: [date]
• Delivery address: [location]

Could you please send the quotation with itemised pricing, lead time, and payment terms by [date]? If you need any further specifications to prepare the quote, please let me know.

Sincerely, [Your full name] [Role, Organisation, Contact]

When to use: any first-contact request to a vendor for pricing. What to swap: the spec list. Vague specs produce vague quotes, and vague quotes waste two more rounds of email.

5.4 — Job application cover note

Subject: Application for [Role title] — [Your name]

Dear [Hiring manager name],

I am writing to apply for the [Role title] position at [Company], advertised on [LinkedIn / company site] on [date].

With [X years] of experience in [relevant domain] — most recently as [current role at current company] — I bring [one specific, relevant strength]. I have attached my CV for your review and would welcome the opportunity to discuss how my background aligns with the role.

Sincerely, [Your full name] [Phone number] [LinkedIn URL]

When to use: any formal job application sent by email. What to swap: find the hiring manager’s name. Take five minutes on LinkedIn before settling for “Dear Sir/Madam” — that small effort is often the reason one application gets read and another gets skimmed.

5.5 — Emailing a professor or senior

Subject: [Course code] — question on [specific topic]

Dear Professor [Chen],

I am a student in your [course code, semester] class. I have a question about [specific topic or assignment]: [your specific question, in one or two sentences].

I have already checked [the syllabus / the lecture slides / the assignment brief] and [briefly state what you found / didn’t find]. Would you be able to clarify, or recommend a reference?

Thank you for your time.

Sincerely, [Your full name] [Student ID, course]

When to use: any first-contact email to a professor, senior academic, or senior outside your direct chain of work. What to swap: the specific question. Vague questions get short answers — “see the syllabus” is what comes back when you have not shown that you already checked.

6. Common mistakes that cost you credibility

Eight mistakes I see over and over, in roughly the order they damage you:

1. Burying the question to ask. Three paragraphs of context, then the request. The reader has already left.
2. Vague subject lines. “Quick question”, “Hi”, “Update” — these tell the recipient nothing and signal you didn’t think about them.
3. Wrong register. Over-casual to a senior reads as presumptuous; over-stiff to a peer reads as cold.
4. Reply-all when you mean reply. Once is forgivable. Twice is a pattern. The whole department now associates your name with their notification fatigue.
5. Sending while emotional. The 12-hour rule: if the email needed to be written angry, it should not be sent until you have slept on it.
6. Random sign-offs. “Cheers” to a stranger, “Regards” to a friend. Match the sign-off to the opening register.
7. Attachment failures. Saying “please find attached” with no attachment. Attaching the wrong file. Attaching the right file with a confusing name. Rename files clearly before attaching: Proposal-Acme-2026-05-01.pdf, not final_v3_FINAL.pdf.
8. CC’ing the boss as a passive-aggressive escalation. The recipient will notice. So will the boss. So will everyone copied. It is the corporate equivalent of raising your voice in front of the class — embarrassing for everyone, including you.

A pattern I see across the 48,000+ working professionals we have trained in Singapore: the writers who get email wrong in high-stakes contexts are almost always the same writers who get it wrong in low-stakes contexts. The fix is not “be careful with important emails”. The fix is to clean up the everyday habits, so that the high-stakes one writes itself correctly. If you want a wider plan for improving your soft skills deliberately, the same drill-then-deploy logic that works for emails works across communication and presentation, leadership, and EQ.

7. When email is the wrong channel

The most under-appreciated email skill is knowing when not to send one. Four situations where email is the wrong tool:

• Emotional content. Anything that needs the reader to read between the lines, calibrate tone, or sit with bad news. Email strips emotional context. Use a call, or if you are in the same office, walk over.
• Fast back-and-forth. If the topic will need more than two or three exchanges, you are recreating a slow, badly-formatted instant-messaging session over email. Use Slack, Teams, or WhatsApp instead.
• Sensitive feedback. Performance issues, interpersonal conflicts, anything career-affecting. Email creates a permanent record at exactly the moment you want a private, deletable conversation.
• Complex multi-decision discussions. If the email has more than three decisions in it, you are going to get a partial reply, and you will spend two more rounds chasing the un-answered bits. Move it to a meeting with an agenda — and if you find yourself avoiding that meeting because speaking up there feels harder than typing, speaking confidently in meetings is its own skill worth practising.

Here is a simple decision rubric. If the topic is emotional, fast, sensitive, or multi-decision, pick a different channel. Email is for asynchronous, single-decision, low-emotion communication. That is a wide enough use case to cover most of work — but not all of it.

The cost of a misfired email is high precisely because it is permanent. The reply you regret will sit in someone’s inbox for years. A two-minute conversation often saves a two-hour clean-up later.

8. A quick-reference cheat sheet

The whole article on a single screen. Save this. Screenshot it. Paste it above your desk.

📋 Professional email checklist

Before you write

• ☐ Is email the right channel? (See section 7.)
• ☐ Do I know the recipient’s correct name and title?
• ☐ Is there an attachment I need? Add it now, before you forget.

Subject line

• ☐ Under 50 characters
• ☐ Previews the ask, not just the topic
• ☐ No “Hi”, “Update”, or “Quick question”

Salutation

• ☐ Matches the relationship and the register
• ☐ First and last name correctly spelled
• ☐ Title used where appropriate (Dr, Professor, Mr, Ms)

Body

• ☐ Opening line (one sentence of context)
• ☐ Ask in the first 30 words of the body
• ☐ Action items bulleted if more than one
• ☐ Deadlines specific (date, not “soon”)

Sign-off

• ☐ Matches the opening register
• ☐ Full signature (name, role, organisation, contact)

Final pass

• ☐ Re-read for tone — would you be comfortable if it were forwarded?
• ☐ Recipients correct (To / CC / BCC)
• ☐ Attachment actually attached

---

Wrapping up

Most professional email skill is not about better grammar or fancier vocabulary. It is about getting the structural moves right — the subject line that previews the ask, the salutation that matches the relationship, the body that puts the ask first, the sign-off that closes at the right register, and the channel choice that decides whether to write the email at all.

Pick one rule from this article and apply it to your next ten work emails. Just one. Maybe it is the ask in the first 30 words rule. Maybe it is the match the sign-off to the opening rule. Setting that kind of small, concrete goal is how habits actually shift. The compounding effect over a year of work emails is what separates the writers who get taken seriously from the ones who do not. Do try it out — your inbox, and your boss, will notice the difference.

Hero and in-body images by Khwanchai Phanthong via Pexels.