When and How to Contact a Potential PhD Supervisor

Contacting a potential PhD supervisor can be useful, but it is not a required ritual for every doctorate. In some routes, a supervisor is named on a live project and the vacancy tells applicants to contact that person. In other routes, a central doctoral programme handles applications and asks applicants not to approach individual academics before applying. A fellowship may need a host conversation, while a funded project may already have a defined supervisor and a formal selection process. The page that advertises the route decides what contact means.

The best message is therefore not the longest message or the most flattering one. It is a short, informed question that fits the route and gives the recipient enough context to decide whether a reply is useful. Before you write, check the current project or programme page, the department or research-group page, the university contact instructions, and the formal application route. If those pages say that contact is unnecessary or should not happen, respect that instruction.

This guide is for pre-application contact about a STEM PhD or a related research-training route. It explains when contact can help, when it is better not to write, how to research before sending a message, what a useful question looks like, and how to follow up without creating pressure. It does not promise a reply, admission, funding, or supervision. A positive response can mean only that an academic has answered one question. It cannot replace an eligibility check, an application portal, a funding decision, or a government process.

The short answer: let the route decide, then send one useful question

Start with the current opportunity or programme page. Look for instructions such as “contact the supervisor”, “contact the principal investigator”, “identify a supervisor”, “you do not need to contact a supervisor before applying”, or “applications are accepted only through the portal”. These words are more important than general advice on social media or in an old blog post.

If the page invites contact, write only after you understand the project or research route. Name the opportunity, show one relevant connection to the work, and ask one factual question that is not already answered on the page. Keep the message short enough to read on a phone. Use a clear subject line, a professional greeting, and a simple closing. Attach a document only when the instructions ask for it or the recipient invites it.

If the page does not mention contact, check the programme, department, graduate-school, and application instructions. A central programme may assign supervisors after admission. A project vacancy may list a named contact for questions but not for informal applications. If the route remains unclear, ask the office that owns the application process. Do not assume that silence means you should email every academic in the department.

If the page says not to contact potential supervisors, do not send a speculative message. You can still read the research group's work to decide whether the programme fits, and you can use the formal route to ask an application question. Following the stated process is evidence of care, not a missed opportunity.

The purpose of contact is to resolve a real uncertainty or to establish whether a host conversation is part of the route. It is not to persuade someone to create a place, to obtain a private admission decision, or to make your application skip a queue.

When not to contact a potential supervisor

The easiest way to make contact professional is to know when contact is not appropriate. A message can create extra work for an academic and still fail to help your application if the route does not use informal conversations. Read the instructions before you search for an email address.

Follow an explicit no-contact instruction

Some programmes state that applicants should not contact potential supervisors before submitting. That instruction may reflect how the programme allocates supervision, how applications are reviewed, or how staff time is managed. It may also mean that the programme wants all applicants assessed through the same process. Do not try to find a private address after the page has told you not to write.

If you have an important factual question, send it to the admissions office or the named programme contact. Explain that you read the instruction and ask for clarification through the accepted route. This shows that you are not trying to bypass the process.

Do not use a supervisor message as a substitute for the portal

A reply from an academic does not count as an application unless the official instructions say that it does. If the route requires a central form, a vacancy application, a funding form, or a reference process, complete those steps. Do not send your CV to a supervisor and assume that the university has received it. Do not ask an academic to forward an informal application when the page gives a different submission method.

This matters especially for funded vacancies. A project may name a supervisor because that person leads the research, while the employer or university portal controls recruitment. The supervisor can answer a question about the research, but the portal still controls the application, deadline, required files, and selection process.

Do not write when the call is closed or withdrawn

A closed call is not an open invitation to request a place. If a page says that the position is filled, the deadline has passed, or the funding is no longer available, remove it from your active contact list. A department may advertise a similar project later, but you should wait for a current route rather than asking an academic to reopen a closed process.

You can write to a general office if the page gives a factual reason to do so, such as a problem with an application record or a request for an accessible format. Keep the question tied to that process. Do not turn a closed vacancy into an unsolicited proposal unless the person or programme has clearly invited such conversations.

