VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Note-Taking Systems | Selection, Structure, Retrieval and Later Use

Three secondary students review open books and notes together in a classroom.

eduKateSG · Study & Learning Methods Hub · Note-Taking Systems · 1 October 2026

A note is useful only if it improves a later act: remembering, explaining, comparing, deciding, writing, solving or doing. That is why note-taking systems should be judged less by appearance than by what they allow the learner to recover after the original lesson or text has disappeared.

This guide owns WEP107 under eduKateSG’s Study & Learning Methods Hub. It does not replace the existing class-specific guides such as How to Take Notes in Class Effectively or the primary-school note-taking owner. Its distinct job is systems selection: when outlines, Cornell notes, maps, tables, question–answer notes, source notes or digital knowledge bases are useful, and how notes should change between capture and later use.

The evidence does not support one universal medium rule. A 2022 systematic review and meta-analysis of longhand versus digital note-taking found no overall performance difference under controlled conditions, while noting that distraction can help explain some apparent longhand advantages. See The effect of notetaking method on academic performance. Older meta-analytic work also found a modest positive encoding effect for taking notes, but with substantial variation across conditions. The design problem is therefore richer than paper versus laptop.

Notes are an external memory system, not a transcript

Notes are an external memory system, not a transcript is mainly about capturing enough structure to support later thinking rather than copying everything. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is writing the claim, evidence and one example from a lecture instead of every sentence. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is transcribing continuously until attention leaves the explanation. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the notes preserve the meaning needed for later retrieval. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Selection is the first note-taking skill

Selection is the first note-taking skill is mainly about deciding what deserves capture. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is recording a definition, a decision rule and an exception while leaving decorative detail out. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is writing everything because omission feels risky. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the learner can explain why each major note exists. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Compression forces structure

Compression forces structure is mainly about rewriting information in a shorter form that preserves the core relation. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is turning a paragraph into a two-line cause-and-effect statement. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is copying full textbook sentences. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the compressed note can be expanded accurately later. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Organisation should reflect the subject

Organisation should reflect the subject is mainly about using structures that fit how the knowledge is related. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is a hierarchy for taxonomy, a flow for processes and a table for comparisons. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is forcing every topic into one favourite template. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the structure makes the content easier to inspect. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

The Cornell system is a retrieval scaffold

The Cornell system is a retrieval scaffold is mainly about separating main notes, cues and summary so later review becomes active. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is turning left-column cues into questions during revision. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is drawing Cornell boxes but never using the cue column. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the page supports recall rather than decoration. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Outline notes fit hierarchical material

Outline notes fit hierarchical material is mainly about using indentation to show levels and dependencies. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is organising a history lecture into event, cause, evidence and consequence. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is outlining material whose relationships are mainly spatial or cyclical. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the hierarchy mirrors the knowledge. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Mapping notes fit relationships

Mapping notes fit relationships is mainly about using nodes and links where connections matter. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is mapping how monetary policy affects rates, demand and inflation. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is drawing a colourful web with unlabeled relationships. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the arrows or links carry explicit meaning. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Tables fit comparisons

Tables fit comparisons is mainly about placing comparable attributes side by side. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is comparing mitosis and meiosis across purpose, stages and products. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is using prose paragraphs for repeated attribute comparisons. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that differences and similarities become visible at a glance. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Flow notes fit processes

Flow notes fit processes is mainly about showing sequence, branching and feedback. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is drawing the stages of an experimental procedure with decision points. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is using a flowchart for a list with no sequence. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the visual form matches the process. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Question–answer notes fit retrieval

Question–answer notes fit retrieval is mainly about turning content into prompts rather than summaries alone. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is writing ‘Why does increasing surface area speed a reaction?’ with a separate answer. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is rereading a dense summary repeatedly. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the note naturally generates self-testing. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Worked-example notes need decisions, not just steps

