Enugu, Nigeria
Nigeria
Enugu State
Nigeria

How To Analyse Quantitative Data In Your Final Year Project

You have done the hard part. Your questionnaires are back, your responses are counted, and your screen is full of numbers. Now comes the part that worries most final year students: turning those numbers into a Chapter Four that your examiner can actually read and believe. The good news is that you do not need advanced statistics to do this well. You need to describe your numbers clearly, present them in clean tables and charts, and say in plain words what each result shows.


Academic Integrity & Digital Research Tools

Writing a high-quality Project Thesis requires more than just data; it requires precision. To ensure your Research Methodology meets international standards, we recommend using advanced AI Plagiarism Checkers and Grammar Correction Software before submission.

Professional Proofreading and Formatting

Many academic institutions now use automated AI Detection Tools. If you are preparing your Statement of Purpose (SOP) or Manuscript, investing in professional Academic Proofreading Services can help you maintain a high Similarity Index score while ensuring your research remains authentic and impactful.


This guide is about that job. It covers the descriptive side of quantitative analysis: frequencies, percentages, means and standard deviations, and how to turn them into tables and charts that speak for themselves. It does not repeat the regression interpretation covered in How to Interpret Your Research Findings, and it does not walk through software clicks the way How to Use SPSS for Data Analysis in Your Final Year Project does. Think of this as the chapter between your raw data and your interpretation, the part where you show your reader exactly what you found.

Start by cleaning your numbers before you analyse a single one

Before you calculate anything, give your dataset a careful once over. Check for questionnaires that are half blank, answers that fall outside the scale you used, and duplicate entries where the same respondent appears twice. A single typing error, a 55 where the scale only goes to 5, can quietly wreck a whole table, and examiners notice these things.

Count your usable responses and compare the number with the number you sent out. If you sent out 220 questionnaires and 198 came back usable, your response rate is 90 percent, and you should say so in your first paragraph. A low response rate is not a disaster, but hiding it is. Write one short sentence for every number you report: how many you sent, how many came back, how many you could use, and how many you had to drop and why. Your examiner trusts a student who shows the working.

Describe who answered, in one short section

Your first table is usually about your respondents, not your findings. Age, gender, level of study, department, or whatever background details your study collected. Keep it short. One table, one paragraph, and move on. Nobody needs three pages of demographic tables, and your examiner will skim past them anyway.

Here is the pattern to follow. Give the table a number and a clear title, for example "Table 4.1: Distribution of Respondents by Level of Study". Then write one sentence that states the main pattern: "Most respondents (62 percent) were in their final year, while 24 percent were in 300 level and 14 percent in 200 level." That is all the text you need. Do not list every number in the table again in words. Your reader can see the table. Your job in the text is to point at the pattern that matters.

Frequencies and percentages: your first tool for survey answers

When your questionnaire asked people to choose an option, frequencies and percentages are your tools. A frequency is simply how many people chose an answer. A percentage is that number expressed as a share of everyone who answered. Together they are the clearest way to present most undergraduate survey results.

Use whole numbers or one decimal place for percentages, never three or four. A sample of 200 students cannot support 63.50 percent, because one student changing their mind would move the figure. Round to 63.5 percent, or even 64 percent, and your result is both honest and easier to read. Always show the total number of respondents under the table, so your reader can see what the percentages are based on.

One warning: percentages without a base are meaningless. "80 percent agreed" sounds impressive until your reader learns that only ten people answered the question. Always report the number of respondents alongside the percentage. In your text, write "160 of the 200 respondents (80 percent) agreed", not just "80 percent agreed". That small habit is what separates a careful project from a careless one.

Means and standard deviations: when your questions used a scale

If your questionnaire used a Likert scale, where respondents chose from strongly disagree to strongly agree, you will usually report a mean and a standard deviation for each item. The mean is the average score. The standard deviation tells your reader how spread out the answers were. A mean of 4.1 with a small standard deviation means most people agreed and agreed by a similar amount. The same mean with a large standard deviation means the group was split.

Here is the rule students get wrong most often: never report a mean without its standard deviation. A mean on its own hides how much your respondents disagreed with each other, and your examiner knows it. Write it like this: "Students rated the statement 'Online lectures help me understand the course' at a mean of 4.12 (SD = 0.67), which shows general agreement with little variation." One sentence, both numbers, and the meaning in plain words.

