Hi,
it would be nice to have some Setting for a Default value to set the next Review date to.
For example our policy for document Control says that a Review for documents has to be done at least once a year.
So when I do the Review I have to set the next Review date by Hand on every Review.
It would be nice to have the next Review date set to a Default value “one year from now”.
This would be really nice. Although I’ll note that I’ve heard of some auditors that require the next review date to be 1 year - 1 day in the future. So if reviewed in 2024-12-19 the next review should be 2025-12-18.
What’d be even better is recording on the item to be reviewed the review period (monthly, quarterly, annually etc) and have that be added to the default next review date.
You should be able go a step further and set up a custom status to identify any audits that do not meet the specified interval and then alert based on that.
I dont understand the need here, when you review a policy you need to set a date. You can put any date, including 366 days in the future. Is a date picker. Can you explain then what is that you can’t do now? you want this field to be “forced” to be 366 days so whoever creates a policy can not change that? but then that person could change any other attribute of the document, including its content (which is far more relevant that the review date) … so is not clear to me the value of this.
I would see it as a usability thing - if the system pre-populates the date in the date picker based upon some configuration setting, it makes it easier for the user to simply accept it instead of selecting the wrong one.
Exactly as David says, it is an ease of use thing.
If I’m reviewing a policy/document/thing on an annual/quarterly/whatever basis, then the next review date is trivially calculated. Why should I have to click through in the date picker, or as I normally do, control-c the actual review date I’ve picked, then control-v the next review date field and increment the year and decrement the day.
Also, the next review date doesn’t have to forced, just pre-populate it, just as the “Reviewer” field is pre-populated based on the currently set reviewer.