Bullet Journaling
The Bullet Journal method (Ryder Carroll) — a system for rapid, structured note-taking in a plain notebook. The core idea: capture everything as short, signifier-tagged entries, then periodically migrate what still matters forward and let the rest drop.
Rapid logging
Every entry is a single line, marked with a signifier so its type is visible at a glance:
| Signifier | Meaning |
|---|---|
• |
Task |
X |
Task complete (fill in the bullet) |
> |
Task migrated forward |
< |
Task scheduled / moved to a collection |
○ |
Event |
– |
Note |
* |
Priority (added before the signifier) |
! |
Inspiration |
Entries stay short — a phrase, not a paragraph. If something needs more detail, it gets its own note entry directly underneath, indented.
The four core collections
Index — first few pages of the notebook. As you add a new collection, add its title and starting page number here. This is what makes an undated, freeform notebook navigable.
Future Log — a single spread split into 6 (or 12) boxes, one per month, for anything with a known future date that doesn’t belong in this month’s log yet (birthdays, deadlines, trips).
Monthly Log — opens each month: a calendar-style list of the month’s dates down one page (for events), and a task list on the facing page for things to get done that month.
Daily Log — the day-to-day rapid log. Add a date header, then log tasks/events/notes as they come up through the day, in order, no pre-formatting needed.
Migration
At the end of a day, review unfinished tasks:
- Still relevant? Rewrite it (
>) into tomorrow’s log, or if it’s not urgent, into next month’s log. - Belongs to a specific collection instead? Mark it
<and move it there. - No longer relevant? Leave it unmigrated — that’s the point. A task you keep declining to migrate is telling you something.
At the end of a month, do the same at the collection level: migrate the Monthly Log’s leftovers into next month’s log or into the Future Log.
Custom collections
Anything beyond the four core ones — a reading list, a habit tracker, meeting notes for a specific project, a packing list — is a “collection”: start it on the next open page, give it a title, and add it to the Index. There’s no fixed format; a collection is just a page (or spread) dedicated to one topic.
Threading
When a collection continues on a later page (e.g. project notes that span months), note the previous and next page numbers directly on the page:
Project Notes 42 <- this page
...continued on 78 ->
This keeps a topic navigable across a notebook without needing tabs or a rigid pre-planned structure.
Common additions (not in the original method, but widely adopted)
- Habit tracker — a grid, days across the top, habits down the side, filled in daily.
- Weekly spread — a lighter-weight layer between Monthly and Daily for people who plan weekly.
- Key/legend page — a personal reference for whatever signifiers and collections you’ve settled on, since most people extend the original set over time.
Why plain notebook over an app
The method’s value is mostly procedural, not tool-specific — rapid logging, migration, and collections work in any notebook. The common reasons people stick to analog for this: writing by hand forces the “is this still worth migrating?” filter the digital cut/paste doesn’t, and an undated notebook doesn’t punish you for missing a day the way a dated planner does.