How to write a results chapter: quantitative structure, tables, and reporting order

You have run the analysis, exported the tables, and still do not know what to write first. The numbers are sitting in SPSS, Excel, R, Jamovi, or another tool, but the chapter feels like a pile of outputs rather than an academic section. If you are searching for how to write a results chapter, the real problem is usually not the statistics alone; it is the order, the level of detail, and the line between reporting results and discussing meaning. Students often either paste everything from the software output or explain every number so heavily that the chapter turns into a discussion section too early.

A quantitative results chapter reports what the analysis found in a clear sequence: sample description, descriptive statistics, assumption checks where relevant, then findings for each research question or hypothesis. It uses tables and figures selectively, states statistical results accurately, and leaves interpretation, theory, implications, and recommendations for the discussion chapter.

In this guide

• How do you write a results chapter for quantitative research?
• What is the difference between results and discussion?
• What order should quantitative findings be reported in?
• What tables and figures belong in a quantitative results chapter?
• How do you report statistical tests without overexplaining them?
• What does a results section example look like?
• What mistakes do students commonly make when writing a quantitative results chapter?
• How can you revise a quantitative results chapter before submission?

How do you write a results chapter for quantitative research?

Write a quantitative results chapter by matching the structure of the chapter to your research questions, hypotheses, and statistical tests. Start with the sample and descriptive statistics, then report each main analysis in a consistent pattern: purpose, test used, key result, table or figure reference, and brief factual statement. Do not build a theoretical argument in the results chapter; save explanation and meaning for the discussion.

Start with the question-output match

The easiest way to create order is to build a map between your research questions and the outputs you need. If your paper asks whether study time predicts exam performance, your chapter should not begin with every demographic variable you collected. It should begin with the sample, then move toward the descriptive statistics and regression results that answer that question.

A results chapter is the section that reports analysed findings without turning them into a broader interpretation. A quantitative results chapter reports numerical findings from surveys, experiments, secondary datasets, or structured measurements. The reader should be able to see what was tested, what values were obtained, and whether each hypothesis was supported, partially supported, or not supported.

For example, in a psychology research paper on social media use and sleep quality among undergraduates, the results chapter might report the average hours of social media use, the average sleep quality score, the correlation between the two variables, and the regression result if control variables were added. The chapter should not yet claim that social media “damages student wellbeing” unless the design and analysis support that wording and the discussion later develops the argument.

Build the chapter around repeatable reporting units

Many student chapters become confusing because every subsection has a different pattern. One subsection starts with a table, the next starts with a long paragraph, and another opens with interpretation. A repeatable unit keeps the reader oriented.

Use this basic pattern for each finding:

1. State which research question, hypothesis, or objective the subsection addresses.
2. Name the statistical procedure used.
3. Refer to the table or figure if one is included.
4. Report the key numerical result.
5. State the factual outcome in relation to the hypothesis.
6. Avoid theory, recommendations, or causal claims unless the design allows them and the discussion develops them.

This pattern works for many undergraduate and master’s papers because it gives enough detail without reproducing the entire software output. If your methodology chapter already justified your design, sampling, variables, and tests, the results chapter can focus on what the analysis found. If that earlier chapter is still unclear, use a method-planning resource such as methodology chapter stages from design to justification before finalising the results.

What is the difference between results and discussion?

The results section reports the findings; the discussion section explains what those findings mean. Results answer “What did the analysis show?” while discussion answers “Why does this matter in relation to the research question, literature, limitations, and implications?” Keeping results vs discussion separate prevents the chapter from becoming either a data dump or an unsupported argument.

Separate factual reporting from interpretation

A useful rule is simple: if the sentence describes a number, test result, pattern, or table, it probably belongs in the results chapter. If it explains why the pattern occurred, compares it with prior studies, discusses consequences, or recommends action, it belongs in the discussion.

Consider a nursing capstone project examining whether a discharge education checklist is associated with medication adherence among older adults receiving home care. A results sentence might say, “Participants who received the checklist reported higher adherence scores than those who did not.” A discussion sentence might say, “This finding may suggest that structured discharge education reduces uncertainty during the transition to home care.” The first sentence reports the observed pattern; the second explains a possible meaning.

