Mind map for lecture notes that you can revise from

Capture the lecturer's claims

A lecture is an argument with a schedule attached, so notes that follow the schedule end up as a transcript you cannot revise from. Start with the claims instead, and write each one as a node label in your own words.

One branch per claim is the rule, and a claim has to be arguable. If you cannot imagine disagreeing with it, it is probably background the lecturer passed over. The Study Notes starter, one of the 13 templates Canvasola ships with, gives you somewhere to put these.

Build it live if the room allows it. Select the root and press Tab to add a child, Shift+Enter to add a sibling beside the node you are on, and type the claim as you hear it. When the lecturer speaks faster than you can type, open the rich note and use Dictate.

• One branch per claim, phrased so that you could argue with it
• The label carries the claim, the note carries everything else
• Background the lecturer skipped over is not a branch
• Six to ten claims is a normal lecture

Note: If a single lecture produces thirty branches, you are recording the schedule instead of the argument. Collapse the branches you did not follow with the chevron on the node, and add them afterwards from the reading.

Attach the evidence they used

Every claim rests on something: a definition, a worked example, a number, a case study, or a reading they told you to check. Make those the children of the claim node, so the branch you are reading is the claim and the leaves underneath are the reasons you accepted it.

A node label holds one line, so the detail belongs in the rich note attached to that node. Use its bulleted list, one bullet per figure, example or term, and switch to the numbered list when the steps run in an order you have to reproduce.

Mark the evidence that points at reading you have not done yet with one of the seven node icons. Later, Ctrl/Cmd+F while the map is active searches both labels and notes, so you can pull a term back on screen when the lecturer says something that rings a bell.

• Definition, example, figure, case study and reading each become a child node
• Bulleted lists inside the note keep one piece of evidence per line
• Node icons flag evidence that still depends on unread reading
• Words you did not catch belong in the note, never in the label

Note: Notes are for the evidence, not for a rewrite of the lecture. A rich note can hold up to 80,000 characters, so nothing has to be thrown away, but a note that becomes a second transcript is the most common way a lecture map stops being worth anything later.

Write your own question per claim

The node that makes a lecture map worth keeping is the one where you push back. Add a child node to the claim, title it with your question, and say exactly what is unclear: why the lecturer chose that method, or how the worked example would behave if the rate fell instead of rising.

Questions belong on the claim they come from, not in one list at the root. On a map you can see at a glance that one claim has three open questions and the rest have none, which tells you where the revision time should go.

Before the seminar, run Ctrl/Cmd+F while the map is active and search for the keyword your lecturer is likely to use. If the map already answers it, you know what to listen for. If it does not, that is the question you take into the room with a pen on the page.

• Question nodes reuse the wording of the claim they sit under
• Ask what would change the conclusion, not only what the definition is
• One question per node keeps the map scannable
• Take two questions per claim at most, or you will forget them

Note: A question you cannot phrase is not yet a question. It is usually a sentence with the word why in it, and rewriting it as a claim you could answer usually tells you what to look up.

Mark what you still do not understand

Most lecture maps are honest about three things: what was said, what was shown, and what you actually understood. The third one belongs on the map, because it is the only part that changes between two people listening to the same lecture.

Use the color palette for status rather than decoration. The 8-color palette plus the recent colors row gives you enough to set one rule and keep it: a color for claims you can restate, a color for claims that are still fuzzy, a color for questions you have answered.

Collapse what you have settled. The chevron on a node folds its branch away, and Collapse All and Expand All handle the whole map when you want a clean read of the structure. A map with every branch open tells the reader nothing about your own progress.

• Two status colors are enough: settled and unresolved
• Collapse resolved branches before you show the map to anyone
• A node with no children and no note is the one you never wrote down
• Rewrite a fuzzy label until you can say it out loud

Note: The map records your understanding, not the lecture. If you missed ten minutes, the map will be confident and wrong, so check it against your own recording or the reading before you rely on it in an exam.

Turn the lecture into a revision map

