How to Log a Complex Day With Four Bullet Journal Marks
To record a complicated day without building a complicated legend, use four marks: • for a task, ○ for an event, – for a note, and > for a task you decide to migrate. Put one short entry after each mark, then review unfinished tasks at day’s end. This keeps appointments, actions, and useful details distinct while leaving the page quick to scan. The example below uses a deliberately simplified key; the official method has additional task states, which you can add if they help.
What should the symbols distinguish?
The official Bullet Journal rapid-logging guide uses bullets to mark three kinds of entries: tasks, events, and notes. Tasks are actionable, events are tied to a date, and notes capture facts, ideas, thoughts, or observations that are not immediately actionable. Its standard marks are a dot (•) for a task, an open circle (○) for an event, and a dash (–) for a note. The official rapid-logging guide also describes short, objective wording as part of the approach.
Keep a small key and mark migration clearly
Migration is a review decision, rather than a fourth kind of daily content. The guide uses > to mark a task moved forward to a later Monthly Log or Collection, and < for one scheduled in a Future Log. For a compact daily key, you can reserve > for the simple question “Should this unfinished task move forward?” The destination should still be written beside it or made clear in the later log.
This is an editorially simplified key based on the official categories, not a claim that the notation is the only valid one. Keep the symbols stable through the day. If a note creates an action, record a separate task instead of stretching the note mark to cover both meanings. That small habit keeps later review easy.
Worked example: a day with appointments, tasks, and loose details
Imagine a day with a morning call, an agenda to send, an errand, a delivery update, and a new follow-up. These entries are illustrative; they show how to apply the key, not a reported real person’s day.
Tuesday, illustrative Daily Log:
Each line earns its mark by answering a different question. The call and review are dated events, even though they may also produce work. “Ask facilities” and “Email revised scope” are tasks because they require action. The room requirement and parcel closing time are notes: useful details that do not themselves say what to do. A compound line such as “review call, ask about the room, and send scope” would be harder to scan and harder to review; splitting it preserves the distinction without adding more symbols.
How to do the end-of-day migration
At the end of the day, inspect only the task lines that remain unfinished. For each, decide whether it is still relevant and where it belongs next. The official Daily Log instructions recommend reviewing entries after the day ends to identify notes that should be migrated for future reference or items that are no longer needed. The Daily Log page is dated, and entries can be added as they occur.
Continue the example: the agenda was sent and the parcel collected, so mark those complete if you use a completion mark. The “Ask facilities” task remains open because no estimate arrived. The room booking depends on that answer, so it remains open too. If both still matter tomorrow, carry them forward with > and write them in tomorrow’s log; keep the dependency visible: “Ask facilities for estimate” and “Book room when estimate arrives.” If the parcel note is no longer useful after collection, leave it behind rather than copying it. If the project scope email is already sent, it does not need migration.
The official system uses X for a completed task and > for a migrated one; its guide also includes < for tasks scheduled backward into a Future Log. Choose whether those task states belong in your key. If you want the fewest marks possible, use the basic four above and cross out completed tasks, provided your choice is unmistakable to you. If your notebook already uses the official X and <, preserve those meanings rather than assigning them new ones.
A small decision aid for ambiguous entries
When an item could fit more than one category, separate the information from the action. In the example, “Rowan needs the room estimate” is a note about the conversation; “Ask facilities for room estimate” is the task it suggests. Likewise, a meeting remains an event even when you add notes from it. This avoids inventing special marks for meetings, errands, decisions, or follow-ups.
Before adding another symbol, ask whether the existing marks already tell you what to do. The official guide says its three primary bullets are enough for most people and presents signifiers as optional ways to add context, such as priority or research. Start with the small key; only add a mark when a recurring distinction genuinely needs faster scanning. Nielsen Norman Group’s recognition-rather-than-recall heuristic recommends making needed information visible in digital interfaces. A journal is not an interface study, so the cautious editorial analogy is to keep a tiny key visible until your marks are familiar rather than relying on memory alone. See the official guide to rapid logging and signifiers.