Handling Repeating Actions
The key to handling repeating actions is to use a combination of the best parts of both Shadow Plan and the built-in Tasks application. Shadow Plan is great for planning projects, for slicing and dicing the actions, collecting together other related information and viewing the results in different ways. The Tasks application is very good at handling repeat actions and can switch between categories very easily. Shadow Plan's ToDo links can integrate the two applications into a powerful GTD system.
In essence, Shadow Plan is used to plan all of the actions. The tags don't need to be used to define contexts, but it may help to do so. I use just a single tag to identify 'Next Actions'.
There is also a *Scheduled category, which is used to park any scheduled or repeat actions that are not currently due. Repeat actions have entries in Tasks since Shadow Plan cannot be configured with the details of their reoccurrence. Scheduled actions have an entry so that they are remembered when I carry out my daily review of scheduled actions.
Let's step through how each type of action is handled. They are:
- Ordinary actions, with no specific target date.
- Scheduled actions, that have a specific target date.
- Repeat actions, that are configured to recurr at set intervals.
Ordinary Actions
Adding the ToDo link means that the action will now appear in the Tasks application under the relevant context. When I mark the action as complete in Tasks it will be automatically completed in Shadow Plan too.
Scheduled Actions
An alternative to keeping linked copies of all scheduled actions in the Tasks *Scheduled category is to use Shadow Plan's 'Today's target items' filter and only link them to Tasks when they fall due. However my experience has been that it is quicker and easier to link them to Tasks at the time that the target date is first set.
Repeat Actions
Repeat actions are created in exactly the same way as scheduled actions, setting a target date in Shadow Plan and then adding a ToDo link to the *Scheduled category in Tasks. The recurrence details can then be set in the Tasks application. When a repeat of the action falls due it will appear at the top of the *Scheduled category during the daily review and can be moved to the relevant Context category.
When a Repeat Action is marked as completed in Tasks the additional step of moving its category back to *Scheduled is needed, ready for the next occurence. By the way, don't mark Repeat Actions as complete in Shadow Plan - it will cancel the action from Tasks completely, including all future reoccurences.