Question for more experienced GTD'ers. I suppose this situation is dependent on the type of tool one uses, I use Facilethings, so the option to do this exists for me...doesn't mean its right. Here is my scenario...with regards to projects and next actions, almost all of my projects begin with an idea that requires me to meet with others to further develop the project, so first the next action is "ask secretary to set up meeting with @name", the project name is usually what I envision as an outcome from my initial idea but all of my ideas almost always require meeting with others to further develop. The thing that I do and I'm wondering if I'm technically breaking GTD rules. As mentioned earlier, my normal mode of operation is when I process the idea "ask secretary to set up meeting with @name" and assign it to the appropriate project name, I let that sit in my next actions until I complete the task "ask secretary...". Once I complete the task "ask secretary...", rather than marking the task as complete, I use the task editor in Facilethings and I change the task name to something like "waiting for confirmation of meeting set up with @name" and I then move this task to the Waiting For list, but still within the original project. Then, when I get confirmation that the meeting has been set up, I add the meeting date to my calendar and I change the "waiting for confirmation..." task to something like "prep for meeting with @name re: project X" and I move this task back to my next action list, still within the project. This method of editing task names works for me, but if you are familiar with Facilethings, within the the project itself, where you can track all of your actions...I don't actually have any "done" or "complete" items...I just keep changing the original task name to meet the current next action. What does everyone think about this method...is this bad news to operate this way? Thanks for any input.