How to Write a Professional Email: A Guide for Freshers

A professional email has five parts, in a fixed order, and most of what goes wrong in a fresher’s inbox is one of those five parts missing. This isn’t about sounding more formal. It’s about a placement officer, faculty member, or recruiter being able to read your email once and know exactly what you’re asking for.

Email is the one placement skill nobody actually teaches. Colleges run mock interviews and group discussion practice, but the email that gets you to the interview, that follows up after it, and that confirms your joining date rarely gets the same attention. This guide covers the structure, the templates, and the mistakes worth fixing before you send the next one.

The Five Parts of a Professional Email

Every professional email has the same five components, whether it’s three lines or fifteen.

• Subject line: states the topic and, where useful, your name or ID. The recipient should know what the email is about before opening it.
• Greeting: addresses the recipient by name when you know it, or by role when you don’t.
• Body: states the purpose in the first one or two sentences, then gives only the context needed to act on it.
• Closing line: a short sign-off sentence like “Thank you for your time” or “Please let me know if you need anything else,” not a repeat of the whole request.
• Signature block: your full name, course and year (for a student email) or role (for a professional one), and a phone number if you’re expecting a call back.

Skip any one of these and the email reads as incomplete even if the sentences inside it are grammatically fine. A missing subject line means your email competes for attention with a blank preview. A missing signature block means the recipient has to scroll back up to find out who’s writing and from which department.

The order matters as much as the presence. Put the ask before the backstory. A TPO or recruiter reading on a phone between other tasks decides in the first line whether your email needs a reply now, later, or not at all.

Subject Lines That Don’t Get Skipped

A subject line has one job: let the recipient sort your email correctly without opening it. Two rules cover most of it.

Say what you want, not what happened. “Regarding my placement” describes a topic; “Requesting Interview Reschedule - 3rd CSE” describes an action. Recipients scanning a full inbox act on the second kind faster because it tells them what to do with the email.

Keep it short enough to survive a mobile inbox. Most phone mail clients cut subject lines off somewhere around 30 to 40 characters, so anything longer risks losing its second half exactly where the useful information usually sits, a formatting constraint Purdue OWL’s email etiquette guide flags as one of the most common reasons a clear email still gets misread. “Interview Confirmation - Priya Raman” survives; “Confirming my availability for the technical interview scheduled next week” doesn’t.

• Weak: “Doubt” / “Important” / “Regarding college”
• Better: “Doubt on Assignment 3 Submission Format”
• Better: “Interview Availability - Arjun Nair, 4th ECE”
• Better: “Follow-up: Backend Developer Role - Applied Aug 12”

Never leave the subject line blank and never reuse the same subject across an entire email thread once the topic has moved on. If a conversation about an internship interview turns into a conversation about joining paperwork, start a new subject line rather than replying seven times under “Internship Interview.”

Three Templates You’ll Actually Use

Most fresher emails fall into one of three categories. These aren’t scripts to copy word for word; they’re structures to adapt.

Emailing your TPO or placement cell:

• Subject: [Request Type] - [Your Name], [Branch/Year]
• Greeting: Dear Ma'am/Sir, or the TPO’s name if you know it
• Body, line 1: state the request directly (“I would like to request a change in my interview slot for [Company] scheduled on [date].”)
• Body, line 2: give the specific reason and any relevant reference (roll number, registration ID, prior email thread)
• Closing: “Thank you for considering this. Please let me know if any additional information is needed.”
• Signature: full name, branch, year, roll number, phone number

Emailing a faculty member:

• Subject: [Course/Project] - [Specific Ask] - [Your Name]
• Greeting: Dear Professor [Name],
• Body, line 1: name the course or project and what you need (an extension, a signature, feedback on a draft)
• Body, line 2: one line of context, only if it changes the answer
• Closing: “Thank you for your time” or “I appreciate your guidance on this.”
• Signature: full name, class/section, roll number

Following up with a recruiter after an interview:

• Subject: Thank You - [Role Title] Interview - [Your Name]
• Greeting: Dear [Interviewer's Name],
• Body, line 1: thank them for the interview and reference one specific thing discussed, so it doesn’t read as a template
• Body, line 2: restate your interest in the role in one sentence
• Closing: “Please let me know if you need any further information from my end.”
• Signature: full name, phone number, LinkedIn (if applicable)

If the first email you’d send to a recruiter feels like a cold introduction rather than a follow-up, the same “state your ask, then your evidence” order used in introducing yourself in an interview works here too: lead with who you are and why you’re writing, then support it.

Mistakes That Make an Email Look Unready

None of these are about English fluency. British Council’s guide to workplace email makes the same point for non-native speakers writing in English at work: tone and structure matter more than idiom. They’re about attention to a handful of details a reader notices in the first five seconds.

• No subject line, or a one-word one. “Hi” or a blank subject forces the recipient to open the email just to find out what it’s about.
• A personal email address that doesn’t match your name. A recruiter reading [email protected] on a resume forms an impression before reading a single line of the email body.
• A wall of text with no line breaks. Three sentences of context before the actual request buries the ask. Put the request first; the reader can ask for context if they need it.
• Attachments referenced but not attached, or attached with an unclear filename. resume(3)final_USE THIS.pdf reads as careless. FirstName_LastName_Resume.pdf doesn’t.
• Ending without a name. An email that trails off after the last sentence, with no signature, leaves the recipient checking the sender address to figure out who wrote it.
• Copying the same email to five people with no explanation of who needs to do what. If three of the five only need to be informed, say so, or move them to BCC.

Fixing these is mechanical, not a matter of talent. A five-minute read-through before hitting send catches most of them, and it’s the same habit that improves every other written and spoken interaction in placement season, from group discussions to the written test instructions you’re expected to follow exactly. The broader plan for building that habit across formats sits in FACE Prep’s communication skills guide.

Before and After: Rewriting a Weak Email

Here’s the same request, written twice. The first version is common; the second version gets a faster, clearer response.

Before:

• Subject: (blank)
• Body: “hello sir i wanted to ask about the interview date because i am not sure when it is and also i have another exam that day so please tell me what to do thank you”
• Signature: (none)

After:

• Subject: “Interview Reschedule Request - Sanjay Kumar, 3rd IT”
• Greeting: “Dear Sir,”
• Body: “I have an interview scheduled for [date] which clashes with my [Subject] end-semester exam on the same day. Could I request an alternate slot, or should I proceed with the exam and contact the recruiter separately?”
• Closing: “Thank you for your help with this.”
• Signature: “Sanjay Kumar, 3rd Year IT, Roll No. 21IT045, +91-XXXXXXXXXX”

The second version answers three questions in the first read: who is writing, what they need, and what the options are. The first version answers none of them without a follow-up question from the recipient, which is exactly the delay a placement week doesn’t have room for.

Follow-Ups, Replies, and When to CC Someone

Getting the first email right solves half the problem. The other half is what happens after you hit send.

Wait before following up. A week is a reasonable default unless the sender gave you a specific timeline (“we’ll get back to you by Friday”). Following up after a day reads as impatience; following up after three weeks reads as having moved on. One follow-up email, politely worded, restating your interest, is normal. A second and third in the same week isn’t.

Reply, don’t restart. If a thread already exists about an interview or an internship, reply within it instead of sending a fresh email with a new subject line. The recipient loses the context you built in the first email, and now has two threads to track instead of one.

Use CC and BCC with intent. CC someone only if they need to see the exchange to act on it later, such as a TPO who needs visibility into an internship offer thread. BCC is for genuinely one-way updates, like sharing your placement result with extended family, where recipients don’t need to see each other’s addresses. Neither is a default; both are a decision.

None of this replaces the spoken half of placement communication. A well-written follow-up email gets you the interview slot. What happens once you’re in the room is a separate skill, covered in how to speak confidently in interviews and placement rounds. Email is the first impression you make before anyone hears your voice, so it’s worth getting the five parts right before you need the sixth: the interview itself. For the wider transition this sits inside, from your first placement email to your first day at a desk, the journey from campus to corporate picks up where this article leaves off.