Tree outliner for notes and plans

Flat notes hide the shape of the work. You open a folder of meeting-final-v3.txt files and still cannot tell what depends on what. A tree outliner fixes that by making hierarchy the interface: topic → subtopic → detail, editable like a table of contents you actually use.

SEO Note is a free Windows outliner built around that model. One local file, tree on the left, editor on the right. No account. It will not replace a team wiki or a phone-first app — and it does not try to.

What the tree is for

Good in a tree

• Projects with nested decisions
• Plans you reorganize often
• Reference you look up by topic
• Long notes split into children

Better elsewhere

• Live multi-user editing
• Kanban with assignees
• Phone capture on the go
• Huge media libraries

Why hierarchy helps thinking

The left panel is a map; the right panel is a page. You see both at once. Moving a subtree moves the whole topic — useful when “Acme” becomes “Acme / Phase 2” overnight. Naming nodes also forces clarity: a branch called stuff under a client is a visible smell, not a buried file name.

• Overview without scrolling a 40-page mega-document
• Depth where it belongs (checklists under a milestone, not mixed into the brief)
• Search that still respects structure — you land on a node, not a random paragraph in a pile
• Export of one branch when you share, instead of your whole private archive

How SEO Note implements the outliner

• Left panel — tree of articles (nodes)
• Right panel — editor for the selected node (plain text / rich text / HTML)
• Bookmark panels — several independent trees in one file (Work vs Personal is the usual split)
• Hotkeys — Insert (child), Ctrl+Shift+Insert (sibling), F2 (rename), Ctrl+F (find)

Install size is small (~2.45 MB). You save one data file wherever you like and copy that file for backup.

Build a useful tree in one sitting

1 Create roots: Inbox, Projects, Reference, Archive

2 Add only active projects as children

3 Dump today’s mess into Inbox

4 File Inbox under the right parent

5 Save the file; copy it once to USB

A practical tree for work

Work
  Inbox
  Clients
    Acme Corp
      Brief
      Meetings
      Deliverables
      Invoice notes
  Internal
    Processes
    Snippets
  Someday
  Archive

Keep Someday so unfinished ideas do not pollute active client branches. When a project ends, drag the whole client subtree under Archive — do not leave dead branches next to live work.

A practical tree for home / study

• Health — appointments, insurance numbers, questions for the doctor
• Money — recurring payments, warranty info (not passwords in plain sight if the PC is shared)
• Learning — courses with nested lecture notes; exam prep as a sibling, not buried inside one lecture
• Travel — packing lists and booking references

Uneven depth is fine. One course may need five levels; a packing list may be a single node with bullets. Force symmetry only when it helps you find things.

Outlining habits that scale

1. Capture fast, structure later. Dump into Inbox, then file under the right parent. Stopping mid-call to invent the perfect path is how notes never get written.
2. Prefer depth over mega-pages. When a note grows past a screen or two, split children: Context, Decisions, Open questions.
3. Stable roots. Rename leaves freely; rename top-level folders rarely so backups and muscle memory stay recognizable.
4. Titles that mean something next month. “Notes from call” ages badly. “Acme — scope change 12 Aug” ages well.
5. Export when sharing. Send HTML/RTF of a branch, not the whole private file.
6. Back up the file. See the USB backup guide.

Rule: if you cannot say the parent’s job in one phrase, the tree is already too vague — rename or split before adding more children.

A 20-minute practice session

Open a throwaway file (or a throwaway branch) and rehearse the gestures you will use every day. Create five siblings under a fake project, nest two of them, rename with F2, then drag a subtree to another parent. Search for a word you just typed. That muscle memory matters more than reading another feature list.

When the practice feels boring, you are ready for the real file. Boring is good: outlining should be quiet work, not a second job of configuring plugins.

When the tree goes wrong

• Everything under one client. Meetings, invoices, and personal reminders share a parent — split by job, not by “where it arrived.”
• Duplicate titles. Three nodes named “Notes” mean you will open the wrong one. Add a date or a verb.
• Archive avoidance. Active Projects stays long; you stop scanning it. Archive is not deletion — it is how the map stays readable.
• Deep for depth’s sake. Five levels for a two-line reminder is theatre. Flatten until each click earns its place.

Repair is usually a drag-and-drop afternoon, not a migration project. That is the outliner’s quiet advantage over a folder of files with locked names.

Outliner vs notebook apps

	Notebook apps	Tree outliner (SEO Note)
Mental model	Pages / notebooks	Hierarchy first
Strength	Free-form, often sync	Deliberate structure, local file
Account	Often required	Not required
Best when	You need phones + collab	You need overview + depth on Windows

OneNote and Evernote shine at free-form pages and sync. An outliner shines when reorganizing is part of the work. SEO Note picks the outliner side on purpose. More context: OneNote offline alternative.

Honest limits

• No live collaborative editing
• No built-in AI chat over your vault
• Mobile is not the design center — desktop Windows is
• You must open the file and maintain the tree; plugins will not do that for you

Mini FAQ

How deep should the tree go? Deep enough that each node has one job. If a child title repeats the parent, flatten. If a node needs three scroll screens, deepen.

One file or many? Start with one. Split only when Work and Personal need different backup rhythms — or use bookmark panels for two trees in the same file.

What about passwords? Treat the outliner like any unencrypted document: fine for context, risky as your only password store.

Can I outline plans and notes together? Yes — plans as checklists under a project node, narrative notes as siblings. Separating “plan” and “note” into two apps usually creates two half-truths.

Next steps

1. Install SEO Note and create one file with Inbox / Projects / Reference / Archive
2. Move today’s three most important scraps under Projects or Inbox
3. Rename any node still called “New” or “Notes”
4. Copy the file once to another disk or USB
5. Schedule a weekly empty-Inbox pass (15 minutes is enough)

If you want hierarchy you can move with the mouse and own as a file, download SEO Note free and grow the tree from Inbox outward.

Related: Free notes manager · Notes organizer · Offline notes · Quick Start · FAQ