Can a next action have both an Errands context and a due date?

Hasan Bjaili

Hasan Bjaili

Registered
Can a next action have both an Errands context and a due date?

Suppose I have the following next action:

Buy printer ink
Context: Errands
Due date: Friday

If I am already out running errands on Tuesday, should this action appear on my Errands list even though it is not due until Friday?

My understanding is that the due date indicates the deadline, while the Errands context indicates that the action can be completed while I am out. However, the action itself already makes it obvious that I need to go to a shop, so I am questioning what practical value the generic Errands context adds.

Would you assign both a due date and an Errands context to this action? If so, how do you use the Errands context in practice without confusing the due date with the date on which the action becomes available?
 
Hasan Bjaili said:
Can a next action have both an Errands context and a due date?

Suppose I have the following next action:

Buy printer ink
Context: Errands
Due date: Friday

If I am already out running errands on Tuesday, should this action appear on my Errands list even though it is not due until Friday?

My understanding is that the due date indicates the deadline, while the Errands context indicates that the action can be completed while I am out. However, the action itself already makes it obvious that I need to go to a shop, so I am questioning what practical value the generic Errands context adds.

Would you assign both a due date and an Errands context to this action? If so, how do you use the Errands context in practice without confusing the due date with the date on which the action becomes available?
Click to expand...
@Hasan Bjaili

@Context 'means' first opportunity?

Due Date 'means' do on 'Calendar Friday', and if still undone by Friday, then must be done on 'Calendar Friday' unless renegotiated for any appropriate reason(s)?

As such, that would be the GTD understanding on this end and this particular Next Action could and 'should' be made available on both 'lists' and would be cleared during the Weekly Review from both lists in the event of its prior completion, ET CETERA


As one sees how GTD fits best. . . .

Ps. On this end, preventing anything from falling through any cracks distraction-free is a worthy GTD principle for Mind Like Water, and as such, makes it most appropriate to have one Next Action on more than one 'list' as one sees fit?
 
Last edited:
Hasan Bjaili said:
Can a next action have both an Errands context and a due date?

Suppose I have the following next action:

Buy printer ink
Context: Errands
Due date: Friday

If I am already out running errands on Tuesday, should this action appear on my Errands list even though it is not due until Friday?

My understanding is that the due date indicates the deadline, while the Errands context indicates that the action can be completed while I am out. However, the action itself already makes it obvious that I need to go to a shop, so I am questioning what practical value the generic Errands context adds.

Would you assign both a due date and an Errands context to this action? If so, how do you use the Errands context in practice without confusing the due date with the date on which the action becomes available?
Click to expand...
I use Things 3 as my GTD list tool. It has both start dates and due dates, taking care of that issue. However, with almost any tool, you can set up a “tickler file” and move items to the appropriate list when the tickler date is reached. An alternative is just to write “START” in the description. When the start date arrives, erase or cross it off.
 
mcogilvie said:
I use Things 3 as my GTD list tool. It has both start dates and due dates, taking care of that issue. However, with almost any tool, you can set up a “tickler file” and move items to the appropriate list when the tickler date is reached. An alternative is just to write “START” in the description. When the start date arrives, erase or cross it off.
Click to expand...
@mcogilvie

Good GTD thinking

Helps to keep the Calendar cleaner until necessary; then, if still necessary, only needs to be placed on the Calendar on that day for that day?

Thank you very much
 
I would just put it on my calendar as an all day event. If it really HAS to be done friday. If it doesn't I would have it on @Errands. One or the other.
 
fooddude said:
I would just put it on my calendar as an all day event. If it really HAS to be done friday. If it doesn't I would have it on @Errands. One or the other.
Click to expand...
@fooddude

For something that has to be done by the Due Date with the possibility of it being done sooner

"One or the other" . . . Calendar or Contexts

What about Tickler File?

Thank you very much
 
gtd solo-studente said:
@fooddude

For something that has to be done by the Due Date with the possibility of it being done sooner

"One or the other" . . . Calendar or Contexts

What about Tickler File?

Thank you very much
Click to expand...
I don't understand. If it has to be done on a certain date or you decide that is the date, by definition it wouldn't be done sooner. And it's not date specific so it would go in a context. So yes I would only put it on one or the other. A "tickler" is date specific. That is why I use my calendar as a tickler. How do you use a tickler file?
 
fooddude said:
I don't understand. If it has to be done on a certain date or you decide that is the date, by definition it wouldn't be done sooner. And it's not date specific so it would go in a context. So yes I would only put it on one or the other. A "tickler" is date specific. That is why I use my calendar as a tickler. How do you use a tickler file?
Click to expand...
@fooddude

