How to Trace Every Reported Result into the Discussion Section

The basic rule for results and discussion

Every reported result should have a place in the discussion, even if the discussion is brief. The reader should be able to move from a number, figure, or table entry to an explanation of what it means in the context of the assignment. If a result never appears again, the report can feel like two separate documents stitched together.

This does not mean every data point needs a long explanation. It means the report should show deliberate follow-through. The discussion should refer back to the most important results and make clear why they matter within the bounds of the evidence shown.

• Ask where each result is interpreted
• Check that major tables and figures are discussed
• Keep discussion claims tied to the reported data

Use a result-by-result tracing pass

A practical method is to list the reported results in order and mark where each one is addressed in the discussion. The match might be explicit, such as a sentence that directly references a figure value, or it might be implicit, such as a paragraph that explains a trend shown in a table. Either way, the connection should be visible.

When you find a result with no discussion anchor, decide whether the result is minor enough to omit from emphasis or important enough to discuss. If it is important, add the connection. If it is not important, consider whether it belongs in the results section at all.

• Create a checklist of results, figures, and tables
• Mark the discussion sentence that explains each item
• Remove unsupported extra claims if they are not tied to a result

Watch for discussion drift

Discussion drift happens when the section starts interpreting things that are not actually in the results. That can include bringing in a new variable, a new comparison, or a new explanation that never appears in the reported data. The result is a section that sounds thoughtful but is not fully anchored to the report.

A consistency checker can help identify where claims, citations, or references to figures and tables no longer match the earlier sections. LabCrux focuses on that internal alignment, but human review is still needed to decide whether the discussion is educationally appropriate and properly supported.

• Tie each interpretive claim to a specific reported result
• Avoid introducing new evidence in the discussion
• Make sure every comparison comes from the report itself

Connect units, equations, and citations back to the discussion

Discussion sections often refer to calculated values, percent changes, or normalized quantities. If those are mentioned, the units and equations should be the same ones used earlier in the report. A mismatch here can make the explanation hard to trust, even if the underlying calculation was done correctly.

Citations should also remain consistent. If the discussion references a standard model, method, or published comparison, the citation needs to be present and correctly placed. That keeps the report internally coherent and avoids leaving the reader to guess where an idea came from.

• Check whether discussed values keep the same units
• Verify that any equation-based explanation matches earlier notation
• Make sure cited comparisons are actually cited in the report

A clean pre-submission review routine

Read the results section first, then read the discussion with a highlighter and connect every major result to a sentence or paragraph. If the path is weak, revise the discussion before submission. This is one of the most useful final-pass checks in undergraduate STEM and engineering writing because it catches missing interpretation and unsupported commentary at the same time.

Remember that consistency does not prove correctness. A well-aligned discussion can still be scientifically limited. The point is to make the report complete and readable, not to overstate what the data show.

• Trace every main result into the discussion
• Flag unsupported claims that have no result anchor
• Keep the discussion within the evidence shown

Sources and discussion

• University of Michigan: lab report rubric (official)
• Reddit: engineering students waiting for report feedback (community)

Community posts describe individual experiences and questions; they are not treated as universal proof.

Related resources

• /guides
• /tools
• /blog