My software has both types of timers. The review frequency is separate from the start or due date. I use both types depending on my needs for that particular project.
Originally Posted by Folke
A Someday/Maybe project that is a perhaps this lifetime may have a review frequency of once a year and no start or due date. A project on handling monthly financial inputs may have a review frequency of every week (because things may be due during the month) a repeat of every month and a due date of say the 15th of the month.
A project to vaccinate lambs will have a start date adjusted for each breeding season based on when the lambs are born. Once the rams go in with the ewes for breeding a whole lot of my recurring projects with start dates will get adjusted as they have to happen a certain number of days after breeding or lambing. They also have due dates that work off that as well. Some are cascading dates, i.e. I may have a project to vaccinate early lambs. Based on when the sheep were bred I know that the early lambs will be born within a certain timeframe (start and end dates for that batch of lambs). But until they are born I won't know exactly what those dates really are. I do have flock average gestation dates but it can vary from year to year based on weather, condition and food quality. I have to vaccinate no earlier than a certain number of weeks after birth but there is a range of time after that which is ok. S I set the vaccinate start date based on when the last early lamb is born. We then have some variable amount of time when the shots can be given. What day we actually do it is weather dependent. Once we actually give the vaccinations then I have to set the second shot date. New lambs typically require 2 shots a specific number of days apart. So once I know the day we really gave the first shot I can set the rolling dates for the second shot. Again it must be a minimum of a certain number of days from the first shot and no later than a certain number of days after or I have to start over. The actual timing varies depending on what vaccine we use so I can't set them up ahead of time because until I buy the vaccine for the year I don't know the actual timings. The vaccine we use may depend on what is available or the disease risks per our vet based on perhaps new diseases appearing or old ones disappearing. Plus some vaccines have an initial series that is 3 shots so I may have to add another set of timings if that is the vaccine we use. That is why vaccinate lambs is a major project with a lot of detail. I have it set to start at the approximate time lambing starts and once it's starts I review it weekly. But once the lambs re vaccinated for the year, at my next weekly review I set the new start date to when I expect to have the rams in (so I can reset the start date based on that) and also the review time goes to once a month or even once every 3 months.
There are lots of projects like that on a farm. Once I've done the hard thinking about them I try to save that thinking and re-use it as much as possible next year. No sense reinventing the wheel so to speak.
Omnifocus is very flexible that way and very useful for managing my complex range of recurring projects.
Oogie McGuire - Mac, iPhone & Omnifocus
OogieM on Twitter
Paonia, CO USA