Quote Originally Posted by mladensk
Also, what about things that don't have to be done ON a specific day but rather BY a specific day. Again, let's use taxes as an example. In Canada personal taxes are due by April 30th. Client brings in there stuff (this is a project, I assume), the next action is to enter data into tax program. Where do I record this next action? On my calendar? In an action list?
If entering the tax data is the next action, and that needs to be done by a certain date, and if you know how long it ought to take, then it's a good idea to drop something in your tickler or on your calendar that says that it should have been started, just in case.

If you are reviewing your context lists, though, you will probably realize that it needs to be started if time is running out, especially if your list says something like "Enter tax data for so and so for 8/14 deadline."

I think that the key here is finding the right place and format for the reminders. I mean, if putting a duck egg under the sink will remind you to enter that tax data, then that's the right thing to do. A next action can be terse or detailed, but as long as it reminds you to take the appropriate action and is in a place where you will review it then you are likely to succeed.

I use a paper tickler file like David described in his book. For things like this I'll put in a slip of paper that says "You should have started..." or "This is due on..." a few days before the due date so I know to go back and work on the "real" action item, which I may be avoiding or simply unable to get to - but now I have a heads up that it needs special attention. My tickler gets emptied on my desk every morning, and its contents are hard to ignore. Even if I never glance at my calendar, these things keep me honest.