Sample Emails to a Professor, Taken Apart Line by Line

Support Center · Select Advisor/ProfessorUpdated November 12, 20268 min read

Asked on the help desk, 2014: “Sample Email to contact professor”

Dear Sir/Madam, I am very interested in your esteemed research. I have attached my CV. Please let me know if there is any position available in your lab.

That email, give or take a few adjectives, landed in our lab inbox several times a week. It was polite. It was grammatical. It went straight to the archive folder, and not because anyone was cruel. It asked the professor to do all the work: open the attachment, guess what the sender studied, figure out whether there was money, and then write a reply that would fit nobody in particular.

A good email does that work for the professor. Below are two full samples, one from a PhD applicant asking about a research assistantship and one from a master’s student asking about funding, each followed by a teardown of why every sentence is there. Copy the structure, not the words. Faculty learn to recognize templates.

Before you type a word

You need to know three things.

First, what the professor is working on now. That means papers from the last two or three years and any grant that started recently. Older work tells you their reputation. New work tells you what they are hiring for.

Second, whether they are likely to have money. A newly started NIH or NSF award is the clearest signal that a lab needs hands. On an NIH record, a project number that begins with 1 is a new award and one that begins with 2 is a competing renewal, per the NIH ExPORTER data dictionary, and the listed project end date includes future years already committed, so you can see how long the money runs. Our grant search exists for exactly this, and the guide on how to contact professors walks through reading award records.

Third, how admission works in that department. In most US PhD programs a committee admits students, not a single professor. Your email cannot get you in. It can get you noticed, and in many lab-based programs it can get a faculty member to flag your file when the committee meets. Write with that goal.

Sample 1: PhD applicant asking about a research assistantship

Subject: Prospective PhD applicant, Fall 2027: soil carbon under drought (your new NSF award)

Dear Professor Alvarez,

I am applying to PhD programs in ecology for Fall 2027 and am writing to ask whether you expect to take a new student into your lab for that cycle.

I read your 2025 paper on drought legacy effects in grassland soil communities, and I saw that your NSF project on microbial carbon use under repeated drought started this fall. The open question in your discussion, whether legacy effects persist through several rewetting cycles, is close to what I worked on as an undergraduate.

At Oregon State I spent two years in Dr. Kim’s lab running incubation experiments on rewetted soils. I designed a 16-week experiment, ran the CO2 flux measurements, and wrote the analysis in R. That work became my senior thesis and a poster at the ESA annual meeting in 2026. I also have basic experience with 16S amplicon data from a summer workshop.

If your lab is recruiting, I would be glad to send my thesis abstract or to talk briefly at a time that suits you. If you are not taking students this year, I would appreciate knowing that too.

Thank you for your time.

Best regards, Maya Chen B.S. Environmental Science, Oregon State University (2026) ORCID: 0000-0000-0000-0000 | CV attached (2 pages)

Teardown, line by line

The subject line does three jobs. It says who you are and for which year, it names your topic, and it names something of theirs. Professors search their inboxes by keyword weeks later, and a subject line naming their grant topic is findable.

“I am applying… and am writing to ask whether you expect to take a new student.” The request sits in the first sentence. No “I hope this email finds you well,” no life story. The reader knows what you want in the time it takes to read one line.

“I read your 2025 paper… and I saw that your NSF project… started this fall.” One recent paper, named accurately, is enough. Three papers in a row looks like a list pasted from Google Scholar. Mentioning the grant tells the professor you understand how students get paid, which already puts you ahead of most of the inbox.

“The open question in your discussion…” This is the sentence that proves you read past the abstract. Discussion sections are where authors admit what they don’t know yet. Get it right: a misread paper is worse than no paper.

“I designed a 16-week experiment, ran the CO2 flux measurements, and wrote the analysis in R.” Verbs that describe actual work, plus numbers. Notice what is missing: “passionate,” “hardworking,” “always been fascinated.” Nobody on a faculty has ever been persuaded by an adjective the applicant chose for themselves.

“I also have basic experience with 16S amplicon data.” Honest scoping. If you oversell a skill, someone will ask you about it on a video call in February.

“If your lab is recruiting, I would be glad to send…” A small, easy next step. Compare it to “please let me know if any position is available,” which asks for a description of their whole funding situation.

“If you are not taking students this year, I would appreciate knowing that too.” This line gives permission to say no. In our experience it makes a reply more likely, because “No, sorry, not this year, good luck” now takes ten seconds to write, and a no is useful information for you.

