🎓 EduPathHub
📝 In-depth guide Edited by Alex Lirik · 2026-11-15 · ~6 min read · 36 views

PhD Chapter 4 Findings: Justification paragraph missing

PhD Chapter 4 Findings: Justification paragraph missing

Yes, you can satisfy your supervisor’s “statistical justification” comment by weaving the rationale for each p‑value directly into the narrative of your results; a separate subsection is only necessary if your department’s style guide explicitly calls for it.

Do I need a separate subsection for statistical justification?

One common mistake is to treat the comment as a request for a stand‑alone “Statistics Explained” block. In most doctoral programs the findings chapter is expected to read like a story: you state the test, present the statistic, then immediately explain why that number matters for your hypothesis. If you simply list a table of coefficients and leave the reader guessing, the chapter feels unfinished, which is what triggers the supervisor’s note.

Consider two recent drafts. Student A added a new heading called “Statistical Justification” and pasted a paragraph that recited every assumption check, the alpha level, and a generic statement that “p < .05 indicates significance.” The reviewer marked it “redundant” because the same information already lived in the methods and the new section broke the flow. Student B, by contrast, went back to each result sentence, inserted a brief clause such as “this effect is significant (p = .032), supporting the prediction that X predicts Y,” and then added a single footnote referencing the relevant assumption checks. The reviewer praised the concise integration and noted no further justification was needed.

Unless your department’s template explicitly reserves a separate “Statistical Justification” section, the safest route is to embed the justification. Keep each justification to one sentence: state the test, the statistic, the p‑value, and the implication for the research question. If a result is marginal (e.g., p = .07), note the trend and why it still informs theory. This approach respects the narrative flow and shows you understand the meaning behind the numbers.

What terminology does my supervisor expect in the findings chapter?

The module guide typically circles terms like “effect size,” “confidence interval,” “statistical significance,” and “hypothesis support.” When you see “statistical justification,” the grader is looking for those exact phrases, not a vague “the numbers are important.”

Student C wrote, “The ANOVA yielded F(2, 57) = 4.21, p = .019.” The reviewer marked it “incomplete” because the effect size (η²) and the confidence interval for the mean difference were missing. Student D revised the sentence to, “The ANOVA yielded a significant main effect, F(2, 57) = 4.21, p = .019, η² = .13, indicating a medium effect; the 95 % confidence interval for the group means did not overlap, confirming hypothesis H1.” The reviewer approved the revision.

To hit the terminology targets, make sure each statistical result includes:

  • The test name (t‑test, ANOVA, regression, etc.).
  • The test statistic with degrees of freedom.
  • The exact p‑value (avoid “p < .05” when you have the precise number).
  • The effect size (Cohen’s d, η², R², etc.) if the rubric asks for it.
  • The confidence interval for the estimate.
  • A brief statement linking the statistic to the hypothesis.

When you embed these elements, the justification becomes automatic rather than an afterthought.

Which technical details most often cause a ‘missing justification’ comment?

The most frequent technical dead ends are:

  1. Omitting the effect size or confidence interval even though the methods chapter promised them.
  2. Reporting only “p < .05” without the exact value, which makes it impossible for the reader to gauge the strength of evidence.
  3. Failing to note whether assumptions (normality, homogeneity of variance) were met, especially when the methods section lists those checks.
  4. Presenting a table of raw output without any narrative tie‑in, leaving the reviewer to wonder what you think the numbers mean.

Below is a concise rubric that many PhD committees use for the findings chapter. Aligning your draft with each row will eliminate most “justification” flags.

CriterionWhat to includeCommon omission
Statistical test identificationExact test name and notation (e.g., t(34) = 2.45)Only “t‑test” mentioned
p‑value precisionExact p‑value to three decimalsUsing “p < .05”
Effect sizeCohen’s d, η², R², or odds ratio with interpretationLeaving it out entirely
Confidence interval95 % CI for means, differences, or coefficientsNever reported
Link to hypothesisSentence stating support or non‑supportOnly “significant” or “non‑significant”

When you cross‑check each result against this matrix, you’ll see exactly where the “justification” is missing.

How can I avoid integrity flags while rewriting my results?

Statistical sections are often scanned by similarity‑checking software because students sometimes copy‑paste output from SPSS or R. The software flags large blocks of unchanged output as potential plagiarism. To stay safe, rephrase the output in your own words and cite the software version.

Student E copied the entire SPSS output table into the manuscript, resulting in a 45 % similarity score. The committee asked for a rewrite, and the deadline slipped. Student F transformed the same output by summarizing: “The regression model explained 27 % of the variance in satisfaction (R² = .27, F(3, 96) = 11.84, p = .001).” He added a brief note, “Analyses were performed in SPSS v27.” The similarity score dropped below 5 % and the reviewer approved the revision.

