Menu Menu
Research & citation

How to Write a Research Proposal: Seven Sections, a Realistic Timeline and the Questions Your Reader Will Ask

In short

  • A proposal argues two things: that a question is worth answering, and that you can answer it with the time and means you have.
  • Most proposals follow the same seven sections: title, introduction, literature review, research questions, methods, timeline and references.
  • Write one main research question and two or three sub-questions; each one should point to a method and to a kind of evidence.
  • Plan ethics, access to data and a timeline with slack before you submit; a feasible small project beats an impressive impossible one.

A research proposal is the document you write before the research itself: for a dissertation, a master's or PhD application, a funded project, or a course that wants to see your plan before you start. It is short compared with the work it describes, but it is read closely, because the person reading it has to decide whether your project should go ahead and whether they want to supervise it. This guide explains what a proposal has to prove, walks through the sections most proposals use, and ends with a checklist of the questions a supervisor or reviewer is likely to ask.

What a proposal has to prove

Every proposal, in every discipline, makes two arguments at once. The first is that the question is worth answering: there is a gap, a problem or a debate, and your project would add something to it. The second is that you can answer it: your methods fit the question, you can get the data or sources, and the plan fits the time you have. The USC Libraries guide to research proposals puts it as three questions every proposal must answer: what do you plan to accomplish, why do you want to do it, and how are you going to do it. It adds that a proposal contains every element of a completed study except the findings and their analysis.

Keep both arguments in view. Students often write a strong case for the topic and a vague paragraph on method, or the reverse. A reader who finishes your proposal should be able to say, in one sentence each, what you will find out, why it matters and how you will do it.

Check the brief first

Length and format vary more than students expect. An undergraduate dissertation proposal may be a two-page form; a PhD application may ask for a free-form document with a strict word limit; a funding body will have its own template and headings. Before you write, find out:

  • the word or page limit, and whether references count towards it;
  • whether there is a required template or set of headings;
  • whether a timeline, a budget or an ethics statement is expected;
  • who will read it: your own supervisor, an admissions panel, or reviewers outside your field.

If a template exists, its headings win; the logic below stays the same.

The seven sections most proposals use

SectionWhat it must do
1. TitleName the topic, the population or material, and ideally the approach. A working title is fine.
2. IntroductionSet out the problem, why it matters now, and your main research question.
3. Literature reviewShow what is already known, where scholars disagree, and the gap your project fills.
4. Aims and research questionsState one main question and a few sub-questions, precisely enough to be answered.
5. MethodsExplain how you will answer each question: design, data or sources, analysis, ethics.
6. TimelineShow the stages of the work and that they fit the time available.
7. ReferencesList the works you cite, in the style your department uses.

Introduction: start from the problem, not the topic

"Social media and students" is a topic. A problem is narrower and has a tension in it: universities increasingly use group chats for course communication, but little is known about how this affects students who are not in those chats. Open with the problem in two or three sentences, explain why it matters (to practice, to policy, to a scholarly debate), and end the introduction with your main research question. The reader should know what you are asking before they reach the literature review.

Literature review: build the case for the gap

In a proposal, the literature review is not a summary of everything you have read. It is an argument that leads to your question. Organise it by themes or debates rather than by author, and end each part with what remains unknown. Three moves work well: what is established, where the evidence is thin or contested, and how your project responds. Cite the foundational works in your area as well as recent studies. Our guide to writing a literature review covers the synthesis techniques in detail, and the guide to finding scholarly sources explains how to search databases systematically, which you will need to describe if your method includes a review.

Research questions you can actually answer

Good research questions are specific, answerable with evidence you can obtain, and tied to a method. Compare:

Too broad: How does social media affect students?

Answerable: How do first-year undergraduates in one department use course group chats, and do students who are not members report missing course information?

Sub-questions: (1) What kinds of information circulate in course group chats? (2) Which students are absent from them, and why? (3) How do staff currently communicate the same information?

Each sub-question should point to evidence: messages or announcements you can analyse, a survey, interviews. If you cannot name the evidence that would answer a question, rewrite the question. One main question with two or three sub-questions is enough for most student projects; a list of eight questions is a sign that the project is not yet focused.

Methods: match each question to a way of answering it

The methods section is where proposals are most often judged weak, because students describe a method in general terms instead of explaining what they will actually do. Cover:

  • Design. Survey, interviews, experiment, case study, archival or textual analysis, secondary data, systematic review. Say why this design suits your question better than the alternatives.
  • Data or sources. Who or what, how many, and how you will get access. If you depend on an organisation's permission or on a dataset, say whether you already have it.
  • Analysis. How you will move from raw material to findings: a coding approach for interviews, the tests you will run, the theoretical lens for a text.
  • Scope and limits. Time, place and population. Stating what you will not cover makes the project look more controlled, not less ambitious.

A simple test: could another student carry out roughly the same study from your description?

Ethics and data

If your project involves people, through surveys, interviews, observation or their personal data, it will almost certainly need ethical approval from your university before you collect anything. The proposal should show you have thought about informed consent, anonymity, how data will be stored and who can see it, and any risk to participants or to you. In the UK, the Economic and Social Research Council's Framework for Research Ethics sets out principles that many universities' own procedures follow, including that participation should be voluntary and that participants should be told what the research involves. Your own institution's ethics committee and forms take precedence; find them early, because approval can take weeks.

A timeline with slack in it

Break the project into stages and put realistic dates on each one: reading and finalising the question, ethics approval, data collection, analysis, writing, revision. A table or a simple chart is clearer than a paragraph. Two habits make timelines credible:

  • Put dependencies in order. You cannot interview anyone before ethics approval, and you cannot analyse data you have not collected.
  • Leave slack. Recruitment is slower than planned and archives close. Leave buffer time, and say what you would cut if time ran short.

Our guide to time management for students shows how to work backwards from a deadline, which is exactly how a proposal timeline should be built.

Common reasons proposals are sent back

  • No clear question. The proposal describes an interest, not a question.
  • Too big. A national survey or a comparison of five countries in a one-year master's dissertation.
  • Methods that do not fit. A question about why people act as they do, answered with a multiple-choice survey alone.
  • No access. The project depends on data, archives or participants the student cannot reach.
  • A thin literature review that misses the main studies on the topic.

Final checklist

  1. Can you state your main research question in one sentence?
  2. Does the literature review end in a gap that your question addresses?
  3. Does each research question have a matching method and a named source of evidence?
  4. Have you shown you can get access to the data, sources or participants?
  5. Have you covered consent, anonymity and data storage if people are involved?
  6. Does the timeline include ethics approval, buffer time and a realistic writing period?
  7. Is it within the word limit, in the required template, with references in the right style?

Once the project is done, the same structure will help you write the finished paper's abstract: question, method, findings and implication, with the findings you could only promise here.

Sources

More research & citation guides