The separation is not just a style issue. It protects the logic of the paper. Readers need to inspect the evidence before they are asked to accept your explanation of that evidence.

Use the results chapter for evidence, not argument

Students sometimes believe that a results chapter sounds “too plain” unless they add interpretation after every test. Plain is not the same as weak. In quantitative writing, restraint can make the chapter more credible because the reader sees the evidence in a clean order.

Here is a practical comparison:

Student version	Better chapter placement	Why it works better
“The low p-value proves that online learning is effective.”	Results: “The difference was statistically significant, p = .018.” Discussion: explain effectiveness with caution.	The revised version avoids overclaiming and separates the statistic from the interpretation.
“This means nurses should use the checklist in all wards.”	Discussion or recommendations, not results.	Practice recommendations need interpretation, limits, and context.
“Students with higher motivation scored better because they cared more.”	Results: report the correlation or regression coefficient.	The cause is not shown unless the design supports causal inference.
“The table clearly shows the hypothesis is true.”	“The result supports H1 under the criteria used in this study.”	The revision uses measured evidence rather than vague certainty.

Link claims back to your variables

A variable is a measurable feature that can take different values, such as age, test score, stress level, income, medication adherence, or number of absences. Results chapters become clearer when every claim uses the same variable names introduced in the methodology section.

If you are still changing labels between “motivation”, “engagement”, and “student interest”, your reader may not know whether these are the same construct or three different measures. Before writing the results chapter, check that your independent and dependent variables are defined consistently. A variable map such as independent and dependent variables relationship diagram can help when your findings feel scattered.

What order should quantitative findings be reported in?

Report quantitative findings in the order that best matches your research questions or hypotheses, not in the order produced by the software. A common order is sample characteristics, data screening or assumptions, descriptive statistics, then inferential findings for each question or hypothesis. This structure helps the reader move from context to evidence.

Use research questions as the spine

The reporting order should feel predictable. If Research Question 1 asks about differences between groups and Research Question 2 asks about prediction, the results chapter should not jump to the regression first simply because it looks more advanced. Put the reader’s question first.

A clear reporting sequence often looks like this:

1. Brief chapter opening that states what the section reports.
2. Sample description, including usable responses or cases.
3. Missing data treatment or exclusions, if relevant.
4. Descriptive statistics for main variables.
5. Assumption checks, where required by your course or test.
6. Results for Research Question 1 or Hypothesis 1.
7. Results for Research Question 2 or Hypothesis 2.
8. Brief closing statement that points to the discussion without interpreting the findings at length.

This order works in many quantitative student projects because it mirrors the logic of analysis. The reader sees who or what was analysed, what the variables looked like, and how the tests answered the research questions.

Report descriptive statistics before inferential statistics

Descriptive statistics are numerical summaries of the data, such as mean, standard deviation, median, frequency, percentage, minimum, and maximum. They give the reader a first view of the data before any hypothesis test appears.

For example, in an education research paper on attendance and exam performance, descriptive statistics might show the average attendance rate, average exam score, and spread of scores. Only after that should the chapter report whether attendance significantly predicted performance. If the descriptive statistics are missing, the inferential result appears without context.

Use a table when you have several variables or groups. A paragraph is enough when there are only one or two simple values. If you are unsure what belongs in this first numeric overview, a resource on the descriptive statistics table concept can help you decide what to include and what to leave out.

Place assumption checks where they support the test

Assumption checks can appear before the relevant inferential test or in a short preliminary analysis subsection. Your choice depends on course requirements and how much detail your marker expects.

For a t-test, you may need to mention normality or equality of variances. For regression, you may need to report checks for linearity, multicollinearity, normality of residuals, and influential cases. Do not include every diagnostic chart from the software unless your assignment asks for it. Report the checks that affect whether the test is appropriate.

A business research paper on customer satisfaction and repeat purchase intention, for instance, might report that variance inflation factor values were within an acceptable range before presenting regression coefficients. That tells the reader the model was checked without turning the chapter into a software manual.

