Task vs. Next Action in a Bullet Journal
A task names something you intend to do; a next action names the first visible step that moves a larger project forward. In a bullet journal, record that step as a task in the Daily Log when you plan to do it that day. For instance, change “plan weekend trip” into “list three nearby towns to compare.” The project can remain as a broader reminder elsewhere; the daily entry should tell you what to do when you sit down.
What’s the difference between a task and a next action?
A task is an actionable item in the bullet journal’s own terminology. The official Bullet Journal FAQ describes tasks as items represented by a dot bullet, while the Daily Log is a day-to-day place to record tasks, events, and notes. It also describes migration: unfinished tasks can be moved forward into a Monthly Log or Collection, or scheduled in the Future Log. These conventions tell you how to capture and track an item; they do not require every task to be the first step in a project. The official Daily Log page confirms that the date heads a page containing tasks, events, and notes; the next-action wording here is an editorial adaptation of that format.
“Next action” is a useful planning distinction. In Getting Things Done’s overview of its method, the David Allen Company says that when an item is actionable, you decide the next action and, when more than one action is required, the project. Taken together, these ideas give a practical rule: a project is an outcome that takes multiple actions, while its next action is one concrete move you can actually make. A next action is still a task when you write it in your journal; the term emphasizes its place in the sequence.
For example, “prepare a family photo book” describes an outcome, not a single sitting’s work. “Find the folder with last summer’s photos” is a next action if that is the first thing needed. After doing it, the next useful action may be “choose 20 photos for the book.” The project label can be helpful for remembering the larger result, but it does not tell you which move to make now.
How can you rewrite a vague project as an observable next step?
Use this short conversion sequence as an editorial decision aid. It is a practical synthesis, not a prescribed bullet-journal rule.
A quick test: could another person tell whether the action is finished from the wording alone? If not, add a concrete object, deliverable, or observable result. “Research venues” might become “Open the town events page and note its room capacity and booking contact.” That does not claim the venues will suit the event; it defines what the research step produces.
Worked example: represent a project in a Daily Log
Suppose you want to host a small book-club gathering next month. That outcome involves more than one action, so writing only “book-club gathering” in today’s log leaves the immediate move unclear. The example below is invented to demonstrate the distinction; it is not a report of an actual event.
Project reminder: Arrange next month’s book-club gathering.
Possible first action: “Message the group to ask which two evenings work for them.” The message being sent is an observable result. If you first need the contact list, “Find the book-club email thread” could be the actual first action.
A sample Daily Log for Tuesday, 12 May could include one task: “Message the book club to ask which two evenings work next month,” followed by the note: “Need replies before choosing a date.”
The dot marks the actionable item in the method’s notation; the dash marks a note. This sample follows the official Rapid Logging descriptions in the Bullet Journal FAQ, which identifies tasks with a dot and notes with a dash. The date and wording are illustrative. If you send the message, mark the task complete using the completion mark your journal follows. If you do not do it, decide whether it still matters and when it belongs. The FAQ describes migrating unfinished tasks to a Monthly Log or Collection, and scheduling an item in a Future Log; migration is a deliberate review step, not merely copying every unchecked line forward.
When replies arrive, “Choose a date based on the replies” becomes a new next action if it is now the clearest move. If no one responds, the next action could instead be “Send a follow-up asking for replies by Friday,” if that fits your plan. The next action can change as circumstances change; the journal records the current actionable move, not a fixed script for every future event.
Where should the project itself go?
The Daily Log is designed for day-to-day entries, according to the Bullet Journal FAQ. A multi-step outcome can be kept as a broader reminder in a Collection or another place you will review; the same FAQ describes Collections as groups of information and events you want to track and find later. Choose a location that fits how you use your notebook, and make sure you can reconnect the daily action to its larger purpose when you review it.
For a single-step item, the distinction may not matter. “Return the library book” can be both a complete task and the next action; it does not need a separate project label. The distinction is most useful when a line describes an outcome with several steps, an unclear starting point, or a dependency on information or another person.
A compact check before writing the bullet
Before putting an item in today’s Daily Log, ask:
If the line still reads like a topic—“trip,” “newsletter,” “gathering”—rewrite it as a move. That small distinction makes the Daily Log more useful at the moment of action while preserving the larger project for review.