Three practical steps to keep integrity intact:

  • Replace raw tables with narrative summaries; keep a compact table in an appendix if required.
  • Always write a short sentence that interprets the numbers before inserting the actual statistic.
  • Include a software citation in the methods or a footnote, e.g., “Statistical analyses were conducted using SPSS Statistics 27 (IBM Corp.).”

By converting the output into prose, you demonstrate understanding and avoid the red flag of duplicated text.

What’s a realistic 48‑hour plan to add justification and survive the internal review?

With only two days, focus on high‑impact moves. The plan below breaks the work into three short blocks, each with a concrete goal.

  1. Hour 1–2: Identify gaps. Print the findings chapter, highlight every statistical result, and mark where any of the rubric elements (effect size, CI, exact p‑value, hypothesis link) are missing. Use the table above as a checklist.
  2. Hour 3–6: Write justifications. For each highlighted result, add a single sentence that includes the missing elements. Example: “The t‑test showed a significant difference, t(28) = 2.87, p = .007, Cohen’s d = 0.68, indicating a medium effect; this supports H2 that the intervention improves scores.”
  3. Hour 7–9: Clean up narrative flow. Read each paragraph aloud; ensure the justification feels like a natural continuation, not a tacked‑on clause. Remove any redundant “statistical justification” heading.
  4. Hour 10–12: Verify technical compliance. Run a quick check that all assumptions are mentioned (e.g., “Levene’s test confirmed homogeneity, p = .42”). Ensure the software citation is present.
  5. Hour 13–15: Run a similarity scan. Use your university’s plagiarism checker on the revised chapter. If any block exceeds 10 % similarity, rewrite that block in your own phrasing.
  6. Hour 16–18: Final polish. Check formatting (APA 7 tables, italicized statistical symbols), proofread for typos, and confirm that the total word count of the chapter meets the program’s requirement.
  7. Hour 19–24: Rest and mental reset. Take a short walk, hydrate, and return with fresh eyes for a final skim before submission.

Following this schedule keeps you focused on the most critical elements—adding the missing justification, preserving narrative flow, and avoiding integrity issues—while leaving enough time for a quick sanity check before the internal review meeting.

Both the struggling path and the smoother path share a common thread: they treat statistical justification not as a separate chore but as an integral part of the story you’re telling. By aligning your language with the rubric terminology, filling in the technical details the reviewers flag, and phrasing the output in your own voice, you turn a potential rejection into a solid, defensible chapter. Use the checklist above, respect the table’s criteria, and you’ll walk into that meeting confident that the “missing justification” comment has been addressed.

Frequently asked questions

Do I need a separate subsection for statistical justification?

One common mistake is to treat the comment as a request for a stand‑alone “Statistics Explained” block. In most doctoral programs the findings chapter is expected to read like a story: you state the test, present the statistic, then immediately explain why that number matters for your hypothesis. If you simply list a t…

What terminology does my supervisor expect in the findings chapter?

The module guide typically circles terms like “effect size,” “confidence interval,” “statistical significance,” and “hypothesis support.” When you see “statistical justification,” the grader is looking for those exact phrases, not a vague “the numbers are important.” Student C wrote, “The ANOVA yielded F(2, 57) = 4.21,…

Which technical details most often cause a ‘missing justification’ comment?

The most frequent technical dead ends are: Omitting the effect size or confidence interval even though the methods chapter promised them. Reporting only “p Failing to note whether assumptions (normality, homogeneity of variance) were met, especially when the methods section lists those checks. Presenting a table of raw…

💬 This article was written based on a community question:

PhD Chapter 4 Findings: Justification paragraph missing? →

Related articles

PhD & Doctoral Study topic hubShould Your Table of Contents List Figures and AppendicesWhy Your EdD Literature Review Feels Like a Laundry ListYour 48-Hour Literature Review: Turning Research into InsightThe Surprising Shift from High School Writing to Doctoral StyleHow does research question specificity differ between a senior thesis and journal?Refusing Raw Data Requests: How to Cite Your Consent Limits

Related questions

Turnitin flagged my narrative essay as AI, how do I fix?APA 7 codebook formatting for rejected methodology chapter?PRISMA protocol flagged for similarity: is it fatal to my PhD?DNP capstone justification missing rubric help?

Have a question about college or student life?

Ask the community →
This guide was researched and reviewed by the EduPath Hub editorial team. Information is based on the original community question and may not reflect the most current developments. See our About page for details.