How to Email Your TA or Instructor (and Actually Get a Reply)

Every semester, thousands of student emails are composed with care, sent with hope, and read by nobody — not out of cruelty, but because they were unanswerable as written. “Hey, I have a question about the assignment” asks the receiver to do archaeology: which assignment, which part, which student, what specifically? Instructors and teaching assistants answer a surprising volume of email, and they answer the good ones fast. Learning what makes an email good is a transferable, one-afternoon skill that will keep paying off long past graduation.

Why student emails get ignored

Six failure modes account for almost all of it:

• Surveillance-grade subject lines: “Question”, “Urgent”, “Regarding” — the inbox equivalent of a blank envelope.
• No context. The instructor teaches several sections, of possibly several courses; “the assignment” identifies nothing.
• Questions already answered. The announcement page, the outline, the course channel, or the previous email usually contains it — checking first is the difference between a reply and a sigh.
• Buried asks and buried answers. A question mark on line 14 of a diary entry gets missed; a specific ask in paragraph one gets answered.
• The wrong channel. Grade disputes and personal circumstances rarely belong in a cold email; most courses have a proper process and prefer you start there.
• The wall of text at the wrong hour. Three screens of distress sent at 2 a.m. about a deadline that evening. Send shorter, send earlier.

The five-part structure

The reliable format is small:

1. Subject line with coordinates: [Course code] — [specific topic]. Your course code plus “re-marking request for Quiz 3” or “extension request for Assignment 2” tells the reader everything before the click.
2. One-line greeting using the correct title and name. Precision here is free and noticed.
3. Context in one or two sentences. Who you are (name, section or roll number if customary) and what the situation is. Not your whole semester: a single paragraph setting.
4. The specific ask, as an actual question: “Could we meet in office hours Thursday about the recursion error in Question 3?” or “Could you clarify whether the report references count toward the word limit?” One email, one ask, in bold if your style permits.
5. Sign-off with logistics: name, identifier, and any helpful specifics (file already attached, demo link, what you have tried). If it's an extension request, include the constraint honestly and early — “the demo is Thursday and I need ten more days for X reason” — so the answer isn't a second round of emails.

That is a five-minute email. It reads well, takes less of everyone's time, and — this is the part nobody mentions — round-tripping less means you get answers while they still matter.

Timing rules that do the quiet work

• Check three places before sending: the outline, the announcement feed, the last email you received. Most “ignored” questions were already answered in one of them.
• Ask about policy as policy, and specifics in the right venue. General questions work fine by email; grade discussions and academic circumstances often have a designated process — find it, use it, and let email do the scheduling around it.
• Give it two working days before following up, and when you do, reply in the same thread with a short addition: “following up in case this got buried — happy to ask in office hours instead.” Not a fresh email, not a countdown timer.
• Ask early. The same email sent four days before a deadline gets a helpful answer; sent four hours before, it gets a rule citation and a sigh. Emergency is a time, not a topic.

A skeleton you can adapt

Subject: CS-201 — extension request for Assignment 2

Dear Dr. [Name],

I'm [Name], from the Tuesday section. I've been unwell since Sunday and I'm behind on Assignment 2.

I've completed the implementation and the first two report sections; I would like to request a three-day extension so the testing section reflects the final code. If an extension isn't possible, could you tell me the minimum acceptable submission so I can prioritise?

Thank you, [Name] — [ID], [section]

Note the texture: specific, early, respectful of the reader's decision, and it offers the fallback. Even a declined request gets a useful answer from this email.

FAQ

How long should I wait before following up?

Two working days is a fair baseline for coursework email; one week outside term time. When following up, bump the same thread — a new email chain restarts every context cue the reader had.

Can I ask about grades by email?

You can ask for a conversation about a grade by email — “could we go over the feedback on Question 4?” — and that is usually welcome. Written arguments about marks, sent before reading the feedback carefully, rarely land well; most systems would rather discuss it. Start with the returned paper, form specific questions, then pick the venue the course actually designates.

What about group emails to staff?

One sender, one voice: pick an owner, draft together, send once. Four separate emails asking the same question from the same team reads as chaos, and chaos gets deprioritised — for exactly as long as it takes your group to notice.

The takeaway

An email that gets answered has coordinates in the subject, one paragraph of context, one precise ask, and timing that respects everyone's clock. It is five minutes of writing, and it demonstrates the single most underrated professional skill you own: making the other person's job easy. If your next ask is an evaluation or viva slot, pair this with the evaluation preparation guide, and if the email is about group-work logistics, the group project guide has the coordination layer covered.