[HiramNetherlands]

Would this be a good idea? Many tasks, like calling business relations, can only be taken care of during office hours. A check box in the Date pane could make sure that such tasks were not displayed as 'available' after office hours and in weekends. This would reduce the number of items in my 'phone', 'mac' and 'errands' contexts a lot on Saturday mornings such as this one.

Of course, the user would define local office hours. A 'shopping hours' check box might be useful, too.

[markbrown00]

A period of time in which you can or can not do a task, for whatever reason, sounds pretty much like a context to me. You could do some nested contexts like "office hours > errands" and "non-office hours > errands".

[HiramNetherlands]

Originally Posted by markbrown00

A period of time in which you can or can not do a task, for whatever reason, sounds pretty much like a context to me. You could do some nested contexts like "office hours > errands" and "non-office hours > errands".

You are probably right. I just discovered that in this case, nested contexts make sense (top level: all phone calls; just one sub level: calls that can also be made outside office hours), whereas, for instance, nesting 'home alone', 'home with lovely wife' and 'home with others' under an abstract top level 'home' would be useless. As you can see, I am only just beginning to think about GTD principles.

[markbrown00]

Ah yes, I see, HiramNetherlands. That's good way to do it.

I find that with any GTD system it is next to impossible to control for every possible context. Rather, you have to work out what context distinctions have the most importance for you, and make those contexts the center of your system. It sounds like the office/home distinction makes a big difference to you, and therefore should feature heavily in your context structure.