Many trainers write a session plan for the file, then teach without reopening it. That is not a lack of discipline: the document written to justify is not the one that helps you conduct.
The phrase covers two very different objects, and confusing them explains most of the frustration.
The first is the compliance document: learning objectives, prerequisites, assessment methods, total duration. It addresses a funder, an auditor or a client. It is indispensable, and it is of no use during the session.
The second is the teaching score: what you do, in what order, with which material, and how long it takes. It addresses you alone, in the room, usually skimmed between two stretches of talking.
Writing the first does not excuse you from the second. Many trainers write only the first, keep the second in their head, and discover the problem on the day they are tired, the group drifts, or a colleague has to stand in.
A useful teaching plan fits on one page per half-day. Each line describes a sequence — a unit with a start, an end and a single objective — across four columns:
What you leave out matters just as much: no written content, no restated objectives, no methodological justification. All that lives in the other document.
A training day always takes longer than planned, and always in the same place: the exercises, never the lectures. An experienced trainer is rarely far off on the length of their presentation; they are consistently wrong about the practice.
Two habits absorb the gap:
Mark the optional sequences. A realistic plan contains ten to fifteen per cent of content explicitly flagged as droppable. Deciding in advance what you will sacrifice avoids deciding it at half past four, in a hurry and usually badly.
Set checkpoints. Two or three moments in the day where you write the real time next to the planned one. The gap then shows before it becomes unrecoverable, not at the end.
And note the actual duration on the plan itself, while it is fresh. That is what makes the next version accurate.
The plan is also where the day's rhythm — or its absence — becomes visible. Read flat, it immediately reveals long lecture blocks and afternoons with no interaction.
A few tested markers:
The most useful plan is not only read: it works as a dashboard. Each sequence points at the material it uses, and you go from the line to the material without hunting elsewhere.
Concretely, a line reading “exercise on joins” points at the exercise itself — not at a folder where you will have to find it. This is where the exercise bank and the plan complete each other: one files, the other orders.
The side effect is welcome: preparing the next day means duplicating the previous plan and replacing two or three lines. What took an evening takes twenty minutes.
A plan is not thrown away at the end of the day: that is when it acquires its real value. Three notes taken in the ten minutes that follow beat a report written a week later.
After three or four sessions, the plan is no longer a forecast but an observation. That is what separates a trainer who repeats the same day from one who improves it.
An exercise written once should serve ten times. Here is how to build a bank you can actually find things in, without spending more time than you save.
PedagogyInstalling an environment on twenty machines eats the start of every session. Here is how to write and run code in the browser, what it genuinely allows, and where the limits are.
PedagogySQL is learned by querying, not by listening. Here is how to put a real database in a group's hands without installing a server, and in what order to unfold the concepts.
Create your first interactive room in under 5 minutes. Free plan, no credit card.
Get started for free