Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong lab report makes the experimental logic traceable: the method is reproducible at the level the assignment requires, data are reported accurately with units and uncertainty where relevant, analysis distinguishes observation from interpretation, and the conclusion answers the stated question without claiming more than the experiment supports.
Lab report framework Title: [specific experiment] Question/aim: [x] Background/hypothesis if required: [x] Method: [materials, variables, procedure, deviations] Results: [tables/figures + factual observations] Analysis/discussion: [pattern + calculations + uncertainty + limitations] Conclusion: [answer supported by evidence]
Results paragraph The [measure] changed from [value + unit] to [value + unit] across [conditions]. [Main pattern]. [Anomaly or range]. These observations show [bounded result]; interpretation is reserved for the discussion.
Discussion paragraph Finding: [x]. Evidence: [specific result]. Explanation: [mechanism/theory]. Limitation: [specific source + likely direction/magnitude if known]. Comparison: [expected/reference relationship when required]. Implication: [what the experiment supports].
Lab-report audit Question answered? [ ] Method matches what was done? [ ] Units/figures checked? [ ] Results separated from inference? [ ] Uncertainty/limitations specific? [ ] Conclusion no stronger than evidence? [ ]
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].