Worked-example notes need decisions, not just steps is mainly about capturing why each step was chosen. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is annotating a mathematics solution with method-selection cues. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is copying the final worked solution only. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the learner can reconstruct the method on a new problem. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Error notes deserve a separate status

Error notes deserve a separate status is mainly about recording mistakes that reveal a reusable misconception. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is keeping an error log entry showing the wrong rule, the trigger and the correction. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is mixing mistakes into ordinary notes until they disappear. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that future practice can target the misconception. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Meeting notes and study notes are different jobs

Meeting notes and study notes are different jobs is mainly about separating decisions and actions from conceptual learning. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is capturing owner, deadline and decision in a project meeting. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is using lecture-style notes for a meeting and losing the action items. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the note supports the next task. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Reading notes should be delayed enough to require thought

Reading notes should be delayed enough to require thought is mainly about pausing after a section and writing from memory. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is closing the book and summarising the argument before checking. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is copying highlights line by line as you read. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the note reflects understanding rather than selection by highlighter. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Lecture notes have time pressure

Lecture notes have time pressure is mainly about balancing listening and capture. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is using abbreviations for examples while marking unclear points to revisit. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is writing so much that the next explanation is missed. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that attention remains on the live lesson. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Digital and longhand are tools, not identities

Digital and longhand are tools, not identities is mainly about choosing based on task, distraction control and later workflow. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is typing structured notes quickly in a fast lecture while using handwriting for a diagram-heavy tutorial. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is claiming handwriting always learns better or laptops are always superior. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that method choice is based on evidence and context. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

The 2022 meta-analysis weakens simplistic longhand claims

The 2022 meta-analysis weakens simplistic longhand claims is mainly about recognising that device type alone showed no overall performance difference under controlled conditions. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is choosing the format based on distraction and task rather than folklore. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is telling every student handwriting is automatically superior. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that advice reflects the meta-analytic evidence. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Distraction is a separate variable

Distraction is a separate variable is mainly about distinguishing note method from notifications and multitasking. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is using a laptop in full-screen note mode with unrelated apps closed. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is blaming digital note-taking for losses caused by switching tasks. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the study environment controls avoidable distraction. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Copy-paste is a special digital risk

Copy-paste is a special digital risk is mainly about recognising that frictionless capture can remove processing. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is pasting a quotation only when the wording itself matters and adding your own interpretation. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is collecting pages of copied material and calling it notes. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that borrowed text is surrounded by a reason for keeping it. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Searchability is useful only with good naming

Searchability is useful only with good naming is mainly about creating retrieval-friendly digital structure. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is using consistent filenames, headings and tags for a semester. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is saving notes as random documents with generic titles. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the learner can find the right note quickly months later. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Links can preserve provenance

Links can preserve provenance is mainly about keeping source identity attached to ideas. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is recording the page number or URL beside a key claim. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is collecting claims without knowing where they came from. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that later verification is possible. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Highlighting is not note-taking by itself

Highlighting is not note-taking by itself is mainly about using highlighting as a selection signal that must be processed later. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is highlighting one sentence and turning it into a question or summary. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is marking half the page in colour. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the highlight leads to a later cognitive action. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Annotation is local conversation with the source

Annotation is local conversation with the source is mainly about placing short questions, connections and objections near the material. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is writing ‘evidence?’ beside a claim and returning to verify it. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is filling margins with paraphrases that add no thought. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that annotations capture a decision or question. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Revision notes should become smaller over time

Revision notes should become smaller over time is mainly about compressing after understanding grows. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is reducing a chapter to one page of cues before an exam. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is rewriting the textbook repeatedly. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that later notes represent stronger organisation. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Retrieval should begin from cues, not the full note

Retrieval should begin from cues, not the full note is mainly about using headings, questions and blank diagrams as prompts. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is covering the answer column and recalling aloud. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is reading the page from top to bottom every review. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the note becomes a testing device. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Spacing determines when notes are reopened