Do not ask an academic to confirm a rule they do not own

Supervisors can often explain research topics, methods, group work, or a project's academic context. They may not control international admissions, fee assessment, scholarship eligibility, or immigration rules. If your question is about a transcript format, fee category, visa evidence, or funding condition, use the official office or government source named on the page.

It is fine to mention that the answer affects your planning, but do not ask the supervisor to make a decision owned by another organisation. A reply such as “I think the office handles that” is useful only as a direction to the controlling source.

Do not send a mass message when the route asks for a fit check

A mass email usually shows that the recipient has not been selected for a reason connected to their work. It also makes it difficult to ask a question that is specific enough to answer. If you are exploring several groups, keep a private research table and contact only the person whose current work fits the route and whose page permits contact.

You do not need to mention that you have contacted ten other academics. You also do not need to make a broad promise that you would work on any topic. A focused message is more respectful to the person and more useful to you.

Do not contact someone only because an old profile names them

Researcher profiles can remain online after a person changes institution, role, or research focus. ORCID can help you find works and affiliations, and Crossref can help you follow publication metadata, but neither is final proof of a current university role or recruitment status. Check the person's current university, institute, department, or employer page before writing.

If you cannot find a current institutional page, ask the programme office for the correct contact rather than using a personal address found in an old document. A university directory, staff page, or current project page is a stronger starting point than a cached profile.

Do not contact a person who is not connected to the route

The most visible researcher in a field may not supervise the project, teach on the programme, or accept doctoral students. Read the vacancy, group, department, and programme pages to understand the connection. If the route lists a principal investigator, admissions contact, or training network, start with those names and roles.

When a programme uses a panel or a doctoral school, an individual academic may not be able to answer whether you would be admitted. That does not make the person unhelpful. It means you should ask a research question only if the page invites it and send admissions questions to the proper office.

Do not write when you have not read the page

An email asking “Is this funded?”, “What are the requirements?”, or “Are you taking students?” may already be answered in the first paragraph of the current page. Read the page, follow its links, and record what remains unclear. If the page is difficult to understand, ask about one exact sentence or missing link. This is faster for both sides.

Situations where a focused message can help

There are several situations in which contact can add value. They all share one feature: the route leaves a legitimate question that the named person can answer, or it makes a host conversation part of the application.

A named project asks applicants to contact the supervisor

A defined vacancy may name a principal investigator or supervisor and invite questions about the project. In this case, contact can help you understand the research scope, expected methods, available data, or the team's working context. It still does not replace the employer or university application.

Read the instructions closely. “For informal enquiries, contact...” is not the same as “applications should be sent to...”. Use the email for the purpose stated. If the page asks for a formal application through a portal, submit there even if the supervisor replies.

An open-topic route expects a host before application

Some doctoral or fellowship routes ask applicants to identify a host or supervisor before they can submit. The host may need to support a proposal, confirm facilities, or approve the research direction. Here, contact is part of the route itself. The current call or programme instructions control what the host must provide and when.

Do not assume that any academic who works in the broad field can be a host. Check the eligibility of the host, the institution, the research area, and any mobility or partnership rule in the current call. If the route has a host form or template, use it rather than inventing a separate process.

MSCA Postdoctoral Fellowships illustrate a host-led model in which an applicant and a host organisation develop a proposal under the current call conditions. The fellowship page explains the route at a high level, but the current call documents and the host institution's instructions control the application. You still need to confirm that the researcher, host, and proposed route meet the current rules.

The project is clear, but one academic detail is not

Sometimes the opportunity page explains the topic and application route but leaves a narrow question about the research. You might need to know whether the project expects a particular experimental method, whether a named dataset is already available, or whether an applicant's closely related background is relevant to the advertised scope. A supervisor or principal investigator may be the right person to answer that question.

Make the question easy to answer. Quote or paraphrase the relevant line from the page, explain the small point that remains, and ask whether your understanding is correct. Do not ask the person to evaluate your whole career in the first message.