Meaning . . . something that has to be done by a certain date . . . and if the opportunity arises for the something to get done soon via Context . . . all the better?

Tickler File . . . 'same' in principle as Calendar . . . with some added nuances . . . as such, only a serious Tickler Filer could use the Tickler Filer for something that had to be done on a particular day?
 
gtd solo-studente said:
Meaning . . . something that has to be done by a certain date . . . and if the opportunity arises for the something to get done soon via Context . . . all the better?
Click to expand...
I am not going to argue with myself like that. Done by a date and done on a date are two different things. "Done by" a date is not date specific. "Done on" a date is date specific. So I would put it only in one place. Calendar or context. Not calendar and context. If it is a project with a due date (rare for me) I would add "by xx-xx-xx" next to the project on my project list.
 
fooddude said:
I am not going to argue with myself like that. Done by a date and done on a date are two different things. "Done by" a date is not date specific. "Done on" a date is date specific. So I would put it only in one place. Calendar or context. Not calendar and context. If it is a project with a due date (rare for me) I would add "by xx-xx-xx" next to the project on my project list.
Click to expand...
@fooddude

Very good . . . thank you very much for your most worthy GTD perspective in regards to Calendar and Context utilization . . . most appreciated . . . thank you very much
 
I would enter it like this on my errands list:

Markdown (GitHub flavored): 
- [ ] Buy printer ink ==Deadline this Friday 2026-08-07==

The double equals makes the deadline highlighted. There is no magic sauce here. The item will just be on my lists and will be available for me to do any time before Friday. If I miss the deadline, it will remain on my lists and I'll see that I have missed the deadline.
 
cfoley said:
I would enter it like this on my errands list:

Markdown (GitHub flavored): 
- [ ] Buy printer ink ==Deadline this Friday 2026-08-07==

The double equals makes the deadline highlighted. There is no magic sauce here. The item will just be on my lists and will be available for me to do any time before Friday. If I miss the deadline, it will remain on my lists and I'll see that I have missed the deadline.
Click to expand...
@cfoley

:cool:

Clearly GTD professionalism at its elegant best

Trusting one's GTD operative design system(s) so that nothing will 'fall through the cracks' as 'simply' as possible is key principle in GTD for Mind Like Water ?

Thank you very much sir
 
Last edited:
My claim

If a task has a due date, I must do it.
If I must do it, I will make the context happen.
Therefore, I don’t need @computer.

This is perfectly logical. Isn't it?

If something must be done, I will:

go home,
borrow a laptop,
find a café,
use my phone hotspot,

I do whatever is needed.

So the context becomes irrelevant because you will force it to exist.

Is this a valid critique?

Why do I need a context if it has a due date?!!
 
Hasan Bjaili said:
My claim

If a task has a due date, I must do it.
If I must do it, I will make the context happen.
Therefore, I don’t need @computer.

This is perfectly logical. Isn't it?

If something must be done, I will:

go home,
borrow a laptop,
find a café,
use my phone hotspot,

I do whatever is needed.

So the context becomes irrelevant because you will force it to exist.

Is this a valid critique?

Why do I need a context if it has a due date?!!
Click to expand...
A couple of thoughts: First, I often have items with due dates I may not do. Obvious examples are shows or exhibits with limited runs, but there are others. Second, I often am able to do tasks without deadlines along with tasks with deadlines in the same context. This is particularly useful for me with @Errands items.
 
Hasan Bjaili said:
My claim

If a task has a due date, I must do it.
If I must do it, I will make the context happen.
Therefore, I don’t need @computer.

This is perfectly logical. Isn't it?

If something must be done, I will:

go home,
borrow a laptop,
find a café,
use my phone hotspot,

I do whatever is needed.

So the context becomes irrelevant because you will force it to exist.

Is this a valid critique?

Why do I need a context if it has a due date?!!
Click to expand...
Correct. The time becomes the context in a sense. You may need to use one of your context tools but you are "forced" by time to make it happen.
 
@fooddude @mcogilvie

Indeed . . . good GTD thinking . . . perhaps an item on the @Errand lists is discounted~ 'On Sale' until a particular 'buy' date and if one of one's GTD principles is a opportunity willingness to do what one can to help the Disabled, Elderly, etc. neighbors in keeping inflation down for the Disabled, Elderly, etc. neighbors, and if inclined to complaining about inflation, through some good GTD effort?

Doing what we can for those when while we can beyond oneself is a good GTD operative principle to do?

Thank you very much for your good GTD post
 
Last edited:
You must log in or register to reply here.
Top