A research statement is the document in a PhD application where you explain what you want to study, why it matters, and why you are prepared to study it. Admissions committees read it to judge whether your interests are focused, whether your experience supports them, and whether your plans fit the programme and the supervisors available. A strong statement answers those questions directly, in your own voice, without exaggeration.
Many applicants write either a life story or a technical proposal, and neither works on its own. A life story does not show a researchable question, and a technical proposal without personal context does not show why you are the person to pursue it. This guide explains how to combine the two: a clear question, evidence of preparation, a realistic plan, and an honest account of fit.
Committees read research statements comparatively, often under time pressure, and they look for four things. First, a question that is specific enough to be researchable and broad enough to sustain several years of work. Second, evidence that you have already begun to develop the skills the question requires, through coursework, projects, employment, or independent study. Third, a plausible fit with the programme: supervisors, groups, facilities, or strengths that match your direction. Fourth, judgement: an awareness of what is known, what is uncertain, and what your proposed work would add.
They also read for warning signs. A statement that names no question, or names one so broad that no thesis could answer it, suggests unfocused interests. A statement that claims expertise the rest of the application does not support invites scepticism. A statement addressed identically to every programme suggests the applicant has not researched any of them. Avoiding these faults matters as much as any positive quality, because committees remember the statements that made their job easy and those that made it hard.
Before drafting, study each programme you apply to as if you were choosing a supervisor, because you are. Read faculty profiles and recent publications, note the groups and facilities relevant to your question, and understand the programme's structure: coursework, examinations, teaching duties, and expected timelines. A statement that names a supervisor and explains, in specific terms, why their work connects with your question reads very differently from one that praises a department in general language.
Contact potential supervisors where the programme encourages it, with a brief, specific message: your question, your relevant experience, and a question about fit or availability. Some programmes expect this contact; others prefer that you apply first, so follow each programme's stated guidance. Even when contact is not expected, the research you do for it will make your statement concrete, and it may save you from applying to a programme where no suitable supervisor is available.
A reliable structure has four parts. Open with your research question and why it matters, in two or three sentences that a reader outside your subfield can follow. Avoid opening with childhood anecdotes or general claims about passion; committees value focus over narrative, and your opening sentences set the tone for everything that follows.
Then present your preparation: the experience, skills, and knowledge that qualify you to pursue this question, with concrete examples rather than lists of qualities. Follow with your proposed plan: the approaches you would use, the stages of the work, and the questions each stage would answer, stated as intentions rather than promises. Close with fit: why this programme, these supervisors, and these facilities are the right place for this work, and what you would contribute to the research community there.
A good PhD question sits between two failures: too broad to answer and too narrow to matter. A question such as how to improve animal health could fill a library but not a thesis, while a question about one measurement in one setting may not justify years of work. Aim for a question that names a problem, a population or system, and an approach, and that can generate several related studies rather than a single experiment.
Test your question by asking what would count as an answer, what methods could produce it, and what would change if you found it. If you cannot answer those questions, the question needs narrowing or reframing, and it is better to discover that before you apply than during your first year. Show this thinking in the statement itself: a sentence explaining why you framed the question as you did demonstrates the judgement committees are looking for.
Committees trust evidence more than adjectives. Instead of writing that you are passionate, hardworking, and detail-oriented, show the work: a dissertation that asked a related question, a project where you learned a method, a job where you handled data, or independent reading that shaped your interests. Name the method, the scale, and the outcome, briefly, and explain what each experience taught you about the research you now propose.
Be honest about gaps. If you lack experience with a method your proposed work requires, say how you plan to acquire it: through programme coursework, training, or collaboration. Committees expect applicants to be learners, not finished researchers, and a candid plan for filling a gap reads more credibly than a claim of expertise that the rest of your application contradicts. What damages an application is not a gap, but a gap the applicant pretends does not exist.
A research plan in an application is a statement of direction, not a contract. Describe the approaches you would take and the order in which you would take them, but frame them as intentions: you propose to begin by, you would then test, and you expect the findings to inform the next stage. This language shows that you understand research is uncertain, and it leaves room for the supervisor's guidance, which is how doctoral work actually develops.
Include a sense of scale and sequence. A plan with two or three stages, each answering a distinct question, reads more plausibly than a list of ten experiments or a single vague aim. Mention ethical or practical considerations where they apply, such as approvals, access to data or participants, or field conditions, briefly and realistically. Committees notice when an applicant has thought about feasibility, because feasibility is where many ambitious proposals fail.
Fit is specific or it is nothing. Name the supervisors whose work connects with your question, cite a recent paper or project of theirs, and explain the connection in a sentence or two. Name the group, laboratory, archive, or facility you would use, and say why it matters for your plan. If the programme has a distinctive strength, such as interdisciplinary supervision or a particular training provision, explain how you would use it.
Avoid generic praise. Sentences such as your world-renowned department would be an honour to join could be sent to any university and therefore persuade none of them. Equally, avoid claiming fit that does not exist: if no supervisor works in your area, applying anyway wastes your time and the committee's. A statement that shows you understand the programme, and have chosen it deliberately, is one of the strongest signals an application can send.
Write in a clear, professional tone, in your own voice. Avoid jargon where plain language serves, but use the technical terms of your field correctly where they are needed; committees read for precision as well as clarity. Avoid grand claims about transforming a field or solving a major problem; doctoral research contributes incrementally, and committees trust applicants who understand that.
Respect the length limit, which is commonly one to two pages, and follow the programme's formatting instructions exactly. A statement that exceeds the limit, or ignores a requested structure, suggests carelessness, however good its content. Proofread carefully, and ask a supervisor, mentor, or experienced colleague to read it before submission: they will notice vague passages, unsupported claims, and errors that you, as the author, will miss.
Most applicants apply to several programmes, and the efficient approach is to write one strong core statement, then adapt its opening, its plan details, and especially its fit section for each programme. The question and the preparation remain largely the same; the fit section must change, because supervisors, groups, and facilities differ. A statement whose fit section is identical for every programme is easy to spot, and it undermines the credibility of the whole application.
Keep a separate version for each programme, labelled clearly, and check before submitting that the right version has gone to the right programme. Sending a statement that names another university's supervisor is a memorable error, and not in a good way. A final checklist per application, covering the programme name, the supervisor names, and the document version, prevents a mistake that no amount of good content can undo.
The most common mistake is vagueness: a statement that discusses an area of interest at length without ever stating a researchable question. A second is a mismatch between the statement and the rest of the application, where claimed experience does not appear in the transcript, CV, or references. A third is excessive length or autobiography, where the applicant's life story crowds out the research itself.
Other mistakes include naming supervisors who have retired, moved, or do not work in the stated area; proposing work that requires facilities the programme does not have; and copying a statement written for another purpose, such as a funding proposal, without adapting it. Each of these is avoidable by the same discipline: research the programme, state a clear question, support it with evidence, and proofread the final version as if it were the only document the committee would read.
Use this checklist on the final version for each programme: the research question is stated early and can sustain a thesis; preparation is shown with concrete evidence; the plan has stages and a sense of feasibility; fit is specific, naming supervisors and facilities; the tone is professional and the claims are honest; the length and format follow the programme's instructions; and the correct version has been sent to the correct programme. If any item fails, revise before submitting.
Finally, remember that a research statement is the start of a conversation, not a finished thesis proposal. Committees expect your plans to develop under supervision, and they judge the statement on its focus, its evidence, and its judgement rather than on whether the plan survives unchanged. Write clearly, choose deliberately, and let the quality of your thinking carry the application. For the wider publication journey, see our guide on how to publish a research paper and our guide on how to write a research introduction.
| Section | Purpose | What committees check |
|---|---|---|
| Question | State what you want to study | Specific, researchable, thesis-sized |
| Preparation | Show relevant experience | Concrete evidence, not adjectives |
| Plan | Outline stages and methods | Feasible sequence, honest about uncertainty |
| Fit | Connect to programme and supervisors | Named people, groups, and facilities |
| Length | Usually one to two pages | Follow each programme's instructions |
These authoritative external resources explain the standards and tools mentioned in this guide:
How long should a research statement be?
Most programmes ask for one to two pages, though the exact limit varies, so follow each programme's instructions precisely. A statement that exceeds the limit suggests carelessness, while one far below it may leave the question, preparation, or fit unclear.
Should I name a supervisor in my statement?
Yes, where the programme allows it. Name supervisors whose work connects with your question, cite a recent paper or project of theirs, and explain the connection specifically. Generic praise of a department persuades nobody, while a specific connection shows deliberate choice.
Can I use the same statement for every programme?
Use one strong core statement, but adapt the fit section for each programme, since supervisors, groups, and facilities differ. Sending an identical statement, or worse one naming another university, undermines the credibility of the whole application.
What makes a good PhD research question?
A good question names a problem, a population or system, and an approach, and it can generate several related studies rather than a single experiment. Test it by asking what would count as an answer, what methods could produce it, and what would change if you found it.
How do I show preparation without exaggerating?
Give concrete evidence: a dissertation, project, job, or independent study, naming the method, the scale, and what you learned. Be honest about gaps and explain how you plan to fill them through coursework, training, or collaboration.
Should my plan be detailed or general?
Give a plan with two or three stages, each answering a distinct question, framed as intentions rather than promises. Committees expect plans to develop under supervision, so they judge focus, evidence, and judgement rather than whether the plan survives unchanged.