You need to check whether your proposed work fits an open topic

An open-topic programme may invite applicants to propose a research question. A brief contact can help you learn whether your idea sits within the group's active work, available methods, and supervision capacity. It is a fit conversation, not a pre-approval.

Share the idea at a level that can be read quickly. State the problem you want to study, the method or evidence you are considering, and why the person's current work is relevant. Ask whether the direction appears close enough to discuss further under the programme's route. If the person says that the idea is outside the group's work, that answer saves you time.

A formal host conversation is required for an external fellowship

Some fellowships require a host institution, a support letter, or a discussion of the proposed work before submission. Read the call and host guidance before writing. The host may need to confirm supervision, facilities, employment arrangements, training, or institutional approval. Your message should make clear which route you are considering and which stage you are at.

Do not use a generic PhD message for a fellowship host. A fellowship proposal may have a different purpose, assessment form, and timetable. P15, the guide to preparing a postdoctoral application and fellowship host proposal, covers that kind of conversation in more detail.

A programme tells you to identify a supervisor after an initial application

Some routes ask applicants to submit centrally and discuss supervision only after an academic or admissions stage. In that case, do not move the contact earlier just because you have found a name. Keep your research-fit notes and prepare for the formal stage. If the programme provides a contact window, follow it exactly.

The distinction can feel small, but it protects fairness and helps you receive an answer from the correct person. A programme that assigns supervisors after selection may not want individual academics to make informal commitments before the panel has reviewed applications.

Research before writing

A good message usually depends on work the recipient never sees. Your private research should show that you understand the route, the person, and the question. It also gives you a way to decide that writing is unnecessary.

Confirm the current role and connection

Start at the university, institute, or employer website. Confirm the person's current title, department or group, and the route or project connection. If a vacancy names a supervisor, compare the vacancy with the current staff page. If the pages do not match, do not guess. Ask the programme office or use the named contact on the live opportunity page.

An ORCID record can help you locate recent work or an affiliation, and a Crossref record can help you follow a DOI or publication. These tools are discovery aids. ORCID records can contain information added or maintained by different sources, and the current institution page is needed to confirm a person's present role. Crossref metadata describes publication records; it does not show whether someone is accepting students.

Read the opportunity like an applicant

Copy the exact title, host, department, route, deadline or stage, and application method into your notes. Read the eligibility and funding sections even if you plan to ask only a research question. A supervisor cannot repair an application submitted to the wrong route.

Make a two-column note. In the first column, write what the page states. In the second, write what you need to understand. For example:

Do not put a question in the second column if the first page already answers it. If the answer is on another official page, follow the link and add that page to your source record.

Read the group and department pages

The group page can help you understand the research setting, methods, facilities, collaborators, and current projects. The department page can show the wider training environment and the route through which doctoral researchers are admitted. Use these pages to refine your fit note, not to copy a description into the message.

Look for current work that connects to your question. A person may publish in one area while supervising a project in another. A department may have a method facility that is relevant even when no single publication matches your idea. The goal is not to prove that your interests are identical. It is to show why a specific question belongs in a short conversation.

Use publications carefully

Choose one or two recent or clearly relevant works. Read the abstract, methods, and conclusion rather than citing a title alone. Note the problem, data, method, and limit that connect to your proposed question. Do not say that a paper “proves” your project is a fit when it only shares a keyword.

Use the publisher page, journal page, institutional repository, or current research page to verify the publication. Crossref can help confirm metadata, and ORCID can help find a person's works. The final message does not need a long publication list. One accurate connection is stronger than five names copied from a profile.

The Declaration on Research Assessment from DORA is a useful reminder that journal metrics are not a substitute for understanding the work. Do not praise a person by listing impact factors or rankings. Explain the research question or method that matters to your own preparation.

Check methods, facilities, and supervision context

A research fit is more than a topic. Consider whether the group has the methods, data access, facilities, software, field relationships, or training environment your idea would need. This does not mean you must have a complete project design before contacting someone. It means you should avoid asking a group to support work that clearly depends on resources the page does not mention.

