Standard FYP report structure
Most FYP reports follow the same five-chapter pattern: introduction, literature review, methodology, results and discussion, and conclusion. Front matter comes before Chapter 1 and the references and appendices come after Chapter 5.
Some faculties, especially in IT and engineering, replace the methodology and results chapters with system design, implementation and testing chapters. Check your faculty's FYP handbook for the required headings, and use this page as a default outline. For more detail on each chapter see our thesis chapter structure guide.
Chapter 1: Introduction
The introduction tells the reader what the project is about and why it matters. A typical order is:
- Background of the study
- Problem statement
- Research objectives (and research questions, if required)
- Scope and limitations
- Significance of the study
- Definition of key terms (if required)
- Outline of the report
Make sure the problem statement leads naturally to the objectives, and that each objective can be answered or achieved in the later chapters.
Chapter 2: Literature review
The literature review shows what is already known about your topic and where your project fits. Organise it by themes or concepts, not by author one after another.
Include the key concepts and theories, a review of related studies, and a short summary pointing to the research gap. If your project has a framework or hypotheses, introduce them here. For software projects, review existing systems and compare their features. See our literature review guide for a step-by-step method.
Chapter 3: Methodology
Methodology explains exactly how you carried out the project, in enough detail for someone else to repeat it. For a survey-based project include the research design, population and sample, instrument, data collection procedure and data analysis methods. For a software project include the development methodology (for example Agile or Waterfall), requirements, design and tools.
Write in the past tense and justify your choices ("A survey was used because..."). Mention reliability, validity and ethical considerations where relevant.
Chapter 4: Results and discussion
Present the results first, then discuss them. Show your data in tables and figures, describe the main patterns and relate them to each objective. For system projects, report test results, user feedback and performance.
In the discussion, explain what the results mean, compare them with the literature from Chapter 2 and note any unexpected findings. Keep results (what you found) separate from interpretation (what it means) unless your faculty combines them in one chapter.
Chapter 5: Conclusion
The conclusion should be short and tied closely to your objectives. Summarise the main findings, state the contributions, acknowledge limitations and suggest realistic recommendations and future work.
Do not introduce new data or new references here. A good test: someone who reads only the conclusion should see how each objective was met.
Front matter and appendices
Front matter usually includes the title page, declaration, acknowledgements, abstract, table of contents, list of tables, list of figures and list of abbreviations. Number these pages with lower-case Roman numerals if your university requires it.
Back matter includes the reference list and appendices, such as questionnaires, interview protocols, code listings, user manuals or ethics approval letters. Use the format and order set by your faculty, and update the contents list after your final edit.