You do not have to draft a final-year project in its final reading order. The introduction promises things your project has not yet delivered, so you are guessing. A final year project goes better when you write in the order the work happens, then assemble it in the order the reader expects.
This guide gives you that order, a 16-week schedule you can adapt, what a supervisor expects at each stage, and links to a detailed guide for every chapter.
Turn the material you have into a draft you can review, rather than borrowing a finished project. UniDraft helps organise your confirmed topic, instructions and real results into an editable Word document. Start your project document and review the project workflow. You remain responsible for the research, source checks and final review.
The short answer
- Get an approved outline first: topic, problem, objectives, scope, and your supervisor's sign-off.
- Write methodology and results as the work happens, because they record real decisions and real data.
- Draft the literature review early, finish it late, after you know what you found.
- Write the introduction, abstract and reference check last; they summarise work that must already exist.
- Submit chapter by chapter to your supervisor, and keep every version.
- Never invent anything. Your results, activities and sources must be real. If a result is disappointing, report it honestly and explain it in the discussion.
Write in this order, not the reading order
Nigerian projects usually follow a five-chapter structure: Introduction, Literature Review, Methodology, Results, and Discussion/Conclusion/Recommendations, with front matter (title page, certification, dedication, acknowledgement, abstract, tables of contents) and back matter (references, appendices). Some departments merge or rename chapters, add a chapter for system design and implementation (common in computing and engineering), or split results and discussion. Your department's project guideline overrides any generic outline, including this one.
That is the reading order. The writing order is different, and the steps below describe it.
Why this order beats writing straight through
Chapter 1 asks you to state your objectives, significance and scope with confidence. That is far easier once you know what you did and found, because you are introducing a finished piece of work rather than predicting one months ahead. Chapter 5 depends on everything before it, so it cannot sensibly come earlier. Methodology and results, by contrast, record decisions and data you already have, so they are the natural place to start writing.
Getting past the blank-page problem
Do not begin with the hardest chapter. Begin with whichever chapter has the most concrete material available to you, often the methodology, because it describes a decision you have already made rather than something you must discover. Before that, write the one-page outline in Step 1: topic, three-sentence problem, objectives, scope. A rough page of facts is easier to improve than a perfect opening paragraph is to produce.
Step 1: Lock the topic, problem and objectives
Everything downstream depends on a topic your supervisor has approved and a problem you can state in three sentences. If you are still choosing, read how to choose a final year project topic and try the free topic generator for ideas by department. A good topic is narrow enough to finish in one session, has data you can realistically access, and matches your supervisor's area.
Then write, on one page:
- The problem: what is wrong, missing or unknown, and for whom. See how to write a problem statement.
- A manageable set of objectives that start with measurable verbs (determine, design, compare, evaluate), plus matching research questions or hypotheses. See how to write research questions and objectives.
- Scope: what you cover and what you deliberately leave out (location, population, time period, tools).
If your department requires a proposal before the project proper, how to write a final year project proposal covers what to include. Get your supervisor to approve the outline in writing (retain the form of approval your institution requires; messages can record discussion but may not replace formal approval). If objectives change, preserve the original plan, record why and obtain any required revised permission.
If you are unsure what the project is expected to be at all, what a final year project is explains the purpose, and seminar paper vs final year project shows how the two differ.
Step 2: Start reading and keep a source log
You do not need to read everything before you start writing, but you do need a system from day one. For each source you read, record: full reference details, the finding in your own words, its method and sample, and which objective it supports. That log becomes your literature review and your reference list, and it prevents the last-week panic of hunting for a half-remembered paper.
Prefer journal articles, standards, and official reports you can verify. Use the free citation finder to locate real sources and format them in APA, IEEE or Harvard. Never cite something you have not opened; supervisors and panels do check, and a fabricated reference is treated as misconduct.
Step 3: Write the methodology as you decide it
Chapter 3 is the easiest real writing you will do because it records choices: research design, population and sample, instruments, procedure, tools, analysis method, ethical considerations. Write each paragraph on the day you settle the decision, while you remember why you made it.
Two practical points:
- If you collect data with a questionnaire, design it properly first. See how to design a questionnaire, test its validity and reliability before you distribute it, and justify your sample with how to calculate sample size rather than choosing "100" because it sounds round.
- Decide your analysis method now, not after the data arrives. Which statistical test fits your project helps you match test to question.
The full chapter guide is how to write the methodology chapter.
Step 4: Write results as data comes in
Do not wait for "all the data". As each objective is answered, write its results section: a short lead-in, the table or figure, and two or three sentences reporting what it shows. State findings, not opinions; interpretation belongs in Chapter 5. Number and title every table and figure the moment you create it, so you never renumber 30 items on the last night.
Keep your raw data, spreadsheets, code and instrument copies in one folder. Your supervisor or panel may ask for them, and appendices are built from them. Report negative or unexpected results as they are. A project that honestly explains why a hypothesis was not supported is stronger than one that hides it.
Guide: how to write Chapter 4 (results and data analysis).
Step 5: Draft the literature review in parallel
Chapter 2 is where most students lose weeks, because reading has no natural end. Set a limit: a fixed number of sources per objective, organised by theme, not by author. Draft it while data is being collected, then revise it after your results are in. Keep the selection rationale transparent. Do not discard relevant conflicting evidence merely because it differs from your findings. If your department expects a framework, see conceptual vs theoretical framework.
Guide: how to write the literature review.
Step 6: Write Chapter 5 once results are stable
The discussion links each finding back to your objectives and to the literature, then concludes and recommends. Recommendations must follow from your findings; a recommendation with no finding behind it is the classic supervisor red flag. Also state limitations honestly and suggest further work.
Guide: how to write Chapter 5: discussion, conclusion and recommendations.
Step 7: Write the introduction last
By now you know what the project actually did, so Chapter 1 is a summary with context: background, statement of the problem, objectives, research questions or hypotheses, significance, scope and definitions. The objectives in your introduction must match those in your conclusion word for word or nearly so, and a final consistency check helps keep them aligned. Do not quietly rewrite the original research plan to hide unexpected findings.
Guide: how to write the introduction.
Step 8: Abstract, references, front matter, formatting
These come last, in this order:
- Abstract, once every chapter is stable. See how to write the abstract.
- References. Check that every in-text citation appears in the list and vice versa, and that one style is used throughout. See how to write the references list and APA 7 in-text citations. For reference details, the APA Style reference guidelines are the authoritative source; IEEE-style departments (common in engineering and computing) publish their own reference guide.
- Front matter: acknowledgement, dedication, certification page, table of contents, lists of tables and figures.
- Formatting: font, spacing, margins, heading levels, and page numbering with Roman numerals for front matter and Arabic for the body. See format a final year project for a Nigerian university and Roman and Arabic page numbers in Word. Universities differ, so check your own rules in the format guides, then run your file through the free formatting checker, which compares a .docx's font, spacing and margins against a university's requirements (the file is not stored).
Pacing to your deadline: a 16-week plan you can adapt
Work backwards from your submission date: divide your remaining pages by your remaining weeks, and keep a buffer for at least one full correction round before the real deadline. This schedule is illustrative; departments differ in how long the project lasts and when defence takes place, so shrink or stretch it.
| Weeks | Main task | What to hand your supervisor |
|---|---|---|
| 1-2 | Approved topic, objectives, scope | One-page outline |
| 3-5 | Reading, source log, methodology draft | Chapter 3 draft, list of sources |
| 6-9 | Data collection or build; write results as you go | Chapter 4 sections |
| 10-11 | Analysis, discussion, conclusion | Chapters 4 and 5 |
| 12-13 | Literature review final, introduction, abstract, references | Chapters 1-2, full draft |
| 14-16 | Corrections, formatting, binding, defence preparation | Final copy |
Two rules make the plan hold. First, the buffer is not optional: supervisors take days or weeks to return comments, and printing shops are crowded before deadlines. Second, set a weekly word or page target you can actually meet. Steady progress beats bursts followed by silence. Start with roughly 300 to 500 words on a writing day and adjust.
What supervisors look for at each stage
Your supervisor is usually the person whose instructions outrank everything else, including generic guides. Before you write, ask them:
- Which chapter structure and numbering do they expect?
- Which citation style, and does the department have a project handbook?
- Do they want a proposal, and what length?
- How do they want submissions delivered, and how long do they take to respond?
- Do they want to see data before you write it up?
Then check where problems usually surface. Panel members and supervisors commonly flag: objectives that do not match the conclusion, a methodology that does not explain how the sample was chosen, results tables without interpretation, recommendations unsupported by findings, references cited but missing from the list, and inconsistent formatting. Each of these is avoidable with the order above. If a defence follows, read project defence: what it is and how to prepare and common defence questions before you finish the write-up, to practise explaining the rationale for your choices.
When things go wrong
Your data collection is late. Write everything that does not depend on the data (methodology, literature review, front matter) and agree a revised timeline with your supervisor early, rather than telling them at week fourteen. If you are short of respondents, say what you have and discuss it with your supervisor; do not pad numbers.
Your results are not what you expected. That is normal. Report them accurately and use Chapter 5 to discuss why: sample, method, context, or a genuinely different finding from previous studies. Fabricating or "adjusting" results is academic misconduct and can cost you the whole project.
Your supervisor changes direction. Ask for the change in writing and update your objectives and every chapter that refers to them. See managing final year project corrections without losing earlier work, which explains how to keep versions and track what changed.
You are afraid of failing. Assessment outcomes depend on the actual criteria and institutional process. What happens if you fail your final year project explains the options and how to avoid them.
You are tempted to use a downloaded "sample project". A sample can show layout, but copying one is plagiarism and its data is not yours. What a good final year project sample should contain explains what to look at and what to ignore.
Pre-submission checklist
- Objectives match in Chapters 1 and 5 (and in your abstract).
- Every research question or hypothesis has a result and a discussion.
- Every table and figure is numbered, titled, and mentioned in the text.
- Every in-text citation is in the reference list, and the reverse.
- Only real sources, real data and real activities appear anywhere.
- Font, spacing, margins, headings and page numbers follow your department's rules.
- The table of contents and lists of tables and figures are updated after the final edit.
- Your supervisor has signed or approved the final version, and you have kept a copy.
- Similarity or plagiarism-check requirements, if your department has one, have been met.
- You have printed a test copy and read it on paper.
Two cross-cutting skills sit across every chapter: writing testable hypotheses and understanding plagiarism and similarity reports.
Where UniDraft fits in
Check the current price and included correction allowance in the document workflow before payment.
The free tools (citation finder, topic generator, formatting checker and university format directory) need no signup, so you can use them whether or not you use UniDraft.
Sources
- National Universities Commission (NUC): the regulator of university education in Nigeria; it sets minimum academic standards, but individual departments set project handbook details.
- APA Style: reference guidelines: official guidance on constructing APA 7 reference entries.