I think you're probably going to want to have a single action list for each client that acts as the master scheduler, so to speak. Anything that wasn't part of another project would go in there — tasks specific to that client, but not necessarily part of one of the projects. This could be anything from an action to call them to ask about a bill, a reminder to yourself to check something in their file, a yearly action to set up the new year's projects, and so on. I could see going with an action in that project that tells you every appropriate interval to do the client's payroll work, or there could be a repeating action in the client's payroll project that drives it along. For my own stuff, I like to have such things in a single action list, so that there's never any question that I'm going to get each reminder, and nothing is going to be stuck behind some other sequential action that I didn't get done on time. If I have a set of weekly tasks I want to do every week, I usually prefer to set each one up as a separate repeating task instead of a group that repeats when all of the tasks have been completed. That prevents any problems with not getting the next week's tasks in front of me because some relatively unimportant task at the end of the group didn't get completed on time. Does that make sense, or do I need to make up an illustration?