Contacting a supervisor

Writing to a potential supervisor can feel like a small message with a great deal riding on it. You may be learning an unfamiliar university system, writing in another language, or trying to understand whether further study is financially possible. Looking for an example is a reasonable response. This series is intended to make the process clearer and help you introduce yourself with confidence and care.

My perspective comes from supervising and teaching in business analytics and computer science. Other disciplines and programs approach recruitment differently. I would like an inquiry to help me understand what you hope to study, what you have learned about the research, and whether there is a sensible next conversation. You do not need an elaborate writing style or a fully formed thesis to begin.

Begin with the program’s process

Before drafting, check whether a supervisor inquiry is part of the application process. Some research programs expect applicants to find a willing supervisor; others assign supervisors later or ask applicants to use a central process. UBC’s research-supervisor guidance explains that these expectations differ even within one university. A direct email is useful when it serves the process the program actually uses.

Read the program page and the faculty member’s own instructions. An advertised project may specify a contact address, documents, or a subject line. Following those directions matters more than finding a clever opening. If the program says not to contact faculty before applying, use the application route it provides. Questions about eligibility or missing documents may belong with the graduate office, while questions about a research direction may belong with a potential supervisor.

Understand what the reader is trying to learn

When I read an inquiry, I am trying to connect the person’s interests and preparation with work that could realistically be supported. Faculty members may be developing grant applications, carrying out projects, publishing, supporting current students, and maintaining partnerships. An email helps when it makes a relevant connection clear enough to discuss. A strong academic record is useful context, but it does not by itself explain why this particular research group is a good place for your next step.

The question is also whether the group can support your development. Your interests, training needs, and working preferences matter. A supervisor’s agenda should give you context for a conversation about fit, rather than a reason to pretend that your goals are identical to theirs. The academic research guide explains how a student’s contribution can connect to a larger project while retaining an educational purpose and room for independence.

Funding is part of that practical fit. It is reasonable to need financial support and to ask about funded opportunities. Read what is already published, then make the remaining question clear. An email does not need to contain every funding detail, but applicants should not feel that discussing affordability is somehow impolite.

A familiar structure is not the problem

Many inquiries follow a recognizable sequence: a subject line, a greeting, an introduction, a degree and intended start date, a reference to the professor’s work, a paragraph about the applicant, a request, and a courteous close. That is a normal way to organize a professional message. “Dear Professor” and “Prospective MSc applicant” can be perfectly useful wording. You do not need to make every sentence unusual to sound sincere.

The difficulty comes when the same message could be sent to almost anyone after changing a name and paper title. A statement that someone’s work “closely aligns” with your interests does not explain the connection on its own. The reader still needs to know what you noticed, why it matters to you, and how your experience or questions relate to it. A real citation followed by broad praise can leave all of those questions unanswered.

Similar wording can come from shared examples, language-learning resources, editing help, or automated writing. The structure alone does not establish who wrote a message or which tool was used. I would focus on the accuracy and substance of the email rather than trying to identify its author from punctuation or a polite greeting. The AI and writing article explains how to get useful support without losing your own reasoning.

Make the research connection visible

A useful connection develops through reading. Begin with a broad interest, examine a particular piece of work, and identify a question or observation you can explain. You might notice a choice of method, an unexpected result, or a limitation that relates to something you have encountered. You are showing how you think about the research, even when your understanding is still developing.

The diagram illustrates a way to move from a topic to a conversation. It is not a ranking of applicants or a prediction of who will receive a reply. You can write a thoughtful email and still encounter a full lab, unavailable funding, or a program that recruits through a different process. Useful preparation helps you ask better questions; it cannot make those constraints disappear.

Aim for clarity, not perfection

Plain language is enough. Introduce yourself briefly, identify what you are applying for, explain one specific connection, and give the reader a manageable next question. Relevant experience can come from coursework, employment, volunteering, or a personal project; describe what you actually did. It is fine to say that you want to learn a method rather than presenting yourself as an expert in it.

Avoid exaggerating your familiarity with a paper, adding achievements you cannot support, or sending the same inquiry repeatedly from different accounts. These choices make the conversation harder to assess and keep track of. There is no need for excessive praise, an account of every course you have taken, or a request for an immediate meeting. Keep the details that help the recipient understand the possible research relationship.

You deserve a respectful process even if your first draft needs work. Seeking language support or asking someone to explain an academic convention is sensible. The aim is an honest message that you could discuss comfortably if the supervisor replies, with enough detail to make the next step clear.

Read the series at your own pace

In Read before you write, start with the program’s instructions and a focused reading of the supervisor’s work. Write a thoughtful email then walks through the parts of a message and a clearly fictional example. Use it to understand the choices behind the writing rather than as a letter to copy.

Use AI without losing your voice discusses editing support, generic wording, accuracy, and the rules that may apply to application materials. Finally, Follow up with care explains what to do after sending, including how to handle silence, a decline, or an invitation to talk. You can move between the articles using the series navigation on every page.

Examples and diagrams are teaching illustrations. Follow the current instructions for the institution, program, and faculty member you are approaching.