What tables and figures belong in a quantitative results chapter?

Tables and figures belong in a quantitative results chapter when they make the findings easier to read than prose alone. Use tables for exact values across variables, groups, or models; use figures for patterns, trends, distributions, or comparisons that are easier to see visually. Do not include both a table and a figure for the same simple result unless each serves a different purpose.

Choose tables for exact numbers

A table is best when readers need exact values. Use it for sample characteristics, descriptive statistics, correlations, regression models, group comparison results, or frequency distributions. Each table should have a clear title, consistent decimal places, and enough notes for the reader to understand abbreviations or test values.

For example, a psychology paper could use a table showing means and standard deviations for anxiety scores across low, medium, and high social media use groups. A nursing paper could use a table showing adherence rates by discharge education group. A management paper could use a regression table showing whether job autonomy predicts employee turnover intention.

Tables should not be screenshots from analysis software. Reformat them into clean academic tables that include only the values the reader needs. Software outputs often contain extra columns, labels, and technical details that distract from the finding.

Choose figures for visible patterns

A figure is useful when the shape of the data matters. Bar charts can compare group means, line charts can show change over time, scatterplots can show relationships, and histograms can show distributions. Use figures sparingly; a weak figure takes space without adding much.

Before inserting a figure, ask what the reader gains from seeing it. If the figure repeats one sentence — “Group A had a higher mean than Group B” — a sentence or small table may be enough. If the figure reveals a trend, spread, or non-linear pattern, it may deserve space.

For example, in an education paper comparing weekly quiz performance across a semester, a line chart may help readers see whether scores improved gradually or changed sharply after an intervention. In a health sciences paper, a bar chart may show differences in adherence categories more clearly than a dense paragraph.

Avoid table overload

Students often place too many outputs in the chapter because they worry that leaving something out looks incomplete. The better question is not “Can I include this output?” but “Does this output answer a research question, check a needed assumption, or describe the sample?”

Here is a useful table-selection filter:

Output from analysis	Include in main results?	Better choice
Full SPSS frequency table for every survey item	Usually no	Summarise key scale scores or relevant response categories.
Descriptive table for main variables	Yes	Include mean, standard deviation, range, and sample size where useful.
Screenshot of regression output	No	Recreate a clean regression table with coefficients, standard errors, p-values, and model fit.
Scatterplot showing a key relationship	Often yes	Include if it helps the reader see the relationship tested.
Diagnostic plot with no bearing on the written analysis	Usually no	Mention the assumption result briefly if required.

A results chapter is not an archive. It is a curated record of findings that answer the paper’s questions.

How do you report statistical tests without overexplaining them?

Report statistical tests by naming the test, giving the relevant statistic, degrees of freedom where needed, p-value, effect size if appropriate, and the direction of the finding. Keep the explanation focused on what the test found, not a tutorial on how the test works. Readers need enough information to evaluate the result and connect it to the research question.

Use a consistent sentence pattern

A statistical result is easier to read when the sentence follows a stable pattern. Start with the comparison or relationship, then give the test result, then state the outcome in plain academic language.

For a t-test, the pattern might be: “An independent-samples t-test showed that Group A had higher mean scores than Group B, t(df) = value, p = value, effect size = value.” For correlation, it might be: “A Pearson correlation indicated a positive association between X and Y, r = value, p = value.” For regression, it might be: “The model explained X% of the variance in Y, and X was a statistically significant predictor.”

Inferential statistics are tests used to make judgments about patterns, differences, or relationships beyond the observed sample. Statistical significance means that the observed result would be unlikely under a specified null hypothesis, based on the selected threshold. Effect size describes the size or strength of a finding, which can matter even when the p-value receives the most attention.

If you are still deciding which test fits your variables and research question, check a decision resource such as statistical test decision structure for student research before writing the final reporting paragraph.

Report p-values carefully

A p-value is the probability of obtaining a result as extreme as, or more extreme than, the observed result if the null hypothesis were true under the assumptions of the test. It is not the probability that the hypothesis is true, and it is not proof of an effect.

