Mapping a Study Plan Before the Exam, Not After
The Study Notes template gives you a Subject-to-chapter structure before you start reviewing, not after — a small habit that changes how revision actually goes.
"How do I organize my revision notes" is one of those evergreen searches that doesn't depend on any particular year or trend — students have been looking for a better way to structure what they need to cover before an exam for as long as there have been exams, and mind-mapping consistently comes up as an answer. Piskes's Study Notes template is a real, specific instance of that pattern, not a general claim about study tools.
The structure
The template starts you with a Subject node branching out into individual chapter nodes — Chapter 1, Chapter 2, and so on. It's a deliberately simple shape: one root, one branch per unit of material you need to cover. Selecting the template creates the map immediately, already structured this way, so you're adapting an existing skeleton to your actual course material rather than deciding from scratch how to lay anything out.
Why the order matters — map first, review second
The habit this template is built to support is specifically about sequencing: build the map before you start reviewing, not as a summary you write up after you've already gone through everything once. Laying out the full shape of what you need to cover first gives you something concrete to work against as you study — you can see the whole subject broken into its chapters at a glance, track which ones you've actually reviewed, and notice gaps before they become a surprise on exam day rather than after.
Building the same structure after the fact, as a wrap-up summary, is a different and less useful exercise — by then it's documentation of what you did, not a plan for what you still need to do.
Using it
If you've got an exam coming up, don't wait until you're deep into review to open a mind map. Start with the Subject → Chapters structure on day one, before you've reviewed anything, and let it be the thing you check off against as you go rather than something you build after you're already done.