To write a lab report, follow the IMRaD structure: title, abstract, introduction, materials and methods, results, discussion, references. The introduction sells the question, the methods let someone repeat the work, the results show what happened without interpreting it, and the discussion interprets without inventing. Use past tense for what you did, we or passive whichever your rubric allows, and keep raw numbers in figures and tables rather than paragraphs.
Conventions vary by instructor and department, and the lab manual and rubric decide the format — section order, voice, tense exceptions, citation style and length all flex. Every sample sentence, figure caption and budget share on this page is an illustrative placeholder for structure practice, never a real measurement, dataset or experiment. Numbers in brackets are slots for your data.
A lab report is a reproducibility document
Ask three students what writing a lab report involves and most will say "an essay about the experiment." That belief quietly costs more points than any missing unit. A lab report is a reproducibility document: its product is not a story or an argument but a working recipe. The reader is not being entertained or persuaded — the reader is being handed the controls. The fixed IMRaD order, the flat reporting voice, the past tense: all of it exists because reproducibility collapses the moment a report starts performing.
This is also why the lab report paper is graded by different reflexes than an essay or a research paper. An argument paper may build suspense; this genre may not. An essay can earn marks for flair; here, flair that obscures the procedure costs marks. The research-paper walkthrough covers papers whose evidence is other papers, and the general report guide covers reports that argue or recommend — the lab flavor on this page is the strictest member of the family, because it answers one standing question with every sentence: could someone repeat this?
Three consequences follow, and the rest of this page is them in detail. First, the methodology section matters more than students expect — it is the part a reader would actually run, so it gets written like instructions for a stranger, not a diary entry. Second, results report and discussion interprets; blur them and both sections lose marks. Third, honesty is structural: the trial that failed, the value that came out strange, the rerun nobody asked for — those belong in the report, not in the shredder. Writing lab reports well is mostly the discipline of keeping those three promises.
The IMRaD spine: what each section is for
IMRaD stands for Introduction, Methods, Results, Discussion — the spine nearly every lab report hangs on, wrapped in three connective pieces: the title, the abstract and the references. Each section has exactly one job, and knowing the job is most of the craft:
| Piece | Its job in one sentence | Failure mode graders flag |
|---|---|---|
| Title | Names what was studied and how, without decoration. | "Lab Report 3" — a title that describes the filing system, not the study. |
| Abstract | Compresses the whole report into one paragraph: aim, method, headline result, implication. | Written first, so it promises an experiment the final draft no longer contains. |
| Introduction | Sells the question: the background a reader needs, why it matters, and the aim or hypothesis. | A textbook summary with no aim statement at the end of it. |
| Materials and Methods | Lets a stranger repeat the work: materials, apparatus, procedure, analysis choices. | Quoted from the manual, or missing the conditions and replicate counts. |
| Results | Shows what happened, in figures and tables with units, without interpreting. | Interpretation leaking in — "which proves our hypothesis." |
| Discussion | Interprets without inventing: explain, compare, limit, propose the next step. | Brand-new data appearing, or error analysis missing entirely. |
| References | Credits the manual, models and prior work behind the ideas, in the style the rubric names. | In-text citations that never reach the list, and the reverse. |
The four-letter core can be memorized as four verbs: the introduction sells the question, the methods let someone repeat the work, the results show without interpreting, and the discussion interprets without inventing. If a paragraph in your draft does none of those four things, it is decoration, and lab reports mark decoration harshly. Keep the outline budgets honest as you draft — the research paper outline guide shows the budgeting mechanic, which transfers straight over.
Two connective pieces deserve one warning each. The abstract is written last, after the report exists, because its only job is to match the report — an abstract that promises more than the Results deliver is a broken contract on page one. And the references section is short but marked strictly: every idea that came from the manual, a textbook, a journal or a dataset gets a citation, and every citation on the list must appear in the text. Most science departments name a format — the APA paper format and MLA paper format guides cover the two students meet most, and the annotated bibliography guide shows the shape when your instructor asks for notes under each entry.
The IMRaD planner
The planner assembles the six report sections into a working plan: each section gets its job in one sentence, a starting share of the total word count, and two do's and one don't tuned to your course flavor — biology, chemistry, physics or psychology — and your report kind, because a field or observation study spends its words differently from an instrument or simulation analysis. Treat the percentages as a starting budget to argue with, not a law: the rubric decides. Nothing you build here is stored or sent anywhere, and the word counter keeps score while you write.
IMRaD planner
100% private — runs in your browserPick a course flavor and a report kind above, then build — the plan appears here with per-section budgets and do's and don'ts.
A starting budget, not a law: the rubric and lab manual decide the real split. Every bracket is a slot for your own data, and the plan is a structure to write against — not prose to transplant.
Filled example — biology · experiment write-up (illustrative)
Job: compress the report into one paragraph — aim, method, headline result, implication.
- "[The effect of (factor) on (measure) in (system)]" — name the system up front.
- One paragraph: aim, method, headline result with units, implication.
- No citations in the abstract.
Job: sell the question — background, why it matters, then the aim.
- Move from the biological question to your specific aim in three moves.
- Define the trait or process with a citation from your reading.
- No textbook-chapter retelling.
Job: let a stranger repeat the work — materials, conditions, replicates.
- Give the [organism or system source], plus conditions: [temperature], [light], [medium].
- State replicates: how many trials, and how they were chosen.
- Do not copy the handout wording verbatim — paraphrase your actual steps.
Job: show what happened, in figures and tables with units, no interpretation.
- Put every measurement in a table or figure with units — prose points at them.
- State n and what each figure panel shows.
- No "because…" sentences — reasons live in the Discussion.
Job: interpret without inventing — explain, compare, limit, propose.
- Compare your findings with the expected pattern and say where they diverge.
- Name one concrete source of error and the direction it would push the result.
- No claiming proof — evidence supports, it does not prove.
Job: credit the manual, models and prior work in the named style.
- Cite in the style your department names, alphabetized.
- Match every in-text citation to the list, both directions.
- No citing the lab manual alone for a claim from the literature.
Every bracket and value above is an illustrative placeholder — swap in your own experiment, your own numbers and your own reading before a single line reaches your draft.
Run one combo now, then run the combo closest to your actual course. The differences are the point: the planner hands psychology reports a Methods row about participants and scoring rules, hands physics reports a Results row about uncertainty propagation, and shifts word share toward the Introduction for field studies, where siting and observation design carry the argument. Those shifts are conventions — your rubric can overrule any of them, which is why the plan ends where it does and the writing begins.
Writing results honestly
Results is where lab reports are won and lost, and the rule sounds trivial until deadline night: report what happened, not what should have happened. That includes the runs that did not work. If trial three failed midway, the report says so — "the third trial was discarded after [the failure you observed], and the exclusion rule stated in Methods was applied" — because a reader who cannot see the failures cannot judge the survivors. Graders read silent omissions as selective reporting, which is the polite name for cooking data, and it is the one offense lab courses treat as unforgivable.
The second habit is division of labor: raw numbers live in tables and figures, not paragraphs. Prose in Results points — "mean [measure] was [value] before [the change] and [value] after (Table 2)" — while the table carries the full grid. A paragraph that recites forty readings is unreadable, uncheckable and a reliable sign the writer did not know what the data said. Figure captions work the same way: a caption states what is shown and under what conditions, in one or two sentences, and a figure without one is a point killed. Compare:
| Caption that kills points | Caption that survives |
|---|---|
| "Graph of results." | "Figure 2. [Measure] against [condition] for the three trials in Table 1; error bars show [the uncertainty your data carries]." |
| "Temperature vs time." | "Figure 3. [Quantity] in [unit] over [the time window]; [condition] held constant. The full series is in Table 3." |
| "Our data." | "Figure 1. Apparatus layout as actually used; labels match the steps in Methods." |
Uncertainty belongs in this section too. Every measured value carries some, and a result stated without it is a claim wearing a costume. You do not need statistics theater: you need the units, the spread your method allows, and one honest sentence about which measurement is least trustworthy. That sentence — the weakest measurement, named — is the kind graders circle with a happy pen, because it proves the numbers were produced by someone paying attention rather than by someone transcribing.
Voice, tense, and the we question
Can you use we in a lab report? It is the classic question, and the honest answer is: ask the rubric — it is the only authority in the room. Traditions genuinely split. Many courses, and most current research writing, accept first person without blinking: "we measured the [sample] every [ten minutes]." Others — often older syllabi, chemistry especially — expect the passive: "the [sample] was measured every [ten minutes]." Both are correct somewhere; neither is correct everywhere. What loses marks in both worlds is sliding between them: "we weighed the sample" in one sentence and "then it is added to the [flask]" in the next. Pick the voice your rubric names; if it names none, ask once, then stay consistent to the last line.
Tense has its own two-lane rule, and it holds no matter which voice you run: past tense for what you did, present for what the report says. The bench work is history — "the [solution] was heated," "we recorded [values]." The report is alive — "Table 1 shows the values," "Figure 2 compares the trials." The tell-tale mistake is a Methods section written in present ("the mixture is heated") for an experiment that already happened, or a table that "showed" something, as if it stopped. Present tense does legitimately appear where the report is doing something now — "these results suggest…" in the Discussion is present because the suggesting is happening on the page.
When the conventions flex, flex on purpose. Some rubrics ask the Introduction's design rationale in present; some departments want third person ("the experimenter") instead of either we or passive. All of that is negotiable by course. What is not negotiable is the drift — a report that changes voice or tense lane mid-section reads as written by committee, even when the committee was one tired person at 1 a.m. The drill below practices the two-lane rule and the person question on five illustrative sentences; every one is generic structure practice with [brackets], no dataset attached.
Voice and tense drill
Illustrative sentences — structure practice onlyLoading…
The section-purpose sorter
The fastest way to internalize the spine is to catch passages in the wild. Eight illustrative passages follow — two from each IMRaD section. Read the passage, pick the section it belongs to, and the why-line names the tell-tale signal: the tense of the verbs, whether numbers appear without verdicts, whether an aim statement closes the passage, whether interpretation hedges. Every passage is generic structure practice with [brackets]; none comes from a real experiment.
Section-purpose sorter
Illustrative passages — 2 per sectionLoading…
Weak vs strong, side by side
Three failures account for most of the red ink on lab reports. Each tab below pairs the weak version with the strong one and explains the difference in both directions, so you can see what the weak sentence does wrong and what the strong one adds. All drafts are illustrative structures with [brackets], written to be adapted, not transplanted.
Weak: "After [the change], the [values] doubled — which proves our hypothesis was right and the method worked perfectly."
Why it is weak: two violations in one sentence. "Proves" interprets — that is Discussion work — and "worked perfectly" is a self-grade, not an observation. Results also never "prove": one dataset supports a claim, and the proof word alone can cost the section its marks.
Strong: "Mean [measure] rose from [value] to [value] after [the change] (Table 2, Figure 3)."
Why it is strong: units, a table pointer, the trend in prose, and no verdict attached. The reader can find the numbers, check them and form a suspicion — which the Discussion then takes up on schedule.
Weak: "The results clearly demonstrate that [mechanism] is the only possible explanation, and future researchers will certainly find the same."
Why it is weak: "only possible" and "certainly" are certainties the data cannot carry, and not one limitation is acknowledged. A discussion that invents confidence instead of weighing evidence reads as salesmanship, and graders grade it as such.
Strong: "The shift is consistent with [mechanism], though [the rival explanation] was not controlled here; given [the limitation you name], the result supports a cautious version of the prediction."
Why it is strong: the four Discussion moves in three clauses — explain (consistent with a mechanism), compare (against the prediction), limit (rival explanation plus uncontrolled factor) — and nothing invented along the way.
Weak: "The procedure was followed exactly as written in the lab manual (pp. 12–14)."
Why it is weak: it records what you were supposed to do, not what you did — and what you did is the only thing Methods exists to record. Actual amounts, actual equipment, the step that deviated: all missing. This is quoting the manual instead of paraphrasing the procedure, and it is a flagged failure in nearly every rubric.
Strong: "The [apparatus] was assembled as described in the manual, with two changes: [the deviation you made] and [the substitution you used]; the volumes actually used are listed in Table 1."
Why it is strong: paraphrase plus the honest deltas. The changes from the stated procedure are exactly where reproducibility lives — a repeater following the manual alone would miss them — and graders read Methods hunting for precisely this level of truth.
Six point-killers and their fixes
Every card below is a shortcut the deadline offers. Flip each one for the fix — every fix is a structural move, not a wording patch.
Results bleeding into discussion
Tap to flip
Sweep Results for "because," "proves" and "suggests" — move each one to the Discussion. Results report; Discussion interprets. A single overlap sentence costs marks in both sections at once, which is efficient only in the bad direction.
Missing units
Tap to flip
Attach a unit to every number — in prose, in table headers, on axis labels. A value without a unit is not data; it is a guess in a lab coat, and graders treat it as one.
Unlabeled axes
Tap to flip
Every axis gets a quantity, a unit and a scale, and every figure gets a numbered caption naming what is shown and under what conditions. The test: a stranger reads the figure without asking you a single question.
Quoting the manual instead of paraphrasing
Tap to flip
Rewrite the procedure as you actually performed it — your amounts, your equipment, your deviations, in your own sentences. The manual is background reading; your methodology is your own account of what happened on your bench.
The failed run that vanished
Tap to flip
Report it: what happened, and the rule used to exclude it, stated in Methods. Silent omission reads as selective reporting — the one sin lab courses never forgive — while a reported failure with a rule reads as competence.
The abstract that promises a different report
Tap to flip
Write the abstract last, one paragraph: aim, method, headline result with units, implication. If it mentions anything the report does not contain — a condition you dropped, a result that moved — delete it on sight.
The eight-point report check
Run every draft through this list before submission — and once more after formatting, because formatting changes break figures. The bar fills as you tap, honest taps only.
- Every section does its own job — Results report, Discussion interprets, and neither borrows the other's work.
- Methods pass the stranger test: someone who never saw the manual could repeat the work from my account alone.
- Raw numbers live in tables and figures with units — prose points at them, it does not recite them.
- Every figure and table has a numbered caption naming what is shown and under what conditions.
- Failed or excluded runs are reported, with the exclusion rule stated in Methods.
- Tense follows the two-lane rule: past for the bench work, present for what the report says.
- Voice matches the rubric — we, passive or third person — and never slides mid-report.
- Abstract written last, one paragraph, and every in-text citation matches the reference list both ways.
Data collected, write-up stalled?
If the numbers are in but the report will not assemble, a quoted, deadline-bound writer can take the draft from methods to formatted references while the experiment stays yours. Get a free price quote and see the terms first.
Quiz: five questions before you submit
Five questions on report craft — section jobs, voice, honesty. No course-specific knowledge needed, and every wrong answer explains itself.
1. Which sentence belongs in a Results section?
2. Your rubric requires passive voice. What happens to "We poured the [solution] into the [flask] and heated it"?
3. What are Materials and Methods actually for?
4. Trial three failed midway through the procedure. The report should:
5. Where do raw numbers mostly live in a lab report?
Frequently asked questions
Can you use we in a lab report?
Often, yes — the rubric decides, and it outranks tradition. Many courses accept first person ("we measured the [sample] every [ten minutes]"), while some older syllabi, especially in chemistry, expect the passive ("the [sample] was measured"). Whichever your course names, use it consistently: sliding between we and passive mid-report loses more marks than either choice makes. Tense is a separate rule that does not flex — past for what you did, present for what the report says.
How long should a lab report be?
The rubric decides — always. Where no length is stated, the shape holds across sizes: Methods and Results together usually take half or more of the words, the Introduction around a fifth, the Discussion a little less, and the abstract stays one paragraph no matter what. If your Results are thin and your Introduction enormous, the balance is off before a single sentence is graded. The planner above hands you a starting split to argue with.
What goes in the discussion of a lab report?
Four moves, roughly in order: explain what the results mean, compare them with the expected pattern or published behavior, state the limits — error sources, uncertainty, uncontrolled factors — and propose the next step. What does not go in: new data, new analysis, and claims the results cannot carry. The discussion interprets without inventing; if a reader can point to a number you never reported, the section has wandered out of bounds.
What is IMRaD, and do I have to follow it exactly?
IMRaD is the standard lab report spine — Introduction, Methods, Results, Discussion — plus the title, abstract and references that wrap it. It exists because reproducibility needs a fixed order: question, recipe, findings, meaning. Most science courses require some version of it; a few ask for hybrids that fold the aim into the Methods or merge Results and Discussion into one section. The lab manual and rubric decide — when they name a structure, that structure wins over this page.
Do lab reports use past or present tense?
Both, in separate lanes. Past tense covers the work you did: "the [solution] was heated," "we recorded [values]." Present tense covers what the report itself is doing right now: "Table 1 shows the values," "Figure 2 compares the trials." The most common slip is Methods written in present — it reads like a recipe, not a record. The second most common is a table that "showed" something, as if it stopped showing it.
I keep searching write my lab report — what kind of lab report help actually exists?
Deadline panic makes that a common search, so it is worth knowing what legitimate help looks like. Your data, your figures and your raw numbers must be yours — that part is non-negotiable in any course. What lab report help can legitimately add is structure and craft: a TA or campus writing center can check that your Results report without interpreting, your voice matches the rubric and your abstract matches the report it summarizes. A model report — like the filled example in the planner above — earns its keep as a structure to adapt, never as a measurement to transplant.
Did this guide sharpen your report?