This may not work for all types of neverending projects, but for repeating processes like your recruiting example, you could create a standard checklist of tasks for each type and use that as a template. Example:

Step 1: Sift through resumes, sort out ones on construction paper.

Step 2: Call back ones who sound like they’re hot.

Step 3: Arrange meeting at bar with the best wings.

Et cetera, et cetera.

Then, for every new candidate, print that out/copy onto an index card/type in a spreadsheet and check off each step. Disco.

I write little TV and music reviews for a parenting website, and this works well. They’re short and require the same steps every time: watch show/listen to music, write, send to editor, wait for check. Like you said, it doesn’t make sense to make a separate project for each one, so I have one project in my list for the reviews, and that reminds me to look at my checklist.

Thanks, such template might be useful in some situations. Does anybody has some other ideas on how to deal with neverending projects?

"By definition project should lead to completion, so what is your suggestion to deal with such “neverending projects”?"

I define it as actions get completed, projects hold actions together in a grouping. The projects may or may not get completed.

i.e. I have projects called, "Car Maintenance" and "Home Maintenance" Those puppies are never-ending, but it is nice to have a place to put things like "Mow the lawn" and "get oil change."

From your recruiting example, I would create a new project for each position available. This would not be a never-ending project because the goal is met once someone is hired for that position. The next actions for each project would be very similar and you could create a template/checklist of actions that are required for each new hire.

I consider “never ending projects” to be more of an area of responsibility than a project.

In your case, recruiting is one of the things you do, not a project.

So I would have a line item for each recruit and have that tied to a standard checklist of stpes you take, or usualy take, in each case.

That way you have a placeholder for every recruit on your project list and a standard set of actions, which I would place in the front of a folder for each position/candidate, that don’t clutter up the rest of your GTD system with endless duplicate actions.