Student writing

Results Don't Match Theory? Good. That IS Your Discussion.

A Discussion section that says 'results are consistent with theory' when they clearly aren't is the fastest way to lose marks. Write the discrepancy. Name a mechanism. Stop apologizing.

You stare at the graph. Theory says absorbance should climb linearly from 400 to 520 nm. Your data says it spikes at 470 and then crashes. You type 'The results are consistent with the expected trend.' You delete it. You type it again. You delete it. You are now 45 minutes into your lab report and you haven't written one useful sentence, because you are trying to make numbers say something they did not say. Here is the thing nobody told you: the Discussion section was BUILT for this exact moment. A report where everything matches the textbook is a report where you learned nothing. Your 'failed' experiment is the best Discussion you will write all semester.

So why does every first draft start with a hedge? You write, 'It is possible that the results may have been influenced by some experimental errors which could have led to slight deviations.' Four hedges in one sentence. You have not identified a single mechanism. You have performed a ritual of self-blame and called it analysis. The marker reads that sentence and sees zero thinking. Compare: ❌ 'The deviation observed may be due to experimental error.' ✅ 'The absorbance peak shifted 22 nm below the literature value, consistent with a 0.03 M shift in buffer pH introduced during the cuvette preparation step.' The second sentence names a number, names a mechanism, and moves on. You do not need to apologize for the shift. You need to explain it.

Structure beats apology. The paragraph that gets full marks does not follow your emotional arc. It follows a four-beat move: (1) State the discrepancy as a finding, not a confession. (2) Propose the most likely mechanism, specific enough to be testable. (3) Identify one control or step that, if changed, would isolate that mechanism. (4) Close the claim inside its own evidence. No sweeping generalizations. No 'This proves that...'. Here is the ❌→✅ pair that saves you: ❌ 'These results suggest that the hypothesis was not supported, which is due to procedural inaccuracies.' ✅ 'The measured rate constant (1.2 × 10⁻³ s⁻¹) fell below the predicted 3.0 × 10⁻³ s⁻¹, consistent with incomplete catalyst activation at 60 °C; a preliminary 5-minute pre-heat step in the protocol may account for the 60% shortfall.' See the difference? The first one blames 'inaccuracies'—a word that means nothing. The second one gives the marker a sentence to disagree with. That is what Discussion means.

And here is the part that specifically wrecks international students: you reach for defensive English when the result contradicts the hypothesis, because the hypothesis feels like an authority you are failing to please. You write, 'We humbly acknowledge that our experimental design might have introduced certain factors that perhaps affected the outcome.' You sound like you are writing a complaint to a landlord. The detector is not your problem here. The problem is that every 'humbly' and 'perhaps' tells the reader you do not trust your own observation. easydue.ai exists for this exact rewrite—strip the apology scaffolding, keep the analytical claim. You typed the mechanism in your head. The English is just the part where you keep second-guessing yourself at 1 a.m. Paste the paragraph. Cut the hedging. Keep the specific number. That is the edit.

Do not over-explain, and do not blame everything on error. 'Experimental error' is the most useless phrase in undergraduate lab reports. Error is always present. Saying 'error' explains nothing. What you do: identify the specific step, the specific magnitude, the specific direction of the deviation. If you genuinely cannot identify a mechanism, say so plainly—one sentence, then move to the proposed next step. Do not pad three paragraphs of 'there could be multiple sources of error' because that is not analysis; it is stalling. A two-sentence honest uncertainty paragraph beats a 400-word fog. Your word count should track your thinking, not your anxiety.

The uncomfortable truth about lab report rubrics: the Discussion section carries the most weight precisely because it is where a 'clean' experiment gives you nothing to discuss. Students whose results matched perfectly write two paragraphs of textbook restatement and get mid-range marks. Students whose results surprised them—then explained the surprise—write one tight page of real thinking and get the high band. Your unexpected result is not a problem to hide. It is the only legitimate content you are allowed to generate in this section. Use it. Do not manufacture a false consistency. Do not write 'The results are in reasonable agreement with theoretical predictions' over a 40% deviation. That sentence is a lie you are telling yourself at 1 a.m. so you do not have to face the harder question: what actually happened in that beaker?

One last thing before you close the tab. Write the Discussion the way you would explain the result to your lab partner the morning after. Not 'It is observed that a deviation was noted.' Write: 'The peak shifted. I think it was the buffer. Here is the number that bothers me. Here is the one control I would run next.' That voice, that directness, is what the marker is grading. Not your apology. Not your caution. Your willingness to look at a number that does not match and say, out loud, what you think it means. easydue.ai is a draft cleaner, not a ghostwriter. It will not invent your mechanism. You do. But it will stop you from burying the one sentence that matters under four sentences of 'it is possible that perhaps.' You already know what happened. Stop writing around it.