If the project is experimental, read the facility or laboratory page where available. If it is computational, look for the stated data or infrastructure. If it involves human participants, read the programme or institution's research guidance if the opportunity links to it. Do not make claims about access or approval unless the official page confirms them.

P18, the guide to assessing research group and supervisor fit, offers a wider framework for this work. For a first message, use only the parts that help you decide whether contact is appropriate and what question you need answered.

Check the contact instruction itself

Write down the address, name, purpose, and any requested format. Some pages give an administrative contact, some give a project leader, and some direct all queries to a central office. A page may also say that only portal messages are monitored or that attachments should not be sent.

If a staff page has several email addresses, use the one connected to the route. Do not send the same message to every address. If the page lists a general address, copy the opportunity title into the subject so the message can be routed.

Make a stop decision before you draft

After your research, ask whether contact will change your next action. If the page answers all of your questions and you can apply through the stated route, you may not need to write. If one permitted, material question remains, a focused message may help. If the route prohibits contact, stop and use the formal channel.

This decision is part of good research practice. Contact is not a measure of seriousness. The right action may be to submit, clarify, monitor, or remove the opportunity from your shortlist.

Choose a useful question

The question is the centre of the message. It should be narrow enough to answer and important enough to justify writing. It should also respect the recipient's role.

Separate public facts from unresolved facts

Create three buckets. The first contains facts the current page already answers. The second contains facts another official page may answer. The third contains a real gap that the named person or office can clarify.

For example, if the page states the deadline and required documents, do not ask the supervisor for those details. If the university admissions page explains language evidence, do not ask the principal investigator to interpret it. If the project says it will use a particular dataset but does not say whether an applicant may propose a related extension, that may be a useful research question for the supervisor.

Ask about scope, not private selection criteria

A supervisor can often explain whether a question is within the project's academic scope. It is not appropriate to ask what score would guarantee selection, which applicant is likely to win, or whether the person can promise you a place. Selection decisions may belong to a panel or employer, and a private opinion cannot replace the published process.

Good scope questions include:

• whether a closely related method is part of the advertised project;
• whether a proposed dataset or study setting is within the project's stated boundary;
• whether the group expects the applicant to extend the question or follow a fixed protocol;
• whether the route permits an initial research conversation before the formal application; or
• whether the named person is the current contact for research questions.

These are examples of question types, not a script. Use the language of the actual page and your actual situation.

Ask one main question

Several small questions can be combined only when they form one decision. “Is this the current project, and should I apply through the portal?” may be reasonable if the page is unclear. A list of ten questions about funding, admission, methods, supervision, immigration, and future jobs is not a first message.

If you need more than one office, divide the work. Send an academic question to the supervisor and an admissions question to the programme office. Write down the answers separately so that one reply is not mistaken for the other.

Make the question answerable without a meeting

The recipient may not have time for a call. Write a question that can receive a short factual reply. If a longer discussion is needed, ask whether a brief conversation is appropriate after the person has seen the context. Do not assume that a request for a meeting is owed to you.

Keep your personal question connected to the route

Explain why the answer matters in one sentence. “I am trying to decide whether to prepare an application for this project” is enough. You do not need to describe every part of your career, family situation, or long-term plan.

If your question is about a possible open-topic proposal, say what you are considering and what evidence or method you would use. Be honest about what is still an idea. Do not present an untested concept as a confirmed project or imply that the supervisor has endorsed it.

Build the message

The message should be easy to scan. A useful structure has a clear subject, a respectful greeting, a route reference, one relevant connection, one question, and a simple next step. The structure matters more than polished vocabulary.

Write a clear subject line

Use the exact project or programme title and the reason for writing. A subject such as “Question about [project title] before application” gives the recipient enough context. If the page gives a reference number, include it. Avoid subjects that promise an outcome, such as “Future PhD student” or “Urgent supervision request”.

Introduce yourself in one or two sentences

State your current degree or role and the programme or opportunity you are considering. If you are completing a degree, say so plainly. Do not list every qualification in the first line. The recipient can open your profile or CV later if the route asks for one.