Revision wants a fixed order: the claims first, then the evidence in the notes, then the open questions. Presentation mode enforces that order. Press P and the first slide shows the root label; after that there is one slide per first-level branch, showing the branch label with its immediate children.

Rehearse that way, standing up. Expand one claim at a time, restate the claim in a single sentence, check the note for the evidence, and check the question node for what you still owe yourself. Then move to the next branch. It is faster than rereading pages.

After a live capture, press A to auto-arrange. That clears manual positions and re-runs the layout, which is exactly what you want when the tree grew sideways during the lecture. The minimap, toggled with M, gives you the whole map while you zoom into a single claim.

• Presentation mode shows the root, then one slide per branch
• Say the claim out loud before you check the note
• Questions are your revision checklist, not a summary of the lecture
• Auto-arrange with A after any live capture

Note: Presentation mode gives one slide per first-level branch, so a claim with five children still appears on one slide. Open the note separately when a branch needs the detail.

Compare with the reading list

A lecture map only holds what the lecturer said. The reading holds the rest, and the two belong side by side. Put a Reading List branch on the same map and give each item a child node for the claim it is meant to settle.

Then cross-link. A link tube between a claim and the reading item that supports it is the fastest way to spot a claim with nothing behind it, and a claim linked to two items is usually the heart of the lecture. Links work between any two nodes, and the app has no link-label editor, so name the link in the note of the branch.

If the reading list deserves its own tab, keep it in a second workspace tab and use split view to show both side by side with a draggable divider. The same shape works for a longer course, where the thesis guide shows how one root can carry a whole reading plan.

• Each reading item says which claim it settles
• Cross-links expose claims with no supporting source
• Split view lets you read both tabs at once
• Unresolved claims become the preparation for the next session

Note: The comparison is the point of the exercise. A claim you cannot match to a reading item, or a reading item that supports nothing you heard, is where the real gap sits.

A checklist you can reuse

• The root label names the lecture and the date
• Every first-level branch is a claim you could disagree with
• Each claim has at least one child holding its evidence
• Rich notes use bulleted lists for figures, examples and terms
• Every claim carries a question node in your own words
• Presentation mode has been used once as a rehearsal pass
• Claims are cross-linked to the reading items that support them
• One color rule for settled and unresolved is written down

Common mistakes to avoid

• Transcribing instead of claiming. A lecture map that follows the order of the sentences is a transcript, and transcripts cannot be revised from. Capture the claims first, then attach the evidence underneath.
• One branch per topic. A topic branch collects several claims and hides which one you understood. Split it until each branch holds a single claim you could argue with.
• Question nodes at the root. One list of questions at the root hides which claim is unresolved. Hang each question on the claim it belongs to so the gaps show where they are.
• Color by decoration. A different color on every branch makes color mean nothing. Reserve two colors for status and keep the rest of the palette for structure.
• Never coming back to the map. The value of the map arrives on the second pass, not the first. Open it again before the seminar and search for the keywords you expect to hear.

Frequently asked questions

How many nodes should a lecture map have?

Six to ten claims for a normal lecture, with the evidence underneath each. Past thirty nodes you are capturing sentences rather than arguments, and the map becomes hard to revise from. Collapse the branches you did not follow and add them later from the reading.

Can I record the lecture while I build the map?

You can dictate into the rich notes, which is useful when the lecturer speaks faster than you type. Canvasola does not record audio for you, so the recording still comes from your own device, and the map is the part you own afterwards.

How do I find a term again before the exam?

Press Ctrl/Cmd+F while the map is active. The search looks through node labels and notes, ranks the matches and lets you jump straight to the node. Searching for the term is usually quicker than trying to remember which branch it was on.

Is the map enough for revision on its own?

No. It holds the claims, the evidence you wrote down and your questions, which is a strong skeleton, but it does not replace the reading. Canvasola also keeps your work locally unless you turn on cloud sync yourself, so keep a copy of your notes elsewhere.

This guide is part of the mind map use cases collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.