Weak reporting often sounds certain:

Weak: “The p-value was less than .05, which proves that motivation causes better grades.”

A stronger rewrite separates the result from the claim:

Stronger: “The relationship between motivation score and final grade was statistically significant, p = .032. This finding supports H1, although the correlational design does not establish causation.”

The stronger version does three things well. It reports the result, links it to the hypothesis, and avoids claiming causation from a design that cannot support it.

Include non-significant findings without apology

Many students try to hide non-significant results, but they are still findings. If a hypothesis was not supported, say so directly and accurately.

For example: “The difference in mean stress scores between part-time and full-time students was not statistically significant, p = .214.” That sentence is acceptable. You do not need to soften it with phrases such as “unfortunately” or “the test failed.” The result tells the reader what the data showed under the chosen analysis.

Non-significant results can still matter in the discussion, especially if they differ from prior literature, reveal limits in measurement, or suggest that the sample was too small to detect an effect. In the results chapter, however, the task is reporting quantitative findings, not defending them.

What does a results section example look like?

A results section example usually opens with sample information, presents descriptive statistics, then reports each test under a subsection tied to a research question or hypothesis. The wording is concise, numerical, and cautious. It refers to tables where needed and avoids explaining implications until the discussion.

Example structure for a student paper

Imagine a master’s business research paper asking whether perceived supervisor support predicts employee turnover intention among part-time retail workers. The methodology chapter has already described the survey, sample, variables, and regression model. The results section now needs to present the findings in a clean order.

A possible structure would be:

1. Sample description: number of usable responses, basic participant characteristics relevant to the research question.
2. Descriptive statistics: mean, standard deviation, and range for supervisor support and turnover intention.
3. Correlation result: relationship between supervisor support and turnover intention.
4. Regression result: whether supervisor support predicts turnover intention.
5. Hypothesis outcome: supported, partially supported, or not supported.

This structure does not need drama. Its job is to make the evidence easy to follow. If the paper has several hypotheses, repeat the pattern rather than inventing a new structure for each one.

Sample wording for descriptive statistics

Here is a short example of how descriptive results can be written without sounding like software output:

“Table 1 presents the descriptive statistics for the main study variables. Supervisor support had a mean score of 3.42 (SD = 0.81), while turnover intention had a mean score of 2.76 (SD = 0.94). The scores suggest moderate perceived support and relatively low to moderate turnover intention within the sample.”

This paragraph does not interpret the result as a business strategy. It simply reports the distribution of the measured variables. The final sentence gives a cautious factual description, not a theory.

If the paper used survey scales, make sure the scale direction is clear before the reader reaches the results. A mean of 4.2 means very different things depending on whether 1 = strongly agree or 5 = strongly agree. That information usually belongs in the methodology chapter, but the table note may repeat it if needed.

Sample wording for an inferential result

A concise inferential paragraph might read:

“A Pearson correlation was conducted to examine the relationship between perceived supervisor support and turnover intention. The analysis showed a statistically significant negative correlation between the two variables, r = -.46, p = .004. Higher perceived supervisor support was associated with lower turnover intention, supporting H1.”

A regression version might read:

“A simple linear regression was used to test whether perceived supervisor support predicted turnover intention. The model was statistically significant, F(1, 118) = 18.72, p < .001, and explained 13.7% of the variance in turnover intention. Supervisor support was a negative predictor of turnover intention, β = -.37, p < .001.”

These examples show a clear order: test purpose, test result, direction, and hypothesis outcome. The discussion chapter can later explain how these findings compare with employee retention literature.

What mistakes do students commonly make when writing a quantitative results chapter?

Students commonly make mistakes by reporting software output instead of findings, mixing results with discussion, overclaiming statistical significance, ignoring non-significant results, or using tables without explaining them. Most of these problems come from uncertainty about what the reader needs at each point. Fixing them usually means tightening the connection between research questions, variables, tests, and written claims.

Common mistakes and better alternatives