Show one real connection

Refer to the project, group, method, or publication you actually read. Explain the connection in your own words. A sentence such as “My recent work used microscopy to study...” is more useful than “Your excellent research is very inspiring.” Keep the claim accurate and modest.

If you are referring to a publication, name the topic or method instead of making a claim about its importance. If you are referring to a project, use the wording on the live page and do not add a result or facility that the page does not confirm.

State one question

Ask the unresolved question in direct language. If the answer is on another official page, say that you checked the page and explain what remains unclear. This shows respect for the person's time and makes it possible to answer without a long exchange.

Explain the next step without pressure

Say what you plan to do with the answer: decide whether to apply, prepare a proposal, or use the formal portal. If the route asks for a host discussion, ask whether the person would be open to the stated next step. Do not ask for a commitment to supervise before the programme or call allows one.

Attach only what the route permits

A CV, transcript, or proposal can contain sensitive and time-consuming material. Attach it only when the page requests it or the recipient invites it. If an attachment is useful, name it clearly and make sure it matches the route's format. Do not send a large portfolio, unpublished data, or personal documents to an unsolicited address.

If no attachment is requested, a short message with a link to the official opportunity is enough. The recipient can ask for more information if needed.

Keep tone professional and human

Use the person's title or name as the current page uses it. Avoid overly familiar language, exaggerated praise, or a message that sounds copied. Simple English is fine. You do not need to sound like a native speaker to ask a clear research question.

Write the message once, then remove sentences that do not help the recipient answer. Check the project name, spelling, route, and link. Make sure your question cannot be answered by the first page you opened. Then send it through the channel the route provides.

Message decisions, not copy-paste scripts

The following scenarios show how the message changes with the route. They are decision examples, not ready-to-send endorsements or promises of a reply.

Scenario: an advertised project with a research question

The live vacancy names a project leader and says that applicants may ask project questions by email. The page describes a study using an experimental method. You have related experience with a different but connected method and want to know whether the project expects that method to be learned during the doctorate or requires prior experience.

Your message should name the project, state your relevant experience in one sentence, and ask whether the related method is within the expected preparation. It should also say that you will use the university portal for the application. There is no need to ask whether the person will supervise you or whether you will be selected.

Scenario: a central doctoral programme

The programme page says that applicants apply centrally and that supervisors are discussed after the initial stage. You have found an academic whose publication matches your interest, but the programme does not invite pre-application contact.

Do not write a speculative supervision email. Read the programme's research areas and prepare your fit statement for the formal application. If the application instructions do not explain how research interests are matched, ask the programme office. Your private notes can include the academic's work, but your next external action is the route stated by the programme.

Scenario: an open-topic host route

The current call asks applicants to secure a host and develop a proposal. The host must provide a support statement and the application form asks for a supervision plan. You have identified a group whose methods fit your idea.

Your first message should state the call, the host requirement, the research problem, and the small question you need to resolve before preparing a proposal. Ask whether the person is open to discussing the call and whether the group has the relevant capacity described by the route. Do not send a complete application or ask for a signature before the person has agreed to discuss the fit.

Scenario: a named contact is administrative

The vacancy lists a graduate-school address for all application questions and names an academic in the project description. Your question concerns the acceptable transcript format.

Send the question to the graduate school, not the academic. If you later have a permitted research question, use the academic contact listed by the page. This keeps each answer with the organisation that owns it.

Scenario: a possible but unadvertised idea

You have a research idea connected to a group, but no current vacancy or programme route names a project. You may contact the person only if the group or programme makes open-topic enquiries welcome. Your message should be exploratory and modest. Explain the problem and why the work connects to the group, ask whether the idea is within the group's current scope, and make clear that you are looking for the appropriate formal route.

Do not imply that the person has funding or a vacant place. If the group page says that it does not accept unsolicited proposals, stop there and monitor the formal opportunities page.

Follow-up, no response, and a negative answer

Sending a message is not the end of the work. Decide in advance what you will do if there is no reply, a short reply, or a clear no.

