How to Write a Research Proposal: A Practical Guide for University Students in Uganda

A research proposal is not a summary of a topic you find interesting. It is a written argument that a specific study should be carried out, that you have a defensible way of carrying it out, and that the results will be worth the time you are asking your department to approve.

Most proposals are rejected for the same handful of reasons: the problem is stated as a topic rather than a problem, the objectives do not match the questions, and the methodology is described as a list of tools instead of a set of decisions. Working through the sections below in order fixes all three.

Start with the problem, not the title

Your title is the last thing to settle, because it is a compression of everything else. Begin with the problem.

A research problem has three parts:

• Something is happening. A pattern you can point to in a document, a dataset, a policy or an accepted body of published work.
• Something is not known. The specific gap between what is known and what your study needs to know.
• Something is at stake. Who is affected if the gap stays open: students, a department, a regulator, a community, an institution.

Write those three parts as a single paragraph before you write anything else. If you cannot, you do not yet have a proposal problem; you have a subject area. A subject area is a library shelf. A problem is a door.

Problem statement, in one page

The problem statement section should read in this sequence:

1. The wider context, in two or three sentences. No history lessons.
2. The evidence that the issue exists, drawn from sources you have actually read.
3. The narrower gap your study addresses.
4. Why closing that gap matters, and to whom.
5. What your study will therefore do, in one sentence.

Avoid opening with "In recent years, there has been increasing interest in…". It tells the reader nothing and it is the most common first line in submitted proposals.

Objectives, questions and hypotheses must lock together

A common failure is a proposal whose objectives describe the background reading the student intends to do, and whose questions describe what they want to find out. Those are different studies.

Use measurable verbs: describe, compare, examine, determine, evaluate. Avoid "to understand" and "to explore" unless the design is explicitly exploratory and you justify it.

If the study is qualitative, do not force hypotheses to look quantitative. State your guiding questions and how you will know when they are answered.

Literature review: the shortest defensible version

The proposal's literature review is not the review for your final chapter. It is a targeted argument with one job: to show that your gap is real and that you know how others have approached it.

Structure it by idea, not by author:

1. What is well established in this area.
2. What is contested or inconsistent.
3. What remains unexamined, and why that matters here.
4. What your study therefore adds.

Every claim you make about published work should be traceable to a source you can produce on request. If you have only read a title and an abstract, say so to yourself and read the full text before you lean on it. For more on judging a source before you cite it, see How to Find Credible Academic Sources.

Methodology is a set of decisions, not a list of tools

Supervisors read the methodology section looking for whether you have thought through consequences.

Answer these in order, and justify each:

• Design. Case study, survey, experiment, ethnography, mixed methods, secondary analysis. What does it let you claim, and what does it not?
• Population and sampling. Who exactly is your population, how is your sampling frame defined, and how will you select participants? State your target sample size and how you arrived at it.
• Instruments. Questionnaire, interview guide, observation schedule, document analysis protocol. Say how each item relates to a research question.
• Validity and reliability. For quantitative work: how have you reduced measurement error? For qualitative work: what gives your account credibility, and how will you record your reasoning?
• Data analysis. Name the actual technique: descriptive statistics, thematic analysis, content analysis, regression, and the software if any.
• Ethics. Consent, confidentiality, anonymity, data storage, and how you will handle a participant who withdraws. Attach or reference the approval process your institution requires.
• Limitations. State them now. An honest limitation is a strength; a discovered one during defence is not.

A note on scope

Scope defines what your study will not do. It is not an apology. Write it as a boundary: "This study covers X in Y setting between A and B dates. It does not attempt to measure Z, which would require longitudinal data beyond the timeframe of this programme."

Saying this early prevents an examiner from asking why you did not do the impossible.

Referencing and formatting

Most departments publish a required style, usually APA 7, and a proposal template. Use them. If your department's template conflicts with what you read online, the department wins.

Check that every in-text citation has a reference-list entry and vice versa before you submit. If you are unsure about the format, the APA 7 explainer walks through in-text citations and reference entries with worked examples.

Pacing and supervision

Write the proposal in the order you can defend it, not the order it appears on the page. Many students write the methodology first because it is the most concrete, then write the problem statement once the method has made the study's boundaries clear. That is a legitimate way to work.

Send your supervisor something specific. "Is this problem statement defensible?" gets a better response than "Please review my proposal."

Final checklist before submission

• The problem is stated as a problem, with evidence and a stake.
• The main objective, specific objectives and research questions align one-to-one.
• Each research question has a stated method of answering it.
• The literature review ends at your gap, not at a summary of everything read.
• The methodology justifies choices rather than listing tools.
• Scope and limitations are explicit and unapologetic.
• Ethics requirements are addressed and attached where required.
• Every citation matches a reference entry, in the required style.
• The title accurately describes the study you are proposing.
• The document fits the institutional template and page limit.

Key takeaways

• A proposal argues for a study; it does not describe a subject.
• Alignment between objectives, questions and methods is what examiners test first.
• Scope and limitations protect you. Write them deliberately.
• Traceable referencing is the difference between a proposal that reads as academic work and one that reads as an essay.

When the proposal is approved, the same structure carries into the work itself. PassResearch's project workspace mirrors this sequence — problem, objectives, evidence, then writing — so the approved proposal becomes the skeleton of the dissertation rather than a document you abandon after approval.