Spacing determines when notes are reopened is mainly about returning after forgetting begins. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is reviewing on multiple days with progressively less support. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is reviewing five times on the same evening. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that notes support durable memory across time. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Interleaving changes note use

Interleaving changes note use is mainly about mixing cues from related topics so selection matters. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is testing similar grammar structures in mixed order. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is reviewing one topic until the answer pattern is obvious. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the learner must identify which knowledge applies. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

A note archive needs pruning

A note archive needs pruning is mainly about removing duplicated or obsolete material. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is merging three weak summaries into one canonical concept note. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is keeping every version forever because storage is cheap. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the archive stays navigable. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Evergreen notes are for ideas that continue growing

Evergreen notes are for ideas that continue growing is mainly about maintaining a stable concept page across courses and projects. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is updating a note on opportunity cost with examples from economics and everyday decisions. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is turning every temporary class note into an evergreen knowledge base. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that only genuinely reusable concepts receive long-term maintenance. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Project notes should track decisions and uncertainty

Project notes should track decisions and uncertainty is mainly about capturing what was chosen, why and what remains unresolved. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is recording the rejected alternative beside the final design decision. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is saving only the finished answer. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the project can be reconstructed later. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Source notes and synthesis notes should be separate

Source notes and synthesis notes should be separate is mainly about distinguishing what a source said from what the learner concluded. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is keeping a literature note for one paper and a synthesis note comparing several papers. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is blending paraphrase and personal conclusion until provenance disappears. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that claims can be traced. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

AI-generated notes need verification

AI-generated notes need verification is mainly about using AI to organise or condense only after source accuracy is checked. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is asking AI to propose headings for notes you already understand. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is accepting generated notes without reading the source. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the learner remains accountable for meaning and evidence. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Notes should eventually disappear during performance

Notes should eventually disappear during performance is mainly about using notes to build capability rather than permanent dependence. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is solving exam problems without the formula sheet after structured review. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is designing notes so complete that the learner never practises without them. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that independent performance increases. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

The right system is the one that survives later use

The right system is the one that survives later use is mainly about judging notes by retrieval, transfer and action. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is finding a concept quickly and explaining it after three weeks. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is choosing a beautiful system that is never reopened. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the system earns its maintenance cost. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Review notes by purpose, not by age

Review notes by purpose, not by age is mainly about keeping old material only when it still supports a current task. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is retaining a well-structured concept note while archiving last semester’s duplicated lecture capture. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is deleting everything old or preserving everything forever. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the archive reflects future use rather than sentiment. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

A good note distinguishes certainty levels

A good note distinguishes certainty levels is mainly about marking what is known, inferred, unresolved or disputed. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is using labels such as source claim, interpretation and question in research notes. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is writing all statements with equal confidence. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that later synthesis can separate evidence from assumption. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Cross-linking should reveal a real relationship

Cross-linking should reveal a real relationship is mainly about connecting notes only when the relation will help future retrieval or reasoning. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is linking opportunity cost to trade-offs and constrained choice because the concepts genuinely interact. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is creating dozens of links merely to make the knowledge graph dense. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that each link carries a reason. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Version control matters for evolving notes

Version control matters for evolving notes is mainly about preserving meaningful changes without confusing old and current conclusions. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is dating a policy note when a rule changes and keeping the prior version archived. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is editing over an old claim with no record of what changed. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that the learner can tell which information was current when. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

Notes can support collaborative learning

Notes can support collaborative learning is mainly about making shared notes explicit about ownership and verification. The note system should reduce future work by making structure visible, not create a second course of clerical labour. Every extra symbol, colour, folder and tag has a maintenance cost. If a feature does not improve retrieval, interpretation, provenance or action, it is probably decorative rather than functional.

A practical example is one group member records source evidence while another checks the interpretation before synthesis. The example shows why format should follow the information. A comparison table makes repeated attributes visible. A flowchart exposes sequence. A question–answer card creates retrieval. A source note preserves provenance. The learner gets more value when the structure of the note mirrors the structure of the future task.

