The notebook is the course
In a typical physical science class the lab report is an afterthought — a packet filled out from a worksheet, the answers half-copied from a partner, the conclusion a single sentence written on the bus. In this course the lab notebook is the spine of everything. It is where the prediction is recorded before the cart is released, where the measurements land in real time, where the calculation is worked out by hand, and where the student finally has to say what the numbers mean. When the student stands for a lab defense, the notebook is what they defend.
That changes how it must be written. A real physical science notebook is kept in pen, during the experiment, with mistakes struck through by a single line rather than erased — because a crossed-out wrong reading is data too. It is honest, contemporaneous, and complete enough that another student could repeat the work from it alone. This page lays out exactly what a strong entry contains.
If it isn't written down at the bench, it didn't happen. Memory is not data.
Anatomy of an entry
Every entry in this course follows the same skeleton. Learn it once and it becomes automatic — the structure does the remembering so the student can think about the physical science.
| Section | What goes here |
|---|---|
| Title & date | A specific title (not "Lab 4") and the calendar date the work was done. One experiment, one dated entry. |
| Question / purpose | One sentence stating what the experiment is meant to find out or measure — e.g. "Measure how the speed of a cart down a ramp changes as the ramp is raised." |
| Concept & prediction | The idea the experiment relies on, plus a specific numerical prediction written before starting — the expected time down the ramp, the spring-scale reading, or whether the bulb will light. |
| Procedure reference | A pointer to the written procedure ("see handout, steps 1–7") plus any deviation made on the day. Don't recopy the recipe — record what you actually did differently. |
| Data tables | Measurements as they happen, in ruled tables with a header row naming each quantity, its unit, and the precision of the instrument. Every number gets its units and the right number of significant figures. |
| Observations | Qualitative notes the numbers miss — the cart wobbling, the bulb flickering, a wire warming, a spring stretching further than expected. Time-stamped where it matters. |
| Calculations | The math worked by hand with units carried through — speed from distance over time, or the force read off the scale — and the final answer rounded to the correct significant figures. |
| Conclusion | A direct answer to the question, compared against the prediction, stated with its uncertainty. Did the result match? If not, why? |
| Error analysis | The real sources of uncertainty — stopwatch reaction time, ruler precision, friction on the ramp — their likely direction and size, and how they would change the result. |
And here is that template as a finished entry — one real Experiment Day, kept the way we hold students to. The struck-through note in the margin and the honest sources of error are the point: a real notebook shows the reasoning, not a tidy recopy.
| Added mass (g) | Time (s) |
|---|---|
| 0 | 1.42 |
| 100 | 1.40 |
| 200 | 1.43 |
Writing it right: the rules that matter
The structure is half the battle. The other half is a handful of disciplines that separate a physical science notebook from a science-fair poster:
- Units on every number. A measurement without a unit is not a measurement. "1.85" means nothing; "1.85 s" is data. The unit travels with the number into every calculation.
- Significant figures honestly reported. The precision of the answer is set by the least precise measurement. A ruler reading to 0.1 cm and a stopwatch to 0.01 s constrain how many digits the final speed may honestly claim — no more.
- Calculations shown, not just answers. The distance and time written down, the division set up, the rounding step — all visible. A right answer with no work is unverifiable; a wrong answer with clear work is diagnosable.
- Pen, in real time, struck not erased. Record at the bench, not afterward. A misread value gets one line through it, the correction beside it. The struck value stays — it is part of the honest record.
- Observations alongside numbers. The cart that caught for a moment, the bulb that dimmed, the spring that bounced — these are the clues that explain a result the math alone can't.
Data tables, sig figs, and error analysis
Three things make a physical science notebook specifically harder — and more valuable — than a general science journal.
Data tables with units and precision. Build the table before the run starts, with the columns and units already labeled, so that during a fast ramp trial the student is recording, not designing. Trial number, ramp height, distance traveled, time down — each with its unit in the header and its value to the instrument's precision.
Significant figures as a discipline, not a decoration. Sig figs are how a scientist tells the truth about precision. Reporting a speed as "1.0374 m/s" when the stopwatch only justifies three figures is a false claim of certainty. The notebook should show the measurement that limits the precision and round the final answer to match it.
Error analysis with direction and size. "Human error" is not error analysis. A real analysis names a specific source — reaction time on the stopwatch of about ±0.2 s, a ramp that was not quite level, friction slowing the cart — states whether it pushes the result high or low, and estimates how much. This is thinking about uncertainty in plain language, and it is exactly what a lab defense probes.
The lab-notebook defense
At checkpoints the student sits across from the instructor and defends an entry out loud. The questions are simple and devastating to anyone who only copied: Why did you set the ramp at that height? What's your prediction based on? Where does the biggest uncertainty come from, and which way does it push your answer? If you ran this again, what would you change? A student who kept the notebook honestly — who wrote the prediction first, recorded in pen, worked the math by hand, and thought about error — answers easily, because the answers are already on the page.
For the criteria the defense is scored against, see the course rubrics. For the safety and readiness routine that makes a strong entry possible in the first place, use the pre-lab checklist before every experiment.
Why this is AI-proof
A language model can write a flawless-sounding lab report. It cannot produce a contemporaneous record of your stopwatch readings, your struck-through misread, the wobble you noticed on the third trial, or the error analysis that explains why your particular result came in 1.8% high. The notebook's value is precisely that it is tied to a real hand at a real bench on a real day — and that the student can defend every line of it from memory. That is not a thing to be outsourced. It is the thing the whole course is built to develop.