Hi Jamie,

This is a good idea, Ill put in an enhancement bug, hopefully it shouldnt be too difficult to implement.

cheers,

George.

Hi everyone.

After spotting the message from Tom, I thought I'd update you all on an enhancement I've been working on.

After discussing different use cases for certifications, we decided to add a third option for how the recertification dates are calculated. The options will be:

1. Use certification completion date (unchanged) - The time expires is calculated as exactly one "active period" from the day that the cert was completed. This option can cause the time expires to "drift" backwards (when completed early) and forwards (when overdue).
2. Use certification expiry date (small change) - Uses the last expiry date to calculate the next. The first time this is calculated, it adds the "active period" to the "due date" if there is one (this is the small change that will be added), otherwise it uses the date the cert was completed. If the user is overdue or expired, it adds the "active period" to the date the cert was completed, so that certs are active for a minimum of the "active period". This option can cause the time expires to "drift" forwards (when overdue).
3. Use fixed expiry date (new option) - This option causes the expiry time to be calculated based on the specified "due date", and subsequent completions will use that same base date, regardless of whether they are late or early. For example, if the "active period" is one year and a user has a "due date" or 1 Jan 2014, then they complete on 1 Feb 2014 (while overdue), their cert will expire on 1 Jan 2015, just 10 months away. We will also have a "minimum active period" which can be set on a cert when using this option, and which must be at least as big as the "recertification open window". This option will prevent "drifting" forwards or backwards.

I think that you'll be able to achieve what you want using the new "Use fixed expiry date" option and creating one audience for each month of the year.

Nathan