How to Write a Research Proposal: A Practical Walkthrough

A research proposal is not a smaller version of your final paper, and it is not a list of everything you might read. It is a persuasive plan. Before you collect a single piece of data, you are making a case to a supervisor or committee that your question is worth asking and that you have a sensible way to answer it. This guide walks you through the parts of a proposal, shows a worked example, and points out the mistakes that trip up most writers.

What a proposal actually does

Think of a proposal as answering three quiet questions in a reader’s mind:

• What do you want to find out? (your research question)
• Why does it matter, and why hasn’t it been settled already? (the gap)
• How will you find the answer? (your method)

Everything in a strong proposal serves one of those three jobs. If a sentence does not help your reader see the question, the gap, or the method, it is probably decoration. The most common reason a proposal feels weak is that these three pieces drift apart — the question asks one thing, but the method measures something else.

The standard sections

Most proposals, whether for a course paper, a thesis, or a dissertation, follow a recognizable shape. The length of each part changes, but the logic does not.

• Title — specific and informative, not clever. A reader should guess your topic from the title alone.
• Introduction and problem statement — set the context in a few sentences, then narrow to the precise problem you will address.
• Research question or hypothesis — stated plainly, ideally in one sentence.
• Literature review — a focused summary of what is already known, ending in the gap your work will fill.
• Methodology — what you will do, with what data or texts, and how you will analyse them.
• Timeline and scope — a realistic sense of what fits in the time you have.
• References — the sources you have actually used so far.

For a short course essay you might compress several of these into a single planning page. For a thesis, each becomes its own section. The thinking is the same either way.

Start with a sharp question

A vague question produces a vague proposal. Compare these two:

Too broad: “I want to study social media and teenagers.”

Sharper: “How does daily Instagram use relate to reported sleep quality among first-year university students?”

The second version names a specific platform, a specific group, and a specific outcome you can measure. You can picture how you would gather evidence for it. That picture is exactly what your method section needs to describe.

A useful test: read your question aloud and ask, “What kind of evidence would settle this?” If you cannot answer quickly, the question is still too loose.

A worked example

Here is a compact proposal skeleton for the sleep question above. Notice how each line connects back to the question.

Title:    Evening Instagram Use and Self-Reported Sleep Quality
          in First-Year University Students

Problem:  First-year students report widespread poor sleep.
          Phone use before bed is often blamed, but the link is
          rarely studied in this specific group.

Question: Is there a relationship between minutes of evening
          Instagram use and self-reported sleep quality?

Gap:      Existing work focuses on general "screen time." Few
          studies isolate one platform or this age group.

Method:   Survey of 120 first-year students. Measure self-
          reported evening use (minutes) and sleep quality
          (a standard short questionnaire). Analyse for
          correlation.

Scope:    One campus, one term. Self-report only — no clinical
          sleep measurement.

Timeline: Weeks 1-2 design; 3-5 collect; 6-7 analyse; 8 write.

The proposal does not promise to prove anything. It promises a fair attempt to answer one clear question — and it is honest about its limits (self-report, one campus). That honesty makes it more convincing, not less.

Write the literature review as an argument

Beginners often treat the literature review as a stack of summaries: “Smith found X. Jones found Y. Lee found Z.” A strong review instead builds toward your gap. Group sources by theme rather than listing them one by one, and end each theme by noting what is still missing.

A simple sentence pattern helps:

“Several studies have examined ___; however, few have looked at ___, which is the focus of this proposal.”

That single move — from what is known to what is not — is the engine of the whole document. It is the reason your project deserves to exist.

Common mistakes

• Question and method don’t match. You ask about causes but only design a study that shows correlation. Decide which one you can honestly support.
• The literature review has no gap. If you never say what is missing, the reader cannot see why your project is needed.
• Promising too much. A proposal that vows to “solve” a large problem in eight weeks signals inexperience. Narrow scope reads as competence.
• Vague methods. “I will analyse the data” tells the reader nothing. Say which data, gathered how, and analysed by what approach.
• Padding the references. List sources you have genuinely read and will use, not a long bibliography meant to look impressive.
• Forgetting limitations. Naming what your study cannot do builds trust and shows you understand your own design.

Before you submit

Run a final check by reading only three things: your question, your gap, and your method. Do they tell one consistent story? If a stranger read just those three, would they understand what you plan to do and why?

When those three align, the rest of the proposal is mostly description. When they don’t, no amount of polish will hide the gap. Spend your effort there first — on the logic — and the writing will follow.