1. Pasting raw software output into the chapter
   Student example: “The ANOVA output is shown below,” followed by a screenshot with every SPSS row and column.
   Correction: Recreate the relevant values in a clean table and write a sentence explaining the main result. The reader does not need the software interface.

2. Making causal claims from non-causal designs
   Student example: “Stress causes lower academic performance because the correlation was significant.”
   Correction: Write, “Stress was negatively associated with academic performance.” Use causal language only when the research design supports it.

3. Reporting significance without direction or size
   Student example: “There was a significant result for the relationship between sleep and anxiety.”
   Correction: State the direction and, where appropriate, effect size: “Sleep duration was negatively correlated with anxiety score, r = -.31, p = .012.”

4. Leaving the research question invisible
   Student example: “A regression was conducted and the model was significant.”
   Correction: Link the test to the question: “To answer RQ2, a regression tested whether attendance predicted exam score.”

5. Treating non-significant results as failure
   Student example: “The hypothesis failed because p was greater than .05.”
   Correction: Write, “H2 was not supported, as the difference between groups was not statistically significant, p = .176.”

Why these mistakes weaken the chapter

These mistakes make the reader work too hard. A marker should not have to infer which table answers which hypothesis or whether a claim is based on a t-test, correlation, or regression. The chapter needs visible signposting.

The problem is often not that the analysis is wrong. It is that the writing does not translate the analysis into academic reporting. For undergraduate and master’s students, the safest route is to keep each subsection tied to one question or hypothesis and to use the same wording pattern across similar tests.

A clear results chapter also helps the later discussion. If the findings are vague or overclaimed, the discussion will either repeat the confusion or build an argument on unstable wording.

How can you revise a quantitative results chapter before submission?

Revise a quantitative results chapter by checking alignment, order, table quality, statistical wording, and separation from discussion. Read the chapter as if you are a marker asking, “Which question is being answered, what test was used, what did it find, and where is the evidence?” Any sentence that does not answer one of those questions may need moving, cutting, or rewriting.

Check alignment before polishing style

Polishing grammar before checking structure wastes time. First, compare the results chapter with your assignment brief, research questions, hypotheses, methodology chapter, and tables. The same terms should appear across these sections.

If your assignment brief required a specific structure, follow it. If the brief is flexible, use your research questions as the chapter’s organizing frame. Students who struggle to turn assignment requirements into section plans may find it useful to review assignment brief requirements turning into a paper plan before revising.

A good alignment check asks:

• Does every research question or hypothesis have a reported result?
• Does every table support a result that matters?
• Are the variables named consistently?
• Are the statistical tests the same as those promised in the methodology chapter?
• Are unsupported causal claims removed?
• Are discussion points moved to the discussion chapter?

Edit tables and paragraphs together

Tables and paragraphs should work as partners. The paragraph should not repeat every number in the table, and the table should not sit without explanation. Refer to the table, report the key result, and let the table carry the detailed values.

For example, do not write: “Table 2 shows the mean was 3.22, the standard deviation was 0.71, the minimum was 1.00, and the maximum was 5.00 for variable A; the mean was 2.98…” That sentence forces the reader through numbers already visible in the table. A better version is: “As shown in Table 2, mean scores were highest for perceived usefulness and lowest for perceived ease of access.”

Check decimal places too. In many student papers, two decimal places are enough for means and standard deviations, while p-values often use three decimal places unless p < .001. Follow your required style guide when one is specified.

Before you move on: quantitative results chapter checklist

• The chapter follows the order of the research questions, hypotheses, or objectives.
• The sample or dataset is described before inferential tests are reported.
• Descriptive statistics are included for the main variables.
• Each statistical test is linked to a specific research question or hypothesis.
• Tables are recreated cleanly rather than pasted as software screenshots.
• Figures are used only when they make a pattern easier to see.
• p-values are reported accurately and not treated as proof.
• Effect sizes or model-fit values are included where your course or test requires them.
• Non-significant findings are reported clearly rather than hidden.
• Discussion, theory comparison, implications, and recommendations are saved for the discussion chapter.
• Variable names match the methodology chapter.
• The final paragraph points forward to the discussion without interpreting every finding.