How to Take Notes You Will Actually Read Again
The problem with most notes is not the tool, it is that notes are treated as a destination rather than a step. You write them during the meeting, feel productive, and never open them again. This guide describes a system that ends with notes being used: capture without thinking, structure once afterwards, and a review loop that forces them back in front of you.
Why most notes fail
Transcription is not note-taking. A wall of text written during a meeting preserves the sequence of what was said and almost none of why it mattered. The notes you will actually reuse are the ones you wrote after the meeting, when you knew what the important part was.
- Capturing during the meeting slows the meeting and captures the wrong things — logistics, not decisions.
- Never revisiting means the notes are a record of a moment, not a resource.
- Organising as you capture is the classic trap: it turns a five-minute job into a thirty-minute job and you stop doing it.
A system that survives a real week
- Capture raw and fast. One note per thing, no formatting, no filing. Friction at this step kills the habit.
- Process once, in a batch, later in the day. Highlight the two or three things that would matter if you were asked a month from now.
- Write those up in your own words. If you cannot restate it, you did not understand it — that is the real test of a note.
- Attach a next action to anything with a task in it. An un-actioned note is a guilt item.
- Review on a schedule. Weekly, ten minutes, and the only question is: which of these is now actionable or now wrong?
Shapes worth having
- Outline — hierarchical, best for anything with structure: a book, a course, a project.
- Cornell — notes in one column, questions in another, summary at the bottom. Best for lectures and reading.
- Zettelkasten — one idea per note, linked. Overkill for most people, excellent once you have thousands of notes.
- Plain dated log — chronological, no structure. Surprisingly effective, because it never has an organisation problem.
Tools for each step
Capture, structure, review and turn into something you can actually test yourself on — all in the browser, none of it needing an account.
All of these run in your browser — no account, no upload, free forever.
Commands for the processing step
Summarize Anything
Compress any text into a faithful summary at the length and reading level you choose.
Use it in: ChatGPT / Gemini / Claude · copy → paste → replace bracketed placeholders with your details
Compare Options
Build a weighted comparison table and give a clear recommendation.
Use it in: ChatGPT / Gemini / Claude · copy → paste → replace bracketed placeholders with your details
Checklist Project
Convert into an actionable checklist a project — e.g. a website redesign project due in 8 weeks.
Use it in: ChatGPT / Gemini / Claude · copy → paste → replace bracketed placeholders with your details
Plan Project
Turn into a realistic, sequenced plan a project — e.g. a website redesign project due in 8 weeks.
Use it in: ChatGPT / Gemini / Claude · copy → paste → replace bracketed placeholders with your details
Flashcards Concept
Produce spaced-repetition flashcards for a concept — e.g. the concept of eventual consistency in distributed databases.
Use it in: ChatGPT / Gemini / Claude · copy → paste → replace bracketed placeholders with your details
Explore the Full SlashAI Library
Every prompt in our guides is part of our offline-ready vault of verified commands and instant browser tools. Free forever, no account required.
Browse All Commands