Wait according to the route, not your anxiety

Academic schedules, conferences, fieldwork, teaching, leave, and application periods can affect response time. A page may name a general office or a process for questions. Use that process rather than treating a delay as a signal about your fit.

If the application deadline is close, do not wait for an informal reply when the formal instructions allow you to apply. Submit through the route and keep your message as context. If a reply is required before submission, check whether the page gives a contact window or alternative contact.

Send at most one polite follow-up when contact is allowed

If the page permits direct contact and you have not received an answer, one short follow-up can be reasonable after a sensible interval. Refer to the original message, repeat the single question in a sentence, and say that you will proceed through the formal route. Do not resend the entire message, add new questions, or use several email addresses at once.

If the page says not to follow up or directs questions elsewhere, follow that instruction. If the route is now closed, stop the follow-up. Repeated messages do not create a stronger application and can make the contact burdensome.

Treat no response as information about the route, not your worth

No response may mean that the person is busy, not the correct contact, unable to take students, or not using informal contact for that route. It does not prove that your research is poor or that you are ineligible. Check the current page and decide whether you can continue without an answer.

If the unanswered point is essential, mark the opportunity “clarify” and contact the official office that owns it. If it is only a preference, continue with the formal application or remove the opportunity from your shortlist according to your own decision.

Read a negative answer carefully

A person may say that they are not taking students, that the idea is outside the group's work, or that the programme uses a central process. Thank them, record the reason, and move on. A negative answer is not a judgement on your potential as a researcher. It tells you that this route or person is not the right next step.

Do not argue, ask the person to reconsider, or ask them to recommend someone else unless the reply invites that question. If they direct you to a programme page, follow it. If they say that they are not involved in the advertised opportunity, return to the current source and correct your record.

Keep a contact record

For each message, save the opportunity, contact role, date, route, question, response, and next action. Do not store more personal information than you need. A short record prevents duplicate messages and helps you explain your decision later.

Three contact-route scenarios

The decision flow below helps you place a message in the right route.

Advertised project

The vacancy names the work, host, and supervisor. First, read the application instruction. If it invites project questions, contact the named person with one research question. Submit through the vacancy or university portal. Treat the reply as context, not as selection or admission.

Central programme

The programme owns the application and may assign supervisors later. If it says that applicants should not contact academics, use the programme office for factual questions. Keep your research-fit notes for the application and wait for the stated matching stage.

Host-led fellowship or open-topic call

The call requires a host or a host proposal. Check the call rules, host eligibility, institutional process, and proposal requirements. Contact a suitable host with a short description of the idea and the decision you need to make before drafting. Ask for a conversation only if the route supports one. The current call and institutional process control the next step.

Preserve the formal application route

A supervisor's interest can be encouraging, but it does not change the rules of the opportunity. Keep the formal route visible at every stage.

A reply is not an offer

An academic may say that your idea sounds interesting, that the project is a possible fit, or that they would be happy to discuss it. None of those phrases means that the university has admitted you, that funding is reserved, or that supervision is guaranteed. Use the exact language of the reply in your private record.

If the person says “please apply”, treat that as an invitation to use the formal route. Read the requirements and submit the requested documents. If the person says “we can discuss this”, ask whether the discussion is part of a call or simply an informal conversation. Do not claim a supervisor's support unless the route asks for a formal support statement and the person provides it through the required process.

Keep admission, funding, and immigration questions separate

Use the programme or admissions office for degree, language, document, and portal questions. Use the funder, provider, employer, or fees office for funding and fee questions. Use the government authority for immigration questions. A supervisor can point you to a source, but should not be expected to make a decision owned elsewhere.

This separation is especially important for international applicants. A supervisor may not know the current government evidence rule or the funding treatment for an international fee category. Read the current controlling pages and keep your source notes.

Do not bypass equal application steps

If the route requires an application form, references, a research proposal, or an assessment, complete those steps. Do not ask the supervisor to accept a document privately, to mark an application as received, or to tell a panel to overlook a missing item. If the portal has a technical problem, contact the office listed in the instructions and keep the evidence of the problem.

