By AOLYTIX Research Desk 12 min read · Research Methods · Nigerian Postgraduate Research
We had a client whose proposal was returned — twice — before she came to us.
The research idea was solid. Her topic was genuinely underexplored. Her supervisor liked her, and she's clearly intelligent. But the proposal kept coming back with the same note: "Problem statement needs work. Methodology unclear."
When we looked at it, the issue was simple. She was writing what she thought a research proposal should sound like, rather than what it actually needs to do. And nobody had ever explained the difference.
This guide fixes that.
A research proposal isn't a form you fill in to get permission. It's an argument. It says: here is a real problem, here is why it matters, here is how I will investigate it, and here is why I'm the right person to do it.
Every section exists to advance that argument. The moment a section stops doing that — the moment it becomes padding or boilerplate — a reviewer's attention starts to drift. And once you lose a reviewer, you rarely get them back.
In Nigerian institutions, a strong proposal determines whether you get admitted into a postgraduate programme, receive ethics clearance, get matched with a willing supervisor, or qualify for a grant. A weak one wastes months. Sometimes a full academic year.
So let's get it right.
Specific. Focused. Under 20 words.
"A Study of Education in Nigeria" will get you a polite but firm request to revise. "Effect of Teacher-Pupil Ratio on Academic Performance in Public Primary Schools in Ibadan North Local Government Area" will get you a nod.
Your title should tell a reviewer exactly what you're studying, where, and who's involved. If it could describe five different studies, it's too vague.
Start with the problem, not with history. Not "Since the dawn of civilisation, education has been important." Start with: here is something that is broken, missing, or misunderstood — and here is the evidence.
Good introductions move like a funnel. Broad context at the top, narrowing steadily down to the specific gap your study will fill. By the time a reviewer reaches your problem statement, they should already sense it coming.
This is the most important section in your proposal. Get this wrong and nothing else can save you.
A weak problem statement: "Not much research has been done on this topic in Nigeria."
That tells a reviewer nothing about why it matters, who's affected, or what the consequences of inaction are.
A strong problem statement: "Despite a 41% increase in out-of-school children in Kano State between 2018 and 2023 (UNICEF, 2024), no study has examined the specific role of insecurity on parental school enrolment decisions in affected LGAs — leaving a critical gap in both policy design and intervention planning."
See the difference? Numbers. A named location. A named consequence. A named gap.
One more thing: cite current sources. We've seen proposals returned because the problem statement cited a 2007 World Bank report as though it were recent. Reviewers notice. If your "current evidence" is 15 years old, your problem may already be solved — or your literature search isn't serious. Neither is a good look.
Write these as active statements. Not "to understand" — that's vague. Use:
One or two main objectives for a master's thesis. Three to five for a PhD. Any more than that and reviewers start wondering whether you understand what a single study can realistically achieve.
Every objective needs a corresponding research question. And if your study is quantitative, those questions should become testable hypotheses.
Research Question: Is there a significant relationship between staff welfare and employee retention in Nigerian commercial banks?
Null Hypothesis (H₀): There is no significant relationship between staff welfare and employee retention in Nigerian commercial banks.
Alternative Hypothesis (H₁): There is a significant positive relationship between staff welfare and employee retention in Nigerian commercial banks.
Always write both. Reviewers who see only H₁ know you copied a template. Reviewers who see both know you understand what you're doing.
Don't write "this study will contribute to the body of knowledge." Every study does that. It means nothing.
Write specifically who benefits and how:
Concrete. Named. Stakeholder-specific.
Define your boundaries clearly: which state, which LGA, which institution, which time period, which population. "Nigeria" is not a scope. "Public secondary school teachers in Enugu North Senatorial District" is a scope.
Then briefly acknowledge your limitations — access constraints, sample size, time, researcher positionality — and how you plan to address them. This doesn't weaken your proposal. It signals research maturity. Reviewers are far more suspicious of a proposal that claims no limitations than one that honestly names and addresses them.
Three jobs, in this order:
Cite current, peer-reviewed sources — within the last 10 years unless you're referencing foundational theory. If your literature review reads like a summary of abstracts you found on Google Scholar at 2am, reviewers will know. You need to engage with sources — compare them, contrast them, note where they conflict or fall short.
And the review should funnel, just like your introduction. End it with a paragraph that makes your study feel inevitable — the logical next step given everything that has and hasn't been done.
Your framework is the lens through which you view your research problem.
Theoretical framework: built on an existing theory — Social Learning Theory, Resource-Based View, Health Belief Model, etc.
Conceptual framework: your own model, showing how your variables relate to each other. Draw it. A simple diagram showing independent variables → dependent variable, with moderating or mediating variables where relevant, communicates your thinking faster than three paragraphs of explanation.
If your supervisor tells you "this section is weak," they almost always mean: your framework doesn't connect clearly to your specific variables and context. The theory must fit — not just be named.
This is where proposals live or die.
You need to address all of these — clearly, specifically, and with justification for every choice:
Research Design: Quantitative, qualitative, or mixed? Descriptive, correlational, experimental, case study? And why that design for this problem?
Population and Sample: Who is your target population? What is your sample size — and show how you calculated it. Yamane's formula, Cochran's formula, or G*Power are all acceptable. "I chose 100 respondents" with no explanation is not.
Sampling Technique: Random, stratified, purposive, snowball? Justify it based on your population and research design.
Research Instrument: How was your questionnaire or interview guide developed? How was validity established (face validity, content validity)? How was reliability tested (pilot study, Cronbach's alpha)?
Data Analysis Plan: Which software — SPSS, R, Python, NVivo? Which specific tests address which specific research questions?
Every one of these must be specific. "Appropriate statistical tools will be used" is the sentence that gets proposals sent back most often.
A simple Gantt chart or table. Show that you understand the work involved and have a realistic plan for doing it.
| Phase | Activity | Duration |
|---|---|---|
| 1 | Literature Review & Proposal Finalisation | Month 1–2 |
| 2 | Instrument Development & Piloting | Month 3 |
| 3 | Data Collection | Month 4–5 |
| 4 | Data Analysis | Month 6 |
| 5 | Write-up and Submission | Month 7–8 |
If your timeline has data collection starting the week after proposal approval, reviewers know you haven't thought it through. Build in buffer. Things always take longer than expected — especially data collection in Nigeria.
For grant applications, break down every cost and justify it. Reviewers are more impressed by a realistic, itemised budget than an inflated one. Padding budgets is obvious. So is underestimating.
Every source cited in the body must appear here, formatted in your institution's required style — APA, MLA, Chicago. Missing references are red flags. Citing sources you clearly didn't read (wrong year, wrong author, wrong findings) is worse.
Not "the topic wasn't interesting enough." The real reasons:
But here's the one that stings most: a brilliant idea, poorly written. We've seen this. The research question is genuinely important, the student is capable — but the writing is unclear, the structure is muddled, and the reviewer simply can't tell what the study is doing. A great idea in a weak proposal is still a rejected proposal.
Read approved proposals in your department. Most departments have archives or can point you to past work. Study what got through — not just the topic, but the structure, the language, the way objectives are framed.
Get feedback before you're done. Don't write 25 pages and then show your supervisor. Show them your problem statement at page 3. Show them your methodology outline before you flesh it out. Early feedback is surgical. Late feedback is a rewrite.
Write clearly, not impressively. Academic writing isn't about long sentences and complicated vocabulary. It's about precision. Say exactly what you mean. If a sentence requires a second reading to understand, it needs to be rewritten.
A rejected proposal doesn't just delay your programme — it can shake your confidence in ways that take months to recover from. We've seen it happen. And it's almost always preventable.
AOLYTIX Group supports students and researchers across Nigeria at every stage of the proposal process:
Not sure if your problem statement is strong enough? Share it with us. We'll give you honest, specific feedback — the kind your supervisor is thinking but might not say out loud.
Talk to the AOLYTIX Research Desk →
AOLYTIX Research Desk is the publishing arm of AOLYTIX Group — a Nigerian academic research and consulting firm supporting postgraduate students, researchers, and organisations across Africa with data analysis, dissertation support, and research consulting.