Decide what you want the notes to do
Start with the purpose of the notes. Are you trying to understand an article, prepare a brief, compare arguments, or remember why you chose an approach? Each purpose calls for a different structure. A short summary may suit a reference; a decision needs reasons and conditions.
Write the requested output before supplying material. For article notes, ask for the central argument, supporting evidence, qualifications and open questions. For a decision draft, ask for options considered, the proposed choice, reasons and unresolved issues.
Treat this as a drafting workflow with a human review step. Define what should be preserved exactly, what can be shortened, and what must remain uncertain. That gives you a concrete standard for accepting or revising the resulting notes.
Provide source material and clear boundaries
Use text you are permitted to share and identify its source. Include enough context to preserve the meaning of the passage: title, author, date and surrounding explanation when relevant. Keep the original separately so you can check the draft against it.
A useful request is: Organize the supplied text into notes. Separate explicit statements, interpretations and unanswered questions. Preserve names, dates and numbers exactly. Do not add missing details. Mark anything the supplied material does not establish.
These are instructions for the output you want, not guarantees about a product's behavior. Review whether the result followed them. When a detail matters to a decision, compare it with the original rather than relying on how confidently the draft presents it.
Use a structure you can review quickly
Choose headings that make omissions visible. A consistent structure helps you compare notes across sources without forcing every source into the same conclusion. Leave a heading empty when the material does not answer it.
For a reading note, separate the author's argument from your response. For a work note, separate an agreed action from a suggested action. That distinction keeps a convenient draft from becoming an inaccurate record of what somebody decided.
- Source: where the material came from and when it was published.
- Main point: the argument in plain language.
- Evidence: passages or details supporting that argument.
- Qualifications: limits, exceptions and unresolved questions.
- My interpretation: what the material might mean for my work.
- Next step: an action I have actually chosen.
Check the draft before making it your record
Read the draft alongside the source. Check names, dates, quantities and statements that affect your next action. Look for missing qualifications, especially words that change certainty, scope or responsibility. A compact note should retain the conditions that make a claim meaningful.
Keep quotations visibly separate from paraphrases. If you cannot locate a quotation in the original, do not preserve it as a quotation. If a conclusion combines several sources, identify which source supports each part.
Finish by checking decisions and actions. Did you actually approve the action, or was it merely proposed? Is an owner or deadline stated in the source, or added during drafting? Resolve those questions before sharing the notes or treating them as instructions.
Make continuity an explicit part of your process
Do not assume that discussing a detail once is enough for future work. Keep a record you can locate, inspect and provide again. This workflow does not depend on a particular chat memory setting, account configuration or retention promise.
For each lasting decision, preserve the choice, the reason, the relevant source and the conditions for reconsidering it. Before starting another task, locate that record and check that it still represents your position. This makes continuity something you can verify.
Keep only what earns its place. A useful lasting note answers a future question: What did I decide? Why? What evidence mattered? What remains unresolved? Working drafts can help you think; the approved record should make your actual position clear.
Use KnowMan for searchable reading and decisions
KnowMan gives you a knowledge base built from saved reading. Save articles through the browser extension or web app. KnowMan reads their full text and organizes them with automatic tags. Search also covers your highlights and notes.
Ask questions about saved reading and inspect the citations in the answer. Memories keep decisions and their reasons alongside the reading behind them. These features support a workflow in which your source, annotation and approved conclusion remain available for review.
Keep the connection boundary clear. This guide describes a manual note-taking workflow involving ChatGPT. For agent access to KnowMan over MCP, the listed clients are Claude, Codex, Cursor and your own agents. Agents can read Memories and save links, but cannot write Memories.
Build a routine around the plan you intend to keep
Begin with one useful article and one question. Save the article in KnowMan, inspect its contents, add your own note, and ask a question you can check against the source. Record a Memory if the reading leads to a decision worth keeping.
Free includes keyword search, highlights, notes, Memories and Ask capped at five questions a day. Pro adds semantic search; on Free, semantic search falls back to keyword search. Feeds, newsletters and ingestion rules are Pro features. Pro also supports export to Obsidian, Logseq and EPUB.
Every new account starts with a 14-day Pro trial, with no credit card required. Use that period to evaluate your real routine. Choose a repeatable question, review its sources, and decide which features help you return to knowledge you already chose to save.