How to mind map a semester of study

Start from the module list

A semester is a known quantity before it starts: a list of modules, each with contact hours or credits. That list is the first level of the map, and the only part of a term that is fully known on day one. Starting there means later decisions are about how the term fits together.

Keep the module names exactly as your university writes them, because you will search for them in emails and reading lists. Add a child under each module for the topics you already know, and add branches with Tab and Shift+Enter as the term reveals them.

The map is the whole term in one view, and a map of the term is the thing most students never draw. The guide for students covers the other habits this map fits into, and the study mind map template gives you a shape to start from.

• Module names exactly as the university writes them
• One first-level branch per module
• Add topics as the term reveals them
• The map is the term in one view, not a list of modules

One branch per assessment

Coursework is what the term is judged on, so give each assessment its own branch instead of hiding it inside a topic branch. You want to answer "what is due and when" from the first level, and see the weight of an assessment next to the others.

Name the branch with the task and its position: "Dissertation proposal", "Midterm", "Group presentation". Under it, hang the parts: the question, the reading, the draft, the submission. That structure turns an assessment into a sequence of small pieces instead of one heavy block, and it is the structure you can carry into a week.

When an assessment turns out to be shared across two modules, which happens with group work, Shift+Tab moves the branch back to the level where it belongs. The branching rules cover keeping those sibling labels parallel.

1. List every graded piece. Add one first-level branch per assessment, using the name from your course handbook.
2. Break it into stages. Under each assessment, add the question, the reading, the draft and the submission as children.
3. Move shared work once. If an assessment spans two modules, lift the branch with Shift+Tab and re-file it where you can see it.

Weekly sub-branches under each topic

Under each topic branch, add a child for each week the topic is scheduled in, then a grandchild for what that week covers. The result answers "what am I supposed to have learned by week six" without a separate timetable, and it makes gaps obvious: a week branch with no children is a week you will meet unprepared.

Keep the depth to three levels, since deeper nesting is where a map stops being scannable. If a week needs a fourth level, the detail belongs in the note. Rename a node with Enter or F2 and re-parent it with Shift+Tab as the term moves on.

Collapsing helps here more than in a shorter map. Fold a topic branch with the chevron on the node and the term view returns to modules and assessments, the level you want when deciding what to do this week.

• One child per teaching week, one grandchild per session topic
• Stop at three levels of depth
• A week branch with no children is a gap, not a rest
• Fold a topic branch to get back to the term view

Note: A semester map is often the first map you build with more than 100 nodes, so use the minimap and search early rather than scrolling.

Put dates and weights in notes

Dates and percentages are the details that change and that everybody forgets. Put them in the node note rather than the label, because a label reading "Essay 60% due 3 March" is unreadable at a glance and becomes wrong the moment the deadline moves.

Node notes hold rich text, so you can paste the brief into a bulleted list, add the submission link, and dictate a note while walking. Each note takes up to 80,000 characters. Keeping the brief in the note means the map is a record of what was asked, not a label you look up again in week nine.

When a deadline changes, edit the note and the label stays clean. Search finds notes as well as labels with Ctrl/Cmd+F, so "essay" pulls up every branch and every note that mentions it. The notes guide covers the panel and the link button.

• Date, weight, word count and brief link in the note
• Labels stay readable when the deadline moves
• Dictate a note when you are walking between classes
• Ctrl/Cmd+F finds every mention of an assessment

Color by topic or by assessment

The 8-color Coggle-style palette can carry one scheme for a whole term, and you have to pick one. Color by topic and the map reads as disciplines; color by assessment and it reads as load, with the heavy assessments standing out. Topic coloring is easier to live with in week one.

The mechanics are simple. Press C to cycle the color of the selected node, and the first child inherits its parent's color while siblings cycle through the palette, so a whole branch arrives colored. Set the color on the first-level branch and the rest of the branch follows without extra work.

Keep the rule in the root note so you remember what each color means in week eight, and check the map once without color: if a branch disappears, its label needs more work.

• Pick one scheme: by topic, or by assessment weight
• Set the color on the branch, not on every child
• C cycles the color of the selected node
• Write the color rule in the root note

Re-check the map every week

The review method for a semester map is a weekly load check. On a fixed day, open the map, look at what is scheduled for the coming week, and count what each week is asking of you. Then read the notes on the assessment branches and check the dates and weights against reality.

Update the map as you go rather than rebuilding it. The 2D layer tabs scope the map to one layer, so you can work on a single module while the rest of the term stays out of the way, and a map holds up to 8 layers, enough for a normal set of modules plus one for revision.

Mark the milestones with node icons so the fixed points stay visible. Each node can carry an icon from a fixed set of 7, enough to mark a submission, an exam and a deadline. At the end of the term the map becomes a record of the whole course, and the weekly check is what keeps it true.

• A fixed fifteen-minute check, on the same day each week
• Count the work in each week, not just the topics
• Use layer tabs to work on one module at a time
• Node icons mark submissions, exams and deadlines

A checklist you can reuse

• One first-level branch per module, named as the university names it
• One first-level branch per assessment
• Each assessment branch breaks into question, reading, draft, submission
• Weekly sub-branches sit under the topics, three levels deep at most
• Dates, weights and brief links live in node notes
• One color scheme, written in the root note
• The map is re-checked on a fixed day each week

Common mistakes to avoid

• Assessments buried in topic branches. A percentage that hides three levels down is a percentage you forget. Give every assessment its own first-level branch.
• Deadlines in the label. A label with a date in it becomes wrong the day the date moves. Keep the date in the note and the label short.
• Four levels of nesting. Depth past three levels is where a map stops being scannable. Move the detail into notes instead of adding a level.
• No weekly review. A semester map drawn in week one is a plan, not a record. Fifteen minutes a week turns it into the truth about your term.
• Too many colors. If every module has its own color, the palette stops meaning anything. Pick one scheme and hold to it.

Frequently asked questions

How many modules can one semester map hold?

A single map holds up to 2,000 nodes, so a term of six modules is never the limit. If the map becomes hard to navigate, use the 2D layer tabs to scope it to one module at a time, with a maximum of 8 layers available. The limit that matters is whether you can still read the first level.

Should every topic get its own branch?

No. Branches should carry the parts of the term you act on: modules, assessments and the weeks that need work. A topic that appears once in a week can be a child of that week branch. If you have more than about eight first-level branches, something is one level too deep.

Can I keep a separate map per module?

You can, but a single map with layers is usually better, because the workload between modules is the thing you cannot see otherwise. Put each module on its own layer, keep the assessments on a shared layer, and use the layer tabs to work one module at a time.

What do I do when the plan changes mid-term?

Move the branch, do not rebuild the map. Shift+Tab lifts a node to its parent, Enter or F2 renames it in place, and the notes hold the current dates. A map edited every week stays useful, while a map rebuilt from scratch loses the history you wanted to keep.

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