The signature carries your degree, school, year, and one identifier or link. An ORCID or Google Scholar profile works if you have output. ORCID calls its iD a unique, persistent identifier, free of charge to researchers, so there is no reason not to register one before you start writing. Replace the placeholder in the sample with your own. A personal site works if it is current.

Sample 2: master’s student asking about funding

Master’s funding works differently. Many US master’s programs, especially professional ones, admit students without any funding at all. Support, where it exists, usually comes from department TA lines or from an RA position paid by a specific professor’s grant. So the email has to be honest about what you are asking for.

Subject: Admitted MS student, Civil Engineering, Fall 2027: RA openings on your bridge monitoring project?

Dear Dr. Okafor,

I have been admitted to the MS program in Civil Engineering at [University] for Fall 2027, and I am writing to ask whether your structural health monitoring group expects to hire a master’s student as a research assistant this year.

I saw in NSF Award Search that your project on sensor networks for aging steel bridges began in September 2026. My undergraduate capstone involved installing accelerometers on a pedestrian bridge and processing the vibration data in Python to estimate modal frequencies. A one-page summary of that project is attached.

I understand that RA positions for master’s students are limited, and I plan to complete the thesis track either way. If you have an opening, or if you could point me to the department’s TA application process, I would be grateful.

Thank you for considering this.

Sincerely, Arjun Rao B.Tech. Civil Engineering, [University] (2026) github.com/arjunrao (capstone code and data)

Teardown

“I have been admitted.” Your admission status changes the conversation. Before admission, many professors cannot promise anything. After, you are a known quantity with a student ID on the way. If you have not been admitted yet, say “I am applying” and ask whether the group has supported master’s students in the past. That question is lighter and easier to answer.

“I saw in NSF Award Search that your project… began in September 2026.” This is the follow-the-money logic in one sentence. If the record turns out to be a CAREER award, you have found an early-career professor with a minimum of $400,000 over five years, and a lab that is likely still building its team. It also tells the professor you know the hiring window, since a project that started recently is the one with unspent personnel budget.

“I understand that RA positions for master’s students are limited.” This sentence lowers the pressure. It signals that you are realistic and that a no will not produce three more emails.

“Or if you could point me to the department’s TA application process.” A fallback that any faculty member can answer in one line. If you are unsure how teaching, research, and graduate assistantships differ in duties and pay, read what TA, RA and GA positions involve before you ask.

Subject lines that get opened

Keep it short enough to read on a phone screen without truncation. Never write “urgent.” Your deadline is not their emergency.

When to send, and when to follow up

For US PhD programs with December and January deadlines, the best window is September through early November of the year before you start. Faculty know by then whether a grant came through and whether they can afford a student. Avoid finals week, and if the professor is NIH-funded, avoid the days just before the standard submission dates: February 5, June 5, and October 5 for new R01 applications, and a month later for resubmissions and renewals.

Follow up once, after ten to fourteen days, as a reply in the same thread so the original is right there. Three sentences is plenty: you wrote on a date, you remain interested, and you understand they are busy. If another two or three weeks pass with no answer, stop. Move that professor to your “apply anyway, mention in statement” list.

Writing to US faculty when English is your second language

Many of the strongest emails we received came from international applicants, and so did many of the weakest, for the same reason: register. Formal phrases carried over from other languages, such as “Respected Sir,” “your esteemed lab,” or “kindly do the needful,” read to US faculty as signs of a mass mailing, even when the sender wrote every word personally. The fix is mostly structural, not grammatical. Put the request in the first sentence, give each paragraph one job, keep paragraphs to three or four sentences, and prefer plain verbs to ornate ones. If you want a worked model of that layout, this explanation of how to structure a professional email when English is not your first language follows the same request-first, short-paragraph pattern that reads well in a professor’s inbox. Then have a fluent friend read your draft aloud, and rewrite anything they stumble on.

Mistakes that sink otherwise good emails

• Mail-merge leftovers. The wrong professor’s name, or the previous university’s name in paragraph two. Read every email aloud before sending.
• Five attachments. One PDF at most. Transcripts and writing samples can wait until someone asks.
• Length. Past about 250 words, cut.
• Asking what they research. Their lab page answers that. Asking signals you did not look.
• Asking for a guarantee of admission. They cannot give one, and the question makes you look unfamiliar with how committees work.

And never send the same email to two professors in the same department on the same day. They share a hallway, and sometimes they forward your message to each other with a one-word note: “Yours?”