[Gardener2]

Actually, there's another place where I do frequently use something like an On Hold Waiting For - when a project is dependent on another project.

So, let's say that I'm writing a better set of, oh, zip code lookup code. I want to install this code in every application in which I have zip code lookups. It's going to require a little customization for each application.

So that's a bunch of projects -

Write Zipcode Engine
Install Zipcode Engine Into Widget Application
Install Zipcode Engine Into Gadget Application

and so on. Until I complete the first project, I can't even start on the other projects, so I want them to be on hold and usually hidden from me. But I do create the projects, because I might have thoughts about them ("Configure Zipcode Engine to support Canadian postal codes in Widget.") that I want to get out of my head and sorted into a project. Now, I could make all of these projects part of one larger project, but I don't like that - I like my projects smaller than that.

So "Install Zipcode Engine Into Widget Project" has a Next Action of "Waiting for Write Zipcode Engine Project" and a context of HOLDINGFOR, which is an On Hold context. It's going to sit there, idle, until I write that Zipcode Engine.

And the "Write Zipcode Engine" project has a final action of "Wake up Install Zipcode Engine Into Widget Project". Other actions will come and go, but I keep that action at the bottom. And I keep a similar action at the bottom of the first "Install" project, and so on in a waterfall.

Again, I'm not sure if this is proper GTD, but it is another thing that I use On Hold for. If it works, then the completed project will trigger me to wake the On Hold project. If that falls through, then I'll eventually notice the sleeping project in a Review.

Gardener

[Hope]

In case this isn't obvious: You can review all items in a context that is on hold in context mode by selecting that context from the list of contexts on the left. Reviewing these contexts could be part of a weekly review.

I'm not sure that "on hold" is the "intended" function for implementing a "waiting for" context. It is one possibility that will suit some users. Personally, I use future start dates in a context that is not on hold.

On hold functionality has other uses. Gardener2 describes a way to set up dependent projects with an on hold context. I use this method, but only put the first (sequential) action in the on hold context. That way I can assign the appropriate contexts to other actions, but don't have to see them until they are actually available to me.

Contexts can be on hold for other reasons. I may have a "laminator" context, but then lend my laminator to a friend. While I don't have access to the laminator, I can set the context on hold. All of my laminating tasks will stay out of my action lists until I have my laminator back.

Or I may travel a lot. I may have some tasks that I can only do in my Toronto office, and others to do in my Edmonton office. While I'm in Toronto, I don't really need to see the Edmonton items on my action list, so I put that context on hold. Or a colleague who gets his own "Agenda" context may be on vacation. I'll put that context on hold until he's available.

OmniFocus has a lot of flexibility built in - so that you can arrange things the way you like. People may want to have different contexts or projects or even folders disappear from sight for all kinds of reasons. There are a number of ways to make this happen, including "on hold" functionality. It's there as an option - not an official implementation of any particular GTD list.

[Edit: spelling...]

[Brian]

Just chiming in to say that I personally use future start dates to delay on hold actions, as well.

[omnibob]

Perhaps it will be in some future release, but I would find being able to have status for folders would be great. Set a folder to "on hold", then just drop stuff into to. I use both on hold, and future start dates. I picked 1/1/2030 for indefinite (nearly) hold. Maybe I should use 1/1/2525. "In the year, twenty five, twenty five, if OmniFocus is still alive..." (Sorry, you have to be middle aged to get that.)

Bob