if you think the server could handle three concurrent jobs (or whatever number) divide the jobs into that many more or less equal streams, then use policies to start the second in a group when the first finishes, then third when the second finishes, etc
You will still need to manually make changes, should that become necessary, but this will minimise the quiet time between jobs on a routine basis