A research proposal is not a shortened version of your project. It is your Chapters One to Three written in the future tense, presented at a departmental seminar, and approved before you are allowed to collect a single questionnaire. Get it approved and most of your project is already drafted; get it wrong and you rewrite the methodology after you have already used it.
Most Nigerian departments require one, most students write it in a rush the week before the seminar, and almost nobody is told the one thing that makes it easy: you are not writing a new document. You are writing the first three chapters early.
This is the procedure, in order. Each step produces something you will reuse.
Step 1: Get your department’s format, in writing, before you write anything
Proposal requirements are set at department level and they differ across Nigerian universities and even between departments in the same faculty. Find out four things:
- The required sections and their order. Some departments want a numbered Chapter One to Three structure, some want a continuous proposal document with headed sections.
- The page or word limit. Commonly somewhere between fifteen and thirty pages, but your department’s number is the one that counts.
- Whether a seminar presentation is required, and when. This is your real deadline.
- The referencing style. Nigerian universities do not agree on one — this is settled in the guide to what referencing style Nigerian universities actually require.
Expected output: a written format sheet, or a note of what your supervisor told you and the date they told you.
Step 2: Title and background of the study
The title on your proposal is provisional and will very likely change, so do not spend a week on it. What it must do is name the variables, the population and the location — “Effect of X on Y among Z in [location]” is a shape that survives a seminar.
The background then does one job: it moves from a broad problem area to the specific gap your project addresses, in three or four paragraphs. Broad, narrower, narrowest, then the gap. This is the same background you will use in your final Chapter One, so write it properly now.
Expected output: a working title and a background that ends on a gap. The full section-by-section version of the chapter this becomes is in the guide to writing Chapter One.
Step 3: Statement of the problem, objectives and research questions
Three sections that must agree with each other, and the commonest reason a proposal is sent back is that they do not.
The rule is one-for-one. If you have four specific objectives, you have four research questions, and each question answers exactly one objective. A fifth research question with no matching objective is the single easiest defect for a lecturer to find at a seminar, and it takes ten seconds.
Worked example of the mapping:
| Objective | Matching research question |
|---|---|
| 1. To determine the level of X among the respondents | 1. What is the level of X among the respondents? |
| 2. To examine the relationship between X and Y | 2. What relationship exists between X and Y? |
| 3. To identify the challenges affecting Y | 3. What challenges affect Y? |
If your study tests relationships, hypotheses go here too, stated in null form, one per relational question. A hypothesis for a purely descriptive question is a mismatch, and a relational question with no hypothesis is the other half of the same error.
Expected output: objectives and questions that map one to one, with hypotheses only where a relationship is claimed.
Step 4: Scope, limitations and significance
Three short sections that most students underwrite and lecturers read carefully.
Scope bounds the study on three axes: who (the population), where (the institution, local government or organisation) and when (the session or period). A scope that names all three is defensible; one that says “this study covers students” is not.
Limitations name what you cannot do and why — access, time, funds. Writing these honestly at proposal stage protects you later, because a limitation you declared in advance is a design decision, while the same limitation discovered in Chapter Five is a weakness.
Significance names the specific beneficiaries and what each one gains. “It will be useful to students, researchers and the general public” is the sentence every panel has read a thousand times. Name the department, the organisation, the agency.
Expected output: a scope with all three axes, honest limitations, and a significance section with named beneficiaries.
Step 5: The literature review, condensed
This is the section students get most wrong in both directions — some write two pages, some write the whole of Chapter Two.
A proposal’s literature review has one purpose: to show that you have read enough to know the gap is real. That means conceptual review of your key variables, a short theoretical framework naming the theory you are adopting and why, an empirical review of the closest studies, and an explicit gap statement.
Aim for a fraction of your final Chapter Two, and write it so it expands rather than needing replacement. The synthesis method that produces expandable text, rather than a list of summaries, is in the guide to writing Chapter Two.
Expected output: a review that ends on a sentence beginning “However, none of these studies…”.
Step 6: Methodology — and the tense rule that catches everybody
This is the section the seminar actually examines, because it is the only part the department can still change.
Write it in the future tense. “The study will adopt a descriptive survey design.” “A sample of 300 will be drawn using the Taro Yamane formula.” At proposal stage nothing has happened yet, and a proposal in the past tense tells your supervisor you have already collected data without approval — which is a serious problem in departments that require ethical clearance first.
Cover these, in this order:
- Research design — and name it precisely, not just “survey”.
- Area of the study — the institution or location.
- Population — with a figure and where the figure came from.
- Sample size and sampling technique — with the computation shown, not just the answer.
- Instrument for data collection — how many items, what scale.
- Validity and reliability — how they will be established, including the planned pilot.
- Method of data collection — how the instrument reaches respondents.
- Method of data analysis — which statistic answers which research question.
Two of these carry most of the seminar’s questions. The sample-size computation must be shown step by step, because a lecturer with a calculator settles that argument in ninety seconds. And the analysis section must pair each research question with a named statistic — the mapping is set out in the guide to writing Chapter Three section by section.
Expected output: eight subsections, all in the future tense, with the sample computation shown.
Step 7: References, timeline and budget
References in your department’s style, and every in-text citation present in the list. This is checked, and it is free marks to lose.
Many departments also want a work plan and an estimated budget. Both are graded on realism rather than ambition. A timeline that allots one week to data collection in a department where respondents are lecturers is not credible; a budget that omits printing, transport and airtime is not either.
Expected output: a complete reference list, a month-by-month plan, and a budget with real line items.
Step 8: The seminar, and what to do with the corrections
Most departments require you to present the proposal to a panel of lecturers before approval. It is shorter and less formal than the final project defence, and it examines a study that does not exist yet — so nothing you say about findings matters, because you have none.
Expect questions on four things: why this topic, why this population, how you arrived at your sample size, and whether you can finish it in the time you have. Feasibility is the concern that sends most proposals back, and it is worth pre-empting: if your population is hard to reach, say so and say how you will reach them.
Write every correction down verbatim, with the name of the lecturer who gave it. Lecturers contradict each other, and the record is what lets your supervisor arbitrate afterwards. The final defence, which examines a completed study, asks a different and harder set of questions — those are catalogued in the article on what questions are asked during a project defence.
What approval actually locks
This is the part nobody explains, and it matters more than the document.
Once your proposal is approved, your design is fixed. Changing it afterwards — a different population, a different instrument, a different analysis — usually requires going back for re-approval, and in some departments repeating the seminar. Students discover this at the worst possible moment, when analysis reveals that the instrument cannot answer research question three.
So the section to over-invest in is the methodology, not the background. Spend the extra evening checking that each research question has a statistic that can actually answer it, and that your instrument produces data of the type that statistic requires. An ordinal scale cannot feed a test that needs interval data, and finding that out after 300 questionnaires is expensive.
What does not change is the writing. Everything in the approved proposal carries forward — you convert the methodology to past tense, expand Chapter Two, and add Chapters Four and Five. That is the whole reason the proposal is worth writing well.
Converting the proposal into the project
Four mechanical steps, once your data is in.
- Change every future-tense verb in Chapter Three to past tense. “Will be administered” becomes “was administered”. A chapter still in the future tense tells a panel you never went back to it.
- Correct every number that changed. If you planned 300 and retrieved 274, the chapter says 274 — and so does Chapter Four, and so does the abstract.
- Expand Chapter Two to full length with the sources you have read since.
- Write Chapters Four and Five, which the proposal never contained.
How the five chapters are meant to sit together, and what belongs in each, is summarised in the answer to how many chapters a Nigerian final year project has.
Write the proposal once and reuse it
Tesify structures your project in the chapter format your department expects and keeps every citation attached to a source you actually opened, so an approved proposal converts into Chapters One to Three instead of being rewritten. Over 9,000 students have used it to write more than 15,000 chapters, and 100 per cent of the work is still written by you.
Frequently asked questions
What is a research proposal in a Nigerian final year project?
A document setting out what you intend to study and how, submitted and usually presented at a departmental seminar before you are permitted to collect data. In practice it is Chapters One to Three written in the future tense.
How long should a research proposal be?
Commonly fifteen to thirty pages, but the number that governs you is your own department’s. Ask for it in writing rather than copying a senior colleague’s length.
What tense should a research proposal be written in?
Future tense throughout the methodology, because nothing has happened yet. After data collection you convert those verbs to past tense. A proposal written in the past tense suggests you collected data before approval.
Does a proposal include a literature review?
Yes, but condensed — enough conceptual, theoretical and empirical review to establish that your gap is real. It expands into the full Chapter Two later rather than being replaced.
Does a proposal include Chapters Four and Five?
No. Those report data you have not collected and conclusions you cannot yet draw. A proposal stops at methodology.
What is the difference between a proposal and a proposal seminar?
The proposal is the document; the seminar is where you present it to lecturers for approval. Some departments call the session a proposal defence. Both examine a study that does not exist yet.
Can my topic change after the proposal is approved?
Minor refinement of wording is normal and often expected. A change of population, instrument or analysis usually means going back for re-approval, which is why the methodology deserves the most care before you submit.
Do I need a budget and timeline?
Many Nigerian departments require both. Include real line items — printing, transport, airtime, data — and a month-by-month plan you could actually keep. They are assessed for realism, not ambition.
How do I justify my sample size in a proposal?
Show the computation, not the answer. State the population figure, name the formula or table you used, substitute the numbers and show the result. What is not acceptable is a sample size with no stated basis.
What if my supervisor and the seminar panel disagree?
Write both instructions down verbatim with names attached and take the conflict to your supervisor afterwards. Do not attempt to adjudicate between two lecturers in the room.
Can I use AI to help write my proposal?
That depends on your department’s policy, which you should confirm rather than assume. What such tools can and cannot legitimately do for a Nigerian project is set out in the article on whether you can use AI to write your final year project.
What happens if my proposal is rejected?
Usually it is returned with corrections rather than rejected outright, and you resubmit. Where the topic itself is the problem, the department may ask you to change it, which is a much earlier and cheaper failure than discovering the same problem in Chapter Four.