Reading time 3 mins

TABLE OF CONTENTS

• Introduction
• Re-doing the Requirement
• Change the due date for a compliance requirement 
• FAQs
  • Will data from the previous instance of the requirement carry onto the new one?

Introduction

Compliance Requirements can be set to either automatically recur, or to be completed on an ad-hoc basis.   For these ad-hoc requirements, you can choose to have them completed again as and when required.

Also, there may be occasions where the due date for a particular requirement needs updating.  This can do completed on the requirement itself.

All these actions require system permissions to be able to complete.

Re-doing the Requirement

• Once completed an ad-hoc requirement will show as "Not Applicable" in the Due date column

• Select the requirement you wish to have completed again.

• Here you will see each time the requirement has been completed previously. 

• To complete the requirement again, click Redo requirement.

• This will launch a fresh version of the requirement for you to complete, which will show as Pending on your/the user's My Tasks dashboard.

Change the due date for a compliance requirement 

• From within the user's Compliance record, click on the requirement you would like to change the due date for. 

• At the top of the requirement, you will have the option to 'Change due date'.

• Altering the due date for a requirement with multiple workflow steps will update the due date for all outstanding steps in the workflow. 

• If you do not see the Change due date option at the top of the requirement screen then you do not have permission to change the due date for this requirement. 

FAQs

Will data from the previous instance of the requirement carry onto the new one?

• When you re-complete a requirement in this way, no previous data will be carried across, e.g. documents uploaded the first time the requirement was completed will not be shown in the latest version. 

• Any past data entered can be viewed by clicking on the previous submission.