The common failure is merging everyone’s text without knowing who verified what. Notes feel safe because they leave a visible record of effort. That visibility can hide weak learning. A notebook can be immaculate while the learner cannot explain the concept without opening it. A digital vault can contain thousands of highlights while no usable knowledge has been retrieved from them.

The acceptance test is that shared notes remain auditable enough for the group to trust them. The strongest note systems become progressively less necessary. Early in learning, notes carry more support. Later, cues become shorter, retrieval becomes harder, and the learner performs without the page. Notes are therefore scaffolds for knowledge, not proof that knowledge has been built.

A five-stage note lifecycle

  • Capture: record only enough information to preserve the lesson, source or decision.
  • Structure: organise the material into hierarchy, sequence, comparison, relation or question according to the subject.
  • Clarify: repair unclear phrases, add provenance and distinguish source claims from your own interpretation.
  • Retrieve: convert headings and cues into questions, blank diagrams, summaries from memory or changed examples.
  • Compress: merge and shrink notes as knowledge becomes more organised and independent.

Choosing among common systems

SystemBest useWatch for
CornellLectures and readings where later retrieval questions matter.Drawing the layout but never using the cue column.
OutlineHierarchical explanations, definitions and nested topics.Forcing non-hierarchical material into artificial levels.
Concept mapRelations among ideas, systems and causes.Unlabelled links that look connected but express no relation.
Comparison tableCases sharing the same attributes.Using a table when the important structure is sequence or causation.
Flow noteProcesses, algorithms and decisions.Drawing arrows without specifying what causes or follows what.
Question–answerRetrieval-heavy revision and definitions.Reducing complex explanation to isolated trivia.
Source noteResearch and evidence work.Losing page numbers, URLs, dates or the boundary between quotation and interpretation.
Evergreen noteConcepts that continue to grow across projects.Promoting every temporary note into a permanent knowledge object.

Frequently asked questions

Is handwriting better than typing?

Not universally. The 2022 meta-analysis found no overall performance difference under controlled conditions. Task demands, distraction, speed, diagram needs and later workflow matter.

What is the best note-taking system?

There is no context-free best. Choose the structure that matches the information and the later task: hierarchy, comparison, process, relationship, retrieval or source verification.

Should I copy everything the teacher says?

Usually no. Selection and compression are part of note-taking. Capture exact wording only where the wording itself matters, such as a definition or quotation.

Are Cornell notes good for every subject?

No. They are useful when cues and summaries support later retrieval. Geometry, laboratory work or systems thinking may need diagrams, tables or flow structures instead.

How should I use notes for exams?

Turn them into cues. Cover answers, redraw diagrams from memory, answer questions, explain concepts and solve problems without the notes before checking.

Should I rewrite my notes neatly?

Only if rewriting adds structure, compression or correction. Pure recopying often consumes time without enough retrieval or thinking.

Can AI create my notes?

AI can help organise or compress material, but generated notes should be checked against the source. If the learner never processes the source, the neat summary may become borrowed understanding.

How many colours should I use?

As few as needed to encode a useful distinction. Colour should carry a function, such as definitions versus examples, not become the main work.

What should I do with old notes?

Merge durable concepts, archive source material you may need and delete duplication. A note system should remain searchable rather than becoming a museum of every study session.

How do I know whether my notes are good?

Close them. If the cues help you retrieve, explain and apply the material later, the notes are doing useful work.

The quiet conclusion: a note should make future thinking cheaper

The most expensive note is not the one that took ten minutes to write. It is the one that took an hour, looked finished and never helped the learner remember, understand or act. Good notes are selective enough to capture meaning, structured enough to reveal relationships and spare enough to invite retrieval.

The mature note system therefore becomes quieter over time. Capture becomes more selective. Summaries become shorter. Cues replace full answers. Provenance becomes clearer. And eventually the learner can close the notebook and do the work. That is when the notes have succeeded.