Keep dates and versions clear

The date of an email is not necessarily the date of the current call. Save the live opportunity page, the application instructions, and any reply that changes your next action. If a page is updated, read the new version before submitting. Do not rely on a screenshot or a cached search result when the route is time-sensitive.

Use a fit check before you invest more time

After contact, revisit the project, group, and route. Did the reply answer the question? Does the opportunity still fit your preparation, funding needs, and timeline? Is there a new condition or a formal host step? A reply can improve your decision, but it may also show that the route is not suitable.

If the route no longer fits, remove it. Your goal is not to collect replies. It is to make good application decisions with evidence you can explain.

Contact Truth Check

Complete this check immediately before you send a message.

If the permission row is unclear, stop and read the programme or contact instructions. If the current-person row is unclear, find the institutional page or use the official route contact. If the question row is empty, you may not need to write. If the formal-step row is empty, do not treat an email as an application.

A message-preparation checklist

Use this checklist to prepare a message without turning it into a mass-email template.

Before writing, save the current opportunity and programme pages, confirm the person's role, and note the one decision you need to make. During writing, use the exact title, introduce yourself briefly, name one relevant piece of preparation, ask one question, and state the formal next step. Before sending, check the recipient, link, spelling, attachment rules, and tone.

After sending, record the date and set a private reminder only if the route allows a follow-up. If the deadline arrives first, use the formal application route. If the answer is negative or absent, update the opportunity record and move to the next evidence-backed choice.

The checklist is intentionally short. A message should open a clear next step, not make the recipient perform your entire opportunity search.

A simple contact-decision flow

Use the following flow each time you find a name and feel pressure to write immediately. It is deliberately slower than opening an email window, because most poor messages begin before the applicant has decided what the message is for.

Begin with the live route. If you cannot identify a current project, programme, fellowship, or open-topic call, there is no clear application context. Save the research lead privately and continue your search. If you can identify the route, read the contact instruction. A clear “do not contact” instruction ends the flow for the individual academic. A clear invitation moves you to the research check. If the page is silent, read the programme and department instructions and use the formal office when the purpose is not clear.

Next, ask whether the person's current institutional page connects them to the route. A similar topic is not enough. The person may be a former group member, an honorary affiliate, or a researcher who is not involved in doctoral recruitment. If the connection cannot be confirmed, look for the named route contact rather than guessing.

Then write the unresolved decision in one sentence. If you cannot complete the sentence, your message is probably too broad. “I need to know whether my proposed use of method X fits the project boundary” is a decision. “I want to know more about your research” is an opening for your own reading, not a useful first question.

After that, check the owner. If the question concerns research scope, a supervisor or principal investigator may be suitable. If it concerns admission, fees, funding eligibility, document format, or immigration, use the office or authority named in the instructions. A person who is willing to help is not automatically the person who can decide.

Finally, decide what you will do with either answer. If a reply will not change your next action, do not send the message. If an answer would decide whether you prepare an application, a proposal, or a host conversation, contact can be justified. Write the formal route beside the question so that an encouraging reply does not replace the action the university or funder requires.

This flow is also useful when you are comparing several opportunities. It keeps “interesting researcher” separate from “permitted contact for a current route”. That distinction protects your time and the recipient's time.

What to learn from a reply

A reply can carry different kinds of information. Read it by category instead of turning every friendly sentence into a commitment.

The first category is route information. The person may direct you to a portal, a programme office, a call document, or a different contact. Save the official link and follow it. This is often the most valuable reply because it puts you on the right path.

The second category is research information. The person may clarify the scope of a project, the expected method, the status of a dataset, or the relationship between a project and a group. Summarise only what the person actually said. If the reply uses words such as “possibly”, “likely”, or “we can discuss”, keep that uncertainty in your record.

The third category is capacity information. An academic may say that they are not taking students, are on leave, have no role in the listed project, or cannot supervise the proposed work. Treat this as a decision about that route, not a general statement about your prospects. The message may also tell you that capacity is reviewed through a panel or programme, in which case you return to the formal process.

