Book a flight
Back to cockpit
Study Airlines · Inflight magazine

Cargo: notes that actually arrive at the exam

Most notes are never read again. Why a lecture note and an exam document are two different things, and what makes the second one usable.

21 August 2026

Most notes are written once and never read again. They are produced in a lecture hall, filed in a folder, and quietly replaced by something new in the week before the exam. The pages exist, the hand was busy for ninety minutes, and almost none of it reaches the desk where the exam is actually prepared.

The reason is rarely discipline. It is that the note taken during a lecture and the document needed in exam week are two different objects, and most students only ever build the first one.

Copying feels like understanding

Writing down a sentence you have just heard asks very little of you. You hold the words for a few seconds and put them on paper. Meaning is optional in that transaction, which is why you can fill a page about a topic and then discover you cannot say what the topic was.

The illusion comes from effort. The hand moves, the page fills, the folder gets heavier, and all of that registers as productive work. But the part of you that will need this material in six weeks was never asked to do anything. Nothing was decided, nothing was compressed, no connection between two ideas was formed. The lecture passed through you rather than into you.

There is a quick test. When a section ends, put the pen down and write one sentence in your own words about what was just claimed. If that sentence will not come, the page you just filled does not contain understanding either. It contains the lecturer’s sentences in your handwriting.

Raw cargo and finished cargo

The distinction is worth making explicit. A lecture note is raw cargo: taken in real time, under time pressure, incomplete by nature, shaped by whatever happened to be emphasised in that particular hour. An exam document is a different thing. It is built later and on purpose, with the exam in view, and it is organised for retrieval rather than by the order in which things were said.

Most people ask one document to do both jobs, and it fails at both. The lecture note is too rough to revise from. The effort of keeping it tidy during the lecture costs exactly the attention that should have gone into following the argument.

Separating the two removes a lot of pressure. In the lecture you are allowed to be scrappy, to leave gaps, to put two question marks next to the step you missed. The clean version is not due yet. It is due on the weekend, it is a different task, and it has a different purpose.

Notes that only work while the lecture is still warm

A note written in a lecture hall carries an invisible passenger: everything that was said out loud and never written down. At the time, three words are enough, because the rest of the explanation is still in the room. Two months later those three words are a fragment. “Careful: the second condition” means nothing. Careful about what, and why the second one.

This is the most common defect in student notes and the hardest to catch, because it only becomes visible late. The material looks complete every time it is filed and turns out to be unreadable exactly once, in the week it matters.

The repair is unglamorous. Within a day, while the missing half can still be recovered, read the notes back and turn the fragments into sentences that stand on their own. Someone who was not in the room should be able to follow them. In six weeks, that person is you.

One honest page per subject

For each subject, build a single page you would actually reach for. Not a summary of the script, which is the script again with smaller margins. A page in your own words: what the subject is about, which questions it answers, the four or five moves that keep coming back, and where you are still lost.

That last part carries most of the value. Summaries are usually written to look finished, so the unclear passages get smoothed over with a phrase from the slides that sounds authoritative and explains nothing. That smoothing is where exam surprises are manufactured. If you cannot say why an estimator is unbiased, write exactly that: “I can compute it, I cannot say why it works.” That line is usable. It tells you what to do on Tuesday. A confident paraphrase tells you nothing.

The page will be short, and the shortness is the point. At nine pages it is no longer a summary but a rewrite, and it will be avoided just as reliably as the script it was supposed to replace.

Notes that ask instead of store

Most notes are built as storage. A statement is recorded so that it can be found again later. The trouble with a stored statement is that it is easy to read and impossible to fail at. You look at it, it looks familiar, you move on.

A note phrased as a question behaves differently. “Definition of a stationary process” is a label. “What breaks if the process is not stationary?” is something you can be wrong about. Meeting the second version, you either produce an answer or notice that you cannot, and both outcomes tell you something.

None of this requires new software. It is mostly a question of how the left side of a page is written. Turn the labels into questions, keep the answers below a line or on the back, and the same material stops being something you can only stare at.

Where copying word for word is right

Copying word for word has a real place, and the rule against it is usually overstated. Where the exact formulation carries the content, write it exactly. Definitions, formulas, legal provisions, the conditions under which a theorem holds, the standard structure a lecturer expects for working a case: paraphrasing these deepens nothing and introduces errors. In law the wording of a norm is the object of study itself, and a note that captures only the gist of it is worthless. The same goes for an examiner’s scheme, which is usually a literal instruction about the expected shape of an answer.

The second limit is larger. A note system can become an occupation of its own. Colour codes, linked databases, folder hierarchies, a weekly ritual of restructuring: all of it produces visible artefacts, which is why it feels productive, and none of it is studying. Three evenings spent on the architecture of a note collection are three evenings not spent on the subject. The test is simple and mildly unpleasant. If the whole system disappeared tonight, would you know less, or would you only have less to look at?

Notes are cargo, and cargo is worth carrying only if something is unloaded at the far end. The rest is weight.

← All articles