GTD Calendar Rule

The GTD Calendar Rule gives the calendar a deliberately narrow role: it records actions tied to a particular time or day, along with information that matters on a particular date. Everything else that still requires action is organized elsewhere, chiefly on context-based Next Actions lists. The distinction protects the calendar’s credibility: an entry means that the commitment belongs on that day, not merely that it would be desirable to do it then.

What Belongs on the Calendar

The rule assigns the calendar three kinds of entries: time-specific actions, day-specific actions, and day-specific information. A time-specific action is an appointment, such as attending a meeting arranged to discuss a project. Recording the appointment is sufficient; the calendar does not need to become a general inventory of work associated with the project.

A day-specific action must happen on a particular date but need not occupy a particular hour. The example of calling Mioko illustrates the distinction: she will not have a report until Thursday and leaves the country on Saturday, so the call belongs on Friday. Any time that day will work, but moving the reminder to another date would lose the only useful window.

The third category is information to have available on a specific day, whether or not it calls for an action. This can include directions for an appointment, activities involving family or staff, or events of interest. A short-term reminder to call someone after they return from vacation also belongs here: its value depends on the date when it becomes relevant, not on a fixed appointment time.

Why the Calendar Is Not a Daily To-Do List

The rule rejects the traditional daily to-do list as a calendar function. New input and changing tactical priorities continually reshape the workday, so a list of tasks assigned in advance to Monday, for example, may quickly become inaccurate. If unfinished items have to be copied onto another day, the calendar becomes a record of repeated renegotiation, creating unnecessary work and discouragement.

As-soon-as-possible actions remain tracked, but they go on Next Actions lists rather than being preassigned to a day. This keeps them available as a working inventory while allowing the day’s actual demands to change. The system can still provide a game plan, but it must remain open to renegotiation instead of pretending that every desirable task can be scheduled with certainty.

The distinction also preserves the relative importance of genuinely date-bound commitments. If the Friday call to Mioko is placed alongside several less urgent calls on a daily list, a crowded day may cause the one irreplaceable call to be overlooked. A calendar entry instead signals that the action must happen that day or not at all. Under the rule, the only reason to rewrite an entry is a changed appointment; the calendar’s usefulness depends on treating its commitments as firm.

Context-Based Actions and the Next Physical Step

Most actions do not have to occur on a particular date. They should be organized by the context needed to carry them out: a computer, a location, a tool, or access to another person. An action requiring a computer goes on an At Computer list; stopping at a bank or hardware store while driving belongs under Errands; a face-to-face conversation with a partner such as Emily can be kept on an Emily list. The appropriate categories depend on how many actions need tracking and how often available contexts change.

Context is also a way to make the action itself concrete. At any moment, the first question is what can be done where the person is, with the tools and people available. If an action cannot be taken because the necessary place, tool, or person is unavailable, there is no need to keep reconsidering it in that moment. A person stuck in traffic, for instance, can consult the Calls list for actions possible by cell phone rather than sift through unrelated tasks.

This arrangement requires a next physical action to be identified before an item can be filed in the appropriate context. The action must be a visible activity that moves the open matter toward completion, not a vague project label. A miscellaneous list can weaken that decision by allowing an item to be filed without specifying what actually needs to happen. Organizing during inbox processing by the contexts actions require therefore helps translate projects into executable steps.

External Cues and Reliable Recall

The rule is part of a broader effort to keep reminders outside the mind and available when they can prompt action. A practical example is work that must be taken back the next morning: placing it in front of the door or on the keys makes it hard to leave without encountering it. The book calls this Put It in Front of the Door. The household object is a cue arranged in advance for a moment when memory may be unreliable; the same principle applies to the mind’s own “door,” where information should be positioned to surface at the right time.

A calendar can serve as a source of such timely prompts. Reviewing its entries for the next fourteen days may bring to mind an additional action associated with a date. Capturing that thought somewhere that will trigger action can clear attention and help the person respond when the information is useful, rather than relying on spontaneous recall.

The underlying process begins with clarifying the outcome and then naming the next physical action. An exercise asks the reader to identify the project or situation consuming attention, describe in one sentence what success would look like, and write down the immediate visible step. The examples range from taking a Hawaii vacation and resolving a college situation with Susan to implementing an investment strategy; possible next steps include making a call, writing an email, brainstorming with pen and paper, or having a face-to-face conversation. That brief conversion of concern into outcome and action is associated with a small increase in control, relaxation, focus, and motivation. The calendar rule gives such action reminders a place only when a date truly governs them; otherwise, the context-based list holds them until they can be done.

Review and the System’s Promise

A narrow calendar is trustworthy only as part of a regularly reviewed system. The Weekly Review calls for checking open projects and project plans, Next Actions, agendas, Waiting For, and Someday/Maybe lists, as well as collecting and organizing loose strands from recent days. The purpose is to let moment-to-moment choices rest on current reminders rather than forcing the mind to resume the work of remembering.

The resulting division is precise: the calendar marks the day’s hard edges, while context-based lists hold the actions that can be taken as soon as circumstances permit. The rule does not attempt to predict an entire day’s workload. Instead, it protects the few commitments that genuinely depend on a date and keeps the remaining actions ready for the contexts in which they can actually be performed.