Your emails are the most-read thing you will produce all summer. Seniors experience you substantially as an inbox entry, read on a phone, between meetings, in eleven seconds and the difference between a junior whose emails are a pleasure and one whose emails are work is visible within a week. Nobody teaches the genre. Here it is.
The five rules of the genre
- Answer first. The conclusion in the first line, support underneath. 'Model updated, EPS moves from 1.02 to 1.04, driver is the tax rate; detail below.' Seniors read top-down and stop when satisfied; structure for the stop.
- Subject lines are status lines. 'Project Falcon · model updated · 2 questions' tells the reader everything before opening. 'Quick question' and 'Update' tell them nothing and get opened last, the same law that governs the external cold emails covered in the site's outreach article.
- Questions come numbered, with defaults. Closed questions, numbered, each with a proposed answer: 'Unless you prefer the 20-day average, I will use the one-day premium.' A default converts a request for thought into a request for a yes and seniors answer yeses from taxis.
- Attachments carry their own discipline. Right file, right version, named so a stranger could file it: date, project, document, version. Open the attachment before sending, per mistake four in the intern-mistakes list.
- Brevity is respect. Five lines is a long internal email. If it needs ten, it probably needs a call instead.
The model status email
One email, whole genre · status, questions with defaults, next step
SUBJECT: Project Falcon · CIM section 3 drafted · 2 questions
Hi [Name],
Section 3 is drafted and in the shared folder; numbers tie to the 14 May model. Two questions:
1 · Customer chart: keep the top-10 split or top-20? Default: top-10, matching the teaser.
2 · The 2024 one-off: footnote it or adjust EBITDA? Default: footnote, flag for the call with the client.
Next: I will start section 4 tonight unless you would rather I turn comments on 3 first.
Best, [Name]
Notice the last line: the next step, pre-announced. It closes the loop before it opens and it is the written form of the anticipation habit the first-90-days article describes.
Chasing, cc discipline and tone
Chasing: once, politely, after a genuinely reasonable interval and route the chase to the associate rather than re-pinging the MD; the associate exists partly to be that channel. Cc discipline: your direct associate errs on being included, because surprising your own chain is the sin, not over-informing it; never skip levels without a reason you could say out loud and never use bcc for politics, because bcc games are discovered and remembered. Tone: no exclamation-mark enthusiasm, no emoji upward, no 'just checking in', which is a chase pretending not to be; say what you need. And the thank-you economy runs on brevity: 'Thanks, done' outperforms a paragraph of gratitude every time.
When not to email at all
The genre's final rule is knowing its limits. Anything urgent, anything nuanced, anything already three messages deep: stand up and walk over, or call. The ten-message thread that should have been ninety seconds at a desk is a daily sight on every floor and the junior who breaks the chain by appearing in person reads as someone with judgement about bandwidth, which is the actual skill all of this etiquette is a proxy for. Email fluency feeds directly into how you are discussed at conversion time, per the conversion article, because the written trail is the part of your summer everyone can re-read. If you want your own drafts pressure-tested against the genre before you start, that fits naturally in the IBD Recruiting Review.
FAQ
How should I email an MD as an intern?
Answer first, support underneath, inside five lines. Subject lines that work as status lines, numbered questions with proposed defaults and the next step pre-announced.
How do I chase a senior who has not replied?
Once, politely, after a genuinely reasonable interval, routed through the associate rather than re-pinging the MD.
When should I not use email in banking?
Anything urgent, nuanced, or already three messages deep: walk over or call. Breaking a long thread in person reads as judgement about bandwidth.
