Lecture handouts from the same sources as the deck
A lecture handout is not the slides printed six to a page. It is the two or three pages a student keeps after the session: the claims in full sentences, the definitions, one worked example, the reading pointers with page numbers, and a few questions. Write it from the same claim list and sources as the deck, in plain text next to the deck, and regenerate it when the deck changes.
This guide covers what a handout should do, a structure that works, the writing order, and how to keep the deck, the notes and the handout from drifting apart over a term.
What is the handout for?
Slides are for the room; they are terse because you are there to fill them in. A handout is for after the room: the student rereads it before the problem set and the exam, without you. So it needs full sentences where the slide has a fragment, the definition where the slide has the term, the example worked through where the slide has the setup. The printout of the slides fails at exactly this: it repeats the fragments and adds nothing.
A structure that works
# Week 5: Scheduling
## The point of this week
Two or three sentences: what the week establishes and why it matters for what follows.
## Claims
1. A scheduler trades throughput against response time … (Silberschatz 5.2)
2. Round-robin waiting time depends on the quantum … (5.3.4, fig. 5.5)
…
## Definitions
**Quantum.** … **Convoy effect.** …
## Worked example
Three processes, quantum 4: the Gantt chart, the arithmetic, the result, and what it shows.
## Read
- Silberschatz ch. 5.1–5.4 (skip 5.3.6 for now)
- Paper: … §3 only
## Check yourself
Five questions, answers at the end.
One to three pages. If it is longer, it is lecture notes, which is a different document with a different reader.
Write it from the claim list
If the deck was written from a claim list (one claim per slide, each with a source and location, as in lecture slides from your readings), the handout's Claims section is that list in full sentences. The definitions are the terms those claims use. The worked example is the one the deck sets up. The reading pointers are the sources on the list. The questions are the practice questions, or a subset. Nothing in the handout should come from outside the list; if it does, either the list is incomplete or the handout is drifting.
Order of writing
- Deck from the claim list.
- Speaker notes from the same sources.
- Handout: claims, definitions, example, readings.
- Questions, then attach them to the handout.
The handout comes after the notes because writing the notes tells you which claims need a full sentence and which definitions the room asked for.
Keeping the three in sync
The failure mode over a term is a deck edited in week 9 with a handout still from week 1. Three habits prevent it:
- Keep the deck, notes, handout and questions in the same folder, as text. A search for a term finds all four.
- When a slide's claim changes, search for the claim in the handout and questions the same day.
- Date the handout and print the date on it, so a student holding an old one can tell.
Version control helps here: a commit that touches the deck and not the handout is visible in the log.
Writing the handout with an assistant
Give the assistant the deck and the readings and ask for the handout in the structure above, with the source and location after each claim. Read the claims against the deck (nothing new, nothing missing) and the pointers against the readings (right pages). The assistant is good at turning fragments into sentences and bad at knowing which example the room needs; choose that yourself.
In Lecture Studio, a unit's folder holds the deck, an optional instructor guide, and any number of Markdown documents: New file › Markdown creates one with the topic as its heading, and the unit's chat writes into it from the readings attached to the unit and the course, citing them. Documents render next to the chat without the slide chrome. The app runs on macOS 15 or later and needs an Oberik project key; it is free during the beta.
FAQ
What should a lecture handout include?
The point of the session, the claims as full sentences with sources, the definitions, one worked example, reading pointers with pages, and a few self-check questions. One to three pages.
Should I give students the slides or a handout?
Both, but they do different jobs: slides are the record of the room, the handout is what they study from. A slide printout is not a handout.
When should I write the handout?
After the deck and the speaker notes, from the same claim list, and again whenever a claim in the deck changes.
Can an AI write a lecture handout?
It can draft one from the deck and the readings if you require a source after each claim. Check the claims against the deck and the pointers against the readings.