The fourth category is a request for more information. If the person asks for a CV, short proposal, or meeting, check whether that request fits the current route. Send only the material needed for the stated purpose. If the route requires a formal host statement or application attachment, use the form or process named by the call. An informal request does not automatically change the official requirements.

If the reply contains a factual claim that conflicts with the live page, ask where the current rule is published. Keep the reply and the page in your record. Do not edit the page in your notes to match a verbal answer. A person may be describing a local practice, an earlier cycle, or a matter outside their role.

When a second question is reasonable

Sometimes the first reply opens one necessary question. A second message can be reasonable when it is short, the route still permits contact, and the answer is needed for the next formal step. Begin by thanking the person and restating the point that was clarified. Then ask the one new question and explain what you will do with the answer.

For example, a supervisor may confirm that a related method is within the project scope but direct you to the graduate school for admission requirements. Your second question should go to the graduate school, not back to the supervisor. Or a host may agree that an open-topic idea fits the group but say that the call requires a specific support document. The next message can ask the host whether they are willing to provide that document under the call, only if the call's process allows the conversation.

Do not use a second message to add an unrelated request, ask for a recommendation, or restart the introduction. If the exchange has become a general discussion, suggest the formal meeting or application step named by the route. If the person does not reply to the second question, stop and use the source or office that controls the decision.

Protect your privacy and the recipient's time

An early email is not the place for a passport scan, full transcript, financial history, medical information, or unpublished research data. A university or funder may later request a document through a secure portal. Use that channel. If a person asks for material that seems unrelated to the route, ask what it will be used for and whether there is an official upload process.

Remember that researchers receive messages in different roles. A principal investigator may be responsible for a project, while an administrative colleague handles the portal. A group leader may be away from day-to-day doctoral recruitment. Use the role and the instructions on the page rather than assuming that the most senior person is the best contact.

Keep your own record private and concise. A table with the opportunity, source, contact role, question, and next action is enough. Do not publish a private reply or quote a person's words publicly without permission. If you use a response to improve your shortlist, preserve its context and do not present it as a general rule for every applicant.

Good contact is a small part of a larger evidence process. It should help you make a clearer decision while leaving the university, funder, and government to make the decisions they own.

Sources and next action

The official sources below support the method in this guide. They describe research-training routes, researcher records, publication metadata, and responsible assessment. They do not decide whether an individual supervisor is available or whether an applicant will be admitted.

• MSCA Doctoral Networks: an official description of doctoral-network structures. A current network project and vacancy control its recruitment and contact instructions.
• MSCA Postdoctoral Fellowships: an official host-led fellowship route. The current call and host institution's instructions control eligibility, proposal, and host steps.
• UKRI doctoral training investment framework: explains the structure of UKRI doctoral training investment and the role of providers and partnerships.
• UKRI statement of expectations for doctoral training: sets out expectations for doctoral training environments. It is not a promise about a particular supervisor or vacancy.
• NIH postdoctoral and residency training: an official example of postdoctoral training and career development. It is not a universal guide to doctoral supervision.
• Directory of Open Access Journals: a discovery and transparency resource for journals. Inclusion does not decide whether a paper, researcher, or group is a fit.
• Crossref metadata enrichment: explains how publication metadata can support discovery. Verify a person's current role and research connection on the institution's page.
• ORCID: getting started: explains researcher records and works. Use ORCID to discover work, not as final proof of a current appointment.
• ORCID: source of record information: explains where information in a record comes from and why source ownership matters.
• DORA declaration: explains why journal metrics should not replace a careful reading of research quality, contribution, or fit.

For a practical next step, read the AcademicWings guides and choose the guide that matches your decision. If you are still finding possible groups or projects, use How to Find PhD Opportunities Through Research Questions, Methods, and Groups. For research environment questions, explore the current STEM fields and the institution's research pages. For entry rules and the formal application, continue to The International Applicant Guide to PhD Entry Requirements and Eligibility and the AcademicWings application guides.