Thesis proposal structure, with an annotated example

What a proposal needs to prove

Many students treat the proposal as a short essay about the topic. That makes the work feel easier at first, but it creates trouble later. A good proposal should help your supervisor see whether the project is focused enough, academically grounded enough, and feasible within the time and data you have.

The proposal does not have to contain the final answer. It should show that you know what question you are trying to answer, why that question matters, which literature will guide the work, and how you expect to collect or analyse evidence. Where decisions are not final, name them clearly. Uncertainty is acceptable when it is visible.

The core proposal sections

Working title

A working title should include the main topic and, if possible, the key relationship or context. It can change later. Its job is to make the project recognisable in one line.

Background and problem

The background explains the area. The problem explains the tension. Avoid writing only that a topic is "important". Say what is unknown, inconsistent, under-studied, or practically difficult. This is the reason the project deserves attention.

Research question and objectives

The question should follow from the problem. Objectives can break the question into smaller jobs, such as defining constructs, comparing groups, testing a relationship, or interpreting participant experiences.

Preliminary literature and framework

You do not need a full literature review yet, but you should identify the theories, constructs, or debates that will organise it. This prevents the proposal from becoming only personal interest or business intuition.

Method and feasibility

Explain the likely design, data source, sample, recruitment path, measures or materials, and analysis direction. Feasibility matters. A smaller project with available data is usually stronger than an impressive project that cannot be completed.

How to use the proposal before a supervisor meeting

A proposal is most useful when it creates a better conversation. Before the meeting, mark the parts you trust and the parts that are still uncertain. For example, you might be confident about the topic and problem but unsure about sample size, access to respondents, or which theory should organise the literature review. Put those uncertainties in a short list instead of hiding them in the prose.

Bring specific questions. "Is my topic good?" is difficult to answer because it is too broad. Better questions are: "Does this research question match the problem statement?", "Is a survey defensible for this relationship?", or "Would narrowing the population make the project stronger?" Specific questions help your supervisor give usable feedback and help you revise the proposal without rewriting every section blindly.

After the meeting, update the proposal quickly while the advice is still fresh. Record what changed, what stayed open, and which decision affects the next stage. A small update now prevents a much larger mismatch when you start the literature review or methodology.

Proposal review checklist

• The title and research question point to the same project.
• The problem is more specific than "this topic is important".
• The proposal names the core concepts or variables.
• The method can realistically answer the question.
• The data source or recruitment route is plausible.
• Open supervisor questions are listed plainly.
• The proposal does not promise findings before the study is done.

Common mistakes

One common mistake is writing the literature section as a list of famous authors. The proposal should instead explain why those sources are relevant to the question. Another mistake is describing the method in vague phrases such as "a survey will be conducted" without saying who will answer it, what it will measure, or why a survey fits the problem.

A third mistake is hiding risk. If you do not yet know whether you can access a dataset, recruit enough participants, or use a particular statistical test, say so. A good proposal can include open decisions. A weak proposal pretends those decisions are solved and then collapses later when the work becomes concrete.