I didn't realize that advanced GTDers do not need to tie in NAs to projects. I often wonder why I need a reason for all my NAs - I implemented the "full" GTD system this past summer. Most of my NAs belong to projects and some are single NAs. My context lists include the project name. How do you handle larger sets of tasks that I, for example, would put into a project? Some more complex projects would be written out in advance with the NAs in proper order. I assume you must do that though; you just don't need to visually see the project tie-in the context list? Is this how others do it?
That's how I do it.
If you can't tell *why* the NA is on your context list, you haven't worded the NA properly. Proper wording might include a project name, but doesn't have to.