Someone asked me about this last week and I gave a quick answer, but it kept nagging at me, the short version left out most of what actually matters. So here’s the fuller one.
First, do you even need one?
Before writing a single line, it’s worth checking whether a proposal is part of your application at all. Taught master’s programs which are the standard MSc and MA usually don’t ask for one. The research-based routes like MPhil and MRes, normally do. And for a PhD, there’s really no way around it.
The program page or website is the place to confirm this, and it tends to reward a careful read, because requirements vary more than you’d expect between departments, and sometimes between two supervisors in the same department. Some funded positions arrive with a project already defined, in which case a “proposal” might mean something closer to a short statement of why you fit that specific project. Others hand you a blank page and ask what you’d like to work on. If the page is ambiguous, a short email to the department or the professor usually clears it up, and asking about it reads as diligence rather than confusion.
The point is just not to spend a weekend writing something nobody asked for.
A proposal isn’t a contract
This is the part that took me a while to settle into.
A proposal isn’t a contract. My own research shifted quite a bit from what I originally wrote, and that’s completely normal. What the committee is looking for isn’t accuracy. They want to see whether you can take something broad that interests you and narrow it into a question that can actually be answered.
Once that clicks, the writing gets easier, because you stop trying to sound certain about things you can’t be certain about yet.
The structure
Most proposals follow a similar shape. Every section is quietly circling the same thing: the problem you want to solve. It helps to read it that way, as one argument building toward a point and then answering it, rather than eight separate boxes to fill.
1. Abstract. A short summary of the whole thing. Easiest to write last, once you actually know what you’ve said.
2. Introduction. The background of your topic and why it’s worth caring about. This is the context that sets up the problem, the wider landscape the reader needs before your specific gap will mean anything to them.
3. Literature review. What’s already been done, and, more importantly, what hasn’t. This section isn’t there to prove you’ve read widely for its own sake; it’s there to locate the empty space. The gap you find here becomes your problem, so it’s worth being honest about where the space actually is rather than inventing one.
4. Problem statement. State it plainly. A line or two naming the exact thing that hasn’t been resolved. It’s tempting to hedge here, but this is the one place to be direct everything above has been building toward it, and everything below exists to address it.
5. Main objective. Now turn that problem into a question you can genuinely answer. Try narrowing it until it feels almost uncomfortably small, that’s usually the moment it stops being a broad topic and becomes a real research question. Two or three sub-objectives can sit underneath it, breaking the main aim into steps. As a rough feel for the difference: “how materials fail under stress” is a topic; “why a particular kind of crack spreads faster than existing models predict, under these conditions” is closer to a question. Yours doesn’t need to be in mathematical physics, the move is the same in any field.
6. Methodology. How you plan to answer it. Experiments, modelling, simulation, analysis, fieldwork, whatever the work calls for. You don’t need every detail nailed down, just a realistic path from the question to an answer, enough that someone reading it can see it’s actually doable.
7. Work plan. A rough timeline of how the work spreads across the years, reading and background early on, the main study in the middle, writing toward the end. Nobody expects the dates to hold. They mostly want to see you’ve thought about whether the whole thing fits in the time you’ll have.
8. Expected outcomes. What you think you might find, and what would change if you’re right.
A few things that might help
Read the professor’s recent papers before you start. Your proposal doesn’t need to echo their work, but it should feel like it belongs in the same conversation, like something they’d be interested to supervise rather than something arriving from a completely different world.
Check that the work could actually happen where you’re applying. A question can be perfectly good on paper and still not fit the lab, the equipment, or the group’s focus. Proposing something that lines up with what’s genuinely feasible there tends to land better than proposing something dazzling that nobody in that department is set up to support.
Keep it to two or three pages unless they ask for more. Shorter proposals are often the stronger ones, mostly because narrowing down is harder than piling on, and a tight proposal quietly shows you’ve already done that harder thing.
One last thought
If the proposal feels difficult to write, that’s completely normal, and probably a good sign rather than a bad one. Turning a wide interest into a single clear question is genuinely hard. It’s also the exact skill you’ll be leaning on for the whole PhD, so the struggle now is really just the first rep of the thing you’re signing up to do.