For a Likert scale of 1 to 5, use one decimal place for means and standard deviations, for example 3.8 and 0.7. Two decimal places are fine if your department follows APA style, but never report four. And remember that a mean only makes sense for numbers that behave like numbers. You can average a five point scale. You cannot average a list of departments, because department is a category, not a quantity. For categories, use frequencies and percentages instead.

Choosing between a table and a chart

Tables and charts do different jobs, and choosing the right one is half the skill of presenting quantitative results. Use a table when your reader needs the exact numbers, for example when you are reporting the results for ten questionnaire items side by side. Use a chart when the pattern matters more than the exact figures, for example when you want to show at a glance that satisfaction rises across the four years of study.

Keep every table simple. One idea per table, short labels, numbers lined up in columns, and no more than six or seven rows if you can help it. If a table grows past that, split it into two. Give each table a number and a title that says what it shows, and always refer to it by number in the text: "As shown in Table 4.3". Never write "the table below" or "the table above", because tables move when your document is edited, and your examiner should not have to hunt for them.

Charts need the same discipline. A bar chart is the safest choice for comparing groups. A pie chart only works when the parts add up to 100 percent, so it suits a single question with a few options, not a whole section. A line chart suits change over time. Whatever you choose, keep it clean: one chart, one message, labels your reader can read without squinting, and the number of respondents noted underneath. If your chart needs a paragraph of explanation before anyone can read it, the chart is too complicated. Redraw it.

Present your results in the order of your research questions

Here is the structure that works for almost every undergraduate project. Present one research question at a time, in the same order you listed them in Chapter One. Under each question, show the tables and charts that answer it, and write a short paragraph for each one that states the main pattern. Then move to the next question.

This order matters more than students realise. When your results follow your questions, your examiner can check each answer against the question it belongs to, and your discussion chapter almost writes itself. When your results jump around, your examiner has to work out which table belongs to which question, and that is not their job. If you are still shaping your questions, our guide to How to Write Research Questions and Hypotheses for Projects will help you tighten them before you present anything.

Write about the pattern, not the numbers

The single most common mistake in Chapter Four is reading the table out loud in words. "Table 4.2 shows that 38 respondents were dissatisfied, 71 were neutral, and 171 were satisfied. The percentages were 13.6 percent, 25.4 percent, and 61.1 percent respectively." Your examiner can see all of that in the table. What they cannot see is what it means, and that is the sentence they are waiting for.

Write this instead: "As shown in Table 4.2, most respondents were satisfied with the programme (61.1 percent), while about a quarter were neutral (25.4 percent) and only a small group were dissatisfied (13.6 percent)." One sentence, the main pattern, and the numbers that prove it. Save the deeper meaning, the why and the so what, for your discussion chapter. In Chapter Four, your job is to present and describe, not to argue.

If a result surprises you, say so in one sentence and move on. "Contrary to expectations, final year students reported lower satisfaction than 300 level students." That sentence belongs in your results, because it is a fact about your data. The explanation for why it happened belongs in Chapter Five.

A quick checklist before you call Chapter Four done

Run through this list with your draft open, and fix anything that fails.

  • Every table and chart has a number and a title. No unnamed tables, no figures floating without a label.
  • Every table and chart is mentioned in the text. If you never refer to it, either write about it or delete it.
  • Every percentage has a base. Your reader can see how many people the percentage is calculated from.
  • Every mean has a standard deviation. No mean ever stands alone.
  • Percentages are rounded sensibly. One decimal place at most, and whole numbers are fine for a small sample.
  • Your results follow your research questions, in order. One question at a time, tables and text together.
  • You describe patterns, not numbers. The text says what the table shows, not what the table already says.
  • Nothing here belongs in Chapter Five. No long explanations, no recommendations, no conclusions. Those come later.

Your numbers are ready. Let them speak

You do not need a statistics degree to analyse quantitative data well at undergraduate level. You need clean data, the right descriptive tool for each kind of question, and tables and charts that a tired examiner can read in seconds. Frequencies and percentages for categories, means and standard deviations for scales, one clear table or chart per idea, and a short paragraph that states the pattern. That is the whole method, and you already have the data to do it.

Start with your simplest result, the one you understand best, and present it cleanly. Then do the next one the same way. By the time you reach your last research question, you will have a Chapter Four that reads like a clear report of what you found, which is exactly what it should be. And when you are ready to explain what those findings mean, How to Interpret Your Research Findings and our guide to How to Write Chapter Four of Your Final Year Project will help you take the next step.

Check This Out:
Latest Cooperative Economics Project Topics And Materials
Be the First to Share On Social


1GB data
1GB data
1GB data

10